HP MSA 1040 HP MSA Events Description Reference Guide (762785-001, March 2014) - Page 37

This can occur when a snapshot is taken by an application, such as the VSS hardware provider,

Get HP MSA 1040 PDF manuals and user guides View all HP MSA 1040 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 37 highlights

251 Info. A volume-copy operation has started for the indicated source volume. If the source volume is a master volume, you can remount it. If the source volume is a snapshot, do not remount it until the copy is complete (as indicated by event 268). Recommended actions • No action is required. 252 Info. Data written to the indicated snapshot after it was created has been deleted. The snapshot now represents the state of the master volume when the snapshot was created. Recommended actions • No action is required. 253 Info. A license was uninstalled. Recommended actions • No action is required. 255 Info. The PBCs across controllers do not match as PBC from controller A and PBC from controller B are from different vendors. This may limit the available configurations. Recommended actions • No action is required. 256 Info. The indicated snapshot has been prepared but is not yet committed. This can occur when a snapshot is taken by an application, such as the VSS hardware provider, that is timing-sensitive and needs to take a snapshot in two stages. After the snapshot is committed and event 258 is logged, the snapshot can be used. Recommended actions • No action is required. 257 Info. The indicated snapshot has been prepared and committed and is ready for use. Recommended actions • No action is required. 258 Info. The indicated snapshot has been committed and is ready for use. Recommended actions • No action is required. Event descriptions 37

  • 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
Event descriptions
37
251
Info.
A volume-copy operation has started for the indicated source volume.
If the source volume is a master volume, you can remount it.
If the source volume is a snapshot, do not remount it until the copy is complete (as indicated by event
268).
Recommended actions
•
No action is required.
252
Info.
Data written to the indicated snapshot after it was created has been deleted. The snapshot now represents
the state of the master volume when the snapshot was created.
Recommended actions
•
No action is required.
253
Info.
A license was uninstalled.
Recommended actions
•
No action is required.
255
Info.
The PBCs across controllers do not match as PBC from controller A and PBC from controller B are from
different vendors. This may limit the available configurations.
Recommended actions
•
No action is required.
256
Info.
The indicated snapshot has been prepared but is not yet committed.
This can occur when a snapshot is taken by an application, such as the VSS hardware provider, that is
timing-sensitive and needs to take a snapshot in two stages.
After the snapshot is committed and event 258 is logged, the snapshot can be used.
Recommended actions
•
No action is required.
257
Info.
The indicated snapshot has been prepared and committed and is ready for use.
Recommended actions
•
No action is required.
258
Info.
The indicated snapshot has been committed and is ready for use.
Recommended actions
•
No action is required.