Chat now with support
Chat with Support

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

Adding a container for QoreStor from the Manage Devices page

1
In the Navigation pane, click Manage Devices, and then click the plus icon corresponding to the QoreStor device.
2
On the Quest QoreStor page, verify that the Containers option is selected.
3
For the applicable device, click the corresponding icon in the Actions column, and select Add As A Media.
4
On the Add Media page, provide the following details:

Storage Group Name

Select the name of the storage group.

Container

Select the name of the storage container.

Block size

The default block size is 512 KiB. The block size cannot be changed for Quest QoreStor systems.

Stream Limit

The default value for this setting is 64streams. This setting applies to all NetVault Servers to which the container is added. If the number of data streams exceeds the defined limit for the container, the Media Manager reports an error (“Device has too many streams”).

You can set the soft stream limit to any value between 1 and 512.

If the container is added to more than one NetVault Server, set the same soft stream limit on all servers.

Force Add

If the device is already added to another NetVault Server with the same name, select the Force Add check box. This option can be useful if you have performed a disaster recovery to rebuild the NetVault Server.

5
Click Add As A Media.

Adding a container from the Quest QoreStor page

To add a container as a media, see Adding a container as a Media for QoreStor.

Passthrough: When this mode is selected, deduplication processing occurs on the Quest QoreStor system. The passthrough mode requires at least 200 MB of free memory on the NetVault Client.
Optimized: When this mode is selected, deduplication processing occurs on the NetVault Client. The Optimized mode requires at least 4 GB of free memory on the NetVault Client.
Auto: When this mode is selected, NetVault decides the deduplication mode (Passthrough or Optimized) based on the criteria for Passthrough and Optimized.

Object storage

This section includes the following topics:

About object storage

The option to connect NetVault to object storage lets you save backups directly to the cloud. The direct-to-object feature is available only for Azure Blob and S3-compatible storage targets, including AWS S3, Wasabi, RSTOR, and any other S3-compatible storage.

NOTE: For the Direct-to-Object feature work on an HP-UX platform, you must manually copy librofsobjectoca.so from /usr/netvault/dynlib/bit-64/ to /usr/netvault/dynlib/. Without this change, direct-to-object backup does not work on HP-UX.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating