Improved backup retention

Prev Page Next Page
Recovery models
Main backup types
Backing up the database files by copying
The transaction log
Transaction log restore sequence
Log sequence numbers
Truncating and shrinking the transaction log
Backing up the tail
Inside the transaction log
So, what's in a backup file?
Test: A full backup does not contain deleted data
Verifying backup files
Verifying backup files on a budget
Cumulative backups
Recovering individual tables
Backup and restore history details
Backup reads and writes
Speeding up backups
Backup speed details
Speeding up restores
Restore state affects speed too
Backup and restore rights
Log shipping
Log shipping in SQL Server 2000
Setting up log shipping using Enterprise Manager
Checking the set up
Log shipping in SQL Server 2005
Setting up log shipping using Management Studio
Checking the set up
Log shipping status report
Log shipping in SQL Backup
Using the CopyTool utility
3rd party backup applications
VDI versions
VDI errors
SQL Backup - beyond compression
Restoring a chain of transaction log backups
Restoring to the latest possible state
Backing up multiple databases
Backup retention
Making a copy of the backup file
Backup file naming conventions
Restoring the latest backup set
Network resilience
Integrated database verification
Database file relocation
Improved backup retention
High-availability group support
Common SQL Backup issues
Installation checklist
Setting up rights
Configuring service rights
Backup data
Hanging issues
Common backup and restore errors
Error 3201 - when performing a backup to a network share
Full database backup file is larger than database size
Error 3205 - Too many backup devices specified for backup or restore
Error 4305 - an earlier transaction log backup is required
Bringing a database that is in recovery or read-only mode online
Using bulk-logged recovery model but transaction log backup is still large
Error 14274 - unable to delete SQL Server Agent job
Error messages when restoring from different versions of SQL Server.
vdi error codes
Restore speed details
Help, my transaction log file is huge!
Mirror or log ship

# available only in SQL Backup 7.0 and newer

In prior versions of SQL Backup, you had the option of deleting old backup files using the ERASEFILES option.  If your database files were backed up locally, and these files are then copied to a network share, you could implement different retention periods for the local and remote files, using a combination of the ERASEFILES and ERASEFILES_REMOTE options.

However, you would have problems implementing different retention periods if both your backup file and copies of it were kept locally, or if both were kept on remote shares.  In SQL Backup 7, two new options were introduced: ERASEFILES_PRIMARY and ERASEFILES_SECONDARY.

The retention period for ERASEFILES_PRIMARY applies to the backup file and any mirrored files (using the MIRRORFILE option).  The retention period in ERASEFILES_SECONDARY applies to any copies of the backup files, created using the COPYTO option.

Say you have a backup job that backs up your databases to a network share (\\fileserver_backups\backups\) and a copy of the backup file is made to a different network share (\\fileserver_backupcopies\backupcopies\).  You want to retain 5 days worth of backups on '\\fileserver_backups\backups\' and 10 days worth of backups on '\\fileserver_backupcopies\backupcopies\'.  You can do this using the following:



Document history
5/8/2012    Initial release.    
Copyright 2008 - 2017 Yohz Ventures Sdn Bhd. All rights reserved.
All product and company names are trademarks or registered trademarks of their respective owners.