Chat now with support
Chat with Support

NetVault Plug-in for FileSystem 11.0 - User Guide

Restoring cluster database on Windows 2008

On Windows 2008, the Plug‑in for FileSystem uses VSS for backing up and restoring the cluster database. The Windows Cluster Service must be running to use this feature. The Plug‑in for FileSystem only supports the authoritative restore schema. In an Active-Active cluster, VSS stops other nodes when you perform a restore operation. These nodes must be manually restarted after restore. On Windows 2008, the following restore options are not available:
•
Force Cluster Database Restore
•
Use Original Cluster Database Location
•
Cluster Quorum Drive Letter

Additional considerations for domain controllers

•
A Domain Controller in a non-authoritative state does not function as a Domain Controller until it has synchronized with the active Domain Controller. The synchronization is implemented using the Microsoft File Replication Service. If the SYSVOL data on a client has been restored non-authoritatively, the File Replication Service must successfully replicate the data to the active controller with Authoritative version of the SYSVOL data before the machine functions as a Domain Controller.
•
If a restored Domain Controller owns the Flexible Single Master Operations (FSMO) roles, it does not start performing these roles until it has synchronized with the active Domain Controller. It may take some time before the restored Domain Controller starts performing the FMSO roles.

Troubleshooting

•
Common errors

Common errors

This section describes some common errors and their solutions. It includes the following topics:
•
NetVault Backup Service fails to start on Windows
•
NetVault Backup Service fails to start after the machine is restarted
•
NetVault Backup Service starts, but stops immediately on Linux
•
VSS-based backup fails
NetVault Backup Service fails to start on Windows
Description
The NetVault Backup Service fails to start on a Windows-based NetVault Backup Server.
Symptom
Check the Windows Event Viewer to see if it displays the following message:
PDT FATAL: lock file “postmaster.pid” already exists
Solution
NetVault Backup cannot start if the PostgreSQL database that is used to store the system data does not start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Backup Server.
NetVault Backup Service fails to start after the machine is restarted
Description
After restarting the machine, the NetVault Backup Service sometimes fails to start on a Windows-based NetVault Backup Server.
Symptom
Check the Windows Event Viewer to see if it displays the following message:
FATAL: could not create any TCP/IP sockets " for a PostgreSQL source
Solution
NetVault Backup cannot start if the PostgreSQL database that is used to store the system data does not start. To correct this issue, start the Task Manager, and click Show processes from all users. You can see multiple instances of postgres32.exe running on the system. Select any one instance of this process, and click End Process to remove all instances of postgres32.exe. Then, start the NetVault Backup Service.
NetVault Backup Service starts, but stops immediately on Linux
Description
On a Linux-based machine, the NetVault Backup Service starts, and then stops immediately.
Symptom
No error messages are displayed.
Solution
This issue can occur if the Postgres service cannot resolve the host name localhost, and fails to start.
Check the /etc/hosts file, and if the file does not contain an entry for localhost, add the entry.
VSS-based backup fails
Description
When performing a VSS-based backup, if the VSS writer fails to generate a snapshot, the job fails.
Symptom
The log messages show the following errors:
•
Failed to add extra items to the selection tree.
•
Failed to prepare the selection tree and backup options.
Solution
These messages indicate a problem in the VSS subsystem. NetVault Backup cannot complete the backup job if the VSS subsystem is not functioning properly. Before you run the job again, we recommend that you do the following:
•
Delete the existing shadow copies. (You can use the Vssadmin or DiskShadow utilities to delete the shadow copies.)
•
Restart the applicable VSS writer service.
 
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating