Log Shipping Transaction Log Backup Settings
Use this dialog box to configure and modify the transaction log backup settings for a log shipping configuration.
For an explanation of log shipping concepts, see About Log Shipping (SQL Server).
- Network path to the backup folder
Type the network share to your backup folder in this box. The local folder where your transaction log backups are saved must be shared so that the log shipping copy jobs can copy these files to the secondary server. You must grant read permissions on this network share to the proxy account under which the copy job will run at the secondary server instance. By default, this is the SQLServerAgent service account of the secondary server instance, but an administrator can choose another proxy account for the job.
- If the backup folder is located on the primary server, type the local path to the folder
Type the local drive letter and path to the backup folder if the backup folder is located on the primary server. If the backup folder is not located on the primary server, you can leave this blank.
If you specify a local path here, the BACKUP command will use this path to create the transaction log backups; otherwise, if no local path is specified, the BACKUP command will use the network path specified in the Network path to the backup folder box.
If the SQL Server service account is running under the local system account on the primary server, you must create the backup folder on the primary server and specify the local path to that folder here. The SQL Server service account of the primary server instance must have Read and Write permissions on this folder.
- Delete files older than
Specify the length of time you want transaction log backups to remain in your backup directory before being deleted.
- Alert if no backup occurs within
Specify the amount of time you want log shipping to wait before raising an alert that no transaction log backups have occurred.
- Job name
Displays the name of the SQL Server Agent job that is used to create the transaction log backups for log shipping. When first creating the job, you can modify the name by typing in the box.
Displays the current schedule for backing up the transaction logs of the primary database. Before the backup job has been created, You can modify this schedule by clicking Schedule.... After the job has been created, you can modify this schedule by clicking Edit Job....
Modify the schedule that is created when the SQL Server Agent job is created.
- Edit Job...
Modify the SQL Server Agent job parameters for the job that performs transaction log backups on the primary database.
- Disable this job
Disable the SQL Server Agent job from creating transaction log backups.
SQL Server 2008 Enterprise (or a later version) supports backup compression.
- Set backup compression
In SQL Server 2008 Enterprise (or a later version), select one the following backup compression values for the log backups of this log shipping configuration:
Use the default server setting
Click to use the server-level default.
This default is set by the backup compression default server-configuration option. For information about how to view the current setting of this option, see View or Configure the backup compression default Server Configuration Option.
Click to compress the backup, regardless of the server-level default.
By default, compression significantly increases CPU usage, and the additional CPU consumed by the compression process might adversely impact concurrent operations. Therefore, you might want to create low-priority compressed backups in a session whose CPU usage is limited by the Resource Governor. For more information, see Use Resource Governor to Limit CPU Usage by Backup Compression (Transact-SQL).
Do not compress backup
Click to create an uncompressed backup, regardless of the server-level default.