1 |
3 |
Double-click Plug‑in for SQL Server, double-click the All Instances node, and click the applicable instance to select it. |
4 |
• |
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. |
• |
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 Logon 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. |
1 |
3 |
Double-click Plug‑in for SQL Server, and double-click the All Instances node to display the list of SQL Server® Instances. |
4 |
5 |
• |
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: |
• |
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. |
• |
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: 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. |
IMPORTANT: The default credentials are those credentials configured for the All Instances node with no instance name specified. If you enter the logon credentials and omit the Instance Name, NetVault Backup uses the default credentials when it accesses instances for which no information was provided. You might find this method useful in multiple-instance environments. |
8 |
If you need to enter different authentication information for additional SQL Server Instances, repeat Step 4 through Step 7 until all instances are configured. |
1 |
3 |
4 |
IMPORTANT: Add each cluster instance in the Instances field of the Configure dialog box. To add an instance, specify the SQL Server cluster name as VIRTUAL SERVER NAME\INSTANCE NAME. |
a |
b |
c |
e |
g |
Repeat steps Step b through Step f for all remaining Virtual Clients, ensuring that the proper SQL Server Virtual Server is selected for each Virtual Client. |
1 |
3 |
Double-click Plug‑in for SQL Server. |
4 |
In the Configure dialog box, enter the credentials of the domain user that is used as the default user for accessing SQL Server Instances in the group. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center