Configuring replication
To replicate data using Rapid Recovery, you must configure the source and target Cores for replication. After you configure replication, you can then replicate protected machine data, monitor and manage replication, and perform recovery.
The version of Rapid Recovery Core on the server used as the target can be equal to or later than the version of Rapid Recovery Core installed on the source Core. The source Core must never run a version of Rapid Recovery more recent than the target Core runs.
When upgrading Cores that use replication, do the following:
- Always upgrade the target Core first, then upgrade the source Core, and lastly upgrade the Agent software on your protected machines.
- If using the automatic update feature, to ensure the proper upgrade order is followed, set up automatic update on target Cores only. After each automatic update, manually upgrade source Cores before updating Rapid Recovery Agent on your protected machines.
For more information on updating cores configured for replication, see the Rapid Recovery Installation and Upgrade Guide, including topics "Upgrading factors to consider" and "Automatically installing updates."
|
|
NOTE: When you replicate data for a cluster, you must replicate the entire cluster. For example, if you select a node to replicate, the cluster is automatically selected. Likewise, if you select the cluster, all nodes in that cluster are also selected. |
Performing replication in Rapid Recovery involves performing the following operations:
- Set up a repository on the target Core. For more information on adding a repository to the target Core, see Creating a DVM repository.
- Configure self-managed replication. For more information on replicating to a self-managed target Core, see Replicating to a self-managed target Core.
- Configure third-party replication. For more information on replicating to a third-party target Core, see Replicating to a third-party target Core.
- Replicate an existing protected machine. For more information on replicating a machine that is already protected by the source Core, see Adding a machine to existing replication.
- Consume the seed drive. For more information on consuming seed drive data on the target Core, see Consuming the seed drive on a target Core.
- Set the replication priority for a protected machine. For more information on prioritizing the replication of protected machines, see Setting replication priority for a protected machine.
- Set a replication schedule for a protected machine. For more information on setting a replication schedule, see Scheduling replication.
- Monitor replication as needed. For more information on monitoring replication, see Viewing incoming and outgoing replication.
- Manage replication settings as needed. For more information on managing replication settings, see Managing replication settings.
- Recover replicated data in the event of disaster or data loss. For more information on recovering replicated data, see Recovering replicated data.
Replicating to a self-managed target Core
This configuration applies to replication to an off-site location and to mutual replication. The following steps are prerequisite:
- The Rapid Recovery Core must be installed on all source and target machines.
- If you are configuring Rapid Recovery for multi-point to point replication, you must perform this task on all source Cores and the one target Core. For descriptions of these replication configurations, see Replication.
- If you need to create a seed drive and transfer it to a physical removable storage volume to perform the initial transfer of existing recovery points, you must have a suitable portable storage device prepared. You must also have physical access to the source Core machine, to attach the drive to copy the seed drive archive.
- If using a seed drive in a self-managed target Core, you or a trusted administrator must have physical access to the target Core.
A self-managed target Core is a Core to which you have access. For example, a self-managed Core is often managed by your company at an off-site location, or is hosted at a different geographic location than the source Core. Replication can be set up entirely on the source Core, unless you choose to seed your data using a seed drive. In such cases, you must create a seed drive using this procedure, and later attach the seed drive to the target Core to consume the archived recovery point data. For more information, see Determining your seeding needs and strategy.
Complete the steps in the following procedure to configure your source Core to replicate to a self-managed target Core.
- Navigate to the Rapid Recovery Core Console of the source Core.
- On the button bar, click
Replicate.
The Replication Wizard appears.
- On the Target Core page of the Replication Wizard, if you are establishing replication with a target Core that has been paired with this source Core previously, select Use an existing target Core, and then select the appropriate target Core from the drop-down list. Skip to step 5.
- On the Target Core page of the Replication Wizard, if you are establishing replication with a target Core from this source Core for the first time, select I have my own Target Core, and then enter the information as described in the following table.
Table 85: Target Core information Text Box Description Host Name
Enter the host name or IP address of the Core machine to which you are replicating.
Port
Enter the port number on which the Rapid Recovery Core will communicate with the machine.
The default port number is 8006.
User Name
Enter the user name for accessing the machine.
Password
Enter the password for accessing the machine.
- Click Next.
NOTE: If no repository exists on the target Core, a warning appears notifying you that you can pair the source Core with the target Core, but that you are unable to replicate agents (protected machines) to this location until a repository is established. For information about how to set up a primary repository to a Core, see Creating a DVM repository.
- On the Request page, enter a name for this replication configuration; for example, SourceCore1. This is the display name used for the Incoming Replication pane on the target Core's Replication page.
- Click Next.
- On the Protected Machines page, select the protected machines you want to replicate, and then use the drop-down lists in the Repository column to select a repository for each protected machine.
- If you want to perform the seeding process for the transfer of the base data, complete the following sub-steps. If you do not want to seed your data, proceed to step 10.
NOTE: Because large amounts of data need to be copied to the portable storage device, Quest recommends using an eSATA, USB 3.0, or other high-speed connection to the portable storage device.
- On the Protected Machines page of the Replication Wizard, select Use a seed drive to perform the initial transfer.
- If you currently have one or more protected machines replicating to a target Core, you can include these protected machines on the seed drive by selecting Include already replicated recovery points in the seed drive.
- If you do not want replication to begin immediately after completing this procedure, select Initially pause replication.
NOTE: If you select this option, replication does not begin until you explicitly resume it. For more information, see Pausing and resuming replication.
- Click Next.
- On the Seed Drive Location page of the Replication Wizard, use the Location type drop-down list to select from the following destination types:
- Local
- Network
- Cloud
- In the Location field, enter the details for the seed drive file as described in the following table, based on the location type you selected in step c.
Table 86: Archive details Option Text Box Description Local
Output location
Enter the location for the output. It is used to define the location path where you want the seed drive archive to reside; for example, D:\work\archive.
Network
Output location
Enter the location for the output. It is used to define the location path where you want the seed drive archive to reside; for example, \\servername\sharename.
User Name
Enter a user name. It is used to establish logon credentials for the network share.
Password
Enter a password for the network path. It is used to establish logon credentials for the network share.
Cloud
Account
Select an account from the drop-down list.
NOTE: To select a cloud account, you must first have added it in the Core Console. For more information, see Adding a cloud account.
Container
Select a container associated with your account from the drop-down menu.
Folder Name
Enter a name for the folder in which the archived data is to be saved. The default name is Rapid-Recovery-Archive-[DATE CREATED]-[TIME CREATED]
- Click Next.
- On the Seed Drive Options page of the Replication Wizard, enter the information as described in the following table.
Table 87: Seed drive options Item Description Maximum Size
Large archives of data can be divided into multiple segments. Select the maximum size of the segment you want to reserve for creating the seed drive by doing one of the following:
- Select Entire Target to reserve all available space in the path provided on the Seed Drive Location page for future use. For example, if the location is D:\work\archive, all of the available space on the D: drive is reserved if required for copying the seed drive, but is not reserved immediately after starting the copying process.
- Select the text box, enter an amount, and then select a unit of measurement from the drop-down list to customize the maximum space you want to reserve. The default is 250MB.
Recycle action
In the event the path already contains a seed drive, select one of the following options:
- Do not reuse. Does not overwrite or clear any existing seed data from the location. If the location is not empty, the seed drive write will fail.
- Replace this Core. Overwrites any pre-existing seed data pertaining to this Core but leaves the data for other Cores intact.
- Erase completely. Clears all seed data from the directory before writing the seed drive.
Comment
Enter a comment that describes the seed drive.
Add all agents to seed drive
Select this option to replicate all protected machines on the source Core using the seed drive. This option is selected by default.
Build recovery point chains (fix orphans)
Select this option to replicate the entire recovery point chain to the seed drive. This adds some already replicated recovery points to the seed drive, preventing orphans from occurring. This option is selected by default.
- Do one of the following:
- If you cleared the Add all agents to seed drive check box, click Next.
- If you selected Add all agents to seed drive, go to step 10.
- On the Protected Machines page of the Replication Wizard, select Use a seed drive to perform the initial transfer.
- Click Finish.
- If you created a seed drive, send it to your target Core.
The pairing of the source Core to the target Core is complete.
Unless you selected the option to initially pause replication, the replication process begins immediately.
- If you selected the option to use a seed drive, replication produces orphaned recovery points on the target Core until the seed drive is consumed and provides the necessary base images.
- If you specified the use of the a drive, transfer the seed drive archive file to a volume (shared folder, virtual disk, or removable storage media). Then, consume the seed drive.
Replicating to a third-party target Core
A third-party Core is a target Core that it managed and maintained by an MSP. Replicating to a Core managed by a third party does not require the customer to have access to the target Core.
The process of replicating to a third-party Core involves tasks that must be completed by the customer as well as the third party. After a customer submits a request for replication on the source Core or Cores, the MSP must complete the configuration on the target Core by reviewing the request.
|
|
NOTE: This configuration applies to Hosted and Cloud Replication. The Rapid Recovery Core must be installed on all source Core machines. If you are configuring Rapid Recovery for Multi-Point to Point replication, you must perform this task on all source Cores. |
To replicate to a target Core managed by a third party, complete the following tasks:
- Submitting a replication request to a third-party service provider
- Reviewing a replication request from a customer
- Ignoring a replication request from a customer
Submitting a replication request to a third-party service provider
If you are an end user who subscribes to a Core managed by a third party, such as an MSP, complete the steps in this procedure to submit a replication request to your third-party service provider.
- From the icon button bar of the Rapid Recovery Core Console, click
Replicate.
The Replication Wizard appears. - On the Target Core page of the Replication Wizard, selectI have a subscription to a third-party providing off-site backup and disaster recovery services, and then enter the information as described in the following table.
Table 88: Third-party target Core information Text Box Description Host Name Enter the host name, IP address, or FQDN for the third-party Core machine. Port Enter the port number that was given to you by your third-party service provider. The default port number is 8006.
If the Core you want to add has been paired with this source Core previously, you can do the following:- Select Use an existing target Core.
- Select the target Core from the drop-down list.
- Click Next.
- Skip to step 7.
- Click Next.
- On the Request page of the Replication Wizard, enter the information as described in the following table.
Table 89: Third-party target Core details Text Box Description Email Address Enter the email address associated with your third-party service subscription. Customer ID (optional) Optionally, enter the customer ID that was assigned to you by the service provider. - Click Next.
- On the Protected Machines page of the Replication Wizard, select the protected machines you want to replicate to the third-party Core.
- If you want to perform the seeding process for the transfer of base data, complete the following steps.
Note: Because large amounts of data need to be copied to the portable storage device, an eSATA, USB 3.0, or other high-speed connection to the portable storage device is recommended.
- On the Protected Machines page of the Replication Wizard, select Use a seed drive to perform initial transfer.
- If you currently have one or more protected machines replicating to a target Core, you can include these machines on the seed drive by selecting the option Include already replicated recovery points in the seed drive.
- Click Next.
- On the Seed Drive Location page of the Replication Wizard, use the Location type drop-down list to select from the following destination types:
- Local
- Network
- Cloud
- Enter the details for the archive as described in the following table, based on the location type you selected in step c.
Table 90: Archive details Option Text Box Description Local Output location Enter the location for the output. It is used to define the location path where you want the seed drive archive to reside; for example, D:\work\archive. Network Output location Enter the location for the output. It is used to define the location path where you want the archive to reside; for example, \\servername\sharename. User Name Enter a user name. It is used to establish logon credentials for the network share.
NOTE: Optionally, you can select credentials for a user in the Credentials Vault, or you can save credentials you add here to the vault. For more information, see Credentials Vault.
Password Enter a password for the network path. It is used to establish logon credentials for the network share. Cloud Account Select an account from the drop-down list.
NOTE: To select a cloud account, you must first have added it in the Core Console. For more information, see Adding a cloud account.
Container Select a container associated with your account from the drop-down menu. Folder Name Enter a name for the folder in which the archived data is to be saved. The default name is Rapid-Recovery-Archive-[DATE CREATED]-[TIME CREATED] - Click Next.
- On the Seed Drive Options page of the Replication Wizard, enter the information as described in the following table.
Table 91: Seed drive options Item Description Maximum Size Large archives of data can be divided into multiple segments. Select the maximum amount of space you want to reserve for creating the seed drive by doing one of the following: - Select Entire Target to reserve all available space in the path provided on the Seed Drive Location page (for example, if the location is D:\work\archive, all of the available space on the D: drive is reserved).
- Select the blank text box, enter an amount, and then select a unit of measurement from the drop-down list to customize the maximum space you want to reserve.
Recycle action In the event the path already contains a seed drive, select one of the following options: - Do not reuse. Does not overwrite or clear any existing seed data from the location. If the location is not empty, the seed drive write will fail.
- Replace this Core. Overwrites any pre-existing seed data pertaining to this Core but leaves the data for other Cores intact.
- Erase completely. Clears all seed data from the directory before writing the seed drive.
Comment Enter a comment that describes the seed drive. Add all Agents to Seed Drive Select this option to replicate all protected machines on the source Core using the seed drive. This option is selected by default. Build recovery points chains (fix orphans) Select this option to replicate the entire recovery point chain to the seed drive. This option is selected by default.
- Do one of the following:
- If you cleared the Add all Agents to Seed Drive check box, click Next.
- If you selected Add all Agents to Seed Drive, go to step 9.
- On the Machines page of the Replication Wizard, select the protected machines you want to replicate to the target Core using the seed drive.
- On the Protected Machines page of the Replication Wizard, select Use a seed drive to perform initial transfer.
- Click Finish.
- If you created a seed drive, send it as directed by your third-party service provider.