TechNet
Export (0) Print
Expand All

RESTORE HEADERONLY (Transact-SQL)

 

THIS TOPIC APPLIES TO:yesSQL Server (starting with 2008)noAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

Returns a result set containing all the backup header information for all backup sets on a particular backup device in SQL Server.

System_CAPS_ICON_note.jpg Note


For the descriptions of the arguments, see RESTORE Arguments (Transact-SQL).

Topic link icon Transact-SQL Syntax Conventions


RESTORE HEADERONLY 
FROM <backup_device> 
[ WITH 
 {
--Backup Set Options
   FILE = { backup_set_file_number | @backup_set_file_number } 
 | PASSWORD = { password | @password_variable } 

--Media Set Options
 | MEDIANAME = { media_name | @media_name_variable } 
 | MEDIAPASSWORD = { mediapassword | @mediapassword_variable }

--Error Management Options
 | { CHECKSUM | NO_CHECKSUM } 
 | { STOP_ON_ERROR | CONTINUE_AFTER_ERROR }

--Tape Options
 | { REWIND | NOREWIND } 
 | { UNLOAD | NOUNLOAD }  
 } [ ,...n ]
]
[;]

<backup_device> ::=
{ 
   { logical_backup_device_name |
      @logical_backup_device_name_var }
   | { DISK | TAPE } = { 'physical_backup_device_name' |
       @physical_backup_device_name_var } 
}


For descriptions of the RESTORE HEADERONLY arguments, see RESTORE Arguments (Transact-SQL).

For each backup on a given device, the server sends a row of header information with the following columns:

System_CAPS_ICON_note.jpg Note


RESTORE HEADERONLY looks at all backup sets on the media. Therefore, producing this result set when using high-capacity tape drives can take some time. To get a quick look at the media without getting information about every backup set, use RESTORE LABELONLY or specify FILE = backup_set_file_number.

System_CAPS_ICON_note.jpg Note


Due to the nature of Microsoft Tape Format, it is possible for backup sets from other software programs to occupy space on the same media as MicrosoftSQL Server backup sets. The result set returned by RESTORE HEADERONLY includes a row for each of these other backup sets.

Column nameData typeDescription for SQL Server backup sets
BackupNamenvarchar(128)Backup set name.
BackupDescriptionnvarchar(255)Backup set description.
BackupTypesmallintBackup type:

 1 = Database

 2 = Transaction log

 4 = File

 5 = Differential database

 6 = Differential file

 7 = Partial

 8 = Differential partial
ExpirationDatedatetimeExpiration date for the backup set.
CompressedBYTE(1)Whether the backup set is compressed using software-based compression:

 0 = No

 1 = Yes
PositionsmallintPosition of the backup set in the volume (for use with the FILE = option).
DeviceTypetinyintNumber corresponding to the device used for the backup operation.

Disk:

 2 = Logical

 102 = Physical

Tape:

 5 = Logical

 105 = Physical

Virtual Device:

 7 = Logical

 107 = Physical

Logical device names and device numbers are in sys.backup_devices; for more information, see sys.backup_devices (Transact-SQL).
UserNamenvarchar(128)User name that performed the backup operation.
ServerNamenvarchar(128)Name of the server that wrote the backup set.
DatabaseNamenvarchar(128)Name of the database that was backed up.
DatabaseVersionintVersion of the database from which the backup was created.
DatabaseCreationDatedatetimeDate and time the database was created.
BackupSizenumeric(20,0)Size of the backup, in bytes.
FirstLSNnumeric(25,0)Log sequence number of the first log record in the backup set.
LastLSNnumeric(25,0)Log sequence number of the next log record after the backup set.
CheckpointLSNnumeric(25,0)Log sequence number of the most recent checkpoint at the time the backup was created.
DatabaseBackupLSNnumeric(25,0)Log sequence number of the most recent full database backup.

 DatabaseBackupLSN is the “begin of checkpoint” that is triggered when the backup starts. This LSN will coincide with FirstLSN if the backup is taken when the database is idle and no replication is configured.
BackupStartDatedatetimeDate and time that the backup operation began.
BackupFinishDatedatetimeDate and time that the backup operation finished.
SortOrdersmallintServer sort order. This column is valid for database backups only. Provided for backward compatibility.
CodePagesmallintServer code page or character set used by the server.
UnicodeLocaleIdintServer Unicode locale ID configuration option used for Unicode character data sorting. Provided for backward compatibility.
UnicodeComparisonStyleintServer Unicode comparison style configuration option, which provides additional control over the sorting of Unicode data. Provided for backward compatibility.
CompatibilityLeveltinyintCompatibility level setting of the database from which the backup was created.
SoftwareVendorIdintSoftware vendor identification number. For SQL Server, this number is 4608 (or hexadecimal 0x1200).
SoftwareVersionMajorintMajor version number of the server that created the backup set.
SoftwareVersionMinorintMinor version number of the server that created the backup set.
SoftwareVersionBuildintBuild number of the server that created the backup set.
MachineNamenvarchar(128)Name of the computer that performed the backup operation.
FlagsintIndividual flags bit meanings if set to 1:

 1 = Log backup contains bulk-logged operations.

 2 = Snapshot backup.

 4 = Database was read-only when backed up.

 8 = Database was in single-user mode when backed up.

 16 = Backup contains backup checksums.

 32 = Database was damaged when backed up, but the backup operation was requested to continue despite errors.

 64 = Tail log backup.

 128 = Tail log backup with incomplete metadata.

 256 = Tail log backup with NORECOVERY.

 Important: We recommend that instead of Flags you use the individual Boolean columns (listed below starting with HasBulkLoggedData and ending with IsCopyOnly).
BindingIDuniqueidentifierBinding ID for the database. This corresponds to sys.database_recovery_status****database_guid. When a database is restored, a new value is assigned. Also see FamilyGUID (below).
RecoveryForkIDuniqueidentifierID for the ending recovery fork. This column corresponds to last_recovery_fork_guid in the backupset table.

For data backups, RecoveryForkID equals FirstRecoveryForkID.
Collationnvarchar(128)Collation used by the database.
FamilyGUIDuniqueidentifierID of the original database when created. This value stays the same when the database is restored.
HasBulkLoggedDatabit1 = Log backup containing bulk-logged operations.
IsSnapshotbit1 = Snapshot backup.
IsReadOnlybit1 = Database was read-only when backed up.
IsSingleUserbit1 = Database was single-user when backed up.
HasBackupChecksumsbit1 = Backup contains backup checksums.
IsDamagedbit1 = Database was damaged when backed up, but the backup operation was requested to continue despite errors.
BeginsLogChainbit1 = This is the first in a continuous chain of log backups. A log chain begins with the first log backup taken after the database is created or when it is switched from the Simple to the Full or Bulk-Logged Recovery Model.
HasIncompleteMetaDatabit1 = A tail-log backup with incomplete meta-data.

For information about tail-log backups with incomplete backup metadata, see Tail-Log Backups (SQL Server).
IsForceOfflinebit1 = Backup taken with NORECOVERY; the database was taken offline by backup.
IsCopyOnlybit1 = A copy-only backup.

A copy-only backup does not impact the overall backup and restore procedures for the database. For more information, see Copy-Only Backups (SQL Server).
FirstRecoveryForkIDuniqueidentifierID for the starting recovery fork. This column corresponds to first_recovery_fork_guid in the backupset table.

For data backups, FirstRecoveryForkID equals RecoveryForkID.
ForkPointLSNnumeric(25,0) NULLIf FirstRecoveryForkID is not equal to RecoveryForkID, this is the log sequence number of the fork point. Otherwise, this value is NULL.
RecoveryModelnvarchar(60)Recovery model for the Database, one of:

FULL

BULK-LOGGED

SIMPLE
DifferentialBaseLSNnumeric(25,0) NULLFor a single-based differential backup, the value equals the FirstLSN of the differential base; changes with LSNs greater than or equal to DifferentialBaseLSN are included in the differential.

For a multi-based differential, the value is NULL, and the base LSN must be determined at the file level. For more information, see RESTORE FILELISTONLY (Transact-SQL).

For non-differential backup types, the value is always NULL.

For more information, see Differential Backups (SQL Server).
DifferentialBaseGUIDuniqueidentifierFor a single-based differential backup, the value is the unique identifier of the differential base.

For multi-based differentials, the value is NULL, and the differential base must be determined per file.

For non-differential backup types, the value is NULL.
BackupTypeDescriptionnvarchar(60)Backup type as string, one of:

DATABASE

TRANSACTION LOG

FILE OR FILEGROUP

DATABASE DIFFERENTIAL

FILE DIFFERENTIAL PARTIAL

PARTIAL DIFFERENTIAL
BackupSetGUIDuniqueidentifier NULLUnique identification number of the backup set, by which it is identified on the media.
CompressedBackupSizebigintByte count of the backup set. For uncompressed backups, this value is the same as BackupSize.

To calculate the compression ratio, use CompressedBackupSize and BackupSize.

During an msdb upgrade, this value is set to match the value of the BackupSize column.
containmenttinyint not NULLApplies to: SQL Server 2012 through SQL Server 2016.

Indicates the containment status of the database.

0 = database containment is off

1 = database is in partial containment
KeyAlgorithmnvarchar(32)Applies to: SQL Server (SQL Server 2014 (PCU1) through current version.

The encryption algorithm used to encrypt the backup. NO_Encryption indicates that the backup was not encrypted. When the correct value cannot be determined the value should be NULL.
EncryptorThumbprintvarbinary(20)Applies to: SQL Server (SQL Server 2014 (PCU1) through current version.

The thumbprint of the encryptor which can be used to find certificate or the asymmetric key in the database. When the backup was not encrypted, this value is NULL.
EncryptorTypenvarchar(32)Applies to: SQL Server (SQL Server 2014 (PCU1) through current version.

The type of encryptor used: Certificate or Asymmetric Key. When the backup was not encrypted, this value is NULL.
System_CAPS_ICON_note.jpg Note


If passwords are defined for the backup sets, RESTORE HEADERONLY shows complete information for only the backup set whose password matches the specified PASSWORD option of the command. RESTORE HEADERONLY also shows complete information for unprotected backup sets. The BackupName column for the other password-protected backup sets on the media is set to '***Password Protected***', and all other columns are NULL.

A client can use RESTORE HEADERONLY to retrieve all the backup header information for all backups on a particular backup device. For each backup on the backup device, the server sends the header information as a row.

A backup operation may optionally specify passwords for a media set, a backup set, or both. When a password has been defined on a media set or backup set, you must specify the correct password or passwords in the RESTORE statement. These passwords prevent unauthorized restore operations and unauthorized appends of backup sets to media using Microsoft SQL Server tools. However, a password does not prevent overwrite of media using the BACKUP statement's FORMAT option.

System_CAPS_ICON_important.jpg Important


The protection provided by this password is weak. It is intended to prevent an incorrect restore using SQL Server tools by authorized or unauthorized users. It does not prevent the reading of the backup data by other means or the replacement of the password. This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.The best practice for protecting backups is to store backup tapes in a secure location or back up to disk files that are protected by adequate access control lists (ACLs). The ACLs should be set on the directory root under which backups are created.

Permissions

Obtaining information about a backup set or backup device requires CREATE DATABASE permission. For more information, see GRANT Database Permissions (Transact-SQL).

The following example returns the information in the header for the disk file C:\AdventureWorks-FullBackup.bak.

RESTORE HEADERONLY 
FROM DISK = N'C:\AdventureWorks-FullBackup.bak' 
WITH NOUNLOAD;
GO

BACKUP (Transact-SQL)
backupset (Transact-SQL)
RESTORE REWINDONLY (Transact-SQL)
RESTORE VERIFYONLY (Transact-SQL)
RESTORE (Transact-SQL)
Backup History and Header Information (SQL Server)
Enable or Disable Backup Checksums During Backup or Restore (SQL Server)
Media Sets, Media Families, and Backup Sets (SQL Server)
Recovery Models (SQL Server)

Community Additions

ADD
Show:
© 2016 Microsoft