SAP Hierarchy Remove Errors

Symptom:

File system remove fails with file system in use.

Cause:

1. Resource Protection Level was set to Basic or Minimum after the create or extend. When the resource Protection Level is set to Basic or Minimum, the SAP resource hierarchy will not be stopped during the remove operation. This leaves the processes running for that instance when remove is called. If the processes are also accessing the protected file system, LifeKeeper may be unable to unmount the file system.

2. Resource Protection Level was set to Standard for a non-replicated enqueue resource. When the resource Protection Level is set to Standard, the SAP resource hierarchy will not be stopped during the remove operation. This leaves the processes running for that instance when remove is called. If the processes are also accessing the protected file system, LifeKeeper may be unable to unmount the file system.

Action:

1. The Basic and/or Minimum settings should be used to place a resource in a temporary maintenance mode. It should not be used as an ongoing Protection Level. If the resource in question will require Basic or Minimum as the ongoing Protection Level, the Instance should be configured to use local storage and/or the entire resource hierarchy should be configured without the use of the LifeKeeper NAS Recovery Kit for local NFS mounts.

2. The Standard setting should be used for replicated enqueue resources only. Note: Standard is used for ERS resources that were created in LifeKeeper 9.3.2 or earlier and reside at the top of the SAP hierarchy with a dependency on the corresponding central services resource. ERS instances created in LifeKeeper 9.4.0 or later that reside in a hierarchy independent of the central services resource should have their Protection Level set to Full.