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

NetVault 13.0.2 - Administration Guide for Managed Service Providers

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

Working with client clusters

•
About client cluster support
•
Device configuration in cluster environment
•
Installing and upgrading cluster-aware plug‑ins
•
Configuring a cluster-aware plug-in
•
Managing virtual clients
•
Backups using cluster-aware plug‑ins
•
Restores using cluster-aware plug-ins

About client cluster support

NetVault offers cluster-aware versions of various plug-ins that enable data protection for distributed data. These plug-ins require Cluster Support Licenses.

The cluster nodes are grouped into a Virtual Client on which the cluster-aware plug-in is installed. The backups and restores of cluster nodes are performed through the virtual client.

The following table lists the NetVault plug-ins that can be used in a cluster setup.

 
Table 124. Cluster-aware plug-ins
Plug-in
Description

Quest NetVault Plug-in for FileSystem

This plug-in is shipped with the NetVault software and can be used to back up the shared file system data on the following platforms:

•
Windows Server Clusters
•
Linux Clusters
•
Sun Clusters (Solaris SPARC)

For more information about the supported cluster software versions, see the Quest NetVault Compatibility Guide. You can download this guide from https://support.quest.com/technical-documents.

A default installation of NetVault does not require licensing of its native Plug-in for FileSystem. However, to use this plug-in a cluster setup, a File System Cluster Support license is required.

Quest NetVault Plug-in for Exchange

This plug-in can be deployed in an Exchange Server Single Copy Cluster (SCC)/Failover Cluster or Cluster Continuous Replication (CCR) setup to back up the distributed Exchange Server data. For more information, see the Quest NetVault Plug-in for Exchange User’s Guide.

Quest NetVault Plug-in for Hyper-V

This plug-in can be deployed in a Hyper-V failover cluster setup to back up cluster data through a virtual client. For more information, see the Quest NetVault Plug-in for Hyper-V User’s Guide.

Quest NetVault Plug-in for Oracle

This plug-in can be used in Oracle's Real Application Clusters (RAC) setup to back up the distributed Oracle database. For more information, see the Quest NetVault Plug-in for Oracle User’s Guide.

Quest NetVault Plug-in for SQL Server

This plug-in can be used in a SQL Server Failover Cluster setup to back up the distributed SQL Server database. For more information, see the Quest NetVault Plug-in for SQL Server User’s Guide.

Quest NetVault Plug-in for MySQL

This plug-in can be used in a MySQL Server Failover Cluster setup on Linux platform to back up the distributed MySQL Server database. For more information, see the Quest NetVault Plug-in for MySQL User’s Guide.

Virtual clients

A virtual client is created when you install a cluster-aware plug-in. All nodes in a cluster are grouped to form a virtual client.

A virtual client is managed like any other NetVault Client. It can be browsed and added to client groups and policies, granted user access, and included in reports. The NetVault Server administers the creation and configuration of a virtual client. The cluster-aware version of the plug-in runs locally on the cluster nodes and the data is processed locally. A cluster node configured as a SmartClient sends data directly to the locally attached storage device.

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 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 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.
This configuration offers high drive availability. With all cluster nodes sharing the control of drives, the drives are always available. However, the cluster node that currently controls the drive does not need to be the node that currently controls the cluster.
•
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.
However, the disadvantage is that the robotic arm cannot be controlled by a machine within the cluster, limiting the device type usage for this type of configuration to standalone drives. Moreover, the drive becomes unavailable when the cluster node is down.

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
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択