Sybase ASE Active/Active Considerations

In an Active/Active configuration, each server is actively running one or more Sybase ASE Servers, while acting as a backup for the other SPS server in case of failure. The following scenario provides specific requirements that must be adhered to in sequential order when protecting a Sybase ASE resource instance in an active/active configuration.

Scenario 1

The Sybase ASE product is installed locally on all servers in the cluster.

• All Sybase Adaptive Server, Monitor Server, and Backup Server devices are configured on shared storage.

• The Sybase Adaptive Server, Monitor Server, and Backup Server configuration files are stored on a shared file system.

• The Sybase Adaptive Server and Monitor Server shared memory directory is located on a shared file system.

• The interfaces file must be manually updated on all servers to contain common entries for each instance to be protected.

• All interfaces file entries must be resolvable by all servers where the resource will be protected.

• The RUN files for each Adaptive Server, Monitor Server and Backup Server must exist on all servers in the cluster.

• The RUN files for each Adaptive Server, Monitor Server and Backup Server must be executable on all servers in the cluster.

• The RUN files for each Adaptive Server, Monitor Server and Backup Server must contain the same options on all servers in the cluster.

Scenario 2

The Sybase ASE product is installed to one or more shared file systems on the primary server.

• All Sybase Adaptive Server, Monitor Server and Backup Server devices are configured on shared storage.

• The Sybase Adaptive Server, Monitor Server and Backup Server configuration files are stored on a shared file system.

• The Sybase Adaptive Server and Monitor Server shared memory directory is located on a shared file system.

• The interfaces file does not have to be updated on the target servers.

• All interfaces file entries must be resolvable by all servers where the resource will be protected.

• On the SPS backup server, /etc/ld.so.conf must be updated to add entries for the Sybase product libraries.

• º Add an entry for

• º Add an entry for

• º Mount the shared file system containing the Sybase