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

Restore the VLS over the LAN/WAN, Replication,

Page 189 highlights

Replication). One option would be to use the LUN Mapping feature in the VLS to hide the target virtual library from the backup application. But in the event of a disaster recovery, you can perform the sequence shown in Figure 84. (The most recent backups in the media database may not have been fully replicated and thus may not be usable for restore.) Figure 84 Data Recovery from the Target VLS . 1. The source VLS becomes inaccessible to the remote VLS and to the backup host. 2. The source tape library and drive are deleted from the backup host (cartridge media pools remain). 3. The target VLS is enabled using the VLS LUN mapping feature in the GUI. 4. The backup application server configures the target library and tape drives and performs a bar- code scan. 5. The backup application recognizes data cartridges within the new library. 6. Data is restored using target cartridges (unknown to the backup application) where the most recent backup is forward referenced. Restore the VLS over the LAN/WAN Another method of recovery is to restore the backups over the WAN/LAN from the target device back to a rebuilt source device. The restore over WAN/LAN can be initiated from the source device in the "Restore Media" task in LAN/WAN destination library slots, where you can then select which target cartridges you want to restore back to their matching cartridges on the source device. The LAN/WAN restore is a whole cartridge non-deduplicated copy so the entire contents of the cartridge are read back over the LAN/WAN, and the resulting restored cartridges on the source device will never deduplicate against any other cartridges on the device (until they are recycled and then overwritten with new backups). Given this, you would be limited by the bandwidth of the replication link in terms of how much data can be restored, and so generally you would restore the HP StorageWorks VLS and D2D Solutions Guide 189

  • 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
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218

Replication
). One option would be to use the LUN Mapping feature in the VLS to hide the target
virtual library from the backup application. But in the event of a disaster recovery, you can perform
the sequence shown in
Figure 84
. (The most recent backups in the media database may not have
been fully replicated and thus may not be usable for restore.)
Figure 84 Data Recovery from the Target VLS
.
1.
The source VLS becomes inaccessible to the remote VLS and to the backup host.
2.
The source tape library and drive are deleted from the backup host (cartridge media pools remain).
3.
The target VLS is enabled using the VLS LUN mapping feature in the GUI.
4.
The backup application server configures the target library and tape drives and performs a bar-
code scan.
5.
The backup application recognizes data cartridges within the new library.
6.
Data is restored using target cartridges (unknown to the backup application) where the most recent
backup is forward referenced.
Restore the VLS over the LAN/WAN
Another method of recovery is to restore the backups over the WAN/LAN from the target device back
to a rebuilt source device. The restore over WAN/LAN can be initiated from the source device in the
Restore Media
task in LAN/WAN destination library slots, where you can then select which target
cartridges you want to restore back to their matching cartridges on the source device.
The LAN/WAN restore is a whole cartridge non-deduplicated copy so the entire contents of the
cartridge are read back over the LAN/WAN, and the resulting restored cartridges on the source
device will never deduplicate against any other cartridges on the device (until they are recycled and
then overwritten with new backups). Given this, you would be limited by the bandwidth of the
replication link in terms of how much data can be restored, and so generally you would restore the
HP StorageWorks VLS and D2D Solutions Guide
189