Home
  •  

Monitor REC_REPOSITORY_FULL (43)

NetAppESeries.FailureID_0043_Monitor (UnitMonitor)

The failure type is Repository Full.

Knowledge Base article:

Snapshot Repository Volume Capacity - Full

What Caused the Problem?

All of the repository volume's available capacity has been used. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Notes

Recovery Steps

1

If...

Then...

The snapshot (legacy) volume associated with this snapshot (legacy) repository volume is also a source volume in a copy operation and its copy status is Pending or In Progress

Perform the following steps:

a

Go to the Copy Manager by selecting the

Copy Services > Volume Copy > Manage Copies

menu option in the Array Management Window (AMW).

b

If...

Then...

You want to keep the data being copied

Allow the copy operation to complete before going to step 2.

You do not want to keep the data being copied

Highlight the copy pair that contains the snapshot (legacy) volume and select the

Copy > Stop

menu option, and then go to step 2.

The snapshot (legacy) volume associated with this snapshot (legacy) repository volume is also a source volume in a copy operation and its copy status is Failed

Perform the following steps:

a

Go to the Copy Manager by selecting the

Copy Services > Volume Copy > Manage Copies

menu option in the Array Management Window (AMW).

b

Highlight the copy pair that contains the snapshot (legacy) volume and select the

Copy > Stop

menu option.

c

Go to step 2.

Note:

 If you chose to create a new instance of the snapshot (legacy) volume as a part of this recovery procedure, you can create a new copy with new data by highlighting the copy pair that contains the snapshot (legacy) volume and selecting

Copy > Re-Copy

.

2

If...

Then...

You want to delete the snapshot (legacy) volume

Perform the following steps:

a

Highlight the snapshot (legacy) volume on the

Storage and Copy Services

tab in the AMW.

b

Select the

Storage > Volume > Delete

menu option.

c

Go to step 4.

You DO NOT want to delete the snapshot (legacy) volume

Go to step 3.

3

If...

Then...

You wish to create a new instance of the snapshot (legacy) volume now

Perform the following steps:

a

Highlight the snapshot (legacy) volume on the

Storage and Copy Services

tab in the AMW.

b

Select the

Copy Services > Snapshot (Legacy) > Re-Create

menu option.

Note: To keep your snapshot (legacy) volume's repository from becoming full again you should increase its capacity by highlighting it on the Storage and Copy Services tab and selecting the Copy Services > Snapshot (Legacy) > Repository > Increase Capacity menu option.

c

Go to step 4.

You wish to create an instance of the snapshot (legacy) volume at a later time

Perform the following steps:

a

Highlight the snapshot (legacy) volume on the

Storage and Copy Services

tab in the AMW.

b

Select the

Copy Services > Snapshot (Legacy) > Disable

menu option.

Note: To keep your snapshot (legacy) volume's repository from becoming full again you should increase its capacity by highlighting it on the Storage and Copy Services tab and selecting the Copy Services > Snapshot (Legacy) > Repository > Increase Capacity menu option.

c

When you are ready, you can create a new instance of the snapshot (legacy) volume by highlighting on the

Storage and Copy Services

tab and selecting the

Copy Services > Snapshot (Legacy) > Re-Create

menu option.

d

Go to step 4.

4

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:

TargetNetAppESeries.StorageArray
Parent MonitorNetAppESeries.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppESeries.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_REPOSITORY_FULL
The failure type is Repository Full. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppESeries.FailureID_0043_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="NetAppESeries.REC_REPOSITORY_FULL_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="NetAppESeries.StateId843ECFA67FFA42B1B5D7182E4228E095" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="NetAppESeries.StateIdF75B12FAE263D7D265E18707483E048B" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>43</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>