While the seed drive does not contain backups of the source Core registry and certificates, the seed drive does contain encryption keys from the source Core if the recovery points being replicated from source to target are encrypted. The replicated recovery points remain encrypted after they are transmitted to the target Core. The owners or administrators of the target Core need the passphrase to recover the encrypted data.
Retention policies on the source and target Cores are not synchronized. Rollup and on-demand deletion perform independently on each Core on initial action, as well as when running nightly jobs.
For more information on retention policies, see Managing retention policies.
If you click the Replicate icon from the icon bar, the Replication page appears. This page gives you an understanding of replication from the scope of this Core. It includes two panes:
- The Outgoing Replication pane lists any machines protected in this Core that are replicated on another Core.
- The Incoming Replication pane lists the machines replicated on this Core, and the source Core from which these machines are replicated.
This section describes the information shown in these panes.
Information about outgoing replication from this Rapid Recovery Coreis described in the following table.
Table 86: Information about outgoing replication
Select item |
For each row in the summary table, you can select the checkbox to perform actions from the list of menu options above the table. |
Type |
Shows the machine type. You can expand a target Core to show individual replicated machines. |
Status indicator |
Status of replication. Colored circles in the Status column show whether a replicated machine is online or unreachable. If you hover the cursor over the colored circle, the status condition is displayed. Status conditions include green (replication established and online), yellow (replication paused), red (authentication error), and gray (offline or unreachable). |
Replication Name |
The display name of the Core machine to which machines from this source Core are replicated. |
Machines |
Lists the number of machines replicated to the selected target Core. |
Sync |
The date and time of the last replication transfer to the target Core. |
|
When you click the More drop-down menu in this column, you see a list of actions to perform to affect the specific replication relationship. |
You can perform actions on two or more of the target Cores listed in the Outgoing Replication grid. To perform actions on multiple target Cores, select the checkbox for each Core in the grid, and then, from the menu above the grid, select the action you want to perform. You can perform the actions described in the following table.
Table 87: Global actions available in the Outgoing Replication pane
Add Target Core |
Lets you define another target Core to replicate machines protected on this source Core. |
Refresh |
Refreshes the information shown in the table. |
Force |
Forces replication. |
Pause |
Pauses established replication. |
Resume |
Resumes paused replication. |
Copy |
Opens the replication wizard, letting you copy existing recovery points for selected protected machines to a seed drive. |
Delete |
Deletes outgoing replication. |
Seed Drives |
This menu option appears if data was copied to a seed drive when replication was set up.
Displays information about the seed drive file, including the data and time the seed drive was saved. Collapsible menus indicate the target Core and the protected machines from which the seed drive files were generated. |
|
When you click the More drop-down menu in this column, you see a list of actions to perform to affect the specific replication relationship. |
Information about incoming replication from another Core is described in the following table.
Table 88: Information about incoming replication
Select item |
For each row in the summary table, you can select the checkbox to perform actions from the list of menu options above the table. |
Type |
Shows the machine type. You can expand a source Core to show individual replicated machines. |
Status indicator |
Status of replication. Colored circles in the Status column show whether a replicated machine is online or unreachable. If you hover the cursor over the colored circle, the status condition is displayed. Status conditions include green (replication established and online), yellow (replication paused), red (authentication error), and gray (offline or unreachable). |
Replication Name |
The display name of the source Core machine containing protected machines that are replicated on this target Core.
This name can be optionally specified when establishing replication on the source Core using the Replication Wizard. |
Machines |
Lists the number of machines protected on the source Core that are replicated to this target Core. |
Sync |
The date and time of the last replication transfer from the source Core. |
|
When you click the More drop-down menu in this column, you see a list of actions to perform to affect the specific replication relationship. |
You can perform actions on two or more of the source Cores listed in the Incoming Replication grid. To perform actions on multiple source Cores, select the checkbox for each Core in the grid, and then, from the menu above the grid, select the action you want to perform. You can perform the actions described in the following table.
Table 89: Global actions available in the Incoming Replication pane
Refresh |
Refreshes the information shown in the table. |
Force |
Forces replication. |
Pause |
Pauses established replication. |
Resume |
Resumes paused replication. |
Delete |
Deletes incoming 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.