Tchater maintenant avec le support
Tchattez avec un ingénieur du support

NetVault 13.2 - 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

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.

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:

IMPORTANT:  

For more information, see the following sections:

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.

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:

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.

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

Locating a client

The clients that reside in a different subnet are not included in the list of available clients. You can use the Find Machine option to locate and add such clients.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation