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

Creating Archive Tapes from the Target, Recovery Options, Physical Tape

Page 99 highlights

Figure 39 Recovery Options - Physical Tape . Creating Archive Tapes from the Target Even with replication removing the need for physical tape offsite, there are still many users who wish to use physical tape for archive or test recoveries, etc. An archive tape will have the following differences from the original backup: • A different retention time from the original backup (for example, you may keep backups and offsite replicas for three months but keep tape archive for several years). • Different cartridge contents because it will be a different size (optimum virtual cartridge size for deduplication is 50-100 GB but physical tapes such as LTO-4 are 800 GB). • A different barcode and be tracked separately in the backup application. These characteristics mean that the backup application must control the creation of the archive tape and must use an object-copy based system (cannot use a whole-tape copy system). This is easy if the physical library is on the source site because you can use the normal backup application object-copy mechanisms to simply copy from the source virtual library to the physical library via the backup application media servers. However, if the physical library is at the target site and you want to perform the tape archive from the replicated virtual cartridges in the target device, this requires additional steps. This is because the backup application at the target device that sees the replicated virtual cartridges cannot be the same backup application that performed the backups at the source site (see Backup Application Interaction with Replication). The target site backup application does not have any information about the replicated cartridges in its media database because it did not back up to those tapes. HP StorageWorks VLS and D2D Solutions Guide 99

  • 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 39 Recovery Options
Physical Tape
.
Creating Archive Tapes from the Target
Even with replication removing the need for physical tape offsite, there are still many users who wish
to use physical tape for archive or test recoveries, etc. An archive tape will have the following
differences from the original backup:
A different retention time from the original backup (for example, you may keep backups and offsite
replicas for three months but keep tape archive for several years).
Different cartridge contents because it will be a different size (optimum virtual cartridge size for
deduplication is 50-100 GB but physical tapes such as LTO-4 are 800 GB).
A different barcode and be tracked separately in the backup application.
These characteristics mean that the backup application must control the creation of the archive tape
and must use an object-copy based system (cannot use a whole-tape copy system). This is easy if the
physical library is on the source site because you can use the normal backup application object-copy
mechanisms to simply copy from the source virtual library to the physical library via the backup
application media servers. However, if the physical library is at the target site and you want to perform
the tape archive from the replicated virtual cartridges in the target device, this requires additional
steps. This is because the backup application at the target device that sees the replicated virtual
cartridges cannot be the same backup application that performed the backups at the source site (see
Backup Application Interaction with Replication
). The target site backup application does not have
any information about the replicated cartridges in its media database because it did not back up to
those tapes.
HP StorageWorks VLS and D2D Solutions Guide
99