Chat now with support
Chat mit Support

NetVault Plug-in for SQL Server 12.2 - User Guide

Introducing 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 Understanding snapshot-based backups 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
Restoring data Using the CLI with the plug-in Troubleshooting

Entering logon credentials for all instances on a client

If all instances use the same logon credentials, use this procedure to specify the default credentials. The plug-in also lets you omit the name and password and use the Log on as account information defined for the NetVault Process Manager service.

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.
The client node can be a standalone server or Virtual Client.
3
Double-click Plug‑in for SQL Server.
4
Click the All Instances node, and select Configure from the context menu.
5
Complete the applicable fields:
•
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.

If you are using a Linux environment, you must enter the SQL Server Administrative (sa) account credentials. If you do not enter the credentials, the plug-in cannot access SQL Server and backup jobs fail.
•
Login Details: Depending on the option selected in the Logon security mode section, provide the appropriate account information in this section:
•
For Windows authentication, provide the following information:
•
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.
•
Login Timeout (Seconds) (0=Timeout disabled): This option specifies how long to wait, in seconds, before an instance returns from an attempt to log in to a SQL Server Instance. By default, the timeout value is set to 30 seconds; however, you can change the value during a network delay for a particular SQL Server Instance. The maximum that you can use is 800 seconds. If the value is set to 0, the option is disabled.
•
For SQL Server authentication, provide the following information:
•
Administrator User Name: Specify a SQL Server user with the sysadmin role. If you are using a Linux environment, enter the name for the sa account. The default name is sa.
•
Password: Enter the password associated with the user specified in the preceding field. If you are using a Linux environment, enter the password for the sa account.
•
Login Timeout (Seconds) (0=Timeout disabled): This option specifies how long to wait, in seconds, before an instance returns from an attempt to log in to a SQL Server Instance. By default, the timeout value is set to 30 seconds; however, you can change the value during a network delay for a particular SQL Server Instance. The maximum that you can use is 800 seconds. If the value is set to 0, the option is disabled.
6
To save the settings, click OK.

Configuring an instance at the All Instances level on a client

The Add Instance option in the context menu helps you add an instance under the All Instances node. This option is available if the All Instances node is selected. This option is similar to the Configure option; however, this option lets you specify the exact name of 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.
The client node can be a standalone server or Virtual Client.
3
Double-click Plug‑in for SQL Server.
4
Click the All Instances node, and select Add Instance from the context menu.
5
Complete the applicable fields:
•
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.

If you are using a Linux environment, you must enter the SQL Server Administrative (sa) account credentials.
•
Login Details: Depending on the option selected in the Logon security mode section, provide the appropriate account information in this section:
•
For Windows authentication, provide the following information:
•
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.
•
Login Timeout (Seconds) (0=Timeout disabled): This option specifies how long to wait, in seconds, before an instance returns from an attempt to log in to a SQL Server Instance. By default, the timeout value is set to 30 seconds; however, you can change the value during a network delay for a particular SQL Server Instance. The maximum that you can use is 800 seconds. If the value is set to 0, the option is disabled.
•
For SQL Server authentication, provide the following information:
•
Administrator User Name: Specify a SQL Server user with the sysadmin role. If you are using a Linux environment, enter the name for the sa account. The default name is sa.
•
Password: Enter the password associated with the user specified in the preceding field. If you are using a Linux environment, enter the password for the sa account.
•
Login Timeout (Seconds) (0=Timeout disabled): This option specifies how long to wait, in seconds, before an instance returns from an attempt to log in to a SQL Server Instance. By default, the timeout value is set to 30 seconds; however, you can change the value during a network delay for a particular SQL Server Instance. The maximum that you can use is 800 seconds. If the value is set to 0, the option is disabled.
•
Instance Name (Windows only): Type the name of the instance to configure. If it is a named instance, type the full instance name.
6
To save the settings, click OK.

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.
2
In the selection tree, open the applicable client node.
The client node can be a standalone server or Virtual Client.
3
Double-click Plug‑in for SQL Server, and double-click the All Instances node to display the list of SQL Server Instances.
Because you can use a single SQL Server installation to create multiple instances and configure authentication differently for each instance, NetVault Backup supports the use of different authentication information for different instances. If you only create one instance, that node is labeled “(local).”
4
Select the node for the first SQL Server Instance or AlwaysOn Availability Group that you want to configure; if you only have one instance, select the “(local)” node.
5
From the context menu, select Configure.
6
Complete the applicable fields:
•
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.

If you are using a Linux environment, you must enter the SQL Server Administrative (sa) account credentials.
•
Login Details: Depending on the option selected in the Logon security mode section, provide the appropriate account information in this section:
•
For Windows authentication, provide the following information:
•
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.
•
For SQL Server authentication, provide the following information:
•
Administrator User Name: Specify a SQL Server user with the sysadmin role. If you are using a Linux environment, enter the name for the sa account. The default name is sa.
•
Password: Enter the password associated with the user specified in the preceding field. If you are using a Linux environment, enter the password for the sa account.
•
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.
7
If you are configuring Virtual Clients for an AlwaysOn Availability Group and you anticipate having to create additional backup jobs or modify existing backup jobs on the secondary nodes, perform the following steps:
a
Fail over the primary node to the secondary node.
b
Repeat Step 1 through Step 6.
c
Fail back to the primary node.
8
To save the settings, click OK.
9
If you need to enter different authentication information for additional SQL Server Instances, repeat Step 4 through Step 8 until all instances are configured.
With the account properly configured, you can click the All Instances node to display the specified instances.
10
If your environment uses multiple Virtual Servers in the same SQL Server Failover cluster, complete the following steps for each Virtual Client you created:
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 newly created Virtual Client that was set up for the first SQL Server Virtual Server.
c
Double-click Plug‑in for SQL Server, and double-click the All Instances node.
All the SQL Server Virtual Servers within the failover cluster are revealed.
d
Select the first SQL Server Virtual Server in the tree, and then select Configure from the context menu.
e
Complete the applicable fields.
With the configuration set for the first SQL Server Virtual Server in its corresponding Virtual Client, repeat the process for all remaining SQL Server Virtual Servers.
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.

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.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen