676
Part V: Enterprise Data Management
■ (^) msdb.dbo.sp_attach_schedule: Links the restore job to the schedule
■ master.dbo.sp_add_log_shipping_secondary_database: Confi gures the
secondary database
■ msdb.dbo.sp_update_job: Enables the copy job
■ (^) msdb.dbo.sp_update_job: Enables the restore job
On the monitor server, execute the following system stored procedure:
■ (^) master.dbo.sp_add_log_shipping_alert_job: Creates the alert job and adds
the job id to the log_shipping_monitor_alert table.
Post-Log Shipping Configuration
As mentioned earlier, log shipping applies only the changes that are either captured in the
transaction log or the initial full backup of the log shipping database. Any database objects,
such as logins, jobs, maintenance plans, SSIS packages, and linked servers that reside out-
side the log shipping database, need to be manually created on the warm standby server.
After confi guring log shipping, it is important to synchronize the warm standby servers with
all objects that live outside the log shipping database. Most of these objects can be easily
scripted using Management Studio and can be applied on the warm standby servers. The fre-
quency of applying the changes must meet the rate of changes in your environment.
One of the ways to synchronize the logins is to create an Integration Services (SSIS) job
that connects to each server and transfers the logins. The frequency of this job depends on
how often new logins are added to your primary server.
Checking Log Shipping Confi guration
After Log Shipping is confi gured, review the following checklist to verify the log shipping
setup.■ On the primary server:- Right-click the log shipping database and look at the database properties.
On the Transaction Log Shipping page, note that the database is enabled as
the primary database in the log shipping confi guration. On this page you can
review other log shipping details like the backup job schedule on the primary
server, secondary server details, the copy and restore job schedule on the sec-
ondary server, and monitor server details and if backup compression is being
used. - Expand SQL Server Agent and review the backup transaction log job.
■ (^) On the secondary server:
- Expand SQL Server Agent and review the copy and restore transaction log
backup jobs.
c26.indd 676c26.indd 676 7/31/2012 9:49:20 AM7/31/2012 9:49:20 AM
http://www.it-ebooks.info