NetVault Plug-in for SQL Server 12.2 - User Guide

•

Windows Authentication: With Windows Authentication, you connect through a Microsoft Windows user account. SQL Server validates the account name and password using information in the Windows OS. This method is the default, and is much more secure than Mixed Mode, which allows a combination of Windows authentication and SQL Server Authentication.

•

SQL Server Authentication: With SQL Server Authentication on SQL Server 2008 or earlier, you must provide the user name and password for a SQL Server user with the sysadmin role. With SQL Server Authentication on SQL Server 2012 or later the sysadmin role is not supported. However, you can assign the sysadmin role to a domain user account, such as Administrator, or you can set the SQL Server service to run using the Log on as option set to a domain user that has the privileges. For a system that is not part of a domain, you can assign the role to a local user or you can set the SQL Server service to run under the local user that has the privileges. For more information, see Setting up SQL Server Authentication for SQL Server 2012 or later (Windows only).

•

•

•

•

•

Error Encountered During Checksum: SQL Server lets you specify the action that should be taken if an error is encountered when performing checksums on backups and restores. You can specify the default action to take on encountering checksum errors by selecting one of the following two options from the list:

•

Continue after error: This option is the default set during the plug-in installation. With this value selected, the backup or restore job continues in spite of checksum errors.

•

Stop on error: Select this option to set it as the default action. With this value selected, the backup or restore job stops when a checksum error is encountered.

•

New Database Found in Differential/Incremental Backup: This field applies only to Online VDI backups. If a new database is found while performing Transaction Log or Differential Database backups and the Instance Node is selected on the NetVault Backup Selections page, you can ignore it or take a full backup. You can set this action globally for all Transaction Log and Differential Database backups by selecting the applicable action from the list:

•

Do full database backup: This option is the default set during the plug-in installation. Retain this option to perform a full backup of all databases added since the last Full Database backup.

•

Ignore: Select this option to ignore databases created since the last Full Database backup; that is, databases created after the last backup are left out of the Transaction Log or Differential Database backup.

•

Check SQL Service Agent Status When Restoring msdb Database: If the restore job includes the msdb database, use this option to instruct the plug-in to check the running status of the SQL Server Service Agent. To restore the msdb database and to ensure exclusive access to the database, the SQL Server Service Agent must not be running.

•

AlwaysOn Availability Groups Cluster: Use this option to notify the plug-in that your environment consists of AlwaysOn Availability Groups. if AlwaysOn Availability Groups are detected, the plug-in automatically selects this option.

•

Undo file for Standby Restores: For performing Standby Restores, the plug-in requires a temporary Undo File. It is required only when the Action After Restore field is set to With STANDBY.

•

Media Format during VSS Restores: Enter MTF, CPIO, or Default, or leave the field blank.

•

MTF, Default, or blank: If the backup target is tape-based, the plug-in always uses the MTF format. This behavior is used even if a tape target uses Linux or UNIX. MTF is always acceptable for restoring from a backup produced by this version and recent versions of the plug-in. You do not have to enter this setting. Entering Default or leaving the field blank is the equivalent of entering MTF.

•

CPIO: Do not use this setting unless instructed to do so by Quest Support. Quest might ask you to use this setting to restore a backup created and written to a Linux-based tape target with a previous version of the plug-in.

•

SQL Server ODBC Driver: Enter the name of the Microsoft ODBC Driver that the plug-in should use to connect to and query the SQL Server. For example, for SQL Server 2017 on Windows, Microsoft recommends that you use the default driver, Microsoft ODBC Driver 17 for SQL Server.

•

Incomplete Backup of ALL Items Selected: The plug-in can do one of the following when this error condition occurs:

•

Complete with Warnings — Saveset Retained: The job returns a status of “Backup Completed with warnings” and a backup saveset is created that includes the items that were successfully backed up.

•

Complete without Warnings — Saveset Retained: The job completes and returns a status of “Backup Completed.” The errors are logged in the NetVault Backup binary logs and ignored on the Job Status page. A backup saveset is created that includes the items that were backed up.

•

Fail — Saveset Retained: The job returns a status of “Backup Failed.” However, a backup saveset is generated that includes the items that were successfully backed up.

•

Fail — No Saveset Retained: The job returns a status of “Backup Failed” and no saveset of backed-up objects is kept. That is, even if some of the objects were successfully backed up, the saveset is discarded.

•

If a fatal error occurs, the job returns a “Backup Failed” status.

•

If a Partial Database or Differential Partial Database backup is performed on a database whose backup target contains a read-only filegroup, the job returns a “Backup Completed with warnings” status.

•

Operating System VDI Client User Name: Enter the name of the OS root user under which the Client should run.

•

Operating System VDI Client User Group: Enter the name of the OS group under which the plug-in client should run. Make sure that you enter the root group to which the root user belongs.

•

VDI Client Library Location: Enter the path to the directory that contains the VDI Client library “libsqlvdi.so” file. The default directory is /opt/mssql/lib.

•

SQL Server ODBC Driver: Enter the name of the Microsoft ODBC Driver that the plug-in should use to connect to and query the SQL Server. For example, for SQL Server 2017 on Linux, Microsoft recommends that you use the default driver, Microsoft ODBC Driver 17 for SQL Server.

•

Sqlcmd Tool Location: Enter the path to the directory that contains the SQL Server sqlcmd utility. The default directory is /opt/mssql-tools/bin.

•

Undo file for Standby Restores: For performing Standby Restores, the plug-in requires a temporary Undo File. It is required only when the Action After Restore field is set to With STANDBY.

•

Incomplete Backup of ALL Items Selected: The plug-in can do one of the following when this error condition occurs:

•

Complete with Warnings — Saveset Retained: The job returns a status of “Backup Completed with warnings” and a backup saveset is created that includes the items that were successfully backed up.

•

Complete without Warnings — Saveset Retained: The job completes and returns a status of “Backup Completed.” The errors are logged in the NetVault Backup binary logs and ignored on the Job Status page. A backup saveset is created that includes the items that were backed up.

•

Fail — Saveset Retained: The job returns a status of “Backup Failed.” However, a backup saveset is generated that includes the items that were successfully backed up.

•

Fail — No Saveset Retained: The job returns a status of “Backup Failed” and no saveset of backed-up objects is kept. That is, even if some of the objects were successfully backed up, the saveset is discarded.

•

If a fatal error occurs, the job returns a “Backup Failed” status.

•

If a Partial Database or Differential Partial Database backup is performed on a database whose backup target contains a read-only filegroup, the job returns a “Backup Completed with warnings” status.