Home
  •  

Monitor REC_SNAPSHOT_FAILED (44)

IBMStorageSubsystem.FailureID_0044_Monitor (UnitMonitor)

Monitor Description for (44)

Knowledge Base article:

Failed FlashCopy Logical Drive

What Caused the Problem?

Either the flashcopy logical drive's associated repository logical drive is full or its associated base or repository logical drive were failed due to one or more drive failures on their respective arrays. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Notes

Recovery Steps

1

First, fix any problems given in the Summary area affecting the flashcopy logical drive's associated base or repository logical drive using the appropriate recovery procedure.

2

If...

Then...

The flashcopy logical drive is also a source logical drive in a copy operation and its copy status is Pending, In Progress, or Failed

Go to the Copy Manager by selecting

Logical Drive >> Copy >> Copy Manager

. Highlight the copy pair that contains the flashcopy logical drive and select

Copy >> Stop

.

Go to step 3.

Note: You cannot recover or access the data on the target logical drive of this copy operation. However, Step 5 will help you create a new copy with new data if you choose to create a new instance of the flashcopy logical drive in Step 4 of this recovery procedure.

3

If...

Then...

You want to delete the flashcopy logical drive

Highlight the flashcopy logical drive in the Logical View of the Subsystem Management Window. Then, select

Logical Drive >> Delete.

Go to step 6.

You DO NOT want to delete the flashcopy logical drive

Go to step 4.

4

If...

Then...

You want to create a new instance of the flashcopy logical drive now

Highlight the flashcopy logical drive in the Logical View of the Subsystem Management Window. Then, select

Logical Drive >> FlashCopy >> Re-create.

Note: If the flashcopy logical drive's failure was due to the flashcopy's repository logical drive becoming full, you should increase the size of the flashcopy's repository logical drive by highlighting it in the Logical View and selecting Logical Drive >> Increase Capacity.

Go to step 5.

You wish to create an instance of the flashcopy logical drive at a later time

Highlight the flashcopy logical drive in the Logical View of the Subsystem Management Window. Then, select

Logical Drive >> FlashCopy >> Disable.

When you are ready, you can create a new instance of the flashcopy logical drive by highlighting it in the Logical View and selecting

Logical Drive >> FlashCopy >> Re-create.

Note: If the flashcopy logical drive's failure was due to the flashcopy's repository logical drive becoming full, you should increase the size of the flashcopy's repository logical drive by highlighting it in the Logical View and selecting Logical Drive >> Increase Capacity.

Go to step 6.

5

If...

Then...

The new instance of the flashcopy logical drive you just created is also a source logical drive in a copy pair and you want to copy the new flashcopy data to the target logical drive

Go to the Copy Manager by selecting

Logical Drive >> Copy >> Copy Manager

. Highlight the copy pair that contains the flashcopy logical drive and select

Copy >> Re-Copy

.

Go to step 6.

6

Click the

Recheck

button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

Element properties:

TargetIBMStorageSubsystem.StorageSubsystem
Parent MonitorIBMStorageSubsystem.StorageSubsystemAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeIBMStorageSubsystem.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_SNAPSHOT_FAILED
Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="IBMStorageSubsystem.FailureID_0044_Monitor" Accessibility="Internal" Enabled="true" Target="IBMStorageSubsystem.StorageSubsystem" ParentMonitorID="IBMStorageSubsystem.StorageSubsystemAvailability" Remotable="true" Priority="Normal" TypeID="IBMStorageSubsystem.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="IBMStorageSubsystem.REC_SNAPSHOT_FAILED_AlertMessageResourceID">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="IBMStorageSubsystem.StateIdF7FEB000D72674A86240E547D435ABDA" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="IBMStorageSubsystem.StateId8012DB2C4C54DBB1B5AE710B0F5CA8D" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>44</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>