Peer DRS Data Replication Service About-Peer-DRS

Peer DRS Data Replication Service

Peer DRS Data Replication Service Download

| Price - order

Easy Setup

Works in the Background

No need for Downtime

Server 2 available in Read Only

Peer DRS Data Replication Service Pricing

About-Peer-DRS	Download	Licensing
Peer-DRS-vs-PeerSync	Screenshots

Peer DRS is a tool for providing a centralized way to remotely manage and monitor all of your database backups from a single location and from a single application.

Peer DRS has a plug-in architecture allowing it to support different types of database backups from a single application, e.g. MS SQL Server, MS Exchange, MySQL, etc.

The current version of the DRS allows for MS SQL Server replication through the MS SQL Server Replicator module, however we plan on releasing additional modules to fulfill the Exchange, MySQL and other database replication needs.

Peer DRS - Data Replication Service for SQL

Peer DRS is a data replication framework capable of backing up as well as replicating database changes to one or more remote locations acting as warm standby servers.

Ability to perform full backups in real-time or at a scheduled time.
Ability to perform up to the minute incremental backups and replicate 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.
Ability to replicate across a WAN via FTP, SFTP, SSH or a password protected Network Shared drive.
Ability to 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.
Ability to configure backup jobs on a per database basis with different configurations and schedules.
Cross platform Java bases application that can run on various operating systems such as Windows, Linux, Mac, etc.
Ability to use the standby server as a live read-only database.
Ability to 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.
Ability to 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.

Peer-DRS Primary Application
Peer DRS employs a form of log shipping which 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 that it will automatically backup transaction logs throughout the day (for whatever interval you specify) and automatically restore them on a standby server located anywhere in the world. This in effect keeps the two Databases in "synch". 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.

Installation
Peer DRS is delivered/downloaded as a full installation program. To run, simply double-click on the executable in the Explorer window, or choose "Run" from the Start Menu and then select the application and a wizard will walk you through the installation.

Peer DRS can be configured in numerous ways based on your needs and your environment. It is recommended that you perform a site survey to assist you with picking an initial configuration before installing the software. Below are the two most common configurations along with their requirements
Configuration
Remote Centralized Installation
Peer DRS installed on a separate server from the primary database(s) or any of the target databases. This configuration is normally used when you need to backup and replicate two or more primary databases residing on different servers. This configuration is also useful if you want to offload as much I/O and CPU processing as possible from the primary database servers. This configuration will require the following access:

A. TCP/IP and port access to all primary and target databases.
B. A network shared drive accessible from and with the proper read-write permission for the account/user that the Peer DRS application is running under. Also the account that the primary database instance is running under must have read-write permission to the network share. If the shared drive or target database file copy folder is located on the same host as the database server instance then you only need to specify a local path to the backup folder.

Local Installation
Peer DRS is installed on the same server as the Primary Database and has network access to connect to all primary and target databases. This configuration will require the following access:

A. TCP/IP and port access to all primary and target databases.
B. A local path on the Peer DRS installation machine or a network shared drive accessible by all target database instances.

The most important thing to keep in mind is that the account that any of the configured primary and target database instances are run under must have permission to read and write from the drive (usually a network share) where the backup or copied target files are located. Please see the Security Model & Permissions section for more information on security and permission requirements.

Suggestion Box
Your comments can help make our site better for everyone. If you've found something incorrect, broken, or frustrating on this page, let us know so that we can improve it.