HP StorageWorks MSA2012i HP StorageWorks 2000 Modular Smart Array Reference Gu - Page 121

Using Volume-Copy Services, Additional Data Protection, Non-disruptive Use of Production Data

Page 121 highlights

Volume Type Field Description Snap Data - The total amount of data associated with the specific snapshot (data copied from a master volume to a snapshot and data written directly to a snapshot). Unique Data - The amount of data that has been written to the snapshot since the last snapshot was taken. If the snapshot has not been written or is deleted, this field will show a value of 0. Shared Data - The amount of data that is potentially shared with other snapshots and associated amount of space that is guaranteed to be freed if the snapshot is deleted. This represents the amount of data written directly to the snapshot. It also includes data copied from the master volume to the snap pool for the oldest snapshot, since that snapshot does not share data with any other snapshot. For a snapshot that is not the oldest, if the modified data is deleted or if it had never been written to, this field will show a value of 0. Using Volume-Copy Services While a snapshot is a point-in-time logical copy of a volume, the volume-copy service creates a complete, physical and independent copy of a volume within a storage system. It is an exact copy of a master or a snapshot volume as it existed at the time the action was initiated, consumes the same amount of space as the source volume, and is independent from an I/O perspective. Volume independence is a key distinction of a volume copy (versus snapshot, which is a logical copy and dependent on the source volume). Benefits include: ■ Additional Data Protection - An independent copy of a volume (versus logical copy through snapshot) provides additional data protection against a complete master volume failure. If the source master volume fails, the volume copy can be used to restore the volume to the point in time the volume copy was taken. ■ Non-disruptive Use of Production Data - With an independent copy of the volume, resource contention and the potential performance impact on production volumes is mitigated. Data blocks between the source and the copied volumes are independent (versus shared with snapshot) so that I/O is to each set of blocks respectively; application I/O transactions are not competing with each other when accessing the same data blocks. Chapter 3 Managing Storage 121

  • 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
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

Chapter 3
Managing Storage
121
Using Volume-Copy Services
While a snapshot is a point-in-time logical copy of a volume, the volume-copy
service creates a complete, physical and independent copy of a volume within a
storage system. It is an exact copy of a master or a snapshot volume as it existed at
the time the action was initiated, consumes the same amount of space as the source
volume, and is independent from an I/O perspective. Volume independence is a key
distinction of a volume copy (versus snapshot, which is a logical copy and
dependent on the source volume). Benefits include:
Additional Data Protection
– An independent copy of a volume (versus logical
copy through snapshot) provides additional data protection against a complete
master volume failure. If the source master volume fails, the volume copy can be
used to restore the volume to the point in time the volume copy was taken.
Non-disruptive Use of Production Data
– With an independent copy of the
volume, resource contention and the potential performance impact on production
volumes is mitigated. Data blocks between the source and the copied volumes are
independent (versus shared with snapshot) so that I/O is to each set of blocks
respectively; application I/O transactions are not competing with each other when
accessing the same data blocks.
Snap Data – The total amount of data associated with
the specific snapshot (data copied from a master
volume to a snapshot and data written directly to a
snapshot).
Unique Data – The amount of data that has been
written to the snapshot since the last snapshot was
taken. If the snapshot has not been written or is
deleted, this field will show a value of 0.
Shared Data – The amount of data that is potentially
shared with other snapshots and associated amount of
space that is guaranteed to be freed if the snapshot is
deleted. This represents the amount of data written
directly to the snapshot. It also includes data copied
from the master volume to the snap pool for the oldest
snapshot, since that snapshot does not share data with
any other snapshot. For a snapshot that is not the
oldest, if the modified data is deleted or if it had never
been written to, this field will show a value of 0.
Volume Type
Field
Description