Chat now with support
Chat with Support

NetVault 11.3 - Administration Guide

Introduction Getting started Configuring clients Configuring storage devices Backing up data Managing policies Restoring data Managing jobs Monitoring logs Managing storage devices
Monitoring device activity Managing disk-based storage devices in table view Managing disk-based storage devices in tree view Managing tape libraries in table view Managing tape libraries in tree view Managing tape drives in table view Managing tape drives in tree view Adding shared devices
Managing storage media Managing user accounts Monitoring events and configuring notifications Reporting in NetVault Backup Working with client clusters Configuring default settings for NetVault Backup
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 Backup to use a specific VSS provider Configuring default settings using NetVault Configurator Configuring default settings using Txtconfig
Diagnostic tracing Using the deviceconfig utility NetVault Backup processes Environment variables Network ports used by NetVault Backup Troubleshooting

Shared Virtual Tape Libraries

This section includes the following topics:

About Shared Virtual Tape Libraries

NetVault Backup Shared Virtual Tape Libraries (SVTLs) extend the VTL implementation by allowing you to share a VTL with multiple NetVault Backup 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 11. 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.

#!/bin/sh

grep -v "^ *#" /etc/sysconfig/rawdevices | grep -v "^$" |

while read dev major minor;

do

if [-z “$minor”]; then

echo “ACTION==\”add\”, KERNEL==\”${major##/dev/}\”,

RUN+=\\”/bin/raw $dev%N\"“

else

echo “ACTION==\”add\”, ENV{MAJOR}==\”$major\”,

ENV{MINOR}==\”$minor\”, RUN+=\\”/

bin/raw $dev%M%m\”$dev%M%m\””

fi

done

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.

Related Documents