サポートと今すぐチャット
サポートとのチャット

NetVault 12.2 - Administration Guide

Introduction Getting started Configuring clients Managing catalog search Configuring storage devices Backing up data Managing policies Restoring data Managing NetVault Backup 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 Backup Working with client clusters Configuring default settings for NetVault Backup
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 Backup WebUI default settings Configuring NetVault Backup to use a specific VSS provider Configuring default settings using Txtconfig
Diagnostic tracing Managing diagnostic data Using the deviceconfig utility NetVault Backup processes Environment variables Network ports used by NetVault Backup Troubleshooting

About NetVault Backup Clients

The NetVault Backup Clients are machines that you want to protect using the NetVault Backup solution.

These machines require at least the client version of NetVault Backup and TCP/IP connectivity to the server. You can attach physical and virtual storage devices locally to a client after installing the NetVault Backup SmartClient license on it.

To use a client in a backup or restore operation, you must first add the client to the NetVault Backup Server. A single server and its associated clients form a NetVault Backup Domain. A NetVault Backup Server acts as a client to itself, and you can also add it as a client to other NetVault Backup Servers.

Installing software from WebUI (push installation)

This section includes the following topics:

•
About push installation
•
Prerequisites
•
Managing package stores
•
Performing push installations
•
Monitoring deployment tasks
•
Managing deployment tasks

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 Backup Client software and NetVault Backup 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 Backup 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. 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 Backup Server.

By default, NetVault Backup 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 Backup Server and all target machines where you want to install the packages.
Ensure that you use the original names of the installation packages. Renamed packages cannot be selected for push installations.
•
Configure a package store in NetVault Backup: After copying the installation packages, configure the shared location details in NetVault Backup. For more information, see Configuring a package store.
•
Configure the preferred network address setting on multihomed NetVault Backup Servers: On multihomed NetVault Backup 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.
If the remote clients fail to contact the server on the correct address, the task status is not updated on the server. In such cases, the clients are not added to the server and the task either remains in the Running state or completes with warnings.
•
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 Backup 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.
To push the client and plug-in packages to a remote Linux machine, the NetVault Backup Server establishes an SSH connection with the remote machine over port 22.
If there is a firewall between the server and the remote client, ensure that these ports are opened to allow the WMI RPC traffic to pass through the firewall. Also ensure that an inbound rule is created for the HTTP or HTTPS listen port that is configured on the NetVault Backup Server.

When pushing the NetVault Backup 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:
<username> ALL=NOPASSWD: ALL
or
<username> ALL=(ALL) NOPASSWD: <users home directory [/home/username or
/home/domainname/username]>/nvpushinstall/nvclientinstaller
* 
NOTE: If user fails to get sudoers privilege from the sudoers file, the deployment task will always be in the running state with Request sent to launch installation agent on the remote machine message.
 
•
Affirm the password authentication: In the sshd_config file, set the PasswordAuthentication entry to yes.
•
If you are not using the default cipher setting, then support for aes128-ctr should be present. If it is not, then you must add aes128-ctr at the end of the list following a comma in the etc/ssh/sshd_config file.
•
Install libstdc++: If you are pushing the hybrid installation package of the NetVault Backup client on a 64-bit Linux machine, you must first install the 32-bit version of libstdc++.

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

•
Ensure the WinRM version is greater than 2.0.
•
Check WinRM on Windows client machine to verify Kerberos value:
1
Run the following command as an administrator in command line interface to open the config file.
winrm get winrm/config
2
Check the Kerberos value in the Auth section is set to true:
Kerberos = true
For more information on Installation and configuration for Windows Remote Management, see,
https://docs.microsoft.com/en-us/windows/desktop/winrm/installation-and-configuration-for-windows-remote-management.
•
Configure Kerberos on Linux machine:
•
Run the following command to open the krb5 config file:
vi /etc/krb5.conf
In the libdefaults section set the following value:
default_realm=<EXAMPLE.COM>
default_ccache_name = KEYRING:persistent:%{uid}
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択