MS SQL Server Server Requirements

All primary database and target database pairs should be running the same version of MS SQL Server at the same service pack level. For example, you cannot replicate between a SQL Server 2005 database and a SQL Server 2000 database, because of the differences in their structures. The database servers should also be configured similarly. For example, the code page/character set, sort order, Unicode collation, and the locale all must be the same on both servers.

Peer DRS is meant to replace an existing backup plan. If you are currently backing up databases using the Built-in MS SQL Server BACKUP DATABASE T-SQL commands, using built-in Log Shipping or any other replication type that uses the built-in data maintenance plan, or any other technique that uses the transaction log files and truncates the log files, then the existing backup method will need to be disabled and replaced by this application. You can keep existing backup plans intact for any databases that you don’t intend to backup using this application.

The target MS SQL Server database to which the transaction logs are to be restored into must be in an 'unrecovered' state--that is, the last restore process must have been made with the NORECOVERY or STANDBY option. Peer DRS also has the ability to create the database for you on the target which is usually the easiest and best option to use.

Peer DRS can only work with databases configured for FULL or BULK_LOADED recovery models. This method will not work with a database configured for a SIMPLE recovery model unless you disable the incremental backup schedule. You will need to update the recovery model in the Database Properties tab of the Enterprise Manager, or Peer DRS will ask you if you would like it to make the change for you before saving a replication job.

5.	Establish proper security to all the servers. The Windows account you use to set up log shipping must have MS SQL Server systems administrator (sa) privileges on all the servers.

The account that the Peer DRS application is running under must have read-write permission to any network shares being utilized, and the MS SQL Server administrator account being used on the Primary and Target Databases must have read-write access to the configured local directory or network share. When using a network share as the Backup Folder, the network share must be specified as a UNC e.g. \\server\directory and not as a mapped network drive e.g. X:\directory since most MS SQL Server installations are run as a service and will not have access to mapped network drives. Moreover, for network share backups and restores to work, make sure your Primary and Target Database instances are NOT running under a local system account. These services must run using a domain account and this domain account must have read-write permissions on the network share or drive.