DR-Synch 3.0
In a perfect world, everyone would have the resources for costly, clustered SQL Servers that
automatically failover our production SQL Servers. Most organizations find that a standby
server is adequate. This idea is not a new one for most DBAs.
Traditionally, using a standby server for failover has involved manually creating database
and log backups on the production server and then restoring them to the standby server on
a regular basis. Should the production server fail, users can access the standby server instead.
Downtime and data loss could be minimized if the process was heavily monitored, regularly
implemented, and tested often. As most DBA's will attest, this manual process can be
prohibitively time consuming and arduous to monitor. Therefore, a generalized SQL log shipping
tool was introduced to the industry by Microsoft.
Installation Instruction
FAQ
What is Log Shipping? Why DR-Synch?
The Microsoft Log Shipping tool automates the backup of database and transaction log files
on a production SQL server, and then restores them onto a standby server. Data-Rite improved
upon this basic log shipping functionality with DR-Synch by developing additional features
and functions. DR-Synch automates previously manual processes, monitors server status and
sends e-mail notifications in the event of system failures.
Minimal Downtime
The key feature of Data-Rite's DR-Synch is that it will automatically back up transaction
logs throughout the day (e.g. 20 minute intervals) and automatically restore them on a standby
server. This, in effect, keeps the two SQL servers in synch. Should the production server fail,
all that is required is pointing the users to the new server. Data-Rite's DR-Synch solution
provides users with a configurable and flexible automated solution to achieve this.
Advantages of DR-Synch
- Fast and easy installation
- User-Friendly front end that allows custom configurations
- Live status updates on procedures (logging, shipping, restoring)
- E-mail notifications on failed processes
- Constant monitoring of production and recovery servers
- Reliability
- Irretrievable data is limited to the pre-set time interval of DR-Synch's log shipping
(e.g. 20 minutes)
New features of DR-Synch 3.0
- New compression algorithm for faster compression
- Advanced auditing and historical information
- Advanced detection of SQL server failures
How Does It Work?
A full database backup is zipped and sent to the standby server, where it is restored
each night. At regular intervals throughout the day, a backup of the transaction log is
sent to the standby sever where transactions are inserted. A robust monitoring feature
reports live status updates as well as e-mail notifications in the event of any process
failure.
Monitoring System
All backup, sending and inserting activity is logged and monitored in a SQL database.
Live status updates are displayed for at-a-glance inspections. Any end user or DBA will
always know the status of their production servers as well as the standby server.
This leads to the correct and fastest recovery path in the event of a disaster.
Rapid Restore Capabilities
A failover routine is executed by the DBA. Depending upon the nature of the disaster
recovery need, one of two options is available at restore for DR-Synch users:
- Restore the production database from the standby server, then go-live OR
- Rename the standby server to the production server name and go-live
System Requirements
SQL SERVER 2005 REQUIREMENTS
SQL SERVER 2000 REQUIREMENTS
For more information, please contact Mike Feldman.