지금 지원 담당자와 채팅
지원 담당자와 채팅

NetVault 13.0.3 - Administration Guide for Managed Service Providers

Introduction Getting started Configuring clients Managing catalog search Configuring storage devices
About storage devices SAN considerations Quest DR Series systems Quest QoreStor NetVault SmartDisk EMC Data Domain Systems Snapshot Array Manager Virtual Tape Libraries Virtual standalone drives Shared Virtual Tape Libraries Physical tape devices Storage tiers
Backing up data Managing policies Restoring data Managing NetVault dashboard Managing jobs Monitoring logs Managing storage devices
Role-based access to manage storage devices Monitoring device activity Managing disk-based storage devices in list view Managing disk-based storage devices in tree view Managing the Snapshot Array Manager Managing tape libraries in list view Managing tape libraries in tree view Managing tape drives in list view Managing tape drives in tree view Adding shared devices
Managing storage media Managing user and group accounts Managing Tenant Monitoring events and configuring notifications Reporting in NetVault Working with client clusters Configuring default settings for NetVault
About configuring default settings Configuring encryption settings Configuring plug-in options Configuring default settings for post-scripts Configuring default settings for Verify Plug-in Configuring Deployment Manager Settings Configuring Job Manager settings Configuring Logging Daemon settings Configuring Media Manager settings Configuring Network Manager settings Configuring Process Manager settings Configuring RAS device settings Configuring Schedule Manager settings Configuring Web Service settings Configuring Auditor Daemon settings Configuring firewall settings Configuring general settings Configuring security settings Synchronizing NetVault Time Configuring the reporting utility Configuring NetVault WebUI default settings Configuring NetVault to use a specific VSS provider Configuring default settings using Txtconfig
Diagnostic tracing Managing diagnostic data Using the deviceconfig utility NetVault processes Environment variables Network ports used by NetVault Troubleshooting
Common errors Safe Mode in NetVault

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
•
Login fails after any change in the server IP address
•
Unexpected behavior of NetVault WebUI
•
WebUI does not run in Compatibility View in Internet Explorer
•
NetVault installer fails during push installation
•
VSS-based backup fails
•
Modifying TCP/IP socket buffer size on Windows
•
Restores using Data Copy savesets fail on clients running NetVault 10.0.1
•
Restore fails on Itanium platforms if the index is larger than 2GB
•
After upgrade, console error is displayed on WebUI pages
•
Domain user is unable to login NetVault Server if the workstation attribute is set.
•
Domain user is unable to login NetVault Server on Debian 9.
•
Adding the target machine as a client fails, after successful push installation.
•
Unable to install, uninstall or navigate catalog search page after manually uninstalling NetVault Client Host.
•
Unable to install, uninstall catalog search on client after NetVault Server migration with the same or different server name
•
External Azure AD user cannot add an external Azure AD user to NetVault Server
•
Failed to verify target Windows machine from a Linux-based NetVault Server
•
NetVault is unable to send reports as an email attachment in PDF format on RHEL 5.x platform
•
Restore fails on NetVault Database backup
•
When using RDA for backups, only four streams are used at once
•
Unable to create large VTL on Linux
•
Browsing a folder with a large number of files times out

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 to see if it displays 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 to see if it displays 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. Select any one instance of this process, and click End Process to remove all instances of postgres32.exe. Then, start the NetVault Service.

Login fails after any change in the server IP address

Description

Login from WebUI fails after any change in the NetVault Server IP address.

Symptom

When you try to log in, the NetVault WebUI displays a message that the server is not accessible.

Solution

After any change in the IP address of the NetVault Server (for example, due to reassignment at reboot by DHCP), you must clear the browser cache before logging in to the NetVault WebUI. Otherwise, the login may fail with a message that the server is not accessible. Alternatively, you can assign a static IP address to the NetVault Server.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택