Rebuilding Source Device And Re-Establishing Replication; Creating Archive Tapes From The Target - HP StorageWorks 12000 - Virtual Library System EVA Gateway Manual

cartridges containing the last full backup and any incremental backups after this point. These can
then be used by the backup application to import/restore from the source device's virtual library to
replacement servers.

Rebuilding Source Device and Re-establishing Replication

If the entire source VLS device was destroyed (i.e., you had a site disaster) and was replaced with a
brand new blank device, then you must recreate the original virtual library configuration and replication
configuration. If you have a previously saved configuration file (created using Save Configuration in
the VLS GUI) you can perform a "Restore Configuration" in the VLS GUI (loading in a previous saved
configuration). Alternatively you can manually recreate the original virtual library configuration and
replication configuration.
There is currently no method of restoring the entire deduplicated set of cartridges from the target VLS
to the source VLS. Once your source VLS is rebuilt and reconfigured and you have restored your
servers, you must start backups again to the source device and then repeat the initialization process
after the first full backup is finished.
NOTE:
If you need to re-initialize the replication system using tape initialization, then you must create your
echo copy pools with the "Initialize via Tape Transport" option enabled and then repeat the tape
initialization process. This means if you used "Restore Configuration" to recreate your replication
configuration you must delete your Echo Copy pools and recreate them.

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 de-
duplication is 50-100 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 Backup Application Interaction with
have any information about the replicated cartridges in its media database because it did not backup
to those tapes.
190 Virtual Library Systems
Replication). The target site backup application does not