Replication Send - Fujitsu ETERNUS CS800 S6 User Manual

Replication" on page
target, and the original target system is now the source.
Task Overview: Performing a Share or Partition Failback
If a NAS share or VTL partition is lost or damaged on the source system, you can failback
the share or partition to the source system using a received snapshot on the target
system. When you failback a share or partition, it is restored on the source system just as
it was at the point in time when the snapshot was saved.
To perform a share or partition failback:
1. On the original source system, add the original target system to the list of allowed
replication sources (see
For the purposes of failback, the original source system is now acting as a
target because it will receive the snapshot from the original target system.
2. On the original target system, select a received snapshot and perform a failback
operation pointing to the original source system, and then recover the share or
partition on the original source system (see
page 359
The share or partition is now available on the original source system.
3. (Optional) If necessary, map your backup application to the restored share or
partition on the original source system.

11.2 Replication Send

The Replication Send page allows you to manage outgoing replication activity for NAS
shares or VTL partitions. You can replicate shares or partitions on the on the ETERNUS
CS800 (the source) to other ETERNUS CS800 systems (the targets). You can also schedule
replication, and view the status of current and recent replication jobs.
Before you can replicate shares or partitions, you must specify a replication
target (see
To access the Replication Send page, click the Replication menu, and then click the Send
tab (see "Replication Send Page" on page
ETERNUS CS800
344). In this scenario, the original source system is now the
"Adding a Replication Source" on page
or "Performing a Failback For a Partition" on page
"Adding a Replication Target" on page
"Performing a Failback For a Share" on
253).
348).
11.2 Replication Send
259).
370).
347