Options for NetBackup for SQL Server restores
Table: Options for restore operations describes the options that are available when you perform restores.
Table: Options for restore operations
Option | Description |
|---|
| These scripting options are available for restoring from a database image: Produce a script that performs a database restore. This script is the default option. Create a script template for moving the selected database. Restore the most recent backup of every read-only filegroup. Create a template for restoring a database, filegroup, or file from the pages that are contained in the selected backup image. The Microsoft SQL Server service must have full access
permission to the folder install_path\Netbackup\dbext\mssql\temp. This option is only available if the image was backed up with the page verification option. NetBackup processes the image for errors, but does not perform a restore.
|
|
| Restore with the SQL Server replace option. |
|
|
Specify one of the SQL Server recovery options. Use this option during a restore if additional backup images must be applied to the database following the current restore. When you use this option, the database is left in a loading state. Restore the last image in a restore sequence. After the recovery operation, the database is ready for use. If you do not select this option, the database is in an intermediate state, and is not usable. If is selected when an intermediate backup is applied, you cannot continue to restore backups; you must restart the restore operation from the beginning. Create and maintain a standby during a transaction log and database restore. This option requires a standby undo log, which by default is placed in install_path\NetBackup\logs\SQLStandBy\. The account that runs the Microsoft SQL Server service must have full access
permission to the SQLStandBy folder. The database is placed in "standby" state following the restore.
|
|
| Select the consistency check to perform after the restore. Output from the consistency check is written to the SQL Server client progress log. You cannot select consistency checking unless the database is restored to the recovered state. If you select consistency checking for a staged recovery, then the check occurs following the last restore. Do not perform consistency checking. Exclude indexes from the consistency check. If indexes are not checked, the consistency check runs significantly faster but is not as thorough. Only the data pages and clustered index pages for each user table are included in the consistency check. The consistency of the non-clustered index pages is not checked. Perform a low overhead check of the physical consistency of the SQL Server database. This option only checks the integrity of the physical structure of the page and record headers. It also checks the consistency between the pages' object ID and index ID and the allocation structures. Include indexes in the consistency check. Any errors are logged. Check for consistency in and between system tables in the specified database.
|
|
| A performance penalty can happen when you use page verification. These options are available if the source object was backed up with torn page detection or checksum verification. |
|
| Perform a complete database restore using the recovery set that NetBackup found.
|
| Restore only the selected transaction log. |
|
| This list contains the controls for you to restore a transaction log. You can restore the log to a point in time that precedes the time when the transaction log was dumped.
Recover the transaction log to a point in time. Recover the transaction log to a transaction log mark. Recover the transaction log to a transaction log mark but after a point in time. Recover the transaction log recovered to a point before the occurrence of a transaction log mark. Recover the transaction log to a point before the occurrence of a transaction log mark but after a point in time. Restore the entire log.
|
|
| The transaction log mark you want to use for recovery. |
|
| Specify the time to which you want the transaction logs restored. |
|
| Start the restore operation immediately.
is disabled if you are logged into a SQL Server instance that is not on the local host. If you generate a script for a non-local host, you must run it from on that host. |
|
| Generate a script that can be started at a later time. |
|
| Start the restore or generate a restore script.
|
