Replicating To A Core Managed By A Third Party - Dell DL4000 User Manual

Tape library
Hide thumbs Also See for DL4000:
Table of Contents

Advertisement

Text Box
Account
Container
Folder Name
6.
Click Check File.
After the Core checks the file, it automatically populates the Date Range with the dates of the oldest
and newest recovery points contained in the seed drive. It also imports any comments entered in
Configuring Replication For A Self-Managed Core.
7.
Under Agent Names on the Consume window, select the machines for which you want to consume
data, and then click Consume.
NOTE: To monitor the data consumption progress, select the Events tab.
Abandoning an outstanding seed drive
If you create a seed drive with the intent to consume it on the target core but choose not to send it to the
remote location, a link for the outstanding seed drive remains on the source core Replication tab. You
may want to abandon the outstanding seed drive in favor of different or more current seed data.
NOTE: This procedure removes the link to the outstanding seed drive from the Core Console on the
source core. It does not remove the drive from the storage location on which it is saved.
To abandon an outstanding seed drive:
1.
From the Core Console on the source core, select the Replication tab.
2.
Click Outstanding Seed Drive (#).
The Outstanding seed drives section appears. It includes the name of the remote target core, the
data and time at which the seed drive was created, and the data range of the recovery points
included on the seed drive.
3.
Click the drop-down menu for the drive that you want to abandon, then select Abandon.
The Outstanding Seed Drive window appears.
4.
Click Yes to confirm the action.
The seed drive is removed. If there are no more seed drives that exist on the source core, then the
next time that you open the Replication tab, the Outstanding Seed Drive (#) link and Outstanding
seed drives section do not appear.

Replicating to a core managed by a third party

A third-party core is a target core that it managed and maintained by an MSP. Replicating to a core
managed by a third party does not require you to have access to the target core. After a customer
configures replication on the source core or cores, the MSP completes the configuration on the target
core.
NOTE: This configuration applies to hosted and cloud replication. The AppAssure Core must be
installed on all source core machines.
50
Description
Select an account from the drop-down list. To select a cloud account, you
must first have added it in the Core Console.
Select a container associated with your account from the drop-down menu.
Enter the name of the folder in which the archived data is saved; for example, -
Archive-[DATE CREATED]- [TIME CREATED]

Advertisement

Table of Contents
loading

Table of Contents