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

Removing the plug-in from a standalone deployment

For details on removing the Plug‑in for SQL Server in high-availability deployment, see the applicable topic on working with client clusters in the Quest NetVault Backup Administrator’s Guide.

 
* 
CAUTION: Removing the plug-in does not remove the configuration settings that you created. If you reinstall the plug-in or install a newer version, the plug-in typically uses the same configuration settings from the previous installation unless otherwise indicated in the release notes.
1
In the Navigation pane, click Manage Clients.
2
On the Manage Clients page, select the applicable client, and click Manage.
3
In the Installed Software table on the View Client page, select Plug‑in for SQL Server, and click the Remove Plugin button ().
4
In the Confirm dialog box, click Remove.

Removing a SQL Server® Instance

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 the NetVault Backup Virtual Client
•
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.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation