The following dependencies are required and are installed as part of the Agent installer package:
lsscsi, libblkid1, e2fslibs, libpam0g, libc6, libpcre3, perl, make, e2fsprogs, xfsprogs, python-minimal, apprecovery-dkms, rapidrecovery-mono, sysvinit-utils
module-init-tools, gcc, build-essential, coreutils (>= 7.4), patch
lsscsi, libblkid1, e2fslibs, libpam0g, libc6, libpcre3, perl, make, e2fsprogs, xfsprogs, python-minimal, apprecovery-dkms, rapidrecovery-mono, systemd
module-init-tools, gcc, build-essential, coreutils (>= 7.4), patch
lsscsi, make, gcc, pam, pcre, glibc, python, perl, e2fsprogs, apprecovery-dkms, rapidrecovery-mono, nbd, libblkid, e2fsprogs-libs, xfsprogs, ntsysv
apprecovery-dkms
NOTE: nbd is a Network Block Device, used to access storage remotely across the network instead of residing locally. If the nbd module is compiled into the kernel, Linux can use a remote server as one of its block devices. Every time the client machine wants to read |
coreutils, cpio, findutils, gawk, gcc, grep, gzip, sed, tar, bash > 1.99, module-init-tools
lsscsi, make, gcc, pam, pcre, glibc, python, perl, e2fsprogs, apprecovery-dkms, rapidrecovery-mono, nbd, libblkid, e2fsprogs-libs, xfsprogs, systemd
apprecovery-dkms
bash > 1.99, coreutils, cpio, findutils, gawk, gcc, grep, gzip, kmod, sed, systemd, tar, rpmlib
lsscsi, make, libblkid1, libext2fs2, pam, pcre, glibc, xfsprogs, python, perl, apprecovery-dkms, rapidrecovery-mono, sysvinit
coreutils, cpio, findutils, gawk, gcc, grep, gzip, sed, tar, bash > 1.99, module-init-tools
lsscsi, make, libblkid1, libext2fs2, pam, pcre, glibc, xfsprogs, python, perl, apprecovery-dkms, rapidrecovery-mono, systemd
bash > 1.99, coreutils, cpio, findutils, gawk, gcc, grep, gzip, kmod, sed, systemd, tar, rpmlib
Information about Bourne Shell scripting supporting Linux protected machines is now included in the Rapid Recovery 6.3 Commands and Scripting User Guide . See the topic "Using Bourne Shell and Bash scripting with Rapid Recovery."
If AppAssure Agent is currently installed on the Linux machine on which you want to run Rapid Recovery Agent, you must first uninstall AppAssure Agent. Before removing that software, consider backing up the agent ID. For more information, see Backing up and restoring the AppAssure Agent ID and Uninstalling the AppAssure Agent software from a Linux machine.
See the prerequisite steps in the topic About installing the Agent software on Linux machines before continuing with this procedure.
Standard online installations of Rapid Recovery Agent require an internet connection on the Linux machine you want to protect. You can obtain the latest Agent software from the Rapid Recovery License Portal in the form of a repository package (a Linux archive with the appropriate files). The files are extracted and installed using a package manager appropriate for the Linux version you want to protect.
If you want to protect a Linux machine that is offline (such as an air-gapped secure computer or a machine in a remote location), instead of using package managers and repository packages, you can download a shell script from the license portal. This single script can be used to install Rapid Recovery Agent on any supported Linux distribution and version. For more information, see Installing the Agent software on offline Linux machines.
The Linux distributions that Rapid Recovery supports use the package manager utilities shown in the following table.
Linux Distribution | Package Manager |
---|---|
Linux distributions based on Red Hat Enterprise Linux (RHEL), including RHEL, CentOS, and Oracle Linux | yum |
SUSE Linux Enterprise Server (SLES) | zypper |
Linux distributions based on Debian, including Ubuntu | apt |
To install or upgrade Agent on a Linux machine, you must obtain the repository package relevant to your Linux distribution and version. These packages are found on the Rapid Recovery License Portal , as described in step 6.
The package managers work with a local Rapid Recovery repository created as part of this process. The local repository retrieves packages and files from remote repositories that Quest maintains for each specific Linux distribution. This process guarantees you have the correct files accessible for the Linux machine you want to protect.
If installing Rapid Recovery Agent for the first time, there is no need to uninstall software, or back up any configuration files.
If Rapid Recovery Agent is already installed and you are upgrading your Linux machine to a new version, steps are included to remove the previous local software repository.
Complete the following steps to install or upgrade the Rapid Recovery Agent on any supported Linux distribution.
Option | Command |
---|---|
RHEL, CentOS, and Oracle Linux | rpm -qa | grep rapidrecovery-repo |
SLES | rpm -qa | grep rapidrecovery-repo |
Debian and Ubuntu | dpkg -l | grep rapidrecovery-repo |
Option | Command |
---|---|
RHEL, CentOS, and Oracle Linux | rpm -e rapidrecovery-repo |
SLES | rpm -e rapidrecovery-repo |
Debian and Ubuntu | dpkg -P rapidrecovery-repo |
Option | Command |
---|---|
RHEL, CentOS, and Oracle Linux | yum repolist |
SLES | zypper repos |
Debian and Ubuntu | ls /etc/apt/sources.list.d |
Option | Command |
---|---|
RHEL, CentOS, and Oracle Linux | yum clean all (to delete files in the cache and update metadata)
|
SLES | zypper refresh 'rapidrecovery repository' |
Debian and Ubuntu | apt-get update |
Option | Command |
---|---|
RHEL, CentOS, and Oracle Linux | yum install rapidrecovery-agent |
SLES | zypper install rapidrecovery-agent |
Debian and Ubuntu | apt-get install rapidrecovery-agent |
|
NOTE: To ensure that the proper kernel module version is used to protect your machine, the best practice is to restart the machine after theRapid Recovery Agent upgrade is completey. |
Each supported Linux distribution uses a specific package manager, as listed in the table below. The package managers use commands that sometimes differ to accomplish the same task. The appropriate Linux commands required to remove AppAssure Agent, or install, upgrade, or remove Rapid Recovery Agent , are included in each individual topic. Those commands are repeated in this topic, listed by package manager for easy reference. Each cell in this table contains one complete command.
Command description | yum (RHEL, CentOS, Oracle Linux) | zypper (SLES) | apt (Debian, Ubuntu) |
---|---|---|---|
Manually remove AppAssure Agent and dependent files manually | rpm --nodeps -e appassure-vss appassure-vdisk appassure-mono appassure-agent | rpm --nodeps -e appassure-vss appassure-vdisk appassure-mono appassure-agent | dpkg --force-all -P appassure-vss appassure-vdisk appassure-mono appassure-agent |
List all local software repositories | yum repolist | zypper repos | ls /etc/apt/sources.list.d |
Confirm if a local repository for Rapid Recovery Agent exists | rpm -qa | grep rapidrecovery-repo | rpm -qa | grep rapidrecovery-repo | dpkg -l | grep rapidrecovery-repo |
Remove existing rapidrecovery-repo | rpm -e rapidrecovery-repo | rpm -e rapidrecovery-repo | dpkg -P rapidrecovery-repo |
Update the local repository | yum clean all (deletes cache first)
yum makecache (just updates metadata) |
zypper refresh 'rapidrecovery repository' | apt-get update |
Install Rapid Recovery Agent from the repository package | yum install rapidrecovery-agent | zypper install rapidrecovery-agent | apt-get install rapidrecovery-agent |
Remove Rapid Recovery Agent and Mono database | yum remove rapidrecovery-agent rapidrecovery-mono | zypper remove rapidrecovery-agent rapidrecovery-mono | apt-get remove rapidrecovery-agent rapidrecovery-mono |
Remove dependent files | yum autoremove | [Included in previous command] | apt-get autoremove |
Remove the repository package | yum remove rapidrecovery-repo | zypper remove rapidrecovery-repo | apt-get remove rapidrecovery-repo |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center