Chat now with support
Chat with Support

NetVault Plug-in for VMware 13.1 - User Guide

Introducing NetVault Plug-in for VMware Installing the plug-in Configuring the plug-in Defining a backup strategy Using the image-level backup method Using the file-level backup method Restoring image-level backups Restoring file-level backups Troubleshooting

Common errors

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

•
NetVault Service fails to start on Windows
•
NetVault Service fails to start after the machine is restarted
•
NetVault Service starts, but stops immediately on Linux
•
Linux Hybrid version of the plug-in does not run on 64-bit OS
•
Crash occurs during a backup
•
CBT-based image-level backup fails
•
SAN transport reports errors when multiple backups access the same datastore
•
Default SCSI controller type on RHEL 7 and RHEL 6
•
File-level backups do not back up data for a reparse point
•
Restore job fails when using SAN transport
•
Restore job fails to add a virtual machine to the server inventory or to the alternate standalone ESXi Server
•
Disk type is always Thick Provision Eager Zeroed after restoring an image-level backup
•
Backup jobs of virtual machines protected by vSphere FT fail intermittently
•
RDM disks are restored to VMDK files
•
Unable to consolidate image-level backups
•
Restore job fails on Linux when file size exceeds 50 MB
•
Web Service process displays message that indicates the server is unavailable
•
Installing an update puts the VMware Vstor2 MntApi driver into an inconsistent state
•
Backing up and restoring encrypted disks
•
Backing up a cloned virtual machine that has the same UUID
•
Backing up virtual machines that are protected by vSphere FT
•
Error using VVols with a storage array
•
Backup proxy opens in NBD mode instead of HotAdd transport mode

NetVault Service fails to start on Windows

Description

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

Symptom

Check the Windows Event Viewer for the following message: PDT FATAL: lock file “postmaster.pid” already exists.

Solution

NetVault 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 Server.

NetVault Service fails to start after the machine is restarted

Description

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

Symptom

Check the Windows Event Viewer for the following message: FATAL: could not create any TCP/IP sockets " for a PostgreSQL source

Solution

NetVault 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. To remove all instances of postgres32.exe, select any instance of this process, and click End Process. Start the NetVault Service.

NetVault Service starts, but stops immediately on Linux

Description

On a Linux-based machine, the NetVault 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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating