Chat now with support
Chat with Support

NetVault 13.1 - Administrator's 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

Adding multiple clients

When adding clients to a Windows-based or Linux-based NetVault Server, can use the following procedure to add multiple clients at the same time.

 
* 
NOTE: A NetVault Server can only support clients of the same version as itself or older. The NetVault Client software version cannot be higher than the NetVault Server software version.
To add multiple clients to a NetVault Server:
1
In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, select the Install Software/Add Clients option.
2
On the Machines to Be Added as Clients page, next to Machines, click the add (+) icon, and select a method for adding the deployment targets.
3
In the Add Machines window, on the Machine Details tab, enter the following details based on your method selection.
 
Method
Description

By FQDN or IP

To manually add the deployment targets, select this method.

On the Machine Details tab, specify the FQDN or IP address of the client.

Click Next.

From Active Directory

To select machines from an Active Directory Domain, select this method.

On the AD Details tab, provide the following details:

•
AD Server Address: Type the host name or IP address of the Active Directory Server.
•
User Name: Specify a Domain Account that is in the local Administrators group of all target machines.
The user name must be specified in the following format:
<AD domain>\<user name>
— or —
<NETBIOS name>\<user name>
— or —
<user name>@<AD domain>
•
Password: Specify the password for the user account.

Optionally, if you want NetVault to remember the password for this user name, select Save Credential.

NOTE: Saved credentials are visible only to the user who saved them. They are not available to any other users.

Click Connect.

In the list of Active Directory Objects, select the target machines, and click Next.

From a file

To import the target list from a file, select this method.

In the Add machines from file dialog box, click Select a file. After selecting the file in the browse window, click OK to upload the file.

For more information about the file format, see File format for specifying deployment targets.

From available machines

To add a client from available machines, select this method.

On the NetVault Machine Details tab, select the client that you want to add.

Provide the NetVault password in the Machine Password box.

Click Next.

4
Configure the applicable parameters.
 
Option
Description

Installation Settings

On the Installation Settings tab, provide the NetVault password.

If no NetVault password is set for the client, specify the administrator password for the machine.

Click Next.

Client Settings

On the Client Settings tab, provide the following details:

•
Client Description: Type a descriptive text for the client.
Client description can help you determine the location of the client or the role of the machine.
•
Client Group: To add the client to one or more client groups, select the corresponding check boxes.
The client groups that are configured to contain all clients are selected by default. You cannot change these selections.

Click Next.

Firewall Settings

If the client resides on a network that is outside the firewall, select the Client is Outside Firewall check box on the Firewall Settings tab, and provide the TCP/IP port specifications. For more information about these settings, see About firewall settings.

5
To save the client details, click OK.
6
Before submitting the task, do the following:
•
Click Verify to check connectivity to the clients. If any errors are reported, click Edit, and modify the applicable installation parameters.
•
If you want to assign a user-defined task name, type the name in the Task Name box.
7
To submit the task, click Add Clients.
You can monitor the progress and status of the task from the Deployment Task Status page. For more information, see Monitoring deployment tasks.

About firewall settings

Firewall settings are required to communicate with NetVault Clients that reside outside the firewall. You can use these settings to specify the TCP/IP ports for establishing data transfer channels, message channels, and broadcast channels through the firewall.

You can configure the firewall settings when deploying or adding a client, or update these settings from the Change Settings page. You can also use the NetVault WebUI or Txtconfig utilities to configure the firewall settings for new or existing clients.

 
* 

NetVault does not support firewalls using NAT (Network Address Translation)/IP Masquerading.

The following table provides a brief description of the firewall settings.

 
Table 16. Firewall settings
Option
Description

Listen ports for devices

Ports to listen on for device requests.

Configure this option on the NetVault machines that have a locally attached device (for example, NetVault Server or NetVault Clients with SmartClient licenses).

Requirement: Two ports per drive.

Connect ports for devices

Ports that plug-ins use to connect to remote storage devices.

Configure this option on clients that connect to remote devices.

Requirement: Two ports per drive.

Listen ports for NetVault message channels

Ports for receiving messages during data transfers.

Configure this option on both the NetVault Server and the Client. NetVault requires a two-way connection between the Server and the Client for message channels.

Requirement: Three ports per client.

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

Connect ports for NetVault message channels

Ports for sending messages during data transfers.

Configure this option on both the NetVault Server and the Client. NetVault requires a two-way connection between the Server and the Client for message channels.

Requirement: Three ports per client.

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

Connect ports for NDMP control channels

Ports for sending NDMP messages (NDMP control channels).

Configure this option on the NetVault Server (on which the plug-in is installed) when a firewall separates an NDMP filer and the NetVault Server.

By default, NetVault uses port number 10000. You can change it, if necessary.

Listen ports for NDMP data channels

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

Configure this option on the NetVault Server or Client to which the device is attached. These ports are used for data transfers between the NDMP filer and storage device when a firewall separates the two networks.

Connect ports for inter-machine setup

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

Requirement: Two ports per client.

You can use the following formats to specify the ports or port ranges for data channels, message channels, and broadcast channels:

•
A comma-separated list (example: 20000, 20050)
•
A port-range separated by a dash (example: 20000-20100)
•
A combination of comma-separated list and port-range (example: 20000-20100, 20200)
 
* 
NOTE: You must configure the same port-range for data, message, and broadcast channels across all NetVault machines.
 
* 
IMPORTANT:  
•
NetVault does not support firewalls using NAT (Network Address Translation)/IP Masquerading.
•
NetVault uses port number 20031 for TCP and UDP messaging. Make sure that this port is open on the firewall.

For more information, see the following sections:

•
Firewall filtering rules
•
Firewall configuration example

Firewall filtering rules

When creating firewall rules on the server and client machines, make sure that you open the following ports to send and receive traffic from NetVault.

 
Table 17. Firewall filtering rules
From
To
TCP/UDP
Source port
Destination port

Server

Client

TCP

Connect ports for inter-machine connection setup specified on the NetVault Server

20031

Client

Server

TCP

Connect ports for inter-machine connection setup specified on the NetVault Clients

20031

Server

Client

TCP

Connect ports for message channels specified on NetVault Server

Listen Ports for Message Channels specified on the NetVault Clients

Client

Server

TCP

Listen ports for message channels specified on the NetVault Clients

Connect Ports for Message Channels specified on the NetVault Server

Server

Client

UDP

20031

20031

Client

Server

UDP

20031

20031

Server

Client

TCP

Listen ports for devices specified on the NetVault Server and Clients

Connect ports for devices specified on the NetVault Clients

Client

Server

TCP

Connect ports for devices specified on NetVault Clients

Listen ports for devices specified on NetVault Server and Clients

Firewall configuration example

This example illustrates the network port requirements for a NetVault system with the following configuration:

•
Number of drives: 6
•
Number of clients with one plug-in: 10
•
Number of clients with two plug-ins: 2
 
Table 18. Example: Port requirement calculation
NetVault machine
Port type
Requirement
Total ports
Example port range

Server (with locally attached storage device)

Connect ports for inter‑machine connection setup

Minimum two ports per client

24

50300-50323

Connect ports for NetVault message channels

Minimum three ports per client

40

50200-50239

Listen ports for devices

Minimum two ports per drive

12

50100-50111

Client

Connect ports for inter‑machine connection setup

Minimum two ports per client

(These ports can be the same as the ports specified on the server side.)

24

50300-50323

Listen ports for NetVault message channels

Minimum three ports per client

40

50500-50539

Connect ports for devices

Minimum two ports per drive

12

50400-50411

The following table illustrates the firewall filtering rules for this system.

 
Table 19. Example: Firewall filtering rules
From
To
TCP/UDP
Source port
Destination port

Server

Client

TCP

50300-50323

20031

Client

Server

TCP

50300-50323

20031

Server

Client

TCP

50200-50237

50500-50537

Client

Server

TCP

50500-50537

50200-50237

Server

Client

UDP

20031

20031

Client

Server

UDP

20031

20031

Server

Client

TCP

50100-50111

50400-50411

Client

Server

TCP

50400-50411

50100-50111

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating