Chat now with support
Chat with Support

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

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 specify the addresses that are not to be resolved:
1
In the Navigation pane, click Change Settings.
2
On the NetVault Server Settings page, complete one of the following actions:
•
To configure default settings for the NetVault Server, continue to Step 3.
•
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.
You can specify a single address or a range, for example, 192.168.1.2 or 192.168.x.x. If you want to configure multiple addresses or networks, use a comma as delimiter.
To get the list of networks from the machines.dat file, issue the following command on Windows:
findstr Network <NetVault home>\etc\machines.dat
The following is an example output:
C:\NetVault\etc>findstr Network machines.dat
Networks=192.168.203.1,192.168.65.1,172.16.245.1
Networks=10.1.40.81,172.16.211.1,172.16.62.1
Networks=10.1.2.37,172.16.22.1,172.16.128.1
Networks=10.1.240.222,172.16.4.1
Networks=192.168.122.1,10.1.240.52
Networks=10.1.80.83,10.1.2.68,172.16.116.1
Networks=192.168.172.1,10.1.40.98,192.168.147.1
Networks=192.168.174.1,10.1.8.71,192.168.120.1
Networks=192.168.122.1,10.1.8.79
Networks=10.1.8.132,192.168.91.1,192.168.106.1
Networks=10.1.8.163,192.168.233.1,192.168.207.1
Networks=10.1.8.16,200.0.0.1
...
Based on this output, you can configure the following values in the Comma separated list of networks and addresses not to resolve box:
10.0.0.0, 172.0.0.0, 192.0.0.0, 200.0.0.0
Some networks may have names instead of IP addresses. To find IP addresses for such clients, you can use the nslookup tool.
Note the following:
•
To prevent the NetVault Service from resolving all networks, specify the first octet of a network address (that is, 192.0.0.0, 10.0.0.0).
•
Using 0.0.0.0 does not prevent the service from resolving the networks.
•
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.
•
In a domain managed by a Windows-based NetVault Server, you may experience a long delay as the service attempts to resolve all client IP addresses using the NBNS (NetBIOS Name Service) protocol. In this environment, you can use the Comma separated list of networks and addresses not to resolve setting to reduce the startup delay.
You can also use this setting in a NetVault Client Cluster setup to prevent the service from resolving the private cluster IP addresses.
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.

To change the default port for Network Manager:
1
Open the file nvnmgr.cfg in a text editor. You can find this file in the config directory under the NetVault installation directory.
2
Add the following lines to this file:
[network]
UdpPort=<port number>
TcpPort=<port number>
Verify that the ports are not in use by any other application. In a firewall-protected environment, make sure that the ports are open and specified in the firewall settings for the client.
3
Save the file.
4
Restart the NetVault Service to apply the new settings.

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.

To change the default port for Communications Manager:
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:
[machine]
Comms TcpPort=<port number>
Verify that the port is not in use by any other application. In a firewall-protected environment, make sure that the port is open and specified in the firewall settings for the client.
3
Save the file.
4
Restart the NetVault Service to apply the new settings.

Configuring Process Manager settings

This section includes the following topics:

•
About Process Manager
•
Configuring shared memory settings
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating