Tchater maintenant avec le support
Tchattez avec un ingénieur du support

NetVault Plug-in for SQL Server 11.4.5 - 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

Entering default logon credentials for a specific SQL Server Instance

If a specific instance uses different logon credentials, such as those described in Authentication Modes, from the credentials used by default, use this procedure to enter the different credentials. Information that you enter during this process overrides what you specified in Entering logon credentials for all instances on a client.

1
In the Navigation pane, click Create Backup Job, and click Create New next to the Selections list.
3
Double-click Plug‑in for SQL Server, and double-click the All Instances node to display the list of SQL Server® Instances.
5
From the Actions list, select Configure.
Logon security mode: Based on the Authentication Mode set for the SQL Server Instance, you can specify either a Windows® Administrator or a SQL Server Administrator account. To specify a Windows Administrator account, select Windows. For a SQL Server Administrator account, select SQL Server.
IMPORTANT: You can only select SQL Server if the SQL Server Authentication Mode is set to Mixed Mode/SQL Authentication.
Login Details: Depending on the option selected in the Logon security mode section, provide the appropriate account information in this section:
Administrator User Name: Specify either a Local or Domain Windows Administrator user name.
Password: Enter the password associated with the user specified in the preceding field.
Windows Domain: If a Domain Administrator is specified in the Administrator User Name field, enter the name of the domain. You can leave this field blank if a Local Administrator user name is specified.
Administrator User Name: Specify a SQL Server user with the sysadmin role.
Password: Enter the password associated with the user specified in the preceding field.
Instance Name: Usually, the plug-in automatically identifies and completes this field, and you cannot change it. If the plug-in is unable to determine the instance name, such as when you are configuring an AlwaysOn Availability Group, specify the exact name of the SQL Server Instance running. When NetVault Backup locates the instance, the instance is displayed on the NetVault Backup Selections page for browsing and inclusion in a backup job.
b
With the account properly configured, you can click the All Instances node to display the specified instances.
a
In the Navigation pane, click Create Backup Job, and click Create New next to the Selections list.
c
Double-click Plug‑in for SQL Server, and double-click the All Instances node.
f
Repeat steps Step b through Step e for all remaining Virtual Clients, ensuring that the proper SQL Server Virtual Server is selected for each Virtual Client.

Enabling communication between nodes in an AlwaysOn Availability Group

The plug-in uses the NetVault Backup Virtual Client to manage the NetVault Backup processes on all replicas included in one group. If you are using the plug-in with NetVault Backup 10.x or earlier, use the following process to enable communication between the plug-in and the replicas. This process ensures that you can back up and restore the databases that reside on the secondary replicas in a group.

cd <NetVaultBackupInstallDirectory>\util
The default installation directory is C:\Program Files (x86)\Quest\NetVault Backup\util or the corresponding directory under C:\Program Files.
nvclientaccess <clientName>
where <clientName> is the name of the NetVault Backup Client that was added to the Virtual Client. You can run this command for each client from any machine.
For example, if you have two nodes, run nvclientaccess <clientName> on Node1 with <clientName> as Node2, and then run nvclientaccess <clientName> on Node2 with <clientname> as Node1.

Changing the TCP/IP port for SQL Server®

The plug-in does not communicate with a specific port. The plug-in connects with a SQL Server driver, which then communicates with the Database Engine on the configured TCP/IP port. Because the plug-in does not directly use the TCP/IP port itself, you can configure the SQL Server Database Engine to monitor a different port without having to reconfigure the plug-in.

Setting up SQL Server® Authentication for SQL Server 2012 or later

Setting up SQL Server® Authentication for SQL Server 2012 or later

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.

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;
SP_ADDSRVROLEMEMBER '<domainName>\<loginName>', 'sysadmin'
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation