Full check, excluding indexes. Select this to 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 nonclustered index pages is not checked.
Full check, including indexes. Select this to include indexes in the consistency check. Any errors are logged. This option is selected by default.
Physical check only (SQL 2000 only). Select this to perform a low overhead check of the physical consistency of the SQL Server 2000 database. This option only checks the integrity of the physical structure of the page and record headers, and the consistency between the pages' object ID and index ID and the allocation structures.
None. Select this if you are doing sequential restores. Do not run a consistency check after a restore until all sequential restores have been done. If a consistency check is selected during a restore, the restore will complete but the consistency check will not be done. Check the job log for this information.
If you need to recover the database after restores are complete, select one of the following consistency checks when you select the Leave database operational option.
Note: Do not select the Alternate drive option when restoring filegroups. Filegroups must be restored to the same drive letter and path that they were backed up from.
Consistency check after restore
Restore options on the Microsoft SQL Server tab (continued)
Other applications of NetBackup for SQL Server Using NetBackup to restore SQL Server from Backup Exec images
Alternate drive for restoring database files
Use this option to select a drive to which SQL database files can be restored if the drive where one or more of the database files previously resided no longer exists.
When a SQL database is backed up, the physical file names (which include the directory path) of the files that make up the database are stored in the backup set by SQL. For example, for the logical file pubs, the physical file name is stored as E:\MSSQL7\DATA\pubs.mdf. If the database must later be restored, SQL uses these same physical file names to target the restore to. During a restore, NetBackup automatically creates any necessary subdirectories that do not exist.
However, if the drive where one or more of the database files previously resided no longer exists, NetBackup moves those files to their original directory path, but on the alternate drive specified.
Using the same example, if drive C: is specified, then the file with the original directory path of E:\MSSQL7\DATA\pubs.mdf is restored to C:\MSSQL7\DATA\pubs.mdf.
If no alternate drive is specified in this situation, the job will fail.