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. |
- On the source Core, open the Rapid Recovery Core Console, and from the icon bar, click (Replication).
The Replication page appears.
- 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.
- Optionally, click the arrow 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.
- For the seed drive file you want to abandon, click (More options) and then select Abandon.
- 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.