mode) and a remote status of EX_ENORMT, PSUE or PSUS, indicating that there is an error accessing the primary site. The control file script is programmed to handle this condition and will enable the volume groups, mount the logical volumes, assign floating IP addresses and start any processes as coded into the script.

NOTE: In ASYNC mode, the package will halt unless a force flag is present or unless the auto variable AUTO_SVOLPSUE is set to 1.

The fence level of the paired volume—NEVER, ASYNC, or DATA—will not impact the starting of the packages at the recovery site. The Metrocluster CAXP pre-integrated solution will perform the following command with regards to the paired volume.

# horctakeover -g <dev-grp-name> -S

Subsequently, the paired volume will have a status of SVOL_SWSS. To view the local status of the paired volumes.

# pairvolchk -g <dev-grp-name> -s

To view the remote status of the paired volumes.

# pairvolchk -g <dev-grp-name> -c

(While the remote P9000 or XP disk array and source disk site systems are down, the command will time out with an error code of 242.)

After power is restored to the primary site, or when a newly configured array is brought online, the P9000 or XP paired volumes may have either a status of PVOL_PSUE on the primary site or SVOL_SWSS on the secondary site. The following procedure applies to this situation:

1.While the package is still running, from the recovery host.

# pairresync -g <dgname> -c 15 -swaps

This starts the resynchronization, which can take a long time if the entire primary disk array was lost or a short time if the primary array was intact at the time of failover.

2.When resynchronization is complete, halt the Continentalclusters recovery packages at the recovery site.

# cmhaltpkg <pkg_name>

This will halt any applications, remove any floating IP addresses, unmount file systems and deactivate volume groups as programmed into the package control files. The status of the paired volumes will remain SVOL_PAIR at the recovery site and PVOL_PAIR at the primary site.

3.Start the cluster at the primary site. Assuming they have been properly configured, the Continentalclusters primary packages should not start. The monitor package should start automatically.

4.Manually start the Continentalclusters primary packages at the primary site.

# cmrunpkg <pkg_name>

5.Ensure that the monitor packages at the primary and recovery sites are running.

Failback when the Primary has SMPL Status

Use the following procedure when the primary site paired volumes have a status set to SMPL, possibly through manual intervention:

1.Halt the Continentalclusters recovery packages at the recovery site.

# cmhaltpkg <pkg_name>

Completing and Running a Continentalclusters Solution with Continuous Access P9000 or XP 207