サポートと今すぐチャット
サポートとのチャット

NetVault 13.0 - Administration Guide

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
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
Safe Mode in NetVault

Environment variables

•
Environment variables in NetVault

Environment variables in NetVault

The following is a list of NetVault environment variables that can be used in user-defined scripts.

 
Table 161. Environment variables
Variable
Description

NETVAULTCLIACCOUNT

Specifies the NetVault user name. The specified account must have privileges to use the CLI utility.

NETVAULTCLIACCOUNT=<User Account Name>

This variable must be included in the script to access the CLI utility.

NETVAULTCLIPASSWORD

Specifies the password for the NetVault user account.

NETVAULTCLIPASSWORD=<Password>

This variable must be included in the script to specify the password for the user account.

NV_HOME

Returns the NetVault installation directory.

NV_JOBCLIENT

Specifies the target client for a job.

NV_JOBCLIENT=<Name of the NetVault Client>

NV_JOBID

Specifies the Job ID number.

NV_JOBID=<Job ID>

NV_JOBTITLE

Specifies the name of the job.

NV_JOBTITLE=<Job title>

NV_JOB_WARNINGS

Returns TRUE if a job completes with warnings, else returns FALSE.

•
If a backup completes with warnings:
NV_JOB_WARNINGS=TRUE
•
If a backup completes successfully:
NV_JOB_WARNINGS=FALSE

This variable can only be used in a post -script. The mail scripts use this variable, but the variable has general applicability.

If a backup completes with warnings, the NV_STATUS variable returns SUCCEEDED, while the NV_JOB_WARNINGS variable returns TRUE.

The return value is not localized; it is TRUE or FALSE in English.

NV_OUTPUT_FILE

Returns the user-defined output file for reports.

NV_SERVERNAME

Specifies the NetVault Server Name.

NV_SERVERNAME=<Name of the NetVault Server>

NV_SESSIONID

Specifies the Session ID of a job.

NV_SESSIONID=<Session ID>

NV_STATUS

Returns the exit status of a job. It returns either SUCCEEDED or FAILED.

•
If a backup job completes successfully or completes with warnings:
NV_STATUS=SUCCEEDED
•
If a backup job fails:
NV_STATUS=FAILED

This variable can only be used in a post-script. The return value is not localized; it is SUCCEEDED or FAILED in English.

NV_USER_ARG

Specifies the user-defined arguments passed with the pre- or post-scripts.

 

Network ports used by NetVault

•
Ports used or required

Ports used or required

The following table provides a list of network ports used by NetVault.

 
Table 162. Ports used by NetVault
Port
Protocol
Usage
Comments

80

TCP

HTTP Listen port for incoming Web Service connections.

 

135

TCP

RPC port used during the client push installation process.

 

3306

TCP

Port used to make a TCP/IP connection to the MySQL Server.

Configured on the NetVault Client on which the Plug-in for MySQL is installed.

The default port number is 3306. If a non-default port is configured for client connections on the MySQL Server, verify that the same port is configured on the NetVault Client.

To run multiple instances of MySQL on the same machine, a different port is configured for each instance.

5432

TCP

Listener port for PostgreSQL Database.

Configured on the NetVault Client on which the Plug-in for PostgreSQL is installed.

The default port number is 5432. If the PostgreSQL Database is configured to listen on a non-default port, verify that the same port is configured on the NetVault Client.

8443

TCP

HTTPS Listen port for incoming Web Service connections.

 

10000

TCP

Port for sending NDMP messages (NDMP control channels).

Configured on the NetVault Server on which the Plug-in for NDMP is installed.

The default port number is 10000. You can change it, if necessary.

20031

UDP

UDP messaging.

Required on server and clients.

20031

TCP

Port used by Network Manager (nvnmgr).

 

User-defined listen ports for devices

TCP

Ports to listen on for device requests.

Configured on the NetVault Server and SmartClients.

Requirement: Two ports per drive.

User-defined connect ports for devices

TCP

Ports to connect to remote storage devices.

Configured on clients that connect to remote storage devices.

Requirement: Two ports per drive

User-defined listen ports for message channels

TCP

Ports to receive messages during data transfers.

Configured on NetVault Server and Clients.

Requirement: Three ports per client.

To run two or more plug-ins simultaneously on a client, NetVault requires two ports per plug‑in and an extra port per client. For example, to run two plug-ins simultaneously, NetVault requires (2 * 2) + 1 = 5 ports for a client.

User-defined connect ports for message channels

TCP

Ports for sending messages during data transfers.

Configured on NetVault Server and Clients.

Requirement: Three ports per client.

To run two or more plug-ins simultaneously on a client, NetVault requires two ports per plug‑in and an extra port per client. For example, to run two plug-ins simultaneously, NetVault requires (2 * 2) + 1 = 5 ports for a client.

User-defined connect ports for inter-machine setup

TCP

Ports for establishing initial contact (broadcast channels) while adding a NetVault Client, and later to ascertain its availability.

Requirement: Two ports per client.

User-defined listen ports for NDMP data channels

TCP

Ports to listen on for NetVault devices operating as NDMP movers.

These ports are used for data transfers between NDMP filer and storage device. These ports are required on the NetVault Server or Client to which the device is attached.

49152 through 65535

TCP

Dynamic ports that are used during the client push installation process.

 

 

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択