Virtualization

Installing Rapid Recovery agent Linux

If using Rapid Recovery in you environment, most likely you will at some point need to protect Linux. Let's look at installing rapid recovery agent Linux.

If you are using Rapid Recovery in your environment, you will most likely have a Linux box that you would like to add to your protected servers at some point.  Recently I added a Linux box to Rapid Recovery and I wanted to write up a quick post about the process and an issue I ran into during the process.  Let’s take a look at Installing Rapid Recovery agent Linux.

Installing Rapid Recovery agent Linux

The first thing that you need to do is get the .rpm file over to your linux box.  I SCP’ed the file over to the box to the /tmp directory.  After you copy it over to the linux box, you run the command to establish persistent connection with the Dell repository:

rpm -ivh rapidrecoveryagentversion.rpm

rrlinux01

Then we run the command:

yum clean all

Then finally the command:

yum install rapidrecovery-agent


rrlinux02
rrlinux03

Configuration

Now we run the configuration script:

/usr/bin/rapidrecovery-config

This presents with (6) options, however, really only the first (5) are necessary to get everything configured.  Number (1) is already completed with the default port of 8006.  If you want to change this you can certainly do so here.

rrlinux04

Steps 2-4 are the more critical steps.  For step (2) you need to create a user for backup purposes.  It will not allow you to use root (not that you should anyway, but it won’t allow it).  After you create a user, simply type the following with “username” being the user you created.

2 username

Step (3) allows the necessary firewall exceptions locally if you are running a firewall.  It will detect and present the option to allow the exceptions automatically by typing (3) and then the firewall you are running:

3 firewalld

 rrlinux06

Issue during Option (4)

I had an issue with option (4) as it scans your kernel and decides whether or not you have a kernel suitable for installing the agent in.  What was surprising is that I was running a fairly up to date Centos 7 install, but had not ran updates for a while.  I would have assumed the default kernel version would have sufficed.  As you can see below, it errors out with “No kernels suitable for installation were found.  Exiting shell.”

rrlinux07

The resolution for me was to run a kernel update, which in Centos is accomplished with the command:

yum -y update kernel

rrlinux08 rrlinux09

Kernel update was successful.

rrlinux10

Now, we get different results when rerunning the (4) option.  However, a mistake I made was to update the kernel and not reboot.  To instantiate the new kernel you must reboot.  Kernel updates take place offline to the kernel that is running.  When you update, it places it to the side so to speak and then becomes active once you reboot.  So you are able to install the Rapid Recovery agent in the new kernel, but if you try to run option (5) it will just sit there, or at least it did with my install as it can’t really start the agent as it is integrated with the new kernel that isn’t active yet.

rrlinux11 rrlinux12

After a reboot, the option (5) started without issue.

rrlinux13

Final Configuration

That’s it as far as Installing Rapid Recovery agent Linux.  The only thing left to do is to add the machine to protection on your Rapid Recovery core box.  This process is the same as any other machine.  Once you add the machine to protection, you can force a base image if you want or wait until the scheduled default hourly snapshot comes around.

Subscribe to VirtualizationHowto via Email 🔔

Enter your email address to subscribe to this blog and receive notifications of new posts by email.



Brandon Lee

Brandon Lee is the Senior Writer, Engineer and owner at Virtualizationhowto.com, and a 7-time VMware vExpert, with over two decades of experience in Information Technology. Having worked for numerous Fortune 500 companies as well as in various industries, He has extensive experience in various IT segments and is a strong advocate for open source technologies. Brandon holds many industry certifications, loves the outdoors and spending time with family. Also, he goes through the effort of testing and troubleshooting issues, so you don't have to.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.