Advanced Restore Options (Options)
Specifies the type of restore job.
Specifies that the restore operation must restore the selected databases beginning with the most recent full backup and then applying differential and/or transaction log backups up to the selected restore time.
Specifies that the restore operation must perform a step restore by applying the selected transaction log.
Whether the logs are applied to a SQL step restore operation, this option is available only under the following conditions:
- Single database restores
- The restore destination is the source computer
- The database backup and restore histories have not been removed from the SQL Server's history tables
- The selected database was previously restored to STANDBY state for SQL step restore
This option is not available for:
- Instance restores
- Multiple database restores
- File or File Group restores
- When restoring data protection operations that used VSS to create the snapshot
Specifies that the restore operation must recover the databases to an available online state. No data is actually written. All other options are disabled when this option is selected.
Restores transaction marks that exist in the transaction log. For transaction mark restores, you must administer and maintain your Microsoft SQL Server transaction marks so that they are available for use by the SQL Server Agent. This option is enabled when the database selected for restore has transaction marks in the transaction log. The Restore Time list displays a list of transaction marks that exist in the selected database for the given restore time. For some SQL Server environments, you may have multiple databases for which absolute synchronization of the databases after a restore is critical. When multiple databases are being restored, this list shows only those marks that are common in name and time stamp to all the selected databases to run an in-sync restore.
Partial restores, known as "Piecemeal Restore" in SQL Server 2005, allow databases that contain multiple filegroups to be restored and recovered in stages. The process starts with a restore of the primary filegroup, then a restore or recovery of one or more secondary filegroups.
Allows restores of the latest backup data on one or more non system secured database in the SQL Server. You can use this feature to create a spare copy of the primary SQL Server database (hot standby server) within the same domain, a different domain, or across a Wide Area Network (WAN).
Only available when the Latest Backup Data option is selected. Select this option if you wish to include only the transaction log backups completed since the last restore operation. The restore operation will then skip any full backup jobs completed since the last restore operation.
- Before selecting this option verify that the databases are in standby state or restoring state.
- If you do NOT select the Apply Log Backups Only option and the database already exists, all backup jobs completed since the last restore operation will automatically be restored.
- If you do NOT select the Apply Log Backups Only option and the database does not exist, the software will automatically perform a full restore of the database.
Select this option to NOT restore the last full backup since the specified date and time, but to instead restore only the transaction log backups. This option can be useful if the latest full backup has already been restored by third-party software and thus a restore of the SQL Agent full backup is not necessary. Note that in such a case, this option only needs to be selected if a SQL Agent full backup exists which is later than the full backup currently restored on the client by a third-party software.
Select this option to attain exclusive access to a database for restore. Database restore operation fails if exclusive access to the database cannot be obtained.
Select this option to restore the backed up data to a disk either on the same or on a different SQL Server. The restored data on the disk can be later used to perform database restore using SQL Management Studio or any other third party tool.
To restore the data to disk on the same SQL Server, browse or type the path of the destination SQL Server.
To restore the data to disk on a different SQL server, on the General tab of the SQL Restore Options dialog box, select a server from the Destination Server list, and then select the Unconditionally overwrite existing database or files check box. The existing database files are overwritten. If you do not select this check box, the restore job prevents accidental overwrite of data files by failing the job.
- You must rename the databases before restoring them to a disk, either on the same or on a different SQL Server.
- For SnapProtect or VSS-enabled backups, the log backups restored as *.bak files cannot be applied to the restored full and differential backups. You can discard these files.
- For each backup type, one file is created per stream. Naming convention of the file is <DB_name>_<Stream#>_<BackupType>_<DayofWeek, Month, Day, Time, Year>.bak, where date and time are the date and time of the database backup.
- For SnapProtect, VSS-enabled, or availability group backups, ensure that the destination database and the source database have different names.
- For SnapProtect or VSS-enabled backups, if the destination database and the source database have same names, during the Restore to Disk operation, the database to be restored does not get attached to the destination SQL instance. To avoid this situation, manually detach the database on the destination SQL instance prior to running the Restore to Disk operation.
- For SnapProtect or VSS-enabled backups, you can rename the database, but you cannot change the physical names.
Attach to SQL Server (Applies only for VSS and SNAP)
For VSS and SnapProtect backups, during restore to disk the actual database files (MDF, LDF, NDF) will be copied to the folder location provided by the user on the destination SQL Server machine. In this scenario the database can be restored with different names while physical names should be left intact. All log backups which will be restored as *.bak files will not be applied to restored Full and Differential backups. This option is applicable for VSS and SnapProtect backups performed using SnapProtect version 10 or later.
Select this option to run a restore validation job.
On successful validation, the restore job returns a successful message in the SnapProtect Event Viewer:
"Query Result [the backup set on file 1 is valid]"
Restore validation job validates the following before running a restore operation:
- The volumes have sufficient permission to restore the database files.
- The header fields of the database pages exist at the destination.
- The restore destination device has sufficient space.
Select this option to calculate the checksum on a page during backup as it writes to a disk and then calculates the checksum on the page during restore as it reads from disk. Mismatched values returned during the validation are indicative of corrupted database or page corruption on disk.
Note: If you backed up data without selecting the Checksum check box, do not select this check box while restoring that data, else the restore job will fail.
Select this option to configure the SQL Server to ignore the errors encountered during restores and continue till the job completes.
Note: Continue After Error check box overrides the Checksum check box on restoring data.
Select this option to restore the database in a state where only the owner of the database can access the database.