Peer DRS is an application that can give you continuous database protection. It is capable of backing up various types of databases (e.g., MS SQL Server and MS Exchange Server). Peer DRS replicates database changes in near real-time to one or more remote locations acting as warm or cold standby servers based on the supported database platform's capabilities.
Peer DRS employs a form of log shipping. This is the process of automating the backup of databases and transaction log files on a primary server, and then restoring them onto a target standby server. The key feature of log shipping is the automatic backup of transaction logs throughout the day (or on whatever interval you specify), and the ability to then automatically restore them on a standby server located anywhere in the world. This in effect keeps the two databases in synchronisation with one another. Should the production server fail, all you have to do is point the users/applications to the new server and perform a database role reversal.
Peer DRS is unique from other products. It provides a centralised way to remotely manage and monitor all of your database backups from a single location and from a single application. It has a plug-in architecture allowing it to support different types of database backups from a single application, e.g. SQL Server and Exchange Server. In addition, it is extremely flexible and can be configured to handle almost any type of backup scenario. Peer DRS has an easy and intuitive configuration wizard and management interface making backups simple.
Peer DRS's Key Features
- Support for all versions of SQL Server from 2000 to 2008, and all versions of Exchange Server from 2000 SP2 to 2007.
- Performs full backups on-demand or at a scheduled time.
- Performs up to the minute incremental backups and replicates them to one or more warm standby databases.
- Configure and manage all database backups remotely from a central, client-based GUI. It is not necessary to run Peer DRS on the same server as the primary database or target databases are installed on.
- Runs as a system service or run in the background in the system tray.
- Replicate across a WAN via FTP, SFTP, SSH or a password protected Network Shared drive.
- Resume a file copy from where it last left off for failed file copies to target. Very useful for large full backups across a slow WAN.
- Transfer backups securely across a WAN or LAN using SSH or SFTP.
- Configure backup jobs on a per database basis with different configurations and schedules.
- Specify various archiving options and configure how long to keep backups and transaction logs.
- Perform full and incremental backups without restoring to a standby server for remote storage and disaster recovery.
- Cross platform Java bases application that can run on various operating systems such as Windows, Linux, Mac, etc.
- Possible to use the standby server as a live read-only database. The transaction log shipping approach will work, but an exclusive lock on the entire database is required to apply the transaction log changes. Therefore, this will only be possible on lightly loaded read-only databases, or if the user configures Peer DRS to allow the application to close all active connections during a restore.
- Send alert emails if connection to primary database cannot be established or if a backup or restore has not occurred within a configurable period of time threshold.
- Report on all replication activity from a single control panel allowing for easy identification of current errors or for peace of mind by knowing everything is operating smoothly.
- Monitor all replication activity in real-time and capable of setting different debug levels allowing for easy troubleshooting.
- All configured passwords are encrypted and out of reach of prying eyes.
The Small Business Edition has all the great features of the full product, runs on all the same SQL Server versions and Windows versions, but with a few limitations, and a great price! Check out the version comparison matrix.
- Maximum of 2 systems acting as source and target machines
- Maximum of 4 databases per source server
- Maximum of 1 warm standby target servers
- Transfers via SSH and SFTP are disabled