Chat now with support
Chat with Support

NetVault 12.3 - Administration Guide for Managed Service Providers

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

Device configuration in cluster environment

In a cluster setup, a backup device can be connected in different ways. This section describes the pros and cons of some of the device configuration methods.

Connecting a device to the NetVault Backup Server or Client: This type of configuration allows the control of a robotic arm. However, during backups and restores, the data is transferred over the network.
Sharing drives: A derivative of the previous method can be used by connecting the physical library to the NetVault Backup Server, thus, giving it the control of the robotic arm, and sharing the drive with the cluster nodes. This configuration allows the control of the robotic arm and at the same time enables local data transfers.
Connecting a device to a cluster node: This configuration offers the fastest method of data transfer as the data is routed directly to a locally attached device.

Installing and upgrading cluster-aware plug-ins

This section includes the following topics:

Prerequisites

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

Install NetVault Backup Server: Install the NetVault Backup 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 Backup Installation Guide.
Install the NetVault Backup Client: Install the NetVault Backup Client software on the individual cluster nodes. For instructions on installing the client software, see the Quest NetVault Backup Installation Guide.
Add NetVault Backup Clients: Add the clients to the NetVault Backup 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 Backup Server.

Installing a cluster-aware plug-in

In a cluster setup, the plug-in is installed by creating a virtual client on the NetVault Backup 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.

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.

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