HP StorageWorks 6000 HP StorageWorks VLS and D2D Solutions Guide (AG306-96028, - Page 165

are required for more than 10 sources). In the active-active deployment, you would install one license per node in both the source and target devices (for all nodes in those devices). Replication Preparation Prior to configuring replication, ensure that deduplication is licensed and enabled on both the source and target devices and enter the replication licenses on the target device. Create the required virtual libraries on the source and target devices. You also need to create the required virtual libraries and virtual tape drives on source and target VLS devices. With VLS, the virtual libraries/drives on both source and target device are created as normal (the replication configuration is overlaid onto these standard virtual libraries by creating replication targets, LAN/WAN destination libraries, echo copy pools, etc.). If your source device's backup application has media agents in the target site then when mapping the replication library to the front-end Fibre Channel ports in the VLS, remember to hide the target virtual library from the source backup application (e.g., assign it to dedicated front-end Fibre Channel ports that you can zone away from the source backup application agents). Best practices include creating more library slots than initially needed in the source and target virtual libraries to provide room for future growth. NOTE: On a VLS6200 that is acting as a target device, you must enable compression when creating the virtual tape drives in the target virtual library (because all the replicated cartridges on the target device will be software compressed and you will not be able to read these tapes via the target virtual library unless it has compressed tape drives). If the source device is also a VLS6200, this should have software compression disabled on the source virtual library tape drives because deduplication performance will be significantly degraded if software compressed drives are used for backups. After creating the virtual libraries, create the virtual cartridges. If starting from a blank state on both source and target devices, you only need to create virtual cartridges in the replication target library. The matching cartridges are automatically created in the source virtual library when the echo copy pool is created. However, if you are starting with an existing source device that already has a virtual library containing virtual cartridges with backup data, in order to retain the existing backup data you must use the following process to prepare for replication: • Create a virtual library on the target device with enough slots to hold the number of current source device cartridges that you want to replicate (plus additional slots for future growth). • Manually create matching virtual cartridges (with the same barcodes, cartridge sizes, and cartridge type) in the target virtual library that match the source device cartridges that you want to replicate. • When you create the echo copy pool on the source device, this automatically links the matching cartridges on the source and target. NOTE: Only backups performed after replication is configured will be replicated. Backups that were performed before replication configuration will not be replicated until the tapes are overwritten by the backup application (for example, after the retention time for the older backups the virtual cartridges will be recycled and reused for new backups which will then replicate). You must also prepare the TCP/IP network connection between the source and target devices. In VLS devices, the node0 will already have a TCP/IP address assigned to its external Gbit LAN connection to allow device management (GUI, CLI, etc.) and this existing connection is also used for node0 HP StorageWorks VLS and D2D Solutions Guide 165