Chat now with support
Chat with Support

NetVault Plug-in for SQL Server 11.2 - User Guide

Introducing Quest® NetVault® Backup Plug-in  for SQL Server® Planning your SQL Server deployment Installing and removing the plug-in Configuring the plug-in Backing up data
Defining a backup strategy Reviewing the compression features Performing Online VDI backups Performing VSS backups in SQL Server® Example of creating a full VDI backup of an AlwaysOn Availability Group
Restoring data Troubleshooting

Removing a SQL Server® Instance

1
In the Navigation pane, click Create Backup Job, and click Create New next to the Selections list.
2
In the selection tree, open the applicable client node.
3
Double-click Plug‑in for SQL Server, double-click the All Instances node, and click the applicable instance to select it.
4
From the Actions list, select Remove.
5
When the confirmation message appears, click Yes.

Configuring the plug-in

•
Configuring authentication details
•
Configuring plug-in options
•
Entering logon credentials for all instances on a client
•
Configuring an instance at all instances level on a client
•
Entering default logon credentials for a specific SQL Server Instance
•
Enabling communication between nodes in an AlwaysOn Availability Group
•
Changing the TCP/IP port for SQL Server®
•
Setting up SQL Server® Authentication for SQL Server 2012 or later
•
Configuring domain administrator account for service exploration

Configuring authentication details

Before initiating a backup, configure the plug-in’s authentication details, which include authentication mode, user name, and password. Use the Configure dialog to specify this information.

How the information that you enter in the Configure dialog applies depends on whether you are configuring a client for a standalone deployment or a NetVault Backup Virtual Client for a SQL Server Failover Cluster or an AlwaysOn Availability Group. When you enter settings for a standalone client, the settings apply to all backups generated from that client when it is selected in the selection tree. If you use Virtual Clients to support a SQL Server Failover Cluster or an AlwaysOn Availability Group, the authentication information that you enter for a specific instance in the cluster or group is used for all nodes within the same cluster or group. All information that you enter on the Configure dialog for a cluster or group is maintained on the NetVault Backup Server, unlike a standalone deployment for which the information is maintained on the server on which the plug-in is installed.

Authentication modes

SQL Server® provides two authentication modes: Windows® Authentication and SQL Server Authentication.

•
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.
Windows Authentication uses Kerberos security protocol, provides password policy enforcement in terms of complexity validation for strong passwords, supports account lockout, and supports password expiration. Microsoft strongly recommends implementing a Windows Authentication mode for SQL Server.
•
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.

Configuring plug-in options

The settings described in the following topic apply to all backup and restore jobs and to individual clients. Additional logon settings are also available; for more information, see Entering logon credentials for all instances on a client and Entering default logon credentials for a specific SQL Server Instance.

1
Access the Configure dialog box.
•
For standalone clients or clients included in an AlwaysOn Availability Group:
a
In the Navigation pane, click Change Settings.
b
Click Server Settings or Client Settings, as applicable.
c
If you selected Client Settings, select the applicable client, and click Next.
d
On the Settings page, click Plugin Options.
e
Locate the Plug‑in for SQL Server section of the dialog box.
•
For Virtual Clients used in a failover cluster:
a
In the Navigation pane, click Create Backup Job, and click Create New next to the Selections list.
b
In the selection tree, open the applicable Virtual Client.
c
Select the Plug‑in for SQL Server node.
d
From the Actions list, select Configure.
2
Complete the applicable fields:
•
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.
•
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.
Specify the directory path for the temporary UNDO.DAT file in this field.
•
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 either of the following occurs, the plug-in overrides the Incomplete Backup of ALL Items Selected setting and responds as indicated:
•
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.
•
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.
 
* 
IMPORTANT: Quest recommends that you leave this option blank and let NetVault Backup determine the format to use. Only change this option if you need to override the default format during a restore from tape that failed. For more information, see Troubleshooting.
3
To save the settings, click Apply.
4
If you are configuring the clients for an AlwaysOn Availability Group, repeat the preceding steps for each client in the group.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating