Sybase dual-Machine hot standby for database through replication between two separate servers

One of the Sybase replication server application Scenarios

Replication servers support one-to-one replication mode, and the replication server's warm standby maintains a dual database for adaptive server or SQL Server, one of which is a warm backup of another active database. When a user modifies an active database, the replication server replicates the corresponding transaction to the backup database, making the two consistent. One but the active database failed for a variety of reasons, you can switch to the backup database, making it the active database, in addition to a little interruption, almost no impact on the operation of the database.

The schematic diagram is as follows:

The program needs to configure system software: ASE, Rep, SQL Remote.

The advantages of this scheme are high performance (without increasing the burden of as data access, the unique data access and message transmission mechanism), sending update transactions rather than the data itself to ensure the integrity of the data; Independent RSM easier to manage replication systems; Data high availability (automatic resynchronization after failure, Allow dump and load to maintain database initial synchronization characteristics); Full local autonomy (there is full local freedom to view and use replicated data, including data selection, local name names, optimization of native access mechanisms, etc.).

The disadvantage of this scenario is that when one server fails, switching to another server (Warm Standby), the current user transaction terminates abnormally, Dsedit modifies the client's Sql.ini file, and resubmit it with the same name as the same. One solution is to use Sybase's HA software to achieve a smooth transition of user transactions, or the PB8.0 version of the foreground application software supports failover processing and is resolved in PB programming.