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

NetVault 13.1.1 - Administration Guide

Introduction Getting started Configuring clients Managing catalog search Configuring storage devices
About storage devices SAN considerations Quest DR Series systems Quest QoreStor Object storage 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
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 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 default settings for global notification methods 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
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 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, Data Copy and Consolidated backup job on Linux fails After upgrade, console error is displayed on WebUI pages Deployment task hangs on target Linux machine during push installation. Unable to add package store with hostname. Deployment task fails due to network configuration issues. 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 Push installation failed on Linux
Safe Mode in NetVault

Reducing startup delay

When the NetVault Service starts, it attempts to resolve all client IP addresses listed in the machines.dat file, which resides in the etc directory under the NetVault installation directory. Resolving all client addresses can cause a significant delay in the service startup and the machine can appear unresponsive during this time. You can reduce or avoid the startup delay by specifying the addresses that are not to be resolved during startup.

To configure default settings for a NetVault Client, click Choose machine. In the Choose machine drawer, select the client, and click Go to settings.
3
Under Services, click Network Manager.
4
In the Network Manager dialog box, under Connections, configure the following setting:
Comma separated list of networks and addresses not to resolve: To reduce or avoid the startup delay, specify the addresses that are not to be resolved during startup.
To get the list of networks from the machines.dat file, issue the following command on Windows:
Based on this output, you can configure the following values in the Comma separated list of networks and addresses not to resolve box:
The clients that are offline and listed on the Manage Clients page can also cause the startup delay. To speed up the process, you can remove the clients that are offline or no longer in use.
5
Click Apply to apply the new settings and close the dialog box.

Configuring default port for Network Manager

The Network Manager is configured to use port 20031 to open TCP and UDP sockets on a client. If this port is in use by any other application, the NetVault Service fails immediately after startup. When this error occurs, you must change the default port for Network Manager.

Use the following procedure to change the default port on the NetVault Server and all clients.

1
Open the file nvnmgr.cfg in a text editor. You can find this file in the config directory under the NetVault installation directory.

Configuring default port for Communications Manager

The Communications Manager is configured to use port 20032 to open TCP sockets on a client. If this port is in use by any other application, the NetVault Service fails immediately after startup. When this error occurs, you must change the default port for Communications Manager.

Use the following procedure to change the default port on the NetVault Server and all clients.

1
Open the file configure.cfg in a text editor. You can find this file in the config directory under the NetVault installation directory.
2
In the [machine] section, append the following line:

Configuring Process Manager settings

This section includes the following topics:

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택