Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings Repositories Encryption keys Protecting machines
About protecting machines with Rapid Recovery Support for dynamic and basic volumes 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 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 Viewing the recovery progress Starting a restored target server Troubleshooting connections to the Universal Recovery Console Repairing boot problems Performing a file system check on the restored volume
Managing aging data Archiving Cloud storage accounts The Local Mount Utility The Central Management Console Core Console references Command Line Management utility PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Scripting REST APIs About us Glossary

Abandoning a seed drive

If you create a seed drive with the intent of consuming it on the target Core, but later choose not to consume it, you can abandon the seed drive.

Until you abandon the seed drive or consume it, a link for the outstanding seed drive remains on the Outgoing Replication pane on the source Core.

Until you transmit information from the seed drive, orphaned recovery points (which exist on the original protected machine, but not the target Core) cannot be used to restore data.

* 
CAUTION: If you abandon the seed drive, then the original recovery points (defined in the seed drive file) are then transmitted over the network to the target Core during the next replication job. Transmitting old recovery points over the network could slow down the network considerably, especially if there are many recovery points.

Complete the steps in the following procedure to abandon an outstanding seed drive.

* 
NOTE: Abandoning the seed drive in the Core Console does not affect the seed drive file from its storage location.
1.
On the source Core, open the Rapid Recovery Core Console, and from the icon bar, click [Replication] (Replication).
The Replication page appears.
2.
On the Replication page, in the Outgoing Replication pane, click Seed Drives (#).
In the Outgoing Replication pane, a section appears containing information about the outstanding seed drives.
3.
Optionally, click the downward-facing arrow [Expand] to expand the collapsible menu.
Information appears about outstanding seed drives, including the target Core and the date range of the recovery points included in the seed drive.
4.
Click [Actions] to open the drop-down menu for the seed drive file you want to abandon, and then select Abandon.
5.
In the confirmation window, confirm that you want to abandon the seed drive.

The seed drive is removed.

If no more seed drives exist on the source Core, the Seed Drives (#) link and outstanding seed drives section are removed from the Outgoing Replication pane.

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

Rapid Recovery lets you monitor, schedule, and adjust replication at the overall, core, and protected machine levels.

You can edit the following replication settings:

•
To schedule replication jobs, see Scheduling replication.
•
To create a seed drive of a protected machine that is already paired for replication, see Using the Copy function to create a seed drive
•
To monitor the progress of a replication job, see Viewing incoming and outgoing replication.
•
To pause or resume a paused replication job, see Pausing and resuming replication.
•
To force replication of an incoming or outgoing protected machine, see Forcing replication.
•
To manage settings for all target cores and replication procedures, see Managing settings for outgoing replication.
•
To manage settings for an individual target core, see Changing target Core settings.
•
To manage priority settings for an individual protected machine being replicated to a target core, see Setting replication priority for a protected machine.

Scheduling replication

Unless you change the default behavior by setting a replication schedule, the Core starts a replication job immediately after completion of every backup snapshot, checksum check, attachability check, and the nightly jobs. For more information, see Scheduling replication.

You can change the replication schedule to reduce the load on the network.

Complete the steps in the following procedure to set a replication schedule for any replicated machine.

1.
On the target Core, open the Rapid Recovery Core Console, and from the icon bar, click [Replication] (Replication).
The Replication page appears.
2.
In the Outgoing Replication pane, click [Actions] to open the drop-down menu next to the Core for which you want schedule replication, and then select Schedule.

The Replication Schedule for [CoreName] dialog box opens.

3.
Select from one of the following three options:
◦
At All Times. Replicates after every new snapshot, checksum check, and attachability check, and after the nightly jobs complete.
◦
Daily (Start replication only during the specified time period). Begins replicating only within the time range provided.
1.
In the From text box, enter the earliest time at which replication should begin.
2.
In the To text box, enter the latest time at which replication should begin.
* 
NOTE: If replication is in progress when the scheduled time ends, the replication job completes after the allotted time period.
◦
Custom. Begins replicating only within the time range provided, letting you set one time range for weekdays and another time range for weekends.
1.
Next to Weekdays, in the From text box, enter the earliest time at which replication should occur on a weekday; and then in the To text box, enter the latest time at which replication should occur on a weekday.
2.
Next to Weekends, in the From text box, enter the earliest time at which replication should occur on weekends; and then in the To text box, enter the latest time at which replication should occur on weekends.
4.
Click Save.

The schedule is applied to all replication to the selected target Core.

Using the Copy function to create a seed drive

If you chose not to create a seed drive when you configured replication, you can create a seed drive using the Copy function in the protected machine drop-down menu.

1.
On the source Core, open the Rapid Recovery Core Console, and from the icon bar, click [Replication] (Replication).
The Replication page appears.
2.
On the Replication page, in the Outgoing Replication pane, click [Expand] to expand the Core that protects the machine for which you want to create a seed drive.
The selection expands to show each protected machine in the specified Core.
3.
Click in the first row of the table to select each machine for which you want to create a seed drive.
4.
In the menu under the Outgoing Replication pane, click Copy.
The Replication Wizard appears.
5.
On the Seed Drive Location page of the wizard, use the Location drop-down list to select from the following destination types:
◦
Local
◦
Network
◦
Cloud
6.
Enter the details for the seed drive archive, as described in the following table, based on the location type you selected in the preceding step.

Table 113. 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 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.

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]

7.
Click Next.
8.
On the Seed Drive Options page, enter the information as described in the following table.

Table 114. 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 point chains (fix orphans)

Select this option to replicate the entire recovery point chain to the seed drive. This option is selected by default.

* 
NOTE: Typical seeding in Rapid Recovery 5.4.x replicated only the latest recovery point to the seed drive, which reduced the amount of time and space required for creating the seed drive. Opting to build recovery point chains to the seed drive requires enough space on the seed drive to store the latest recovery points from the specified protected machines, and may take additional time to complete the task.
9.
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.
10.
On the Protected Machines page of the wizard, select the protected machines for which you want to create a seed drive.
11.
Click Finish.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating