There are several requirements and restrictions for replicating the master database in an Adaptive Server warm standby environment.
You can replicate Adaptive Server logins from one master database to another.The master database replication is limited to DDL, and the system commands used to manage logins and roles. Master database replication does not replicate data from system tables, nor replicate data or procedures from any other user tables in the master database.
Both the source Adaptive Server and the target Adaptive Server must be the same hardware architecture type (32-bit versions and 64-bit versions are compatible), and the same operating system (different versions are also compatible).
Do not initialize the active and standby databases with a load from another master database. To synchronize the syslogins, suids and roles at each master, use bcp to refresh the appropriate tables or manually synchronize the IDs and roles prior to setting up your replication.
There are several restrictions and requirements when you set up your warm standby application and enable replication with sp_reptostandby, and there are several supported DDL and system procedures that apply to the master database.
Sybase recommends setting longer password expiration intervals on the standby master database compared to the expiration intervals on the active master database. This allows the active master database to control any change of passwords and allows replication of password changes to proceed
Replication Server versions 12.0 and later support master database replication in a warm standby environment, and in an MSA environment in Replication Server 12.6 and later. The primary or active Adaptive Server must be version 15.0 ESD #2 or later.
See Replication Server Administration Guide Volume 1 > Manage Replicated Objects Using Multisite Avaiability > Replicating the Master Database in an MSA Environment for information about master database replication in an MSA environment.