Backup file naming conventions

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

It's a common requirement that a backup file be named with a certain naming convention, so as to allow for it to be quickly identified to as its contents and date it was created.  Using standard T-SQL BACKUP syntax, you must explicitly name the backup files.  To name your files dynamically, you would need to write additional scripts to form the backup file name.

With SQL Backup, you can use tags to dynamically name your backup file.  You can use the <TYPE> tag to identify the type of backup the file contains e.g.


You can also use the <SERVER>, <INSTANCE> and <DATABASE> tags to identify the source of the backup file e.g.


Lastly, there is the <DATETIME> tag that allows you to add a timestamp to the name, and also format the timestamp in various ways e.g.


You can combine all the above tags to generate a file name e.g.


Notice that in the above example, tags were used in place of subdirectory names.  If the subdirectory does not exist, SQL Backup will create it for you (if it has the necessary permissions) prior to backing up your database.

Finally, you can establish a standard naming convention, and simply use the <AUTO> option to generate a file name using that standard naming convention.


Document history
7/12/2010    Initial release.    
Copyright 2008 - 2021 Yohz Ventures Sdn Bhd. All rights reserved.
All product and company names are trademarks or registered trademarks of their respective owners.