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

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

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

About storage devices

NetVault supports a wide range of devices for storing backups. The supported devices include disk-based storage devices, deduplication appliances, physical tape libraries, autoloaders, tape drives, Virtual Tape Libraries (VTLs), and Shared Virtual Tape Libraries (SVTLs).

You can attach the storage devices to the NetVault Server, Clients, or NAS filers in a NetVault Domain. The physical storage devices can be configured for single or shared use, and connected through SCSI, iSCSI, IP, SAS, or Fiber Channel SAN interfaces. A NetVault SmartClient license is required to attach physical or virtual storage devices locally to a NetVault Client.

To use a storage device in a backup or restore operation, you must first add the device to the NetVault Domain. A device attached to a NetVault Client is only recognized after you add the client to the NetVault Server. Similarly, a device attached to a filer is only recognized after you add the filer to the server using NetVault Plug-in for NDMP (Plug-in for NDMP).

SAN considerations

The following requirements apply to a SAN environment:

•
In a SAN environment, you must use persistent binding (also known as SCSI mapping, persistent reservation, or persistent naming).
NetVault cannot communicate with a library if its logical address changes as a result of changes in the SAN. Persistent binding assigns a fixed logical address to the device. This address does not change as devices are added or removed in the SAN.
For Fiber Channel Host Bus Adapters (HBAs), you can map the Fiber Channel device address (World Wide Name (WWN) or World Wide Identifier (WWID)) or Loop ID to the logical SCSI address. This configuration ensures that the changes in the SAN have no impact on the NetVault operations.
•
You must also use persistent binding when the server and fiber devices are attached to separate switches or when zoning is implemented.
NetVault does not support multipathing to a tape library or device. To ensure consistent communication path, you must configure only one logical or physical channel for use.
You should not use tape libraries or drives on the same switch or in the same zone that has disk devices attached. Problems might be encountered if packets from both device types co-exist in a SAN environment. Therefore, you should use separate HBAs for these devices.
•
Apple supports multipathing in FC Host Adapter and XserveRAID. Multipathing is often the default setting after installation. However, multipathing is not supported in NetVault. Therefore, the connections should be logically or physically separated to ensure a consistent communication path.

Quest DR Series systems

This section includes the following topics:

•
About Quest DR Series systems
•
Quest DR Series system prerequisites
•
Adding a Quest DR Series system
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択