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

DB:1 FS &amp, VLS Sizing Example 4

Page 186 highlights

Data types (3 DB:1 FS) & backup type Full size in GB Replicated data (compressed) in GB Database (Full) 1% change 50000 660 File Data (incremental 10%)* 16666 99 Database (Full) 1% change 200000 2640 File Data (incremental 10%)* 66666 3960 * Fulls on the weekend. Time available to replication/time to replicate Link speed available or required in Mbit/sec Combined link speed 9.5 hours 3.3 hours Assume fixed dedicated link speed of 400 Mbit/sec Assume fixed dedicated link speed of 400 Mbit/sec 24 hours 444 at 100% 666 at 100% At greater than 1 Gb/sec+ at high volumes add extra link bandwidth for catch-up 4. Sizing Scenario: Many-to-one (4:1) replication. Figure 82 VLS Sizing Example 4 . Here are four remote sites replicating 2 TB and 10 TB backups daily into a central VLS9000. The best approach in a many-to-one scenario is: • Size each of the individual links separately. • Ensure the links at the target at least match the total remote size replication capacity (in this example 300 Mbits/sec). • If possible, allow 25% extra capacity for "catch up" in the event of a backlog or paused replications should a link go down. 186 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

Combined
link speed
Link speed
available or
required in
Mbit/sec
Time avail-
able to replic-
ation/time to
replicate
Replicated
data (com-
pressed) in
GB
Full size in GB
Data types (3
DB:1 FS) &
backup type
Assume fixed
dedicated link
speed of 400
Mbit/sec
Assume fixed
dedicated link
speed of 400
Mbit/sec
9.5 hours
660
50000
Database (Full)
1% change
3.3 hours
99
16666
File Data (incre-
mental 10%)*
At greater than
1 Gb/sec+ at
high volumes
add extra link
bandwidth for
catch-up
444 at 100%
24 hours
2640
200000
Database (Full)
1% change
666 at 100%
3960
66666
File Data (incre-
mental 10%)*
* Fulls on the weekend.
4.
Sizing Scenario: Many-to-one (4:1) replication.
Figure 82 VLS Sizing Example 4
.
Here are four remote sites replicating 2 TB and 10 TB backups daily into a central VLS9000.
The best approach in a many-to-one scenario is:
Size each of the individual links separately.
Ensure the links at the target at least match the total remote size replication capacity (in this example
300 Mbits/sec).
If possible, allow 25% extra capacity for
catch up
in the event of a backlog or paused replications
should a link go down.
Virtual Library Systems
186