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.
Introduction to Rapid Recovery
The Core Console
Accessing the Rapid Recovery Core Console
Understanding the Quick Start Guide
Navigating the Rapid Recovery Core Console
Viewing the Protected Machines menu
Repositories
Viewing summary information for a protected machine
Viewing replicated machines from the navigation menu
Viewing the Recovery Points Only menu
Viewing the Custom Groups menu
Using the Error dialog box
Viewing the Summary pane
Viewing Volumes on a protected machine
Viewing replication information
Viewing the Exchange Server Information pane
Viewing the SQL Server Information pane
Viewing summary information for a host
Viewing recovery points for a machine
Viewing events for a protected machine
Viewing reports for a protected machine
Understanding repositories
Deduplication in Rapid Recovery
Managing a DVM repository
Managing an Azure repository
About DVM repository optimization
Connecting to an existing repository
Viewing or modifying repository details
Checking a repository
Deleting a repository
Core settings
Core settings key functions
Rapid Recovery Core settings
Protecting machines
Configuring Core general settings
Configuring update settings
Understanding nightly jobs
Modifying transfer queue settings
Adjusting client timeout settings
Understanding deduplication cache or dictionary size and storage locations
Configuring Replay engine settings
Configuring deployment settings
Core-level tools
Configuring database connection settings
Modifying loca database connection settings
Managing SMTP server settings
Configuring cloud account connection settings
Managing report settings
Managing Core SQL attachability settings
Understanding Core jobs
Understanding SNMP settings
Configuring vSphere settings
Managing VMware proxy settings
Configuring vFoglight settings
About protecting machines with Rapid Recovery
Managing protected machines
Factors when choosing agent-based or agentless protection
About protecting Linux machines with Rapid Recovery
About protecting Oracle database servers
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
Entering or editing credentials for Oracle databases
Enabling archive log mode and adding VSS writer for protected Oracle databases
About truncating Oracle logs
Manually truncating Oracle database logs
About managing Exchange and SQL servers in Rapid Recovery Core
About protecting server clusters
Understanding Rapid Snap for Virtual
Benefits of installing hypervisor tools for agentless protection
Understanding crash-consistent and application-consistent backups
Support for Hyper-V guest cluster
Deploying to machines on an Active Directory domain
Deploying to machines on a VMware vCenter/ESXi virtual host
Deploying an upgrade of the Rapid Recovery Agent software to protected machines
Deploying to machines manually
Verifying the deployment to multiple machines
Modifying deploy settings
Understanding protection schedules
Protecting a machine
Protecting a cluster
Creating custom protection schedules in Simple Mode
Creating multiple protection schedule periods in Advanced Mode
Pausing and resuming protection
About protecting multiple machines
Protecting multiple machines on an Active Directory domain
Protecting multiple machines on a VMware vCenter/ESXi virtual host
Protecting vCenter/ESXi virtual machines using agentless protection
Protecting multiple machines on a Hyper-V virtual host
Protecting Hyper-V virtual machines using agentless protection
Protecting multiple machines manually
Monitoring the protection of multiple machines
Enabling application support
Settings and functions for protected Exchange servers
Setting credentials for an Exchange server machine
Forcing log truncation for an Exchange machine
About Exchange database mountability checks
Forcing a mountability check of an Exchange database
Forcing a checksum check of Exchange database files
Settings and functions for protected SQL servers
About managing protected machines
Viewing protected machines
Configuring machine settings
Snapshots and recovery points
Viewing and modifying protected machine settings
Changing the settings for a Hyper-V host or node
Changing the settings for a Hyper-V protected virtual machine
Changing the vSphere settings for a VMware protected virtual machine
Understanding Active Block Mapping
About modifying transfer settings
Customizing nightly jobs for a protected machine
Understanding system information for a protected machine
Managing machines
Removing a machine
Removing a cluster from protection
Viewing license information on a machine
Downloading and viewing the log file for a protected machine
Converting a protected cluster node to a protected machine
Understanding custom groups
Managing snapshots and recovery points
Viewing the recovery points page of a protected machine
Mounting a recovery point
Dismounting recovery points
Working with Linux recovery points
Forcing a snapshot
Removing recovery points
Deleting an orphaned recovery point chain
Migrating recovery points manually to a different repository
Managing privacy
General Data Protection Regulation compliance
How Rapid Recovery uses personal information
Non-phone-home license restrictions
Obtaining and using non-phone-home licenses
Encryption
Understanding encryption keys
Encrypting data in transport over a network
Applying or removing encryption keys
Credentials Vault
Associating an encryption key with a protected machine
Applying an encryption key from the Protected Machines page
Disassociating an encryption key from a protected machine
Managing encryption keys
Understanding the Credentials Vault
Adding accounts to the Credentials Vault
Viewing or changing accounts saved in the vault
Using credentials from the vault
Replication
Replication with Rapid Recovery
Recovery point chains and orphans
When replication begins
Determining your seeding needs and strategy
Performance considerations for replicated data transfer
Viewing incoming and outgoing replication
Configuring replication
Replicating to a self-managed target Core
Replicating to a third-party target Core
Events
Submitting a replication request to a third-party service provider
Reviewing a replication request from a customer
Approving a replication request
Denying a replication request
Ignoring a replication request from a customer
Adding a machine to existing replication
Consuming the seed drive on a target Core
Managing replication settings
Scheduling replication
Using the Copy function to create a seed drive
Monitoring replication
Pausing and resuming replication
Forcing replication
Managing settings for outgoing replication
Changing target Core settings
Setting replication priority for a protected machine
Removing outgoing replication from the source Core
Removing incoming replication from the target Core
Recovering replicated data
Viewing events using tasks, alerts, and journal pages
Reporting
Viewing tasks
Viewing alerts
Viewing a journal of all logged events
Navigating between tasks, alerts, and the events journal
Understanding event notifications in Rapid Recovery
Configuring event settings
About Rapid Recovery reports
Generating a report from the Core Console
Managing scheduled reports from the Core Console
Using the Reports menu
Using the Reports toolbar
Understanding the Job report
Understanding the Job Summary report
Understanding the Failure report
Understanding the Summary report
Understanding the Repository report
Understanding the Classic Summary report
VM export
Exporting to virtual machines using Rapid Recovery
Exporting data to an ESXi virtual machine
Exporting data to a VMware Workstation virtual machine
Exporting data to a Hyper-V virtual machine
Exporting data to a VirtualBox virtual machine
Exporting data to an Azure virtual machine
Restoring data
Working with Microsoft Azure
Managing exports
Azure interface disclaimer
Country codes used on the Azure website
Before virtual export to Azure
About Azure storage accounts
Creating an Azure storage account
Creating a container in an Azure storage account
Creating an Azure Active Directory web application
Obtaining the application ID for an Azure web application
Obtaining Azure subscription information
Obtaining the directory ID for your Azure web application
Obtaining a secret key for your Azure web application
Microsoft Azure documentation
Exporting and deploying VMs for Azure
About restoring data with Rapid Recovery
Understanding Live Recovery
Restoring data from recovery points
r_VM_configuration_backup_and_restore_for_VMware_and_Hyper-V
About the file search and restore feature
About restoring volumes from a recovery point
Bare metal restore
Restoring volumes from a recovery point
Restoring a directory or file using Windows Explorer
Restoring a directory or file and preserving permissions using Windows Explorer
Restoring clusters and cluster nodes
Restoring from an attached archive
Mail Restore in Rapid Recovery
About bare metal restore
Differences in bare metal restore for Windows and Linux machines
Understanding boot CD creation for Windows machines
Managing aging data
Archiving
Understanding driver injection in a boot CD
Using UltraVNC for remote access
Creating a boot CD ISO image
Transferring the boot CD ISO image to media
Loading the boot CD and starting the target machine
Managing a Linux boot image
About the boot ISO image for Linux
Downloading a boot ISO image for Linux
Saving the Live DVD ISO image to media
Loading the Live DVD and starting the target machine
Connecting to the BMR target from the Rapid Recovery Core
Performing a bare metal restore using the Restore Machine Wizard
Using the Universal Recovery Console for a BMR
About the Universal Recovery Console tools
Loading drivers using the Universal Recovery Console
Performing a bare metal restore for Linux machines
Loading drivers in the Universal Recovery Console using portable media
Loading a driver in the URC using Chromium
Selecting a recovery point and initiating a BMR
About disk mapping for a bare metal restore
Performing a BMR from an archive
Loading drivers to the operating system
Managing Linux partitions
Verifying a bare metal restore
Creating partitions on the destination drive
Formatting partitions on the destination drive
Mounting partitions from the command line
Launching a bare metal restore for Linux
Starting the Screen utility
Launching a bare metal restore for a Linux machine using the command line
Restoring volumes for a Linux machine using the command line
Understanding archives
Cloud accounts
Archive creation and storage options
Amazon storage options and archiving
Recovery point chain options for archives
Methods to access an archive
Uses for archives
Creating an archive
Editing a scheduled archive
Pausing or resuming a scheduled archive
Forcing an archive job
Checking an archive
Attaching an archive
Detaching an archive
Importing an archive
About cloud accounts
Considering cloud storage options
Adding a cloud account
Editing a cloud account
Removing a cloud account
Core Console references
REST APIs
Intended audience
Working with Rapid Recovery REST APIs
Downloading and viewing Core and Agent APIs
Recommended additional reading
Glossary
About replication and encrypted recovery points
Replication > Performance considerations for replicated data transfer > About replication and encrypted recovery points
About retention policies for replication
Replication > Performance considerations for replicated data transfer > About retention policies for replication
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.
Viewing incoming and outgoing replication
If you click the ![[Replicate]](/zh-cn/technical-documents/image/1d24f735-2225-4f9c-8ae6-4379911d3111)
- 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.
| UI Element | Description |
|---|---|
| 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. |
![[Actions]](/zh-cn/technical-documents/image/fe1363a2-7a8d-4400-9f19-e3a04edd8e8a) |
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.
| UI Element | Description |
|---|---|
| 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.
| UI Element | Description |
|---|---|
| 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.
| UI Element | Description |
|---|---|
| Refresh | Refreshes the information shown in the table. |
| Force | Forces replication. |
| Pause | Pauses established replication. |
| Resume | Resumes paused replication. |
| Delete | Deletes incoming replication. |
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.