Multi-Data Center Replication To A Common Disaster Recovery Site - HP 12000 Design Manual

recommended for high volumes of data (TBs) because of the time to replicate data wholesale
over a relatively small link speed.
Data can be copied to physical tape at the disaster recovery site then transported to the
primary site and imported to new servers and arrays using physical tape at the primary site.
Tape could also be copied to the VLS and then recovered from there.
Solution advantages:
Automated disaster recovery over cost effective low bandwidth links
Flexible recovery options
Scalable in terms of capacity and performance
Flexible replication implementations: active-to-passive, active-to-active, and many-to–one (up
to four)
Only target nodes need to be licensed for replication
Solution trade-offs:
Deduplication has to be certified with backup applications and data types. Data Protector,
Netbackup, and TSM currently supported.
A one-time initialization process is required the first time replication runs so the source and
target can synchronize. This can be done by co-location, replication over low bandwidth link,
or by using physical tape transport – export and import.
Other information: HP strongly recommends using the backup application to perform the copy
from VLS to physical tape. Single management console for all activities and better utilization of
physical media through object copy technology.

Multi-data Center Replication to a Common Disaster Recovery Site

Company requirements: Full disaster recovery capability for a number of data centers to replicate
data automatically to a single disaster recovery site in a cost effective manner by consolidating
storage at the disaster recovery site and with reduced fixed costs (link costs). Copy to physical
tape at disaster recovery site for archiving and further disaster recovery options.
Solution: VLS with deduplication and many-to-one replication.
Caveats: Allow 24 hours for replication. Scripting may be required on target site for trickle import
of replicated cartridges to ISV software backup catalog.
ISVs: HP Data Protector, Netbackup, and TSM only at this time. (Deduplication is the key enabler
for deduplication enabled replication.)
Device configuration highlights: Setting up replication is done by creating echo copy pools. Identical
cartridges are kept on source and target devices and report "up to date" when they are fully
synchronized.
Backup application configuration highlights: Two separate master servers are required with one
at each site.
VLS Blueprints 69