Why doesn't SnapCenter create Snapshots on the SQL instance system tempdb volume?
Applies to
SnapCenter Plug-in for SQL (SCSQL)
Answer
Note: The fact that SCSQL doesn't back up
tempdb
is documented (see below), but it doesn't explain why.Two reasons:
- none of the data in the SQL instance's system
tempdb
s is of any importance, since it's transitional data not required to restart the instance - the I/O on these databases is relatively high, especially during an
ESEUtil
run
Ergo: it makes no sense to back up the tempdb databases, and due to the high I/O, any snapshots would quickly grow and take unnecessary extra space in the volume/aggregate for the ONTAP LUN or SBM3 Share (supported from SC 6.0 onwards) containing the SQL instance's system
tempdb
databases.Additional Information
Reference (1): the SnapCenter documentation with respect to the concept of SCSQL, specifically this phrase:
" You cannot perform backup,restore, clone, and clone lifecycle operations on tempdb system databases. "
Reference (2): the Best Practice Guide for SQL Server with SnapCenter Plug-in for SQL on Page 15, says:
"Do not include the tempdb database in a backup because the data it contains is temporary. Place tempdb on a LUN or an SMB share that is in a storage system volume in which Snapshot copies will not be created"
Note: since SQL Server 2016, the number of tempdb databases depends on the number of core of the system that SQL Server is running on.