Using database snapshots for SQL Server

Last published : Apr 02, 2026
SQL database snapshots enable you to quickly revert a database back to the state it was in when the database snapshot was created. When you use a database snapshot, a full restore of the host database is not required to revert the database. However, the changes that are made to the host between the time a database snapshot is created and the point at which it is reverted are lost.
The Backup Exec SQL Agent works with the SQL database to create database snapshots, which are read-only, point-in-time copies of an existing host database. When Backup Exec runs a SQL backup job using the Database Snapshot backup method, a request is sent to the host database instructing it to create a database snapshot.
Note: The snapshot backup method for SQL databases is only supported by SQL Server Enterprise Edition.
Database snapshots cannot be backed up to storage media. Rather, they are written to a SQL snapshot file on disk. After running the database snapshot job, Backup Exec creates history and job log information to indicate the job's status.
Because database snapshots cannot be backed up, all database snapshots will be lost if the disk where the host database is installed fails. Therefore, database snapshots should not be used as your sole database protection strategy. They should be used in conjunction with an overall Backup Exec database protection strategy that includes full, differential, and transaction log backups of the SQL database.
For more information, see your Microsoft SQL documentation.
Note: SQL database snapshots are not the same as Microsoft Virtual Shadow Copy Service (VSS) snapshots. Whereas VSS snapshots enable you to create point-in-time snapshots of disk volumes and shares, database snapshots enable you to create point-in-time copies of SQL databases. Note: SQL database snapshot catalog information that refers to deleted database snapshots is periodically removed from the catalogs. If backup media is re-cataloged, the database snapshot catalog information will be periodically removed again.
SQL Server database snapshots created with Backup Exec can be used to revert a SQL database back to the state it was in at a previous point in time, without having to run a full database restore job.
When you view SQL database snapshots in the resource view in the Restore Wizard, they appear as backup sets, in chronological order with the most recent snapshot appearing first.
The following caveats apply when reverting a database:
  • You cannot undo a SQL database that has been reverted.
  • Before reverting a database, Backup Exec deletes all existing database snapshots with the exception of the snapshot used for the revert. After being deleted, the database snapshots cannot be recovered.
  • You cannot redirect a database snapshot restore job.