In a SQL Server Failover deployment, the SQL Server Failover Virtual Instance is automatically detected if the SQL Server Browser Service is running in all the nodes of the Failover Cluster. Otherwise, to add SQL Server Failover Virtual Instance using the Add Instance Action, follow these steps:
1 |
3 |
4 |
IMPORTANT: Add the cluster instance name in the Instances field of the Configure dialog box. To add an instance, if necessary, you might specify the SQL Server cluster name as VIRTUAL SERVER NAME\INSTANCE NAME |
1 |
3 |
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. |
The settings described in the following topic apply to all backup and restore jobs and to individual clients. Additional logon settings are also available; for more information, see Entering logon credentials for all instances on a client and Entering default logon credentials for a specific SQL Server Instance.
1 |
Access the Configure dialog box. |
a |
In the Navigation pane, click Change Settings. |
b |
c |
d |
e |
a |
c |
d |
• |
Error Encountered During Checksum: SQL Server® lets you specify the action that should be taken if an error is encountered when performing checksums on backups and restores. You can specify the default action to take on encountering checksum errors by selecting one of the following two options from the list: |
• |
Continue after error: This option is the default set during the plug-in installation. With this value selected, the backup or restore job continues in spite of checksum errors. |
• |
Stop on error: Select this option to set it as the default action. With this value selected, the backup or restore job stops when a checksum error is encountered. |
• |
New Database Found in Differential/Incremental Backup: This field applies only to Online VDI backups. If a new database is found while performing Transaction Log or Differential Database backups and the Instance Node is selected on the NetVault Backup Selections page, you can ignore it or take a full backup. You can set this action globally for all Transaction Log and Differential Database backups by selecting the applicable action from the list: |
• |
Do full database backup: This option is the default set during the plug-in installation. Retain this option to perform a full backup of all databases added since the last Full Database backup. |
• |
Ignore: Select this option to ignore databases created since the last Full Database backup; that is, databases created after the last backup are left out of the Transaction Log or Differential Database backup. |
• |
Undo file for Standby Restores: For performing Standby Restores, the plug-in requires a temporary Undo File. It is required only when the Action After Restore field is set to With STANDBY. |
• |
Incomplete Backup of ALL Items Selected: The plug-in can do one of the following when this error condition occurs: |
• |
Complete with Warnings — Saveset Retained: The job returns a status of “Backup Completed with warnings” and a backup saveset is created that includes the items that were successfully backed up. |
• |
Complete without Warnings — Saveset Retained: The job completes and returns a status of “Backup Completed.” The errors are logged in the NetVault Backup binary logs and ignored on the Job Status page. A backup saveset is created that includes the items that were backed up. |
• |
Fail — Saveset Retained: The job returns a status of “Backup Failed.” However, a backup saveset is generated that includes the items that were successfully backed up. |
• |
Fail — No Saveset Retained: The job returns a status of “Backup Failed” and no saveset of backed-up objects is kept. That is, even if some of the objects were successfully backed up, the saveset is discarded. |
• |
If a fatal error occurs, the job returns a “Backup Failed” status. |
• |
If a Partial Database or Differential Partial Database backup is performed on a database whose backup target contains a read-only filegroup, the job returns a “Backup Completed with warnings” status. |
• |
• |
MTF, Default, or blank: If the backup target is tape-based, the plug-in always uses the MTF format. This behavior is used even if a tape target uses Linux® or UNIX®. MTF is always acceptable for restoring from a backup produced by this version and recent versions of the plug-in. You do not have to enter this setting. Entering Default or leaving the field blank is the equivalent of entering MTF. |
• |
CPIO: Do not use this setting unless instructed to do so by Quest Support. Quest might ask you to use this setting to restore a backup created and written to a Linux-based tape target with a previous version of the plug-in. |
3 |
To save the settings, click Apply. |
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 |
3 |
4 |
Select the All Instances node. |
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: |
• |
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. |
The Add Instance option in the Actions list helps to add instance under 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 an SQL Server instance.
1 |
3 |
4 |
Select the All Instances node. |
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: |
• |
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: Type the name of the instance to configure. If it is a named instance, type the full instance name. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center