HP StorageWorks 6000 HP StorageWorks VLS and D2D Solutions Guide (AG306-96028, - Page 172
Implementing the Initialization Process, Physical Tape Initialization
![]() |
View all HP StorageWorks 6000 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 172 highlights
5. Run the first full backup (to replicating media in the source echo copy pool). Only backups performed after the echo copy pool is created will be replicated. Any previous existing backups will not be replicated until their cartridges expire in the backup application and are overwritten by new backups. For any backups that you want to replicate, you must ensure your backup application is configured to use the virtual cartridge media in the source device's echo copy pool. Any backups that go to virtual cartridges on the source device that are not in an echo copy pool will not be replicated. 6. Trigger the tape initialization (if tape initialization selected, then trigger after first full backup). If you selected "Initialize via Tape Transport" when creating the echo copy pool, after the first backup to the source device has successfully completed you must trigger the tape initialization process. (See Implementing the Initialization Process). After tape initialization is complete, subsequent replication jobs will transfer over the LAN/WAN. 7. Subsequent backups occur. 8. Run new backups and replicate (over the LAN/WAN to the target device). Replication takes place when the source start and duration and target start and duration windows are aligned and there is a subsequent backup to the source cartridges in the echo copy pool. See Advanced Replication Job Control for design consideration around having different priority jobs on the source device and having job throttling on the target device. Implementing the Initialization Process Before replication can take place, the reference data (the first full backup cycle performed with deduplication and replication enabled) needs to be sent to the target. This initial reference copy of the data is large; if the WAN/LAN replication link was sized around the daily deduplicated data to be transferred it could take a significant amount of time to transfer the reference copy (weeks or months). Once the source tape references are transferred to the target (initialized), the daily deduplication/replication can commence over the WAN/LAN link. There are several options for initialization of the reference data: • Physical tape initialization • WAN initialization • Co-location initialization You must decide whether to use the tape initialization process when initially configuring the VLS replication (when creating the echo copy pool). If tape initialization is not selected, WAN or co-location initialization will be performed over LAN/WAN. Physical Tape Initialization Because in enterprise backup environments the initial backups can be quite large (many TB), in most cases it will be impractical to perform tape transfers using the low bandwidth link (because it would take weeks to replicate the first backup). Tape transfer via co-location at a site might also be impractical because of the size and space requirements of the VLS units and inter-site shipment logistics, or because both devices are always busy (e.g., using active-active or many-to-one deployments). The most popular method for initialization on VLS systems is via physical tape transfer as shown in the following diagram: 172 Virtual Library Systems
![](/manual_guide/products/hewlettpackard-storageworks-12000-hp-storageworks-vls-d2d-solutions-guide-ag30696028-2010-6a6d5af/172.png)