19.7. Managing Changing Roles
For business continuity, a high-availability solution must allow smooth role-switching between the current primary and secondary servers. To accomplish this goal, log shipping requires that certain dependencies are available on the secondary server, because the scope of log shipping is at the database level. Any object outside of the log-shipped database will not be maintained by log shipping. For example, SQL Server logins are contained in the master database, and SQL jobs are contained in msdb. Therefore, these dependencies and others need to be systematically maintained by other procedures to enable users to connect to the secondary server after it becomes the new primary server. Furthermore, a process needs to be developed to redirect the application to the new primary server.
19.7.1. Synchronizing Dependencies
Log shipping applies changes that occur inside the log-shipping database but it does not maintain any outside dependencies. Moreover, log shipping cannot be used to ship system databases. Newly added logins, new database users, jobs, and other dependencies that live in other databases are not synchronized by log shipping. In a failover scenario, when users attempt to log in to the secondary server's database, they will not have a login there. Moreover, any jobs configured on the primary server will not be present either; and if the primary server uses linked servers to access a remote SQL Server, then the database operations would fail ...
Get Professional Microsoft® SQL Server® 2008 Administration now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
