지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Determining the current real client

You can use the Current Real Client option to find out which machine is in control of the cluster application.

To determine the machine that is currently in control of the cluster application:
1
In the Navigation pane, click Manage Clients.
2
In the list of NetVault Clients, select the target virtual client, and click Manage.
3
On the Virtual Client page, click Current Real Client.
In the dialog that appears, the NetVault name of the controlling node is displayed.
Click OK to close the dialog box.

Removing a virtual client

You can remove a virtual client if you no longer want to use the associated plug-in in a cluster setup. When you remove a virtual client, the cluster nodes added as NetVault Clients are not removed from the server. However, it removes the ability of the plug-in to back up the cluster data.

To remove a virtual client:
1
In the Navigation pane, click Manage Clients.
2
In the list of NetVault Clients, select the target virtual client, and click Manage.
3
On the Virtual Client page, click Remove.
4
In the Confirm dialog box, click Remove.

Backups using cluster-aware plug-ins

Backups using cluster-aware plug‑ins

The procedure for performing backups using the Plug-in for FileSystem is similar for both standard and virtual clients. The cluster-aware version of the plug-in can be used in the same manner as the standard version to select the data items. However, when you open the virtual client node on the NetVault Selections page, only the cluster-aware plug-in is listed under the node. The plug-in displays both shared and local drives and mount points in the selection tree. You must make a note of the drive letter or mount point for the shared resource and select the data accordingly. The backup options that can be set for the standard version are also available with the cluster-aware version.

For information about backing up data in the Exchange Server Clustered environment, Oracle RAC setup, SQL Server Failover Cluster, and MySQL Server Failover Cluster, see the relevant plug-in user’s guide.

Note the following:

•
When you back up a virtual client, the data is backed up from a single client and it is accessed from the controlling node.
•
When backing up cluster data using a virtual client, only the LUNs owned by the active node are backed up; the LUNs owned by passive nodes are not backed up.
•
In an Active/Active cluster setup, the NetVault Server may start a backup on a secondary node even if the “primary only” option is selected for the backup. In such cases, the backup is redirected to the primary node, but the server only communicates with the secondary node to which it sent the message to start the backup. If the secondary node becomes unavailable while the backup is in progress, the server loses communication with the parent process running on this client. This process is not restarted even if the secondary node becomes available immediately. Consequently, the backup job becomes unresponsive.
 
* 
NOTE: For cluster backups and restores, the virtual client name is displayed on the Job Status page and the actual client name is displayed on the View Logs page.
Cluster failover during backups

If a failover occurs during a backup, the job is aborted and the status “Job Failed” is returned. You can use the Job Retry scheduling option to run the job again after the failover completes.

With the Plug-in for FileSystem, when a failover occurs on Windows, the reason for the failover has a direct bearing upon the status of the failed job. Depending on the reason, the job returns the following exit status:

•
If the machine in control of the cluster resources goes offline during a backup, the job is aborted and the status “Job Failed” is returned. You can use the job retry feature to run the backup again.
•
If the machine in control of the cluster remains online but the actual cluster resource that is being backed up fails, the job is aborted and the status “Backup Completed with Warnings” is returned. The scheduled job retries do not work for such jobs. In this scenario, examine the job logs to find the missing data or run the job again to back up the data.

Restores using cluster-aware plug-ins

The procedure for performing restores using the Plug-in for FileSystem is similar for both standard and virtual clients. The backups are restored from the virtual client node and not the actual client node. When you submit a restore job, the plug-in communicates with the cluster service to determine the controlling node and targets this machine for the restore.

For information about restoring data in the Exchange Server Clustered environment, Oracle RAC setup, SQL Server Failover Cluster, and MySQL Server Failover Cluster, see the relevant plug-in user’s guide.

 
* 
NOTE: For cluster backups and restores, the virtual client name is displayed on the Job Status page and the actual client name is displayed on the View Logs page.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택