LifeKeeper configurations may use the facilities of shared Small Computer System Interface (SCSI) host adapters and shared disk hardware to switch resources from a failed server to a designated backup server. A Fibre Channel Storage Area Network (SAN) may also be used to switch resources from a failed server to a designated backup server.
Perform the following tasks before creating disk-based application resource hierarchies that enable LifeKeeper to provide failover protection.
- Shared disk arrays must be configured into logical units, or LUNs. Use your disk array management software to perform this configuration. You should refer to your disk array software documentation for detailed instructions. For shared storage, it is recommended that disks are partitioned.
Note: Remember that LifeKeeper locks its disks at the LUN level. Therefore, one LUN may be adequate in an Active/Standby configuration. But, if you are using an Active/Active configuration, then you must configure at least two separate LUNs, so that each hierarchy can access its own unique LUN.
- It is recommended that the shared disks are partitioned with a utility like gdisk.
- Verify that both servers recognize the shared disks (for example, using the gdisk command). If Linux does not recognize the LUNs you have created, then LifeKeeper will not either.
- Create file systems on your shared disks from the system you plan to use as the primary server in your LifeKeeper hierarchy. Refer to the Linux documentation for complete instructions on the administration of file systems.