How SnapManager backup data is organized

SnapManager backup data is stored in backup sets. See the following topics for more information:

SnapManager backup sets

A SnapManager backup set consists of all the data you would need to be able to perform a restore, regardless of whether this data exists on the same LUNs or volumes. A backup set contains the following items:

Volume-wide Snapshot copies of the LUNs that store the SQL Server databases (SQL Server data files and SQL Server transaction log files)
The corresponding subdirectory under the SnapInfo directory

SnapInfo directory

The SnapInfo directory stores information about the backup sets, copies of transaction log files, and other data critical to the backup set. The location of this directory is specified when you run the Configuration Wizard. By default, the directory name is SMSQL_SnapInfo. However, you can specify a different directory name.

Every time a SnapManager backup set is created, SnapManager creates a new backup set subdirectory under the SnapInfo directory. SnapManager populates this subdirectory with the transaction logs backed up as part of that backup set, as well as the recovery information for that specific Snapshot copy. A complete backup set consists of this SnapInfo subdirectory and the corresponding Snapshot copies of the LUNs that store the SQL Server databases and transaction logs.

Note
The SnapInfo directory cannot reside on the same LUN that stores the SQL Server database files. See SQL Server database configurations to avoid.

SnapInfo subdirectory names

SnapManager backup set names identify the configuration of the backed-up databases.

Configuration	Format of the SnapInfo subdirectory name
Databases belonging to the SQL Server default instance	The SnapInfo directory name is `SQL__` followed by the SQL Server computer host name: `SQL`__SqlServerName For example, the subdirectory for databases belonging to the default instance of the SQL Server on the Windows host system `CLPUBS-WINSRVR3` would be named as follows: `SQL`__`CLPUBS-WINSRVR3`
Databases belonging to an SQL Server named instance	The SnapInfo directory name is `SQL__` followed by the name of the SQL Server instance: `SQL`__InstanceName For example, the subdirectory for databases belonging to the SQL Server instance `INST2` on the on the Windows host system `ENGR-WINSRVR7` would be named as follows: `SQL`__`INST2`
Multiple databases sharing one LUN	The SnapInfo directory name incorporates the drive letter assigned to the LUN: `VDisk`__DriveLetter For example, the subdirectory for all the databases sharing one LUN on drive `G:\` would be named as follows: `VDisk`__`G`
Multiple databases sharing two LUNs	The SnapInfo directory name incorporates both the drive letters assigned to the two LUNs: `VDisk`__FirstDriveLetter&SecondDriveLetter For example, the subdirectory for all the databases sharing the two LUNs on drive `F:\` and drive `K:\` would be named as follows: `VDisk`__`F&K`

SnapManager backup set names

SnapManager backup set names identify the configuration of the backed-up databases. These names are displayed in the SnapManager Restore tab and in the SnapManager Restore Wizard.

Configuration	Format of the backup set name
Databases belonging to the SQL Server default instance	The backup set name is the same as the SQL Server computer host name: SqlServerName For example, a backup set for databases belonging to the default instance of the SQL Server on the Windows host system `CLPUBS-WINSRVR3` would be named as follows: `CLPUBS-WINSRVR3`
Databases belonging to an SQL Server named instance	The backup set name is the name of the SQL Server instance: InstanceName For example, a backup set for databases belonging to the SQL Server instance `INST2` on the on the Windows host system `ENGR-WINSRVR7` would be named as follows: `INST2`
Multiple databases sharing one LUN	The backup set name incorporates the drive letter assigned to the LUN: `VDisk`__DriveLetter For example, a backup set for all the databases sharing one LUN on drive `G:\` would be named as follows: `VDisk`__`G`
Multiple databases sharing two LUNs	The backup set name incorporates both the drive letters assigned to the two LUNs: `VDisk`__FirstDriveLetter&SecondDriveLetter For example, a backup set for all the databases sharing the two LUNs on drive `F:\` and drive `K:\` would be named as follows: `VDisk`__`F&K`

SnapManager Snapshot naming conventions

The Snapshot copies created by SnapManager backup operations are automatically named by Data ONTAP. The name of each Snapshot copy created during a SnapManager backup operation includes information that identifies the Snapshot copy contents.

SQL Server name

Database Snapshot copy names and SnapInfo directory Snapshot copy names include the name of the SQL Server for which the backup was made (indicated in this document by the variable SqlServerName).

Backup management group

Database Snapshot copy names and SnapInfo directory Snapshot copy names include the backup management group to which you assigned the full database backup. SnapManager provides backup management groups for designating various levels of backup retention: Standard, Daily, and Weekly:

If you assign a full database backup to the Standard backup management group, the Snapshot copy names for the databases and SnapInfo directory do not include a backup management group name.
If you assign a full database backup to the Daily or Weekly management groups, the Snapshot copy names for the databases and SnapInfo directory include the name of the backup management group (indicated in this document by the variable BackupMgmtGrp).

For more information about using backup management groups, see Using backup management groups in backup and verification.

Most recent backup

SnapManager 1.0 for Microsoft SQL Server always appended the string recent to the name of the most recently created Snapshot copy. This was to allow external scripts--for example, archive scripts-- to be able to identify and operate on the most recent Snapshot copy. With the addition of the Run Command After Operation feature in SnapManager 1.5 for Microsoft SQL Server, appending recent is no longer necessary because the scripts can be integrated into the backup process.

Like SnapManager 1.5 and 2.0 for Microsoft SQL Server, SnapManager 2.1 for Microsoft SQL Server offers two conventions for naming backup Snapshot copies:

Unique backup naming. The most recent Snapshot copy name contains the Snapshot copy creation date and time (indicated by the variable date_time) instead of the string recent. The most recent backup is identified by the Snapshot copy name with the most recent date and time.
Generic backup naming. The most recent Snapshot copy name contains the string recent instead of a date and timestamp. The most recent backup is identified by the Snapshot copy name that includes the string recent. This is the Snapshot copy naming convention used by SnapManager 1.0 for Microsoft SQL Server.

The backup naming convention is selected in the Full Database Backup tab of the Backup Setting dialog box. For information about using this dialog box, see Configuring the profile of a full database backup.

SQL Server database Snapshot names

For SQL Server database backups, Snapshot copy names begin with the string sqlsnap__.

Backup management group	Format of the SQL Server database Snapshot copy name
Standard	Depending on the naming convention selected: `sqlsnap`__SqlServerName_date_time `sqlsnap`__SqlServerName__`recent`
Daily or Weekly	Depending on the naming convention selected: `sqlsnap`__SqlServerName_date_time__BackupMgmtGrp `sqlsnap`__SqlServerName__`recent`

Backup management group

Format of the SQL Server database Snapshot copy name

Standard

Depending on the naming convention selected:

sqlsnap__SqlServerName_date_time
sqlsnap__SqlServerName__recent

Daily or Weekly

Depending on the naming convention selected:

sqlsnap__SqlServerName_date_time__BackupMgmtGrp
sqlsnap__SqlServerName__recent

SnapInfo directory Snapshot names

For SnapInfo directory backups, Snapshot copy names begin with the string sqlinfo__.

Backup management group	Format of the SnapInfo directory Snapshot copy name
Standard	Depending on the naming convention selected: `sqlinfo`__SqlServerName_date_time `sqlinfo`__SqlServerName__`recent`
Daily or Weekly	Depending on the naming convention selected: `sqlinfo`__SqlServerName_date_time__BackupMgmtGrp `sqlinfo`__SqlServerName__`recent`

Backup management group

Format of the SnapInfo directory Snapshot copy name

Standard

Depending on the naming convention selected:

sqlinfo__SqlServerName_date_time
sqlinfo__SqlServerName__recent

Daily or Weekly

Depending on the naming convention selected:

sqlinfo__SqlServerName_date_time__BackupMgmtGrp
sqlinfo__SqlServerName__recent