Chat now with support
Chat with 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

Configuring timeout settings for Network Manager

To configure timeout settings for Network Manager:
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, go to Step 3.
•
To configure default settings for a NetVault Client, click Clients. In the NetVault Clients table, select the client, and click Next.
3
Under Services, click Network Manager.
4
In the Network Manager dialog box, under Timeouts, configure the following settings.
 
Table 133. Network Manager timeout settings
Setting
Description

Time to complete a remote connection

This setting controls how long the NetVault Server tries to establish a connection with a remote client.

The default setting is 300 seconds. To change the timeout interval, type or select a new value. The timeout interval is specified in number of seconds.

Time to wait before dropping inactive connection(s)

This setting controls how long the NetVault Server waits before ending an inactive connection. It helps to reduce the amount of resources consumed by idle connections.

The default setting is 600 seconds. To change the timeout interval, type or select a new value. The timeout interval is specified in number of seconds.

Keep Alive rate

Keep-alive messages are used to verify that a connection between two NetVault machines is still intact. The keep-alive rate controls how often the server sends keep-alive messages.

The default setting is 7 seconds. To change the interval, type or select a new value. The keep‑alive rate is specified in number of seconds.

Time between availability broadcasts

The NetVault Clients broadcast availability messages at regular intervals that provide their status and location on the network. These broadcasts are used to discover new clients and update the client status on the NetVault WebUI.

The default interval for availability broadcasts is 600 seconds. To change the interval, type or select a new value. The broadcast interval is specified in number of seconds.

NOTE: Setting a very small interval can increase the network traffic, while setting a large interval can cause delays in discovering the client and updating client status on the NetVault WebUI.

Time between security broadcasts

Security broadcasts discover the password-protection status of clients, and notify whether its password has been enabled or disabled on a client. The Client Status icons on the NetVault WebUI are updated based on these broadcasts.

The default interval for security broadcasts is 600 seconds. To change the interval, type or select a new value. The broadcast interval is specified in number of seconds.

Time between availability checks

The NetVault Server performs availability checks at regular intervals to scan for changes in the network settings. If a change is detected, the server sends an interim broadcast to propagate the new settings. The broadcast system is then reset to regular pulse, reducing network traffic.

The default interval for availability checks is 10 seconds. To change the interval, type or select a new value.

You can reduce the interval between two checks to quickly detect and transmit changes. If you do not want to apply the changes immediately, use the default value or set it equal to the interval for Availability Broadcasts.

5
Click Apply to apply the new settings and close the dialog box.

Enabling or disabling availability broadcasts

Availability broadcasts are used to discover NetVault Clients and update the client status on the NetVault WebUI. You can enable or disable availability broadcasts from the Change Settings page.

 
* 
NOTE: Although you can disable availability broadcasts, it is not recommended.
To enable or disable availability broadcasts:
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:
•
Broadcast details to machines on local network: This check box is selected by default. Although you can disable this option, it is not recommended.
Availability broadcasts are used to discover NetVault Clients and update the client status on the NetVault WebUI. Without these broadcasts, you can only add clients by using the client FQDN or IP address.
5
Click Apply to apply the new settings and close the dialog box.

Configuring network addresses for multihomed machines

For multihomed machines, you can specify the preferred network address, fallback addresses, and barred addresses from the Change Settings page.

When a connection is initiated, the addresses are attempted in the following order:

•
Preferred network address
•
Fallback addresses
•
Any other addresses in the order defined by the binding order of the host machine
To configure the network addresses for multihomed machines:
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 settings.
 
Table 134. Network settings for multihomed machines
Setting
Description

Preferred network address

Specify the primary IP address for network connection. You can only specify a single IP address.

Comma separated list of barred address(es)

Specify the barred or blocked addresses that you do not want to use for NetVault connections. To specify multiple addresses, use a comma as delimiter.

NOTE: You must restart the NetVault Service to apply any changes to the barred addresses setting.

Comma separated list of fallback address(es)

Specify the fallback addresses to use when the preferred network address is not available. To specify multiple addresses, use a comma as delimiter.

 
* 
IMPORTANT: You should use these settings only if machine is connected to multiple networks, either through multiple Network Interface Cards or through virtual IP addressing.

When configuring the network addresses, make sure that the preferred, barred, and fallback addresses do not conflict with each other

5
Click Apply to apply the new settings and close the dialog box.
Important notes

If the preferred address is unavailable and the NetVault Server starts using a fallback address, it does not automatically revert to the preferred address when the IP becomes available.

To force the NetVault Server to use the preferred address, do one of the following:

•
Remove the client and add it again.
When you remove the client, the message “Machine <NetVault Machine Name> Has Gone Down” (Warning Level: Background) is displayed on the View Logs page. Wait until the timeout for remote connection expires. The timeout interval is determined by the Time to complete remote connection setting (set to 60 seconds by default).
When the client is up and detected on the network, the message “Machine <NetVault Machine Name> Has Come Up” (Warning Level: Background) is displayed on the View Logs page. To add the client, use the Find Machine command, and specify its preferred network address in the box.
•
Alternatively, disable or disconnect the network interface currently in use until the timeout for remote connection expires. The value configured for the Time to complete remote connection setting determines the duration for which the network interface needs to be disabled or disconnected. Restart the NetVault Service when the client is reported as unavailable. The NetVault Server uses the preferred address when the next connection attempt is made after you restart the service on the client.

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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating