HP P4000 9.0 HP StorageWorks P4000 SAN Solution User Guide - Page 214

Single snapshots versus scheduled snapshots, Guide for snapshots, Planning snapshots - application aware snapshot manager

Page 214 highlights

Best practice: Use SmartClone volumes. See Chapter 14 on page 233 . Single snapshots versus scheduled snapshots Some snapshot scenarios call for creating a single snapshot and then deleting it when it is no longer needed. Other scenarios call for creating a series of snapshots up to a specified number or for a specified time period, after which the earliest snapshot is deleted when the new one is created (snapshots created from a schedule). For example, you plan to keep a series of daily snapshots for one week, up to five snapshots. After creating the sixth snapshot, the earliest snapshot is deleted, thereby keeping the number of snapshots on the volume at five. Guide for snapshots Review Chapter 12 on page 205 to ensure that you configure snapshots correctly. When creating a snapshot, you define the following characteristics or options. Table 47 Snapshot characteristics Snapshot Parameter What it means Application-Managed Snapshot This option quiesces VSS-aware applications on the server before SAN/iQ creates the snapshot. This option requires the use of the VSS Provider. For more information, see "Requirements for application-managed snapshots" on page 216. If the VSS Provider is not installed, SAN/iQ will let you create a point-in-time snapshot (not using VSS). Snapshot Name The name of the snapshot that is displayed in the CMC. A snapshot name must be from 1 to 127 characters and is case sensitive. Snapshots have a default naming convention enabled when the CMC is installed. You can change or disable this naming convention. See "Setting naming conventions" on page 30 for information about this naming convention. The following are illegal characters Description (Optional) A description of the snapshot. Assign and Unassign Servers (Optional) Configure server access to the snapshot. Planning snapshots When planning to use snapshots, consider their purpose and size. If you are planning to use schedules to snapshot a volume, see "Storage systems and cluster capacity" on page 180 and Table 48 on page 214 for approximate data change rates for some common applications. Table 48 Common applications' daily change rates Application Daily Change Rates Fileshare Email/Exchange Database 1 - 3% 10 - 20% 10% 214 Using snapshots

  • 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
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350

Best practice:
Use SmartClone volumes. See
Chapter 14
on page 233 .
Single snapshots versus scheduled snapshots
Some snapshot scenarios call for creating a single snapshot and then deleting it when it is no longer
needed. Other scenarios call for creating a series of snapshots up to a specified number or for a
specified time period, after which the earliest snapshot is deleted when the new one is created
(snapshots created from a schedule).
For example, you plan to keep a series of daily snapshots for one week, up to five snapshots. After
creating the sixth snapshot, the earliest snapshot is deleted, thereby keeping the number of snapshots
on the volume at five.
Guide for snapshots
Review
Chapter 12
on page 205 to ensure that you configure snapshots correctly. When creating a
snapshot, you define the following characteristics or options.
Table 47 Snapshot characteristics
What it means
Snapshot Parameter
This option quiesces VSS-aware applications on the server before SAN/iQ creates
the snapshot. This option requires the use of the VSS Provider. For more inform-
ation, see
Requirements for application-managed snapshots
on page 216. If
the VSS Provider is not installed, SAN/iQ will let you create a point-in-time
snapshot (not using VSS).
Application-Managed
Snapshot
The name of the snapshot that is displayed in the CMC. A snapshot name must
be from 1 to 127 characters and is case sensitive. Snapshots have a default
naming convention enabled when the CMC is installed. You can change or
disable this naming convention. See
Setting naming conventions
on page 30
for information about this naming convention. The following are illegal characters:
,'
; : =.
Snapshot Name
(Optional) A description of the snapshot.
Description
(Optional) Configure server access to the snapshot.
Assign and Unassign Serv-
ers
Planning snapshots
When planning to use snapshots, consider their purpose and size. If you are planning to use schedules
to snapshot a volume, see
Storage systems and cluster capacity
on page 180 and
Table 48
on page
214 for approximate data change rates for some common applications.
Table 48 Common applications
daily change rates
Daily Change Rates
Application
1 - 3%
Fileshare
10 - 20%
Email/Exchange
10%
Database
Using snapshots
214