立即与支持人员聊天
与支持团队交流

NetVault Plug-in for SQL Server 10.0.6 - User Guide

Introducing Dell™ 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 Restoring data Troubleshooting

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. To ensure that you can back up and restore the databases that reside on the secondary replicas in a group, use the following process to enable communication between the plug-in and the replicas.
To enable communication:
1
From a command prompt on the first replica included in the group, type:
cd <NetVaultBackupInstallDirectory>\util
The default installation directory is C:\Program Files (x86)\Dell\NetVault Backup\util or the corresponding directory under C:\Program Files.
2
For each NetVault Backup client that was added to the Virtual Client, type:
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.
3
When the prompt appears, type the master password for the specified client.
This password is the same one that you specified when you added the client to the NetVault Backup Server. This password lets remote NetVault Backup machines access the client.
4
Repeat these steps for every replica included in the group.
You can run these two commands for each client from any machine.

Specifying a default configuration (optional)

The plug-in lets you set default options for backup and restore jobs. You can override these options on a per-job basis.
1
In the Navigation pane, click Change Settings.
2
Click Server Settings or Client Settings, as applicable.
3
If you selected Client Settings, select the applicable client, and click Next.
4
On the Settings page, click Plugin Options.
5
In the Plug‑in for SQL Server section of the dialog box, complete the applicable fields:
•
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: 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 or Database - Complete backup.
•
Ignore: Select this option to ignore databases created since the last Full Database or Database - Complete 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.
Specify the directory path for the temporary UNDO.DAT file in this field.
•
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 either of the following occurs, the plug-in overrides the Incomplete Backup of ALL Items Selected setting and responds as indicated:
•
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.
•
Media Format during VSS Restores: By default, the plug-in assumes that the media format for backup tapes is MTF, which is typically used for Windows®. If you are using CPIO, which is used for Linux®/UNIX®, specify CPIO to ensure that restores of VSS-based backups are processed correctly.
 
* 
IMPORTANT: Dell strongly recommends that you leave this option blank and let NetVault Backup determine the format to use. Only change this option if you need to override the default format during a restore that failed because of a media-channel error in which a VSS restore failed from a NetVault Backup Server installed on Linux or UNIX. In most cases, this option should not be used. For more information, see Troubleshooting.
6
To save the settings, click Apply.

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

Beginning 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. use authentication 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,
To use SQL Server Authentication with SQL Server 2012 or later to configure the plug-in:
1
Ensure that the selected domain or local user account has the sysadmin role assigned to it.
2
Complete one of the following:
•
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;
GO
For more information, see https://technet.microsoft.com/en-us/library/ms189751%28v=sql.110%29.aspx.
SP_ADDSRVROLEMEMBER '<domainName>\<loginName>', 'sysadmin'
GO
For more information, see https://technet.microsoft.com/en-us/library/ms186320(v=sql.110).aspx.
 
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级