Sybase Replication Server®

What we provide

Xtivia’s Certified Sybase Replication Server Engineers will provide recommendations and strategies to set up replication server to meet your organizational objectives. Xtivia also provides VDBA system that monitors your replication server activities. We deliver:

• Initial assessments and review requirements
• Design replication system
• Define the approach & plan
• Estimate schedule & cost
• Perform installation
• Test to administer replication server

We understand these new and existing Sybase replication functionalities and can help you implement and maintain the solution that works best for your company.

What is Sybase Replication Server?

Sybase Replication Server is a set of tools that moves and synchronizes data from one server to another. It is created and designed to meet such challenges as:

• Ensuring that data is continuously available or available for prompt recovery should disaster strike
• Integrating and synchronizing operations across multiple locations
• Supporting timely and thorough data reporting

Sybase has developed a workable solution to data distribution which allows companies to reap the benefits of this information strategy while eliminating or minimizing many of the potential costs. There are three type of replication available within Sybase Replication Server.

Publish-and-subscribe model - In a functioning Replication Server system, transactions occurring in a source database are detected by a Replication Agent and transferred to the local Replication Server, which distributes the information across LANs and WANs to Replication Servers at destination sites. The primary data is the source of the data that Replication Server replicates in other databases. You “publish” data at primary sites to which Replication Servers at other sites “subscribe.”

Health Check For Sybase

Virtual-DBA Overview

Sybase Case Study

Warm standby / MSA - Replication Server provides warm standby capability with a pair of databases, one as the active database and one as the standby database, is supported by Replication Server functionality. As clients update the active database, Replication Server copies transactions to the standby database, maintaining consistency between the two. Should the active database fail for any reason, you can switch to the standby database, making it the active database, and resume operations with little interruption.

MSA, a newer product, provides all the features of the warm standby application. In addition, MSA enables replication to multiple standby databases and allows you to replicate or not replicate specific database objects.

Heterogeneous data server support - Sybase Replication Server also supports replicating data to and from non-Sybase data servers. Data can be replicated to non-Sybase data servers such as Oracle, Informix, IBM DB2, and Microsoft SQL Server using Sybase DirectConnect™ gateways. Transactions can be captured and forwarded from non-Sybase data servers using Sybase Replication Agents™. Data can also be replicated from a non-Sybase source, through Replication Server to a non-Sybase destination.

How soon does the data move?

The data moves asynchronously. The time it takes to reach the destination depends on the size of your transaction, level of activity in that particular database (a database as in Sybase systems), the length of the chain (one or more replication servers that the transaction has to pass through to reach the destination), the thickness of pipe (network), how busy your replication server is etc. Usually, on a LAN, for small transactions, this is about a second.

Who uses Sybase Replication Server and why?

A business organization that wants to build distributed system

Data distribution is a tool that helps companies put necessary data in the hands of local decision-makers yet maintain firm central control over the data. With Sybase Replication Server, data can be shared and replicated between databases, allowing system designers to put the data where it's needed.

A business organization that wants to have additional backup strategy

In conjunction with backup, Sybase replication strategies seek to complement traditional approaches by providing alternative levels of data protection and integrity, while minimizing user disruptions. Replication creates a point-in-time copy of the data to be used as the backup source.

A business organization that wants to set up a failover system

Replication Server maintains a near real-time “warm standby” database to which applications can switch with virtually no downtime if the primary site fails. You can manage planned downtime such as routine maintenance, software upgrades and etc. It protect during unplanned downtime due to machine/network outage, for example. It also provides disaster recovery. Any system providing HA services should provide continuous availability of data in any scenarios.

A business organization that wants data replicated from/to non-Sybase data servers.

Data can be replicated to non-Sybase data servers such as Oracle, Informix, IBM DB2, and Microsoft SQL Server using Sybase DirectConnect™ gateways. Transactions can be captured and forwarded from non-Sybase data servers using Sybase Replication Agents™. Data can also be replicated from a non-Sybase source, through Replication Server to a non-Sybase destination.