HP D2D D2D Best Practices for VTL, NAS and Replication implementations (EH985- - Page 118

Step 3, Recover Data to new VTL /Share, Step 4, Reconnect to backup host and tidy up

Get HP D2D PDF manuals and user guides View all HP D2D manuals
Add to My Manuals
Save this manual to your list of manuals

Page 118 highlights

3 Step 3 - Recover Data to new VTL /Share 1. Run the replication recovery wizard on the original D2D appliance, this will reverse replicate the data from the replication target device back to the new source device. 2. Wait for replication to synchronize the devices. 3. Remove the replication mapping from either the source or target D2D Web Management Interface. The new device on the original appliance now contains the same data as the old device did but will benefit from the improved performance Step 4 - Reconnect to backup host and tidy up 1. Delete the target you created D2D device on D2D-B―Connect‖ the backup media server to the new device on D2D-A e.g: - Mount the NFS share - Discover the iSCSI VTL device and connect - Zone the FC SAN so that the host can access the new VTL 2. If using VTL it may be necessary to delete the existing backup application presentation of the VTL and discover the new device within the backup application. This is because the WWN and serial number of the new library may be different to the original. If using NAS and, if the share name is the same as previously used, the backup application should need no re-configuration to use the new share. 3. If using VTL scan/inventory the new device so that it can update its database with the location of the cartridges within the library. The virtual barcodes will be the same as the original cartridges so there is no need to import the cartridge data. 118

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
118
Step 3
–
Recover Data to new VTL /Share
1.
Run the replication recovery wizard on the original D2D appliance, this will reverse replicate the data from
the replication target device back to the new source device.
2.
Wait for replication to synchronize the devices.
3.
Remove the replication mapping from either the source or target D2D Web Management Interface. The new
device on the original appliance now contains the same data as the old device did but will benefit from the
improved performance
Step 4
–
Reconnect to backup host and tidy up
1.
Delete the target you created D2D device on D2D-
B―Connect‖ the backup media server to the new device
on
D2D-A e.g:
–
Mount the NFS share
–
Discover the iSCSI VTL device and connect
–
Zone the FC SAN so that the host can access the new VTL
2.
If using VTL it may be necessary to delete the existing backup application presentation of the VTL and
discover the new device within the backup application. This is because the WWN and serial number of the
new library may be different to the original.
If using NAS and, if the share name is the same as previously used, the backup application should need no
re-configuration to use the new share.
3.
If using VTL scan/inventory the new device so that it can update its database with the location of the
cartridges within the library. The virtual barcodes will be the same as the original cartridges so there is no
need to import the cartridge data.
3