Get Live Help
The Rapid Snap for Virtual feature of Rapid Recovery is supported on vCenter/ESXi or on Hyper-V hypervisors. This feature, also known as agentless protection, lets you protect VMs running on your protected hypervisor in your Core without installing the Rapid Recovery Agent software on each guest machine.
Rapid Snap for Virtual has nearly achieved parity with protection provided by installing the Rapid Recovery Agent software. As a general rule, Quest recommends using agentless protection on ESXi or Hyper-V virtual machines. If the Agent software is installed on ESXi or Hyper-V VMs, unless there is a compelling reason to explicitly protect your VM using Rapid Recovery Agent, Quest recommends removing the Agent software, and protecting your VMs agentlessly.
There are some advantages to protecting agentlessly, and some limitations. These are clearly described in the topic Understanding Rapid Snap for Virtual.
Exceptions to the recommendation to use agentless protection are as follows:
Some features are unique to protection by installing the Rapid Recovery Agent software. The following examples apply:
If you require any of the features described in the previous list for a specific VM, Quest recommends installing Agent instead of protecting the VM agentlessly.
For more information, see the topic Understanding Rapid Snap for Virtual.
As described in the Rapid Recovery 6.3 Installation and Upgrade Guide topic "Managing licenses," Rapid Recovery 6.2 and later uses only two license pools: Capacity, and Enterprise. If licensing for your Core is set up to use a capacity-based pool, you cannot use another pool type.
NOTE: In the future, Quest may add license pools based on other units of measure. Capacity and Enterprise pools continue to be supported.
DL series backup appliances use back-end capacity-based licensing, and are not affected by license pool restrictions. Software-based Rapid Recovery environments using front-end capacity licensing likewise receive no license benefits from using agentless protection. Other benefits for using agentless protection are relevant even when Capacity license pools are in use.
If your Rapid Recovery release 6.2 or later environment uses an Enterprise license pool, then the following rules apply:
You can protect guest VMs on a vCenter/ESXi hypervisor host by running the Protect Multiple Machines Wizard. On the Connection page of this wizard, if you specify Protect selected VMs agentlessly, the guest VMs on that host are protected agentlessly. For those VMs, no licenses are consumed from your license pool. While Rapid Recovery Agent is not installed on the host, adding that host to your Core consumes one license for each CPU socket.
When you protect a Hyper-V Server, Rapid Recovery Agent is installed on the host. For each CPU socket on that hypervisor host, one license from your Enterprise pool is consumed. If you specify protecting the Hyper-V server agentlessly, guest VMs are protected agentlessly, and for those VMs, no licenses are consumed from your available license pool.
When you protect a Hyper-V cluster, Rapid Recovery Agent is installed on each node in the cluster. Only a single license is consumed from your license pool. The total number of CPU sockets in the cluster are consumed. If you specify protecting the Hyper-V cluster agentlessly, guest VMs are protected agentlessly, and for those VMs, no licenses are consumed from your available license pool on the cluster.
The chief licensing benefit to using Rapid Snap for Virtual is a reduction in consumption of licenses from your Enterprise license pool for the VMs you protect. If you specify agentless protection for an ESXi hypervisor host, or a Hyper-V server or cluster, all new VMs created on the host are automatically protected agentlessly, and do not consume licenses from your Enterprise license pool.
If some of the VMs on that hypervisor host previously had Rapid Recovery Agent installed, and your Core is running Rapid Recovery release 6.2 or later, you should do one of the following:
Each virtual machine on a hypervisor added to your Core is protected agentlessly without consuming a license. To obtain this benefit, you must do the following:
The chief licensing benefit to using Rapid Snap for Virtual is a reduction in consumption of licenses from your Enterprise license pool for the VMs you protect. Each virtual machine on a hypervisor added to your Core is protected agentlessly without consuming a license. To obtain this benefit, you must do the following:
For a discussion of benefits and limitations regarding agentless protection, additional software recommended, minimum requirements for the host, and so on, see the topic Understanding Rapid Snap for Virtual.
The Rapid Recovery Agent software is compatible with multiple Linux-based operating systems (for details, see the system requirements now defined in the Rapid Recovery System Requirements Guide ). The Rapid Recovery Core is compatible only with Windows machines. While you can manage protected Linux machines from the Rapid Recovery Core Console, several procedures for Linux machines have steps that differ from their Windows counterparts. Additionally, you can perform some actions directly on a protected Linux machine by using the local_mount command line utility.
If you want to protect a single Linux machine, you can now use the Protect Machines Wizard. See the topic Protecting a machine. To protect multiple Linux machines simultaneously using the wizard from the Core Console, see the topic Protecting multiple machines manually.
To deploy or install the Agent software to a Linux machine from the Core Console, you must have the following:
If a Linux machine you want to protect does not meet these prerequisites, consult with a Linux administrator. Comply with these requirements and then you can complete the relevant wizard to deploy and install the Agent software.
Rapid Recovery expands application support in release 6.2 and later to include Agent-based protection of Oracle 12c relational database servers. You can protect an Oracle database server and all of its databases, and perform related tasks.
In this release, the following restrictions apply:
NOTE: Support for NOARCHIVELOG (the default Oracle database log mode) is planned for a future release. Oracle databases with ARCHIVELOG mode enabled must also be set to archive all online redo logs using the ARCH (archive) process. A database administrator (DBA) can change the mode and set archiving of redo logs using Oracle SQL*Plus or Oracle Enterprise Manager. For more information about enabling ARCHIVELOG mode and archiving, see Oracle documentation or consult a qualified Oracle 12c DBA.
To fully protect Oracle servers, perform the following tasks:
You can also truncate Oracle database logs manually on demand. For more information about this procedure, see Manually truncating Oracle database logs.
Once you install the Agent, protect the machine in your Core, and configure settings properly, you can do the following:
If you boot up a VM of an Oracle database, you may have to manually start the database services, and manually disable backup mode for database data files.
Before performing this procedure, you must first add an Oracle database server to protection on your Core.
To enter or edit Oracle database credentials:
NOTE: SYSDBA is an Oracle systems database administrative privilege required to perform high-level administrative operations. These functions include creating, starting up, shutting down, backing up, or recovering an Oracle database.
After protecting your Oracle database server, you cannot access database metadata or view database details until you enter credentials for each database. This one-time step caches your database credentials securely and provides the Core Console with access to status information about all protected transaction log files, control files, and data files that comprise your Oracle databases.
For example, on the Summary page for the protected Oracle machine, before entering credentials, you cannot expand details about any of the protected databases in the Oracle Server Information pane.
NOTE: This is a one-time step required for each new protected Oracle database.
Complete the steps in this procedure to provide the Rapid Recovery Core Console with access to the required metadata for your protected Oracle databases.
|Host Name||Enter the host name or IP address.|
|Port||Enter the appropriate port. The default port open for this purpose is 1521.|
|SID or Service Name||Select the appropriate connection method. You can use one of the following:
|Service Name||The service name is the TNS alias that you give when you remotely connect to your database and this Service|
|Network Alias||Select this drop-down menu to view database aliases available to the network, and select the appropriate alias.|
NOTE: Your Windows user account must have SYSDBA privileges.
NOTE: Your Windows user account must be a member of the ORA_DBA local group, which ensures the user has SYSDBA privileges.
After entering and caching credentials for all databases on this protected Oracle machine, perform the procedures described in the topic Enabling archive log mode and adding VSS writer for protected Oracle databases.