Chat now with support
Chat with Support

NetVault Plug-in for SQL Server 11.0 - 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
Defining a backup strategy 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
Restoring data Troubleshooting

Troubleshooting

This section describes some common errors and their solutions. If an error occurs that is not described in this table, obtain the SQL Server® error number from the NetVault Backup Logs, and then see the relevant SQL Server documentation for the resolution.
 
Table 1. Troubleshooting
Symptom
Reason/symptom
Solution
NetVault Backup 10.x service (netvault-pgsql) does not start on Windows®
Check the Windows Event Viewer to see if it displays the following message: PDT FATAL: lock file “postmaster.pid” already exists.
NetVault Backup 10.x uses a PostgreSQL database. If the PostgreSQL database does not start, NetVault Backup cannot start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Backup Server. For more information, see https://support.quest.com/netvault-backup/kb/122475.
Transaction Log backup failed
Transaction Log backups are not allowed for Simple Recovery Model databases.
For taking Transaction Log backups, the recovery model for the database must be set to Full Recovery Model.
Or clear the Simple Recovery Model databases.
Backup failed
The File and Filegroup backup fails and the following error message appears in the logs:
“The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS.”
Either modify the Selection Set to include only secondary filegroups for the Simple Recovery Model databases or select the Partial Database or Differential Partial Database backup type.
Backup failed
Login failed for user <userName>.
Verify that the password for the plug-in has been entered correctly.
Backup Completed with warnings
After this status is revealed for backup, check the NetVault Backup Log entries for the job to see if they display one or both of the following messages:
•
“Failed to add backup record”
•
“Failed to write index of backup to the database”
These messages indicate that the selected data was backed up, but the job’s index information was not properly added by NetVault Backup to its database. Without this index information, the data cannot be properly restored.
Method 1:
Open the Manage Devices page, select the backup media, and click Scan. NetVault Backup stores index information for backup jobs in two locations: in the NetVault Database and on the media targeted by the backup. Performing this scan adds the index information to the NetVault Database. To verify that the information was added, open the Manage Job Definitions page, and locate the specific job. If you can run the job now, the scan process has corrected the problem.
Method 2:
If the scan has failed, run the backup job again.
VSS Restore fails from a NetVault Backup Server installed on Linux® or UNIX®.
By default, the plug-in assumes that the media format for backup tapes is MTF, which is typically used for Windows. However, Linux and UNIX use CPIO.
Configure the plug-in to set the Media Format to use CPIO during VSS Restores. For more information, see Configuring plug-in options.
AlwaysOn Availability Group not displayed under the Virtual Client
If a group is not listed under a Virtual Client, it might indicate that the services for the SQL Server Instances are not running. It might also indicate that valid login credentials were not set up for the plug-in at the All Instances level.
•
Use SQL Server Configuration Manager to verify that services are running.
•
Verify that you set up valid credentials for the All Instances node located under the applicable Virtual Client in the selection tree. For more information, see Configuring the plug-in.
Nodes take a long time to open
To populate the next level of the node, the plug-in queries SQL Server for instance and cluster information. If the plug-in queries or logs in to an instance whose Windows service is not running, a lengthy timeout imposed by SQL Server might occur. NetVault Backup uses a five-minute timeout. If the NetVault Backup timeout is exceeded, the plug-in displays an error message and the node is not opened. You must address the issues that are causing a delay in the login and query processes.
•
Use SQL Server Configuration Manager to verify that services are running.
•
Enter default credentials for plug-in logins to SQL Server. For more information, see Entering logon credentials for all instances on a client.
•
If different credentials are required for some of the instances, enter the login credentials for those instances using the applicable instance or AlwaysOn Availability Group node in selection tree. For more information, see Entering default logon credentials for a specific SQL Server Instance.
•
If you must open the All Instances node to configure login credentials for specific instances or AlwaysOn Availability Groups, but the NetVault Backup timeout setting is preventing the All Instances node from opening, use the Physical Client Long Timeout option to change the timeout value for the node. For more information, see the topic on configuring the timeout period in the Dell NetVault Backup Administrator’s Guide.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating