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

Replication Deployment Options - virtual library system price

Page 26 highlights

that allows duplicate data to be detected and stored only once on the HP VLS or D2D system also allows only the unique data to replicate between sites. Because the volume of data being replicated between sites is much less than if the full data set was replicated, you can use lower bandwidth links at correspondingly lower price points. In addition, backup at remote offices can be automated to a local virtual tape library and then replicated back to a regional data center or primary data center allowing end-to-end management from the data center of all data in the remote offices. This transformation is shown in Table 5 which compares the amount of data to transfer both with and without deduplication. The amount of data to back up in this example is 1 TB. Table 5 Estimated Time to Replicate Data for a 1 TB Backup Environment at 2:1 Link Type Data Sent T1 T3 OC12 Link Rate (66% efficient) 1.5 Mb/s Backup Type Without deduplication Incremental 50 GB 4.5 days Full 500 GB 45.4 days Change Rate With deduplication 0.5% 13.1 GB 29 hours 1.0% 16.3 GB 35 hours 2.0% 22.5 GB 49 hours 44.7 Mb/s 3.8 hours 1.6 days 59 minutes 73 minutes 102 minutes 622.1 Mb/s 16 minutes 2.7 hours 4.3 minutes 5.3 minutes 7.3 minutes NOTE: T1/T3 and OC12 are old terms with respect to WAN link terminology. Many link providers use their own names (e.g., IP Clear, Etherflow). This document distinguishes them by their speed using 2 Mbits/sec, 50 Mbits/sec, etc. One consideration with replication is that you must "initialize" the Virtual Tape Libraries with data prior to starting the replication. This ensures that the source and target devices are both synchronized with the relevant reference data to allow them to interpret the changed data (deltas) that comes across the WAN link during replication. Replication Deployment Options You can deploy the HP VLS and D2D systems for replication in many ways depending on your requirements. You should understand the terminology associated with deduplication and replication. The key terminology for replication deployment: • Source: A series of slots/cartridges in a virtual library that act as the source data to replicate. This is the original copy of the backup data, written to and managed by the source site's backup application. • Target or LAN/WAN destination: A series of corresponding slots in another virtual library on another site in another location which receives data from the source library. This is the secondary (disaster recovery) copy of the backup data, managed by the replication system. 26 Concepts

  • 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

that allows duplicate data to be detected and stored only once on the HP VLS or D2D system also
allows only the unique data to replicate between sites. Because the volume of data being replicated
between sites is much less than if the full data set was replicated, you can use lower bandwidth links
at correspondingly lower price points. In addition, backup at remote offices can be automated to a
local virtual tape library and then replicated back to a regional data center or primary data center
allowing end-to-end management from the data center of all data in the remote offices.
This transformation is shown in
Table 5
which compares the amount of data to transfer both with and
without deduplication. The amount of data to back up in this example is 1 TB.
Table 5 Estimated Time to Replicate Data for a 1 TB Backup Environment at 2:1
Link Type
OC12
T3
T1
Data Sent
622.1 Mb/s
44.7 Mb/s
1.5 Mb/s
Link Rate (66% efficient)
Without deduplication
Backup Type
16 minutes
3.8 hours
4.5 days
50 GB
Incremental
2.7 hours
1.6 days
45.4 days
500 GB
Full
With deduplication
Change Rate
4.3 minutes
59 minutes
29 hours
13.1 GB
0.5%
5.3 minutes
73 minutes
35 hours
16.3 GB
1.0%
7.3 minutes
102 minutes
49 hours
22.5 GB
2.0%
NOTE:
T1/T3 and OC12 are old terms with respect to WAN link terminology. Many link providers use their
own names (e.g., IP Clear, Etherflow). This document distinguishes them by their speed using 2
Mbits/sec, 50 Mbits/sec, etc.
One consideration with replication is that you must
initialize
the Virtual Tape Libraries with data
prior to starting the replication. This ensures that the source and target devices are both synchronized
with the relevant reference data to allow them to interpret the changed data (deltas) that comes across
the WAN link during replication.
Replication Deployment Options
You can deploy the HP VLS and D2D systems for replication in many ways depending on your
requirements. You should understand the terminology associated with deduplication and replication.
The key terminology for replication deployment:
Source: A series of slots/cartridges in a virtual library that act as the source data to replicate. This
is the original copy of the backup data, written to and managed by the source site
s backup ap-
plication.
Target or LAN/WAN destination: A series of corresponding slots in another virtual library on
another site in another location which receives data from the source library. This is the secondary
(disaster recovery) copy of the backup data, managed by the replication system.
Concepts
26