HP StoreVirtual 4000 9.0 HP StorageWorks P4000 SAN Solution User Guide - Page 216

Requirements for application-managed snapshots, Understanding snapshots for volume sets

Page 216 highlights

3. If you want to use VSS to quiesce the application before creating the snapshot, select the Application-Managed Snapshot check box. 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). This option quiesces VSS-aware applications on the server before SAN/iQ creates the snapshot. The system fills in the Description field and disables the Servers field automatically. You can assign servers after the snapshot is created. 4. Type a name for the snapshot, or accept the default. 5. (Optional) Enter a description of the snapshot. 6. (Optional) Assign a server to the snapshot. 7. Click OK when you are finished. NOTE: In the navigation window, snapshots are listed below the volume in descending date order, from newest to oldest. Requirements for application-managed snapshots You can create application-managed snapshots for both single and scheduled snapshots. Application-managed snapshots use the VSS Provider to quiesce VSS-aware applications before creating the snapshot. The following are required for application-managed snapshots: • SAN/iQ version 8.5 or later • CMC or CLI latest update • HP StorageWorks P4000 Windows Solution Pack, specifically the HP P4000 VSS Provider (latest update) installed on the application server (refer to the HP StorageWorks P4000 Windows Solution Pack User Guide) • Management group authentication set up for the VSS Provider (refer to the HP StorageWorks P4000 Windows Solution Pack User Guide) • Application on the server that is VSS-aware • Server set up in SAN/iQ with iSCSI connection (see Chapter 16 on page 257) • Microsoft iSCSI Initiator Creating an application-managed snapshot using SAN/iQ is the same as creating any other snapshot. However, you must select the Application-Managed Snapshot option. For information about creating snapshots, see "Creating a snapshot" on page 215. Understanding snapshots for volume sets The snapshot creation process for application-managed snapshots differs only when an application has associated volumes. Associated volumes are two or more volumes used by an application (volume set). For example, you may set up Exchange to use two volumes to support a StorageGroup: one for mailbox data and one for logs. Those two volumes make a volume set. 216 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

3.
If you want to use VSS to quiesce the application before creating the snapshot, select the
Application-Managed Snapshot
check box.
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).
This option quiesces VSS-aware applications on the server before SAN/iQ creates the snapshot.
The system fills in the Description field and disables the Servers field automatically. You can
assign servers after the snapshot is created.
4.
Type a name for the snapshot, or accept the default.
5.
(Optional) Enter a description of the snapshot.
6.
(Optional) Assign a server to the snapshot.
7.
Click
OK
when you are finished.
NOTE:
In the navigation window, snapshots are listed below the volume in descending date order, from
newest to oldest.
Requirements for application-managed snapshots
You can create application-managed snapshots for both single and scheduled snapshots.
Application-managed snapshots use the VSS Provider to quiesce VSS-aware applications before
creating the snapshot. The following are required for application-managed snapshots:
SAN/iQ version 8.5 or later
CMC or CLI latest update
HP StorageWorks P4000 Windows Solution Pack, specifically the HP P4000 VSS Provider (latest
update) installed on the application server (refer to the HP StorageWorks P4000 Windows Solution
Pack User Guide)
Management group authentication set up for the VSS Provider (refer to the HP StorageWorks
P4000 Windows Solution Pack User Guide)
Application on the server that is VSS-aware
Server set up in SAN/iQ with iSCSI connection (see
Chapter 16
on page 257)
Microsoft iSCSI Initiator
Creating an application-managed snapshot using SAN/iQ is the same as creating any other snapshot.
However, you must select the Application-Managed Snapshot option. For information about creating
snapshots, see
Creating a snapshot
on page 215.
Understanding snapshots for volume sets
The snapshot creation process for application-managed snapshots differs only when an application
has associated volumes. Associated volumes are two or more volumes used by an application (volume
set).
For example, you may set up Exchange to use two volumes to support a StorageGroup: one for
mailbox data and one for logs. Those two volumes make a volume set.
Using snapshots
216