HP 12000 HP StorageWorks 12000 Gateway Virtual Library System User Guide (AH81 - Page 50

Tape Initialization, Accelerated deduplication ISV support matrix

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

Page 50 highlights

The following are two of many possible replication configurations: • Data center to data center Designate one VLS as the source and a second VLS as the destination. Configure the destination VLS to present a LAN/WAN replication target that is visible to the source VLS. The source VLS performs normal backups during the regular backup window, and during the availability window the source virtual cartridges automatically migrate to matching virtual cartridges on the destination VLS. The same configuration is also used in the other direction so there is a backup library and a LAN/WAN replication target library on both devices. • Branch office to a main data center Divide a single destination target into multiple slot ranges to allow a many-to-one configuration without needing a separate replication library for each branch office. In this way, the VLS replication can scale to hundreds of branch offices all replicating to a single large device. Replication can be configured to operate in one of two modes: • Deduplication-enabled replication - the virtual cartridge on the source VLS is deduplicated against the virtual cartridge on the target VLS. In this manner, only data that has changed is transmitted over the network to the target VLS. This mode requires that deduplication is licensed and enabled on both the source and the target VLS. • Whole cartridge replication - the entire virtual cartridge is copied from the source VLS to the target VLS. NOTE: All of the information on automigration also applies to replication except where specifically dealing with physical tapes (e.g., ejecting media) and where noted. Otherwise, where the information refers to physical cartridges, for replication assume virtual cartridges instead. NOTE: Replication is deduplication-enabled if you have purchased the appropriate replication and deduplication licenses, and your backup ISVs and data types are supported for deduplication. Check the Accelerated deduplication ISV support matrix at http://www.hp.com/go/ebs/ to see if your system supports deduplication. Tape Initialization When you first configure deduplication-enabled replication on your VLS and set up an echo copy pool to a LAN/WAN destination, the first round of data migration is not deduplicated because there is not yet a set of backups on the target VLS to deduplicate against. Because the first full set of backups can be very large, the VLS system includes a tape initialization process. You can transport the first full set of backups to the target VLS using physical tapes rather than the network. This tape initialization process is optional and must be enabled by the administrator when creating the echo copy pool. The tape initialization process works, very generally, like this: 1. Set up the LAN/WAN replication target on the remote site 2. Set up an echo copy pool on the source site 3. Run a standard deduplication backup on the source site 4. Export the full backup to physical tapes 50 Automigration/Replication

  • 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
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
The following are two of many possible replication configurations:
•
Data center to data center
Designate one VLS as the source and a second VLS as the destination. Configure the destination
VLS to present a LAN/WAN replication target that is visible to the source VLS. The source VLS
performs normal backups during the regular backup window, and during the availability window
the source virtual cartridges automatically migrate to matching virtual cartridges on the destination
VLS. The same configuration is also used in the other direction so there is a backup library and a
LAN/WAN replication target library on both devices.
•
Branch office to a main data center
Divide a single destination target into multiple slot ranges to allow a many-to-one configuration
without needing a separate replication library for each branch office. In this way, the VLS replic-
ation can scale to hundreds of branch offices all replicating to a single large device.
Replication can be configured to operate in one of two modes:
•
Deduplication-enabled replication
—
the virtual cartridge on the source VLS is deduplicated against
the virtual cartridge on the target VLS. In this manner, only data that has changed is transmitted
over the network to the target VLS. This mode requires that deduplication is licensed and enabled
on both the source and the target VLS.
•
Whole cartridge replication
—
the entire virtual cartridge is copied from the source VLS to the
target VLS.
NOTE:
All of the information on automigration also applies to replication except where specifically dealing
with physical tapes (e.g., ejecting media) and where noted. Otherwise, where the information refers
to physical cartridges, for replication assume virtual cartridges instead.
NOTE:
Replication is deduplication-enabled if you have purchased the appropriate replication and
deduplication licenses, and your backup ISVs and data types are supported for deduplication. Check
the
Accelerated deduplication ISV support matrix
at
h
t
tp://w
w
w
.hp
.co
m/g
o/e
b
s/
to see if your
system supports deduplication.
Tape Initialization
When you first configure deduplication-enabled replication on your VLS and set up an echo copy
pool to a LAN/WAN destination, the first round of data migration is not deduplicated because there
is not yet a set of backups on the target VLS to deduplicate against. Because the first full set of backups
can be very large, the VLS system includes a tape initialization process. You can transport the first
full set of backups to the target VLS using physical tapes rather than the network. This tape initialization
process is optional and must be enabled by the administrator when creating the echo copy pool.
The tape initialization process works, very generally, like this:
1.
Set up the LAN/WAN replication target on the remote site
2.
Set up an echo copy pool on the source site
3.
Run a standard deduplication backup on the source site
4.
Export the full backup to physical tapes
Automigration/Replication
50