Configuring NetBackup to support database log-shipping
Log shipping is a SQL Server feature that may be employed to enhance the overall availability of your installation. It uses a primary server, which contains the active database, a monitor, and one or more secondary servers. Under log shipping, copies of the transaction log are supplied to the secondary servers on a per-transaction basis to the secondary servers. This configuration allows each secondary server to be in a standby state in case the primary goes offline.
To use log-shipping with NetBackup, both the primary and the secondary should be set up as clients of the same primary server. During transaction log backups truncation is not performed for these databases even if the policy or the protection plan settings enable truncation. SQL Server requires the transaction logs to keep the log-chain intact for the log-shipping feature to function correctly. A message displays in the progress log if this situation occurs: Truncate option ignored on transaction log backup for log shipping primary database: LogShippingDB.
To configure NetBackup to support database log-shipping
- The hosts that contain both databases should specify the same primary server in their server lists.
- Any policy or any protection plan that backs up the primary should also specify the host that contains the secondary database.
See Backing up SQL Server in an environment with log shipping.
- On the primary server, configure permissions for redirected restores for both the primary and the secondary server.