Filter
Top Products
121
Replication device self replication migration
HP
ProLiant
DL320s
UID
1
2
Original File Share
Original VTL
D2D A
New VTL
New File Share
HP
ProLiant
DL320s
UID
1
2
Replicated File Share
Replicated VTL
D2D B
1
2
3
Existing Replication Mapping
Self Replication
1
Step 1 – Break Existing Replication Mapping
2
Step 2 – Replicate to new VTL/Share on same D2D
3
Step 3 – Create new Replication Mapping
New VTL
New File Share
New Replication Mapping
2 2 2
Use this model if migrating devices that are already in a replication mapping of their own. Both the source and
target libraries/shares should be migrated to new devices.
Bear in mind that during this process the original replication mapping will be broken and therefore any backups
to the source device will not be replicated until the mapping is re-established.
Step 1 – Break existing replication mapping
1. Ensure that the existing replication mapping is synchronized. If a replication target library is hosting
replication mappings from multiple source devices then all replication mappings to the target will need to be
broken, so all mappings must be considered.
2. Remove the replication mappings between the source(s) and target device. Both the source and target devices
are now non-replicating shares/libraries.
3. Create new VTL or share devices on both the original source and original target D2D systems; these will
become the replacement devices for the migrated data with improved performance. It is not possible to use
the same Share or Library names as the original or use the same WWN/Serial numbers for VTL devices.
Step 2 – Self replicate to new VTL/Share on the same D2D Backup System
1. Add a new replication target device to both appliances by providing the D2D Backup Systems’ own IP
addresses or FQDNs.
2. Configure new replication mappings using the Replication Wizard on the D2D Backup Systems to allow
replication of all data from the source device to the new target device.
See the HP StoreOnce Backup System user guide for detailed steps to create a replication mapping for NAS
or VTL.
3. Allow replication to synchronize the two devices on both D2D Backup Systems.
4. Stop any backup jobs from running to the source device so that both source and target now remain identical.
1
2