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

NetVault 13.0 - Administration Guide

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
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
Safe Mode in NetVault

Installing and upgrading cluster-aware plug-ins

Installing and upgrading cluster-aware plug‑ins

This section includes the following topics:

•
Prerequisites
•
Installing a cluster-aware plug-in
•
Upgrading a cluster-aware plug-in

Prerequisites

Before you start the installation procedure for a cluster-aware plug-in, verify that the following requirements are met:

•
Install NetVault Server: Install the NetVault Server software on the designated machine. The server must be a separate machine outside the cluster setup. For instructions on installing the server software, see the Quest NetVault Installation Guide.
•
Install the NetVault Client: Install the NetVault Client software on the individual cluster nodes. For instructions on installing the client software, see the Quest NetVault Installation Guide.
•
Add NetVault Clients: Add the clients to the NetVault Server. For information about adding a client, see Adding clients.
•
Copy the installation file: Copy the “.npk” installation file for the cluster-aware plug-in to the NetVault Server.
The path to copy the file is <NetVault home>\packages\standard on Windows and <NetVault home>/packages/standard on Linux. You can also copy the installation files to subdirectories in the standard directory.
The installation file for the Plug‑in for FileSystem (for the Server operating system) is already available in the standard directory.

Installing a cluster-aware plug-in

In a cluster setup, the plug-in is installed by creating a virtual client on the NetVault Server. All nodes in a cluster are grouped to form a virtual client. During the process, the plug-in is installed on the specified cluster nodes.

To install a cluster-aware plug-in:
1
In the Navigation pane, click Manage Clients.
2
On the Manage Clients page, and click Add Virtual Client.
3
On the Virtual Client page, provide the following information:
•
In Virtual Client Name, type a name for the virtual client. The name must be unique. Spaces are not recognized in a virtual client name and are replaced with an underscore (“_”) character. The virtual client name cannot be changed once it is configured.
•
In Virtual Client Address, type the IP address of the cluster application.
•
In the Package list, select the installation file for the plug-in. This list includes all cluster-aware “.npk” files copied to the packages directory and its subdirectories The following table provides the filenames for the installation files. Here x-x- x-x represents the version, build, and platform numbers.
 
Table 112. Installation files for cluster-aware plug-ins
Option
Description

Plug-in for FileSystem (for Windows)

win-x-x-x-x.npk

Plug-in for FileSystem (for Linux)

nvf-x-x-x-x.npk

Plug-in for FileSystem (for Solaris (SPARC))

nvf-x-x-x-x.npk

Plug-in for Exchange

exs-x-x-x-x.npk

Plug-in for Hyper-V

hv-x-x-x-x.npk

Plug-in for Oracle

ora-x-x-x-x.npk

Plug-in for SQL Server

sql-x-x-x-x.npk

Plug-in for MySQL

mys-x-x-x-x.npk

•
To add a cluster node to the virtual client, select the client node in the Available Clients table, and click the Add button to the left of the item. The selected client is moved to the Chosen Clients table.
•
To remove a cluster node from the virtual client, select the client node in the Chosen Clients table, and click the Remove button to the left of the item. The selected client is moved to the Available Clients table.
4
Click Create Virtual Client.
The NetVault Server starts installing the plug-in on the selected cluster nodes. This process overwrites the standard version of the same plug-in installed on the cluster nodes. However, you can use the cluster-aware version to perform backups of the local non-shared data. When the installation completes, the virtual client is added to the NetVault Clients table on the Manage Clients page.

Upgrading a cluster-aware plug-in

To upgrade a cluster-aware plug-in, the existing virtual client is removed and a new virtual client is created using the latest version of the plug-in.

To upgrade a cluster-aware plug-in:
1
Remove the virtual client that was created with the previous version of the plug-in. For more information about removing a virtual client, see Removing a virtual client.
2
Create a new virtual client using the upgraded version of the cluster-aware plug-in. For more information about installing the plug-in, see Installing and upgrading cluster-aware plug‑ins.
You must assign the old virtual client’s name to the new virtual client. If you change the name for the new virtual client, you cannot run the jobs that were defined for the old virtual client.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択