Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

About Virtual Tape Library

Virtual Tape Libraries (VTLs) emulate tape libraries on disk. VTLs are included in NetVault as a licensable option.

With VTLs, you have the flexibility to perform quick backups to disks, and during off-peak hours migrate or duplicate the backups to physical devices for off-site storage. The Media Manager does not distinguish between virtual and physical tapes. Therefore, you can use the same process to set up backup policies, including retirement period and rotation schemes.

VTLs are represented as directories on the disk. Each VTL contains three directories: drives, slots, and media. These directories contain numbered subdirectories. The virtual drives reside as files in the drives subdirectories. These files contain links to the media files. The virtual tapes reside as media files in the media directory. When a virtual tape is moved between slot and drive, the media file itself stays in the media directory, while the drives and slots files are modified to emulate the moving of the media.

A VTL can handle any number of concurrent NetVault Client backups. As with a physical library, the number of drives contained in the VTL dictate how many simultaneous operations can be performed. The number of slots should be the same as or more than the number of configured drives. Different operating systems may impose maximum file-size limits, which can affect the maximum VTL media size.

 
* 
NOTE: VTLs are independent of file systems (for example, NTFS, UFS, ext3, and others) and disk systems (for example, IDE, SCSI, iSCSI, and others), but VTLs do not support file systems residing on removable drives.

Direct-to-cloud support

Beginning with release 12.3, NetVault supports StarWind Virtual Tape Library (StarWind VTL), which converts physical drives into virtual tapes to emulate tape hardware. It supports standard uplink protocols, including SMB3, NFSv4.1, iSCSI, and works with most virtual environments.

StarWind VTL is available on Microsoft Azure Marketplace, on AWS Marketplace, and as on-premises appliance

NetVault supports public and private cloud object storage replication with StarWind VTL through any of the following storage service providers:

•
Amazon S3 and Amazon Glacier
•
Amazon S3 Compatible
•
BlackBlaze B2 Cloud Storage
•
Microsoft Azure Cloud Storage
•
Wasabi Cloud Storage

Virtual Tape Library considerations

Before creating and adding a VTL, review the following information:

•
Before creating a VTL, NetVault performs a disk space check to ensure that the target disk has sufficient space to accommodate the new VTL.
On normal file systems you can use the disk space check feature to avoid errors during VTL creation. When creating a VTL on a third-party deduplication appliance or compressed file system, you should disable this feature. For more information, see Configuring default settings for Disk Devices Plug‑in.
•
During disk space checks the free space required on the disk is calculated as follows:
Number of Slots * Media Capacity + <x>
Here <x> is the additional disk space considered for the following requirements:
•
Disk space required to create the directory structure for VTL. The requirement varies for different file systems.
•
Disk space required by other applications running on the system.
By default, the additional space requirement is set to 20MB. To change this setting, see Configuring default settings for Disk Devices Plug‑in.
•
If the target disk does not have sufficient space to accommodate the specified VTL, the device emulation process is terminated and a message is displayed.

Creating and adding a Virtual Tape Library

You can use the configuration wizard to create a virtual tape library on the NetVault Server or a SmartClient. When creating a VTL, you can choose the number of virtual tape drives and slots, and specify the size of the virtual tapes. After the device is created, it is automatically added to the server.

To create and add a Virtual Tape Library:
1
In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, click Add Storage Devices.
— or —
In the Navigation pane, click Manage Devices, and then click Add Device.
2
On the Add Storage Devices page, select the Virtual tape library/media changer option, and click Next.
3
In the list of NetVault machines, select the machine on which you want to create the device, and click Next.
4
On the Add Virtual Tape Library page, provide the following details.
Figure 8. Add Virtual Tape Library page
Table 34. Add Virtual Tape Library
 
Option
Description

Choose the location on disk where you wish to create the new device

Enter the location where you want to create the VTL, or use the Browse button to select a location.

When entering a location, make sure that the path is already created on the selected machine. NetVault does not automatically create any non-existing directories in the path.

To create a path, click Browse, select a parent folder, and then click Add new folder, After you click OK, the new folder is added to the parent folder and can be used as the location for the new device.

Choose a name for the device

Specify a unique name for the device.

NOTE: The VTL name does not support non-Latin characters.

Device display name

Specify a display name for the device.

Choose a 5 character media barcode prefix

The NetVault Server automatically generates a barcode prefix and assigns it to the VTL media. If you want to change it, type a unique code for the device.

Specify the media capacity

Type or select the size of the virtual tape. The media size is specified in GiB. Each slot contains a piece of media of the given size. The default value is 32GiB.

Choose number of drives

Type or select the number of drives for the VTL. You can create maximum of 100 drives. The default value is two drives.

Choose number of slots

Type or select the total number of slots that hold the media. You can specify a maximum of 999 slots. The default value is 16 slots.

5
Click Next to create and add the device.
 
* 
NOTE: The amount of time it takes to create a VTL depends on the media capacity and number of slots specified for the VTL. The time required is proportional to the VTL size.
6
After the device is successfully added and initialized, a message is displayed.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation