Complete the follow procedure to consume the data from the seed drive file on the target Core.
This procedure is only necessary if a seed drive file was created as part of Replicating to a self-managed target Core or Replicating to a third-party target Core.
|
NOTE: If the seed data is comprised of multiple segments, all segments must be available in the location type you specify in step 4. For example, all segments should be attached to the local target Core server, in the same network directory, or in the same cloud account container. |
The Consume dialog box appears.
Option | Text Box | Description | ||
---|---|---|---|---|
Local | Location | Enter the path for the archive. | ||
Network | Location | Enter the path for the archive. | ||
User name | Enter the user name. It is used to establish logon credentials for the network share. | |||
Password | Enter the 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.
| ||
Container | Select a container associated with your account from the drop-down menu. | |||
Folder name | Enter the name of the folder in which the archived data is saved; for example, Rapid-Recovery-Archive-[DATE CREATED]-[TIME CREATED] |
The Core searches for the file.
After finding the file, the following text boxes appear in the Consume dialog box, pre-populated with the data gathered from step 4, step 5, and the file.
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. |
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.
Rapid Recovery Core lets you monitor, schedule, and adjust replication at the overall, Core, and protected machine levels.
You can edit the following replication settings:
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.
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.
The Replication Schedule for [CoreName] dialog box opens.
NOTE: If replication is in progress when the scheduled time ends, the replication job completes after the allotted time period. |
The schedule is applied to all replication to the selected target Core.
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center