SIOS TECHNOLOGY CORP.

Sybase ASE Active/Standby Considerations

In an Active/Standby configuration, the backup server is not actively running the Sybase ASE but stands by in case the primary server experiences a failure. The following scenarios provide specific requirements that must be adhered to when protecting a Sybase ASE resource instance in active/standby configurations.

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
$SYBASE/ASE/lib
  • º Add an entry for
$SYBASE/OCS/lib
  • º Mount the shared file system containing the Sybase
ASE installed products and run ldconfig

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment