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

Benefits of Single Library Systems, Backup to VLS in a Simple Deployment VLS9000

Page 34 highlights

Figure 11 Backup to VLS in a Simple Deployment (VLS9000-series with One Shared Library Shown) . Benefits of Single Library Systems • This use model is easy to manage. • It is easy to copy through the backup application because you already have shared devices and they all see and are seen by a copy engine or server. • Some configuration tasks are easier; you don't, for example, have to worry about assigning spe- cific jobs to specific libraries. • You don't have to worry about performance tuning. If, for example, you have enough bandwidth for ten backup streams, you configure ten drives and let the device load balance automatically. The backup application decides how to allocate; you don't have to specify. • Multiple hosts are mixed together in one media set. When you copy to tape, you're using less media. • With the VLS9000 or VLS Gateway, you can consolidate your storage system to use only one large VLS (greater than 500 usable TB) instead of multiple smaller appliances. If you use Data Protector, licensing is relatively economical - media servers do not require individual licenses, object copy doesn't require additional licensing, and virtual tape is licensed per TB. Setup is largely automated and does not require manual intervention. Considerations for Single Library Systems • Not all backup applications are well-suited to this setup. This depends (at least in part) on the application's licensing schemes. If you have to purchase shared drive licenses, this model may be more expensive than a dedicated setup. • Setup can be challenging in some applications. You may have to configure paths to the tape drives from all the backup hosts. The backup application may do some of this automatically, but this, in itself, can be time consuming. And if you change the configuration, you may have to repeat some management steps and do some re-configuration. 34 Backup Solution Design Considerations

  • 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 11 Backup to VLS in a Simple Deployment (VLS9000
series with One Shared Library Shown)
.
Benefits of Single Library Systems
This use model is easy to manage.
It is easy to copy through the backup application because you already have shared devices and
they all see and are seen by a copy engine or server.
Some configuration tasks are easier; you don
t, for example, have to worry about assigning spe-
cific jobs to specific libraries.
You don
t have to worry about performance tuning. If, for example, you have enough bandwidth
for ten backup streams, you configure ten drives and let the device load balance automatically.
The backup application decides how to allocate; you don
t have to specify.
Multiple hosts are mixed together in one media set. When you copy to tape, you
re using less
media.
With the VLS9000 or VLS Gateway, you can consolidate your storage system to use only one
large VLS (greater than 500 usable TB) instead of multiple smaller appliances.
If you use Data Protector, licensing is relatively economical
media servers do not require individual
licenses, object copy doesn
t require additional licensing, and virtual tape is licensed per TB. Setup
is largely automated and does not require manual intervention.
Considerations for Single Library Systems
Not all backup applications are well-suited to this setup. This depends (at least in part) on the
application
s licensing schemes. If you have to purchase shared drive licenses, this model may be
more expensive than a dedicated setup.
Setup can be challenging in some applications. You may have to configure paths to the tape
drives from all the backup hosts. The backup application may do some of this automatically, but
this, in itself, can be time consuming. And if you change the configuration, you may have to repeat
some management steps and do some re-configuration.
Backup Solution Design Considerations
34