HP StoreOnce Backup System Concepts and Configuration Guidelines (BB877-90913, November 2013)

Many to One configurations
The other main usage model for the HP B6200 Backup system is in large-scale remote office
deployments where a fan-in of up to 384 replication jobs to a maximum-configuration HP B6200
Backup System is possible (one stream per device). The sources (remote offices) are more likely to
be single-node HP StoreOnce StoreOnce Backup systems.
For a large number of remote sites co-location is impractical, instead the Floating StoreOnce option
is recommended. Physical tape and seeding over a WAN link both have difficulties, due to capacity
and bandwidth limitations.
Implementing floating StoreOnce seeding
This “floating StoreOnce” method is more complex because for large fan-in (many source sites
replicating into a single target site) the initial replication setup on the floating StoreOnce changes
when it is transported to the Data Center, where the final replication mappings are configured.
The sequence of events is as follows:
1. Plan the final master replication mappings from sources to target that are required and
document them. Use an appropriate naming convention, such as SVTL1 (Source VTL1),
SNASshare1, TVTL1 (Target VTL1), TNASshare1.
2. At each remote site perform a full system backup to the source StoreOnce and then configure
a 1:1 mapping relationship with the floating StoreOnce device, such as:
nl
SVTL1 on Remote Site A -> FTVTL1 on floating StoreOnce where FTVTL1 = floating target VTL1.
Seeding times at the remote site A will vary. If the StoreOnce at site A is an HP StoreOnce
2620 Backup system, it is over a 1 GbE link and may take several hours. It will be faster if a
model with 10GbE replication links is used at the remote sites.
3. On the Source StoreOnce at the remote site DELETE the replication mappings – this effectively
isolates the data that is now on the floating StoreOnce.
4. Repeat the process steps 1-3 at Remote sites B and C.
5. When the floating StoreOnce arrives at the central site, the floating StoreOnce effectively
becomes the Source device to replicate INTO the HP B6200 Backup System at the Data Center
site.
6. On the floating StoreOnce we will have devices (previously named as FTVTL1, FTNASshare
1) that we can see from the Management Console (GUI). Using the same master naming
convention as we did in step 1, set up replication which will necessitate the creation of the
necessary devices (VTL or NAS) on the B6200 at the Data Center site e.g. TVTL1, TNASshare
1.
7. This time when replication starts up the contents of the floating StoreOnce will be replicated
to the Data Center B6200 over the 10 GbE connection at the Data Center site and will take
several hours. In this example Remote Site A, B, C data will be replicated and seeded into
the B6200. When this replication step is complete, DELETE the replication mappings on the
floating StoreOnce, to isolate the data on the floating StoreOnce and then DELETE the actual
devices on the floating StoreOnce, so the device is ready for the next batch of remote sites.
8. Repeat steps 1-7 for the next series of remote sites until all the remote site data has been
seeded into the HP B6200 Backup System.
9. Finally set up the final replication mappings using our agreed naming convention decided in
Step 1. At the remote sites configure replication again to the Data Center site but be careful
to replicate to the correct target devices, by using the agreed naming convention at the data
center site e.g. TVTL1, TNASshare1 etc.
This time when we set up replication the B6200 at the target site presents a list of possible
target replication devices available to the Remote Site A. So, in this example, we would select
TVTL1 or TNASshare1 from the list of available targets presented to Remote Site A when we
are configuring the final replication mappings. This time when the replication starts almost all
102 Implementing replication with the HP B6200 Backup system