Chatee ahora con Soporte
Chat con el soporte

NetVault 13.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

Shared Virtual Tape Libraries

This section includes the following topics:

About Shared Virtual Tape Libraries

NetVault Shared Virtual Tape Libraries (SVTLs) extend the VTL implementation by allowing you to share a VTL with multiple NetVault machines for LAN-free backups.

SVTLs are supported on the following platforms:

The interface can be Fibre Channel, iSCSI, or SCSI. On Linux and Solaris platforms, SCSI_FCP protocol is also supported. The disks can be of any size. However, operating system-imposed limitations do apply. The SVTL size can be changed during runtime using CLI utilities.

Figure 10. SVTL

SVTL considerations

Before setting up an SVTL, consider the following:

SVTL prerequisites

Before creating an SVTL, verify that the following requirements are met:

Binding is performed using a utility named raw, which is normally supplied by the Linux distributor.
On Solaris systems hosting the SVTL or sharing the drives, specify the SCSI ID and LUN values for the applicable disks and volumes in the file /kernel/drv/sd.conf. This requirement is applicable only if you are using a disk or RAID volume on a SAN. Use the following format to specify the values:

To set up raw I/O on Linux-based systems, you require the following:

A raw device controller named /dev/rawctl or /dev/raw. If the controller is not present, type the following command to create a symbolic link:

The following example shows how to set up raw I/O on Linux:

1
At the prompt, type the following command to display information from the file devices.txt. You can find this file in the /usr/src/linux/Documentation directory:

If you require /dev/raw/raw1 and /dev/raw/raw2, follow the same procedure using the proper numbers listed in the devices.txt file and set the same permissions.

The following example shows how to set up raw I/O on Red Hat Linux. The raw partition used is /dev/sda.

3
For persistent binding, open the /etc/sysconfig/rawdevices file and append the following line:

The raw devices interface has been deprecated in Red Hat Enterprise Linux 5; the raw device mapping is now performed using udev rules. To correctly map the raw device, add the appropriate entries to the /etc/udev/rules.d/60‑raw.rules file in the following format:

Here <device name> is the name of the device that you want to bind (for example, /dev/sda1), A and B are the major or minor numbers of the device you want to bind, and X is the raw device number that you want the system to use.

If you have a large pre-existing /etc/sysconfig/rawdevices file, convert it using the following script.

On SUSE Linux, administer the raw disk partitions in the /etc/raw file. This plain text file contains comments and examples for possible configurations. After creating the raw devices, bind the raw devices by starting them with the script /etc/init.d/raw. Use the chkconfig(8) utility to ensure that the raw device binding occurs after any restart.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación