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

Skipped a replication to the indicated secondary volume.

Page 50 highlights

429 Info. A user resumed a replication to the indicated secondary volume. Recommended actions • No action is required. 430 Info. A user aborted a replication to the indicated secondary volume. Recommended actions • No action is required. 431 Error Replication to the indicated volume has been suspended due to an error detected during the replication process. User intervention is required to resume replication. This can occur for several reasons, such as: • The cache request was aborted. • The cache detected that the source or target volume is offline. • The cache detected a media error. • The snap pool is full. • The communication link is busy or experienced an error. • The snapshot being used for the replication is invalid. • There was a problem establishing proxy communication. Recommended actions • If the reported problem is with a primary volume, back up as much of the volume as possible. • Resolve the error and then resume the replication. 432 Error Aborted a replication due to an error in the indicated secondary volume. Recommended actions • Verify that the secondary volume is valid and that the system where the volume resides is accessible. 433 Info. Skipped a replication to the indicated secondary volume. Recommended actions • No action is required. 434 Warning A replication collided with an ongoing replication to the indicated secondary volume. A replication was in progress for the replication set when a new replication was requested. The new replication has been queued. Recommended actions • This can be a normal operation, but in some cases this can indicate a problem. Ensure that: there are no network issues; there is sufficient bandwidth between the primary and secondary systems; the interval between replications is set to a sufficient amount of time to allow replications to complete. Having too many replications queued can result in some replications not completing. 50 Event descriptions

  • 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

50
Event descriptions
429
Info.
A user resumed a replication to the indicated secondary volume.
Recommended actions
No action is required.
430
Info.
A user aborted a replication to the indicated secondary volume.
Recommended actions
No action is required.
431
Error
Replication to the indicated volume has been suspended due to an error detected during the replication
process. User intervention is required to resume replication. This can occur for several reasons, such as:
The cache request was aborted.
The cache detected that the source or target volume is offline.
The cache detected a media error.
The snap pool is full.
The communication link is busy or experienced an error.
The snapshot being used for the replication is invalid.
There was a problem establishing proxy communication.
Recommended actions
If the reported problem is with a primary volume, back up as much of the volume as possible.
Resolve the error and then resume the replication.
432
Error
Aborted a replication due to an error in the indicated secondary volume.
Recommended actions
Verify that the secondary volume is valid and that the system where the volume resides is accessible.
433
Info.
Skipped a replication to the indicated secondary volume.
Recommended actions
No action is required.
434
Warning
A replication collided with an ongoing replication to the indicated secondary volume.
A replication was in progress for the replication set when a new replication was requested. The new
replication has been queued.
Recommended actions
This can be a normal operation, but in some cases this can indicate a problem. Ensure that: there are
no network issues; there is sufficient bandwidth between the primary and secondary systems; the
interval between replications is set to a sufficient amount of time to allow replications to complete.
Having too many replications queued can result in some replications not completing.