SUMMARY
This article describes the steps required to configure the primary and secondary (warm standby) Unitrac servers to replicate the database from the primary to the secondary.
MORE INFORMATION
General Steps:
-
Configure the identity of each instance of SQL server
-
Enable file sharing
-
Create the shares
-
Configure the periodic jobs
-
Test the periodic jobs
-
Enable the shipping jobs
Configure the identity of each instance of SQL server
A single account name and password is duplicated on each server and each instance of SQL server is configured to run under that account. Configuring SQL server to use that account includes configuring the SQL Server Agent to use that account. This document uses the user name SQLServices.
Enable File Sharing
Both servers must be configured for Microsoft file sharing.
Create the shares
Pick a place in the file structure which is to be used to ship the database between servers. Usually this place is on the secondary server but create the share location on both servers for when their roles are switched. Once the folder is created, share it and give user SQLServices “change” and “read” control of the folder. For example use C:\DiffShip on both servers. The shares will then look like \\primary\DiffShip and \\secondary\DiffShip.
Configure the periodic jobs
In Enterprise Manager (SQL 2000) or SQL Server Management Studio (SQL 2005), in the Jobs portion of the SQL Server Agent, edit the Apply Standby DB and the Ship Standby DB jobs to point to the proper share location.
On the primary server, configure the Ship Standby DB job to use the share \\secondary\DiffShip and configure the Apply Standby DB job to use c:\DiffShip.
On the secondary server, configure the Ship Standby DB job to use the share \\primary\DiffShip and configure the Apply Standby DB job to use c:\DiffShip.
NOTE: The default installation assumes that the primary Unitrac is named “unitrac1” and that the secondary is named “unitrac2.” It is also assumed that the name of the shared folder is “DiffShip.” If the default names are used then the periodic jobs need no modification.
Test the periodic jobs
On the primary server, in Enterprise Manager, in the Jobs portion of the SQL Server Agent, run the Ship Standby DB job. Check for errors.
On the secondary server, in Enterprise Manager, in the Jobs portion of the SQL Server Agent, run the Apply Standby DB job. Check for errors.
Enable the periodic jobs
On the primary server, in Enterprise Manager/SQL Server Management Studio, in the Jobs portion of the SQL Server Agent, enable the Ship Standby DB job.
On the secondary server, in Enterprise Manager/SQL Server Management Studio, in the Jobs portion of the SQL Server Agent, enable the Apply Standby DB job.
Comments
0 comments
Please sign in to leave a comment.