Chat now with support
Chat with Support

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

Installing software from WebUI (push installation)

This section includes the following topics:

About push installation

The push installation method lets you install one or more software packages on remote machines. You can use this method to install or upgrade the NetVault Client software and NetVault plug-ins on multiple machines, including Windows-based and Linux-based machines. Push installation is available for Windows-to-Windows, Windows-to-Linux, Linux-to-Linux, and Linux-to-Windows scenarios.

You can run push installation tasks from the NetVault WebUI. When the task starts, a deployment agent is installed on the remote machines. The agent copies the installation packages from a shared location and performs silent installations on the machines. The agent also sends status messages to the server. By default, the client logs are preserved on the target machine. For more information about how to modify this setting, see Configuring default settings for Deployment Manager. You can view the task status from the WebUI. After the packages are successfully installed on the machines, the WebUI automatically adds the new clients to the NetVault Server.

By default, NetVault runs a maximum of 50 concurrent push-installation processes. You can modify the default settings to increase the number of concurrent processes. For more information, see Configuring default settings for Deployment Manager.

Prerequisites

Before you start the push installation procedure, verify that the following requirements are met:

Copy the packages to a shared location: Copy the client and plug-in packages to a shared location. Only CIFS shares, including Linux Samba Shares, are currently supported as package stores. The path must be accessible to the NetVault Server and all target machines where you want to install the packages.
Configure a package store in NetVault: After copying the installation packages, configure the shared location details in NetVault. For more information, see Configuring a package store.
Configure the preferred network address setting on multihomed NetVault Servers: On multihomed NetVault Servers, configure the Preferred Network Address setting to allow the remote clients to send status messages to the correct address. For more information about this setting, see Configuring network addresses for multihomed machines.
Verify that the firewall is configured to allow traffic through the ports required for push installation: To push the client and plug-in packages to a remote Windows machine, the NetVault Server establishes the initial WMI session with the remote machine using RPC over port 135. All further WMI traffic uses the dynamic port range of 49152 through 65535.

When pushing the NetVault client installation to a Linux machine, you need the following additional prerequisites:

Grant the proper access: The user must have root-level access, with the NOPASSWD flag set in the sudoers file on the remote Linux machine. To complete this prerequisite, add one of the following entries to the sudoers file:
Affirm the password authentication: In the sshd_config file, set the PasswordAuthentication entry to yes.
Install libstdc++: If you are pushing the hybrid installation package of the NetVault client on a 64-bit Linux machine, you must first install the 32-bit version of libstdc++.

When you push the NetVault client from a Linux machine to Windows machine, you need the following additional prerequisites:

Ensure the WinRM version is greater than 2.0.
2
Check the Kerberos value in the Auth section is set to true:
Configure Kerberos on Linux machine:
During Push installation specify the domain suffix (for example: domain.com or domain.local) for the same account name or DL format.

Managing package stores

This section includes the following topics:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating