NetVault Plug-in for SQL Server 12.2

Setting up SQL Server Authentication for SQL Server 2012 or later (Windows only)

Starting with SQL Server 2012, security privileges changed and you cannot use the LocalSystem account. Previously, you could use the LocalSystem account as the default for the sysadmin role. For SQL Server 2012 or later, use a domain account — including Administrator — that has the SQL Server sysadmin role or change the Log on as option for SQL Server Service to use a domain user that has the required privileges. If the SQL Server is not part of a domain, you can use a local user that has the sysadmin role or change the Log on as option for SQL Server Service to use a local user that has the required privileges.

Ensure that the selected domain or local user account has the sysadmin role assigned to it.

Complete one of the following:

•

In Windows Control Panel > Administrative > Services, locate and select NetVault Process Manager, and click Stop. Right-click NetVault Process Manager, and select Properties. On the Log On tab, ensure that NetVault Backup runs using the account that has the SQL Server sysadmin role. Start the NetVault Process Manager.

•

In the SQL Server Configuration Manager, click SQL Server Services. In the details pane, right-click the name of the applicable SQL Server Instance, and click Properties. In the SQL Server <instanceName> Properties dialog box, click the Log On tab. For Log on as, select the account that has the SQL Server sysadmin role. In Windows Control Panel > Administrative > Services, stop and start the SQL Server Service.

•

Use SQL Server Management Studio to add the domain or local user account that has the sysadmin privileges to the SQL Server. You can use SQL Server Management Studio to add this account, or enter the following in a command prompt:

CREATE LOGIN [<domainName>\<loginName>] FROM WINDOWS;

For more information, see https://technet.microsoft.com/en-us/library/ms189751%28v=sql.110%29.aspx.

SP_ADDSRVROLEMEMBER '<domainName>\<loginName>', 'sysadmin'

For more information, see https://technet.microsoft.com/en-us/library/ms186320(v=sql.110).aspx.


	NOTE: You can assign the SQL Server sysadmin role to the default Local System user (NT AUTHORITY\SYSTEM), which lets the Plug‑in for SQL Server log into the SQL Server Instances without prompting for credentials. Provisioning the Local System user (NT AUTHORITY\SYSTEM) with the sysadmin role might result in other applications being able to log into the SQL Server Instances without providing credentials. Before assigning the sysadmin role to the Local System user (NT AUTHORITY\SYSTEM), ensure that it is allowed under your compliance requirements.

Configuring domain administrator account for service exploration

For certain activities on Windows, it is necessary to impersonate a member of Administrators group on the client(s). An Enter Domain Administrator option is added in the context menu to configure a Windows Domain Administrator for clusters, even if the default login configuration is not a Windows user.

In the Navigation pane, click Create Backup Job, and click Create New next to the Selections list.

In the selection tree, open the applicable client node.

The client node can be a standalone server or Virtual Client.

Click Plug‑in for SQL Server.

From the context menu, select Enter Domain Administrator.

Enter the login credentials for a domain account which is a member of the Administrators group on all cluster nodes:

•

User Name: Specify a domain Windows Administrator user name.

•

Password: Enter the password associated with the user specified in the preceding field.

•

Domain: Enter the name of the domain.


	NOTE: The user whose login credentials are entered must be a member of the Administrators group on all nodes of a cluster, if the client is a virtual client.

•

Reset to blank saved User Name, Password, and Domain: Select this option to reset to the blank or empty, the values stored in the plug-in for User Name, Password, and Domain.

To save the settings, click OK.

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 on Windows

Defining a backup strategy

The purpose of creating SQL Server backups is to recover a database that is damaged from media failure or data corruption. Reliable use of backup for recovery requires a strategy that maximizes data availability and minimizes data loss, while accounting for defined business requirements.

A backup strategy is divided into two pieces: a backup piece and a restore piece.

•

The backup piece defines the type and frequency of backups that are required to meet the goals for availability of the database and for minimizing data loss.

•

The restore piece defines who is responsible for performing restores, and how restores should be performed to recover from the particular type of damage or failure.


	IMPORTANT: If you use Plug‑in for SQL Server, verify that you are not using a third-party program to complete additional backups of SQL Server. Otherwise, a conflict might occur during the restore or recovery process when the differential backups do not match.

For more information, review the following topics:

•

Reviewing the available backup methods

•

Reviewing SQL Server recovery models

•

Defining an Online VDI backup strategy and reviewing types

•

Examples of VDI online backup sequences

•

Defining a VSS backup strategy and reviewing types

•