NetVault Backup Plug-in for FileSystem 11.4 - User Guide

Troubleshooting

Common errors

This section describes some common errors and their solutions. It includes the following topics:

The NetVault Backup Service fails to start on a Windows-based NetVault Backup Server.

Check the Windows Event Viewer to see if it displays the following message:

PDT FATAL: lock file “postmaster.pid” already exists

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.

After restarting the machine, the NetVault Backup Service sometimes fails to start on a Windows-based NetVault Backup Server.

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

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.

On a Linux-based machine, the NetVault Backup Service starts, and then stops immediately.

No error messages are displayed.

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.

When performing a VSS-based backup, if the VSS writer fails to generate a snapshot, the job fails.

The log messages show the following errors:

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.)

 

Related Documents