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

VLS Recovery Options for a Data Center Rebuild, Creating Archive Tapes from the Target

Page 188 highlights

Figure 83 VLS Recovery Options for a Data Center Rebuild . This target virtual library can be used to restore directly onto new servers that can then be shipped to the replacement site, or to copy the data to physical tape which can be shipped to the replacement site and used to rebuild the new servers there. To prepare for the restore process there are different scenarios depending on which backup application is used for the restore: • If you use a different backup application (not the instance that did the original backups on the source site), you must recreate the media database information from the replicated cartridges. • If this is a blank backup application just used for recovery, you can restore the replicated backup of the media database and then restore from the replicated cartridges that are fully synchronized. (The most recent backups in the media database may not have been fully replicated and thus may not be usable for restore.) • If this is a live backup application (for example, it is performing its own local backups in the target site), you can import the replicated cartridges into the existing backup application database. You can do this manually at the time of the disaster recovery, or you can use an automated import script (see Creating Archive Tapes from the Target) to keep the media database roughly in sync with the replication cartridges (less than 24 hours out of date in the event of a disaster recovery). • If you use the same backup application (the instance that did the original backups on the source site), you need to switch the backup application to "see" the target device instead of the source device. When you initially configuring this type of solution, you would have needed to ensure that the target device was not seen by the backup application. (You cannot have the backup application see two copies of the same cartridge at the same time; see Backup Application Interaction with 188 Virtual Library Systems

  • 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

Figure 83 VLS Recovery Options for a Data Center Rebuild
.
This target virtual library can be used to restore directly onto new servers that can then be shipped
to the replacement site, or to copy the data to physical tape which can be shipped to the replacement
site and used to rebuild the new servers there. To prepare for the restore process there are different
scenarios depending on which backup application is used for the restore:
If you use a different backup application (not the instance that did the original backups on the
source site), you must recreate the media database information from the replicated cartridges.
If this is a blank backup application just used for recovery, you can restore the replicated
backup of the media database and then restore from the replicated cartridges that are fully
synchronized. (The most recent backups in the media database may not have been fully rep-
licated and thus may not be usable for restore.)
If this is a live backup application (for example, it is performing its own local backups in the
target site), you can import the replicated cartridges into the existing backup application
database. You can do this manually at the time of the disaster recovery, or you can use an
automated import script (see
Creating Archive Tapes from the Target
) to keep the media
database roughly in sync with the replication cartridges (less than 24 hours out of date in the
event of a disaster recovery).
If you use the same backup application (the instance that did the original backups on the source
site), you need to switch the backup application to
see
the target device instead of the source
device. When you initially configuring this type of solution, you would have needed to ensure that
the target device was
not
seen by the backup application. (You cannot have the backup application
see two copies of the same cartridge at the same time; see
Backup Application Interaction with
Virtual Library Systems
188