1 |
In the Navigation pane, click Change Settings. |
2 |
3 |
4 |
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. |
• |
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. |
• |
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. |
6 |
To save the settings, click Apply. |
1 |
Ensure that the selected domain or local user account has the sysadmin role assigned to it. |
• |
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: |
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center