Table of Contents
Advertisement
6.
On the target VLS: Create the cartridges to be used by the replication target. Using the same
barcodes as exist on the source will cause the existing source cartridges to be reused.
7.
On the source VLS: Manage the replication library.
8.
On the source VLS: Create the new echo copy pool. Make sure to select tape initialization if
you want to initialize that target data using tape initialization. If you use pre-existing cartridges,
all cartridges will go into the "Waiting for Backup Data" state.
9.
On the source VLS: Follow the normal instructions for performing tape initialization.
10. On the source VLS: In a many-to-one configuration, repeat
source VLS.
Creating Archive Tapes from the Target
Even with replication removing the need for physical tape off-site, there are still many users who
wish to use physical tape for archive or test recoveries, etc. An archive tape will have the following
differences from the original backup:
A different retention time from the original backup (for example, you may keep backups and
off-site replicas for three months but keep tape archive for several years).
Different cartridge contents because it will be different size (optimum virtual cartridge size for
deduplication is 50- 1 00 GB but physical tapes such as LTO-4 are 800 GB).
A different barcode and be tracked separately in the backup application.
The above characteristics mean that the backup application must control the creation of the archive
tape and must use an object-copy based system (cannot use a whole-tape copy system). This is
easy if the physical library is on the source site because you can use the normal backup application
object-copy mechanisms to simply copy from their source virtual library to their physical library
(via the backup application media servers). However, if the physical library is at the target site
and you want to perform the tape archive from the replicated virtual cartridges in the target device,
this requires additional steps. This is because the backup application at the target device that sees
the replicated virtual cartridges cannot be the same backup application that performed the backups
at the source site (see
application does not have any information about the replicated cartridges in its media database
because it did not backup to those tapes.
Figure 58 Creating Archive Tapes from the VLS
In order to have the target backup application copy from the replicated cartridges to a physical
tape library it needs to be "taught" what is on the replicated cartridges. This can be done
automatically as shown in the diagram above, by using a new "ISV Import" email report on the
124 Replication
Backup Application Interaction with
Step 7
through
Step 9
Replication). The target site backup
on each
Advertisement
Table of Contents
