Chat now with support
Chat with Support

Rapid Recovery 6.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings
Core settings key functions Rapid Recovery Core settings Core-level tools
Repositories Managing privacy Encryption Protecting machines
About protecting machines with Rapid Recovery Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Enabling application support Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Verifying a bare metal restore
Managing aging data Archiving Cloud accounts The Local Mount Utility Core Console references REST APIs About us Glossary

Verifying the deployment to multiple machines

Once you have deployed the Rapid Recovery Agent software to two or more machines simultaneously, you can verify the success by viewing each machine listed under the Protected Machines menu.

You can also view information regarding the bulk deploy process from the Events page. Complete the steps in this procedure to verify the deployment.

1.
Navigate to the Rapid Recovery Core Console, click [Events] (Events), and then click Alerts.

The Summary page for the selected machine appears, showing pertinent information including:

Modifying deploy settings

Complete the steps in this procedure to modify deploy settings.

2.
On the Settings page, in the left column, click Deploy to navigate to the Deploy section.

Table 43. Deploy options

Option

Description

Agent Installer Name

Enter the name of the agent executable file. The default is Agent-web.exe.

Core Address

Enter the address for the Core.

Failed Receive Timeout

Enter the number of minutes to wait without activity before timeout.

Maximum Parallel Installs

Enter a number for the maximum installations you want to install simultaneously. The default and limit is 100.

Automatic reboot after install

Select the check box for Yes, or clear it for No.

Protect After Deploy

Select the check box for Yes, or clear it for No.

Understanding protection schedules

A protection schedule defines when backups are transferred from protected agent machines to the Rapid Recovery Core.

The first backup transfer for any machine added to protection on the Core is called a base image snapshot. All data on all specified volumes (including the operating system, applications, and settings), are saved to the repository, which can take a significant amount of time depending on the amount of data being transferred. Thereafter, incremental snapshots (smaller backups, consisting only of data changed on the protected machine since the last backup) are saved to the repository regularly, based on the interval defined (for example, every 60 minutes). This type of backup contains less data than a base image, and therefore takes a shorter amount of time to transfer.

Protection schedules are initially defined using the Protect Machine Wizard or the Protect Multiple Machines Wizard. Using a wizard, you can customize protection schedules (choosing either periods or a daily protection time) to accommodate your business needs. You can then modify the existing schedule or create a new schedule at any time in the Protection Schedule dialog box from the summary page of a specific protected machine.

Rapid Recovery provides a default protection schedule, which includes a single period spanning all days of the week, with a single time period defined (from 12:00 AM to 11:59 PM). The default interval (the time period between snapshots) is 60 minutes. When you first enable protection, you also activate the schedule. Thus, using the default settings, regardless of the current time of day, the first backup will occur every hour, on the hour (12:00 AM, 1:00 AM, 2:00 AM, and so on).

Selecting periods lets you view the default protection schedule and make adjustments accordingly. Selecting a daily protection time causes Rapid Recovery Core to back up the designated protected machines once daily at a time you specify.

You can customize the schedule to define peak and off-peak times using the weekday and weekend periods available. For example, if your protected machines are mostly in use on weekdays, you could decrease the interval for the weekday period to 20 minutes, resulting in three snapshots every hour. Or you can increase the interval for the weekend period from 60 minutes to 180 minutes, resulting in snapshots once every three hours when traffic is low.

Alternatively, you can change the default schedule to define peak and off-peak times daily. To do this, change the default start and end time to a smaller range of time (for example, 12:00 AM to 4:59 PM), and set an appropriate interval (for example, 20 minutes). This represents frequent backups during peak periods. You can then add an additional weekday time range for the remaining span of time (5:00 pm to 11:59 pm) and set an appropriate (presumably larger) interval (for example, 180 minutes). These settings define an off-peak period that includes 5:00 PM to midnight every day. This customization results in snapshots every three hours from 5:00 PM through 11:59 PM, and snapshots every 20 minutes from 12:00 AM until 4:59 PM.

When you modify or create a protection schedule using the Protection Schedule dialog box, Rapid Recovery gives you the option to save that schedule as a reusable template that you can then apply to other protected machines.

Other options in the protection wizards include setting a daily protection time. This results in a single backup daily at the period defined (the default setting is 12:00 PM).

When protecting one or multiple machines using a wizard, you can initially pause protection, which defines the protection schedule without protecting the machines. When you are ready to begin protecting your machines based on the established protection schedule, you must explicitly resume protection. For more information on resuming protection, see Pausing and resuming replication. Optionally, if you want to protect a machine immediately, you can force a snapshot. For more information, see Forcing a snapshot.

Protecting a machine

If you have already installed the Rapid Recovery Agent software on the machine you want to protect, but have not restarted it yet, restart the machine now.

This topic describes how to start protecting the data on a single machine that you specify using the Protect Machine Wizard. To protect multiple machines using one process simultaneously, see About protecting multiple machines.

NOTE: Unless using agentless protection on a VMware or ESXi host, or a Hyper-V host, the machine you want to protect must have the Rapid Recovery Agent software installed to be protected. You can choose to install the Agent software prior to this procedure, or you can deploy the software to the target machine as a part of completing the Protect Machine Wizard. For more information about agentless protection and its restrictions, see Understanding Rapid Snap for Virtual.
NOTE: For more information about installing the Agent software, see “Installing the Rapid Recovery Agent software” in the Rapid Recovery Installation and Upgrade Guide.
 If the Agent software is not installed prior to protecting a machine, you will not be able to select specific volumes for protection as part of this wizard. In this case, by default, all volumes on the agentlessly protected machine will be protected.

Rapid Recovery supports the protection and recovery of machines configured with EISA partitions. Support is also extended to Windows 8 and 8.1, and Windows 2012 and 2012 R2 machines that use Windows Recovery Environment (Windows RE).

When you add protection, you need to define connection information such as the IP address and port, and provide credentials for the machine you want to protect. Optionally, you can provide a display name to appear in the Core Console instead of the IP address. If you change this, you will not see the IP address for the protected machine when you view details in the Core Console. You will also define the protection schedule for the machine.

The protection process includes optional steps you can access if you select an advanced configuration. Advanced options include repository functions and encryption. For example, you can specify an existing Rapid Recovery repository to save snapshots, or create a new repository. You can also specify an existing encryption key (or add a new encryption key) to apply to the data saved to the Core for this machine. For more information about encryption keys, see Encryption.

The workflow of the protection wizard may differ slightly based on your environment. For example, if the Rapid Recovery Agent software is installed on the machine you want to protect, you will not be prompted to install it from the wizard. Likewise, if a repository already exists on the Core, you will not be prompted to create one.

If you are starting from the Rapid Recovery Core Console, from the button bar, click Protect.
The Protect Machine Wizard appears.
2.
On the Welcome page, select the appropriate installation options:
Optionally, if you do not wish to see the Welcome page for the Protect Machine Wizard in the future, select the option Skip this Welcome page the next time the wizard opens.

The Connection page appears.

4.
On the Connection page, enter the information about the machine to which you want to connect as described in the following table, and then click Next.

Table 44. Machine connection settings

Text Box

Description

Operating system

Select Windows or Linux, based on the operating system of the machine you want to protect.

Host

The host name or IP address of the machine that you want to protect.

Port

The port number on which the Rapid Recovery Core communicates with the Agent on the machine.

The default port number is 8006.

User name

The user name used to connect to this machine; for example, Administrator (or, if the machine is in a domain, [domain name]\Administrator).

Password

The password used to connect to this machine.

If the Install Agent page appears next in the Protect Machine Wizard, that means that Rapid Recovery does not detect the Rapid Recovery Agent on the machine and will install the current version of the software. Go to step 6.

If the Upgrade Agent page appears next in the wizard, that means that an older version of the Agent software exists on the machine you want to protect.

5.
On the Upgrade Agent page, do one of the following:
To deploy the new version of the Agent software (matching the version for the Rapid Recovery Core), select Upgrade the Rapid Recovery Agent software to the latest version .
6.
Click Next.
The Protection page appears.
7.
Optionally, on the Protection page, if you want a name other than the IP address to display in the Rapid Recovery Core Console for this protected machine, then in the Display name field, type a name in the dialog box.

You can enter up to 64 characters. Do not use the special characters described in the topic prohibited characters. Additionally, do not begin the display name with any of the character combinations described in the topic prohibited phrases.

To use the default protection schedule, in the Schedule Settings option, select Default protection (hourly snapshots of all volumes).

With a default protection schedule, the Core will take snapshots of all volumes on the protected machine once every hour. To change the protection settings at any time after you close the wizard, including choosing which volumes to protect, go to the Summary page for the specific protected machine.

To define a different protection schedule, in the Schedule Settings option, select Custom protection.

Schedule options are added to the wizard workflow.

9.
At the bottom of the Protection page, if you are re-protecting a machine previously protected in this Core, and want to specify a different repository than the original repository, select the option Select a new repository for this machine.
If you selected a Typical configuration for the Protect Machine Wizard in step 2 and specified default protection, and if a repository exists, then click Finish to confirm your choices, close the wizard, and protect the machine you specified.
If you selected Advanced configuration for the Protect Machine Wizard in step 2, and default protection, then click Next and proceed to step 13 to see repository and encryption options.

The first time protection is added for a machine, a base image (that is, a snapshot of all the data in the protected volumes) will transfer to the repository on the Rapid Recovery Core following the schedule you defined, unless you specified to initially pause protection.

11.
On the Protection Volumes page, select which volumes you want to protect. If any volumes are listed that you do not want to include in protection, click in the Check column to clear the selection. Then click Next.
12.
On the Protection Schedule page, define a custom protection schedule and then click Next. For details on defining a custom protection schedule, see Creating custom protection schedules in Simple Mode.

If you already have repository information configured, did not indicate that you want to change the repository, and you selected the Advanced option in step 2, then the Encryption page appears. Proceed to step 16.

If you already have repository information configured, and you selected the Advanced option in step 2, or if you indicated you want to change the repository, then the Repository page appears. Proceed to step 13.

13.
On the Repository page, do the following:
1.
Select Use an existing repository.
3.
Click Next.

The Encryption page appears. Skip to Step 15 to optionally define encryption.

If you want to create a repository, then on the Repository page, enter the information described in the following table, and then click Next or Finish, as appropriate.

Table 45. Repository settings

Text Box

Description

Name

Enter the display name of the repository.

By default, this text box consists of the word Repository and a number, which corresponds to the number of repositories for this Core. For example, if this is the first repository, the default name is Repository 1. Change the name as needed.

Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases.

Location

Enter the location for storing the protected data. This volume should be a primary storage location. The location could be local (a drive on the Core machine) or it could be a CIFS share network drive.

For a CIFS share, the path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.

CAUTION: Define a dedicated folder within the root for the storage location for your repository. Do not specify the root location. For example, use E:\Repository\, not E:\. If the repository that you are creating in this step is later removed, all files at the storage location of your repository are deleted. If you define your storage location at the root, all other files in the volume (e.g., E:\) are deleted, which could result in catastrophic data loss.

For example, type X:\Repository\Data.

When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

User name

Enter a user name for a user with administrative access. This information is only required when the repository location specified is a network path.

Password

Enter the password for the user with administrative access. This information is only required when the repository location specified is a network path.

Metadata path

Enter the location for storing the protected metadata.

For example, type X:\Repository\Metadata.

When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

14.
On the Repository Configuration page, configure the amount of space on the disk to allocate to the repository. Quest recommends reserving 20 percent of the volume for metadata, which is the default. Optionally, using the slider control or the Size field, you can allocate more or less space on the volume for the repository.
15.
Optionally, if you want to view and enter detailed information regarding storage location settings, select Show advanced options, and adjust the settings as described in the following table. To hide these options, clear the option Show advanced options. When you have completed your repository configuration, click Next or Finish, as appropriate.

Table 46. Storage configuration details

Text Box

Description

Bytes per sector

Specify the number of bytes you want each sector to include. The default value is 512.

Bytes per record

Specify the average number of bytes per record. The default value is 8192.

Write caching policy

The write caching policy controls how the Windows Cache Manager is used in the repository and helps to tune the repository for optimal performance on different configurations.

Set the value to one of the following:

If set to On, which is the default, Windows controls the caching. This is appropriate for Windows 10, and for versions of Windows Server 2012 and later.

If set to Off, Rapid Recovery controls the caching.

If set to Sync, Windows controls the caching as well as the synchronous input/output.

If you chose the Advanced option in Step 1, the Encryption page appears.
16.
Optionally, on the Encryption page, if you want to use encryption keys for data stored in the repository, select Encrypt the data at rest in a repository, and then do one of the following:
To select an existing encryption key to apply to all new data stored in your repository, select Encrypt data using Core-based encryption with an existing key, and from the Select encryption key drop-down menu, select the encryption key.
To define a new encryption key at this time to apply to all future data stored in your repository, select Encrypt data using Core-based encryption with a new key, and then enter information about the key as described in the table below:

Table 47. Define new encryption key

Text Box

Description

Name

Enter a name for the encryption key.

Encryption key names must contain between 1 and 64 alphanumeric characters. Do not use prohibited characters or prohibited phrases.

Description

Enter a descriptive comment for the encryption key. This information appears in the Description field when viewing a list of encryption keys in the Rapid Recovery Core Console. Descriptions may contain up to 254 characters.

Best practice is to avoid using prohibited characters and prohibited phrases.

Passphrase

Enter a passphrase used to control access.

Best practice is to avoid using prohibited characters.

Record the passphrase in a secure location. Quest Data Protection Support cannot recover a passphrase. Once you create an encryption key and apply it to one or more protected machines, you cannot recover data if you lose the passphrase.

Confirm passphrase

Re-enter the passphrase. It is used to confirm the passphrase entry.

17.
Optionally, on the Encryption page, to encrypt all data that transports over a network, select Encrypt the data in transport over a network. This option is enabled by default, so if you do not want to encrypt data in this fashion, clear this option.
18.
Click Finish to save and apply your settings.

The first time protection is added for a machine, a base image (that is, a snapshot of all the data in the protected volumes) will transfer to the repository on the Rapid Recovery Core following the schedule you defined, unless you specified to initially pause protection.

Related Documents