Using Vls With Full Enterprise Backup And Disaster Recovery Capability - HP StorageWorks 12000 - Virtual Library System EVA Gateway Manual

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.
Figure 53 Using VLS with Full Enterprise Backup and Disaster Recovery Capability
.
Recovery options: Primary site data can be recovered directly from the VLS at primary site. If there is
a total disaster at the primary site and all servers and VLS are lost, data can be recovered from the
disaster recovery site in several ways:
• At the disaster recovery site using a separate backup application, master server data can be re-
covered to the new servers.
• A replacement VLS and servers can be installed at the primary site and data can be reverse rep-
licated from the disaster recovery site over the low bandwidth link, although this is not 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, Net-
backup, and TSM currently supported.
HP StorageWorks VLS and D2D Solutions Guide 131