666
Part V: Enterprise Data Management
Best Practice
The monitor server can be an instance on the destination server, but locating the monitor server on the
source server would be a self-defeating plan. If the source server physically failed, the monitor server
would also fail. The best practice is to assign a monitor server to its own hardware to avoid disrupting
monitoring in the event the primary or warm standby server is lost.
Each primary server database can have only one log shipping plan, and each plan can ship
only one database. However, a plan may ship to multiple secondary servers.
Log Shipping Architecture
Log shipping can be confi gured by using one of two methods: either by using SQL Server
Management Studio or by using system stored procedures.
Pre-Log Shipping Configuration
With either method of confi guration, the following prerequisites need to be completed
before confi guring log shipping:
■ (^) Disk space needs to be created and shared. This network share is used by the
backup job on the primary server to store the transaction log backups. Grant read
and write permissions on the network share to the SQL Server service account on
the primary server and read permissions to the proxy account for the copy job (usu-
ally the SQL Server Agent service account) on the secondary server.
■ (^) Destination folder needs to be created on the secondary servers. The copy job on
the secondary server copies the transaction log backups from the network share
to the destination folder on the secondary server. The load job then restores
these transaction log backups from the destination folder. The SQL Server service
accounts on the secondary server need to have read and write permissions on this
folder.
■ (^) The recovery model of the log shipping database must be set to full or bulk-logged.
■ (^) The edition of the SQL Server 2012 participating in log shipping needs to be the
Enterprise, Standard, or Workgroup Edition.
■ (^) If the primary and secondary servers are on different domains, then set up two-
way trusts between the domains. If this is not possible, you can also use net-
work pass-through security. With network pass-through security the SQL Service
accounts for all the SQL Servers participating in log shipping use the same network
account and the same password and enough permission to complete the log ship-
ping tasks.
■ (^) If you have a large database, then it is recommended to take a full database
backup, copy it to the secondary server, and restore it on the secondary server
with NORECOVERY or STANDBY to put it into a state that allows restoring the
c26.indd 666c26.indd 666 7/31/2012 9:49:17 AM7/31/2012 9:49:17 AM
http://www.it-ebooks.info