Table of Contents
Advertisement
Replicating a Subset of Virtual Cartridges - a Use Case
The following is just one possible use case for non-deduplicated replication. In a typical backup
environment, companies rarely have network bandwidth surpassing what meets their needs. For
this reason, the ability to replicate just a subset of business critical data, thus conserving bandwidth,
is advantageous. It is fully supported to have a mixture of standard and automigration tapes in the
same virtual library at the same time.
Replicating a subset of backup data to a remote VLS also provides customers with the flexibility
and simplicity of not having to create a second library target in the backup application just for
replication. Customers can configure one library on the source VLS that performs local backups,
and that also replicates a subset of data they designate.
To replicate a subset of backup jobs:
1.
On VLS1 (local VLS) configure one library with more slots than what you need for regular
backups (to be used for replicating virtual cartridges).
2.
On VLS2 (remote VLS) configure a small replication library.
3.
Configure the SAN zoning so that the VLS2 replication library is presented over the extended
SAN into the VLS1 back-end array zones. That is, the back-end fibre channel ports of VLS1
can see the replication library on VLS2.
4.
On VLS1, "manage" or add the VLS2 replication library as the destination library. See
"Automigration Setup" (page
5.
Create an echo copy pool for the VLS2 replication library, with the library on VLS1 as the
source.
Automigration will automatically create the replicating virtual cartridges on VLS1 in the spare
slots configured in step 1. During the automigration window you created, backups already
copied to replicating virtual cartridges on VLS1 will automatically be copied over to VLS2. If
you back up to a non-automigration tape in VLS1, then nothing else happens. To the backup
application, there is just one target library, though it contains both replicating and
non-replicating tapes. It is easy to put the replicating tapes into a different media pool in the
backup application, and simply configure the backup jobs to use either the replication media
pool, or the non-replication media pool. In either case, all the backup jobs go to the one,
shared destination library.
NOTE:
For cross-replication you can create the reverse configuration. For example, create another
large library on VLS2 for its backups, and create a small replication library on VLS1 that is visible
to the back-end ports of VLS2.
128 Non-deduplicated Replication
81).
Advertisement
Table of Contents
