For more information on this topic, please see the DR Series System Administration 4.0 Web-based Training
NOTE: If you choose to use this alternate workaround method, you must set up a new data storage unit in the DMA, and import the images before a restore to the original location can occur.
To leverage this type of deduplication across the WAN, complete the following:
1. Make sure that the replication operation has completed (between source and target).
2. Delete the current replication relationship, and re-create a replication relationship (reversing the source and target roles).
3. Restore data to the original source container (now the target).
4. Make sure that the replication operation has completed.
5. Delete the replication relationship and re-create a replication relationship (restoring original source and target destinations).
Under this scenario, a fraction of the data to be recovered is sent across the WAN link. This could speed up a remote restore significantly. However, there are some downsides to this type of scenario:
• If step 1 is not followed correctly, any changes not fully replicated are lost.
• During steps 2 and 3, any data that is written to the original DR Series system source container may be lost.
• During step 4, if the data is not fully replicated back before the switch is made, it may be lost.
Alternatively, you could still support this type of effort by completing the following:
1. Create a new container on the target DR Series system.
2. Set up replication from this container back to the source DR Series system container.
3. Set up a new disk storage unit in the DMA and make sure that the DMA is aware of any new images.
4. Import the old images back into the DMA from the target DR Series system (the original source location).
5. Use a new disk storage unit in the DMA, and then restore the data back to the original client.