Specifications

Recovering from a Non-Killable Process
4. Finally, extend each resource hierarchy from the server where the resource hierarchy is in-
service to the re-installed server using the GUI.
Recovering from a Non-Killable Process
If a process is not killable, LifeKeeper may not be able to unmount a shared disk partition. Therefore,
the resource cannot be brought into service on the other system. The only way to recover from a non-
killable process is to reboot the system.
Recovering From A Panic During A Manual Recovery
A PANIC during manual switchover may cause incomplete recovery. If a PANIC or other major
system failure occurs during a manual switchover, complete automatic recovery to the back-up
system cannot be assured. Check the backup system to make sure all resources required to be in-
service are in-service. If they are not in-service, use the LifeKeeper GUI to manually bring the missing
resources into service. SeeBringing a Resource In-Service for instructions.
Recovering Out-of-Service Hierarchies
As a part of the recovery following the failure of a LifeKeeper server, resource hierarchies that are
configured on the failed server, but are not in-service anywhere at the time of the server failure, are
recovered on the highest priority alive server at the time of the failure. This is the case no matter
where the out-of-service hierarchy was last in-service, including the failed server, the recovering
server, or some other server in the hierarchy.
Resource Tag Name Restrictions
Tag Name Length
All tags within LifeKeeper may not exceed the 256 character limit.
Valid "Special" Characters
- _ . /
However, the first character in a tag should not contain "."or "/".
Invalid Characters
+ ; : ! @ # $ * = "space"
Serial (TTY) Console WARNING
If any part of the serial console data path is unreliable or goes out of service, users who have a serial
252Troubleshooting