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

VLS Automigration, Using D2D and VLS in ROBO/RDC/MDC Environments

Page 140 highlights

Figure 59 Using D2D and VLS in ROBO/RDC/MDC Environments . Recovery options: As with all replication solutions using D2D andVLS, under normal situation data is recoverable from local D2D or VLS. If retention period has expired it may be on physical tape at that site. In the event of a major disaster at a site then the replicated copy of data can be accessed in several ways: • At disaster recovery site using a separate backup application master server data can be recovered to new servers. • A replacement VLS and servers can be installed at the primary site and data can be reverse rep- licated from the disaster recovery site over the low bandwidth link, although this is not recommended for high volumes of data (TBs) because of the time to replicate data wholesale over a relatively small link speed. • Data can be copied to physical tape at the disaster recovery site then transported to the primary site and imported to new servers and arrays using physical tape at the primary site. Tape could also be copied to the VLS and then recovered from there. Solution advantages: • High Data availability solution, data always held in three locations and on tape • Total Solution under HP Data Protector control • Cost effective disaster recovery using low bandwidth links. Solution trade-offs: Some scripting of backup application is required to allow background imports of replicated cartridges to take place VLS Automigration In addition to copying virtual media to physical media via the backup application, another option is to use automigration to perform transparent tape migration. The automigration feature allows the VLS to act as a tape copy engine that transfers data from virtual cartridges on disk to a physical tape library connected to the VLS device. Echo copy is the supported VLS automigration scheme. 140 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 59 Using D2D and VLS in ROBO/RDC/MDC Environments
.
Recovery options
: As with all replication solutions using D2D andVLS, under normal situation data is
recoverable from local D2D or VLS. If retention period has expired it may be on physical tape at that
site. In the event of a major disaster at a site then the replicated copy of data can be accessed in
several ways:
At disaster recovery site using a separate backup application master server data can be recovered
to new servers.
A replacement VLS and servers can be installed at the primary site and data can be reverse rep-
licated from the disaster recovery site over the low bandwidth link, although this is not recommended
for high volumes of data (TBs) because of the time to replicate data wholesale over a relatively
small link speed.
Data can be copied to physical tape at the disaster recovery site then transported to the primary
site and imported to new servers and arrays using physical tape at the primary site. Tape could
also be copied to the VLS and then recovered from there.
Solution advantages
:
High Data availability solution, data always held in three locations and on tape
Total Solution under HP Data Protector control
Cost effective disaster recovery using low bandwidth links.
Solution trade-offs
: Some scripting of backup application is required to allow background imports of
replicated cartridges to take place
VLS Automigration
In addition to copying virtual media to physical media via the backup application, another option is
to use automigration to perform transparent tape migration. The automigration feature allows the VLS
to act as a tape copy engine that transfers data from virtual cartridges on disk to a physical tape
library connected to the VLS device. Echo copy is the supported VLS automigration scheme.
Virtual Library Systems
140