The following are the most commonly requested DataKeeper related solutions.
Remove a DataKeeper Resource from LifeKeeper
Scenario:
Remove an existing DataKeeper Resource/Mirror from LifeKeeper/SPS:
- Without impacting the existing resources in LifeKeeper/SPS, i.e. File Shares, SAP, Oracle, SQL, DNS
- Without having to run various emcmd commands, e.g. deletelocalmirroronly, cleanupmirror
Steps to Remove:
In LifeKeeper/SPS:
In the LifeKeeper GUI console, remove the dependency that the Volume has been established to/with:
- Right click on your parent level resource and select “Remove Dependency…”
- Select the appropriate Source Server, then select Next>
- Under Child Resource, select your Volume from the drop down list, Next>
- Their will be dialog pertaining to the Parent:/Child dependency, select “Remove Dependency”, then Done
Now the Volume Resource is listed as a standalone hierarchy, therefore it must be removed:
- Right click on the Volume/Volume Hierarchy and select “Delete Resource Hierarchy . . .”
- Select the Target Server, then select Next>
- There will be dialog pertaining to Volume Hierarchy and Target Server it will be removed from. Select “Delete”
- Select Done
The DataKeeper Storage is no longer a resource in the LifeKeeper/SPS.
Volume still locked after mirror resource removed from LifeKeeper
Issue:
For reasons unknown, a non-mirrored volume becomes locked.
Symptoms:
- Access Denied
- In File Manager
- After the emcmd . unlockvolume {drive letter} command is executed
Scenario for Volume E:
From a LifeKeeper command prompt (c:\lk\bin) executing “volume -d” displays the following:
Locked Volumes:
D: [EM Volume]
E:
L: [EM Volume]
Solution:
In the aforementioned command, LifeKeeper still thinks that Volume E is locked. To unlock Volume E, executed the following:
volume -u E
Volume E is no longer listed as a protected volume by executing “volume -d”
Locked Volumes;
D: [EM Volume]
L: [EM Volume]
Now you should be able to access the volume properly.
Post your comment on this topic.