Use replace option

Restore with the SQL Server replace option.

Scripting

These scripting options are available for restoring from a database image.

Restore selected object

Produce a script that performs a database restore. This script is the default option.

Create a move template

Create a script template for moving the selected database.

Create partial database restore template

(SQL Server 2000 only) Create a template for a partial database restore.

Restore read-only filegroups

(SQL Server 2005 or later) Restore the most recent backup of every read-only filegroup.

Create a page restore template

(SQL Server 2005 or later) Create a template for restoring a database, filegroup, or file from the pages that are contained in the selected backup image.

(Verify backup image, but don't restore

SQL Server 2005 or later) 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.

Recovery

Specify one of the SQL Server recovery options.

Not recovered

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.

Recovered

Select this option when restoring the last image in a restore sequence. After the recovery operation, the database is ready for use. If recover database is not performed, the database is in an intermediate state, and is not usable. If Recovered is selected when an intermediate backup is applied, you cannot continue to restore backups; you must restart the restore operation from the beginning.

Standby

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 database is placed in "standby" state following the restore.

Consistency Check

Select the consistency check to be performed 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.

None

Do not perform consistency checking.

Full check, excluding indexes

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.

Full check, including indexes

Include indexes in the consistency check. Any errors are logged.

Check catalog

Check for consistency in and between system tables in the specified database.

Physical check only

(SQL Server 2000 or later) Select this item to perform a low overhead check of the physical consistency of the SQL Server 2000 or later 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.

Page verification

(SQL Server 2005 or later) These options are available if the source object was backed up with torn page detection or checksum verification.

A performance penalty can happen when using page verification.

Do not perform verification

Do not include page verification in the restore script.

Perform verification

Include page verification in the restore script and stop the restore if an error is encountered.

Stage full recovery

Select this option to recover the database by using the recovery set that NetBackup found. If the transaction log that you select does not belong to a recovery set, this option is disabled.

Restore selected transaction log

Select this option to restore only the selected transaction log. If the transaction log that you select does not belong to a recovery set, this option is disabled.

Transaction log recovery options

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. The individual entries in this group are only enabled if you selected a transaction log backup.

To point in time

Select this option to have the transaction log recovered to a point in time.

To transaction log mark

Select this option to have the transaction log recovered to a transaction log mark. With this option, you must enter a transaction log mark name.

To transaction log mark but after

Select this option to have the transaction log recovered to a transaction log mark but after a point in time. With this option, you must enter a transaction log mark name.

Before transaction log mark

Select this option to have the transaction log recovered to a point before the occurrence of a transaction log mark. With this option, you must enter a transaction log mark name.

Before transaction log mark but after

Select this option recover the transaction log to a point before the occurrence of a transaction log mark but after a point in time. With this option, you must enter a transaction log mark name.

MM, YYYY, DD, HH, MM, SS am, pm

Transaction log mark

Launch immediately

Start the restore operation immediately.

Launch 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, it must be executed on that host.

Save

Generate a script that can be started at a later time.