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

NetVault 12.4 - 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 Backup dashboard Managing jobs Monitoring logs Managing storage devices
Role-based access to manage 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 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 the reporting utility Configuring NetVault Backup WebUI default settings Configuring NetVault Backup to use a specific VSS provider Configuring default settings using Txtconfig
Diagnostic tracing Managing diagnostic data Using the deviceconfig utility NetVault Backup processes Environment variables Network ports used by NetVault Backup Troubleshooting
Common errors Safe Mode in NetVault Backup

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:

•
Windows
•
Linux (x86 and x86-64)
•
Solaris (SPARC and x86-64)

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

SVTL considerations

Before setting up an SVTL, consider the following:

•
The SVTL size depends on your disk size. Therefore, select a disk that meets your SVTL size requirements.
•
Verify that the disk is physically connected to all clients that access the SVTL. The number of virtual drives for the SVTL depends on the number of machines that access the SVTL. However, it is not limited by the number of machines currently connected to the disk. You can configure additional drives for future use.
•
Select the machine that controls the virtual arm changer. Although the SVTL drives can be shared or distributed among multiple clients, only one client controls the virtual arm changer.

SVTL prerequisites

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

•
General requirements
•
Set up raw I/O on Linux-based systems
•
Set up raw I/O on Red Hat Linux
•
Set up raw I/O on Red Hat Enterprise Linux 5 or greater
•
Set up raw I/O on SUSE Linux
General requirements
•
Connect the disk array to all NetVault Backup Clients that will share the SVTL. The interface can be Fiber Channel, iSCSI, or SCSI. On Linux and Solaris platforms, SCSI_FCP protocol is also supported.
•
Use an unformatted disk that contains no mounted partitions or volumes as an SVTL. A partition on a hard disk cannot serve as an SVTL. The additional requirements include the following:
•
The disk should allow multiple interfaces.
•
On Windows, any non-ejectable disk can serve as an SVTL.
•
NetVault Backup does not support Multipath, Powerpath, or software RAID technologies.
•
On Windows, delete the existing volumes on a disk or LUN before using it to create an SVTL.
•
On Windows 2008, Windows 7, and Windows Vista, use the Disk Management administrative utility to bring the disk online. When prompted to initialize the disk, select “No.” If you do not perform these steps, NetVault Backup cannot create an SVTL on the disk.
•
On Linux, bind the pool of raw device nodes to a block device before performing any raw I/O on it. There is a raw device controller that acts as the central repository of raw to block device binding information.
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:
name="sd" class="scsi" target=6 lun=5;
•
On Solaris systems, create a single large partition named “Backup” on the hard disk. Use the applicable commands to set up the target hard disk so that it contains a single partition.
•
Determine the client that controls the virtual arm changer.
Set up raw I/O on Linux-based systems

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

•
One or more free IDE or SCSI disk partitions.
•
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:
ln -s /dev/your_raw_dev_ctrl /dev/rawctl

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:
ls /dev/rawctl
— or —
ls /dev/raw/raw1
2
Logged in as root, type the following command to create the device:
mknod /dev/rawctl c 162 0
3
Set the following permissions:
crw-rw

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.

Set up raw I/O on Red Hat Linux

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

1
Calculate the number of 4096-byte pages in this partition, as shown in the following example:
fdisk /dev/sda
Disk /dev/sda: 255 heads, 63 sectors, 1106 cylinders
Units = cylinders of 16065 * 512 bytes
num_pages = floor( ((1106-524+1)*16065*512)/4096 )
num_pages = 11170736
2
Bind an unused raw device node to this partition. Binding is required each time the machine is rebooted. You must be logged in as root to run this command:
raw /dev/raw/raw1 /dev/sda
3
For persistent binding, open the /etc/sysconfig/rawdevices file and append the following line:
dev/raw/raw1 /dev/sda
Restart the system or type the following command:
/etc/rc.d/init.d/rawdevices start
4
Set appropriate read permissions on the raw device controller and the disk partition. Set appropriate read and write permissions on the raw device.
Set up raw I/O on Red Hat Enterprise Linux 5 or greater

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:

•
For device names:
ACTION=="add", KERNEL=="<device name>", RUN+="/bin/raw /dev/raw/rawX %N"
•
For major or minor numbers:
ACTION=="add", ENV{MAJOR}=="A", ENV{MINOR}=="B", RUN+="/bin/raw /dev/raw/rawX %M %m"

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
Set up raw I/O on SUSE Linux

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.

Creating and adding an SVTL

You can use the configuration wizard to create and add an SVTL. When creating an SVTL, you can choose the number of virtual tape drives and slots, and specify the media capacity. After the device is created, you can assign the drives to different clients or share the drives with multiple clients.

To create an SVTL:
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 Shared virtual tape library option, and click Next.
3
In the list of NetVault Backup machines, select the machine on which you want to create the device, and click Next.
4
On the Add Shared virtual tape library page, provide the following details.
 
Option
Description

Library Device

Select the target drive. Depending on the operating system, the list includes the following items:

•
Windows: PhysicalDrive1, PhysicalDrive2, and so on
•
Linux: /dev/raw/raw1, /dev/raw/raw2, and so on
•
Solaris: /dev/rdsk/c0t0d0s0, /dev/rdsk/c1t1d0s0, and so on

Device Description

Displays the disk type.

Device Size

Displays the disk size.

Device Block Size

Displays the block size.

Previously Formatted as SVTL?

Indicates whether the selected disk was previously formatted as an SVTL.

Barcode Prefix

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

Number of Drives

Type or select the number of drives for the SVTL. The number of drives can be more than the number of NetVault Backup Clients currently connected to the disk. The additional drives can be used in future to connect more clients.

Number of Media Items

Type or select the total number of slots that hold the media.

Media Capacity

Type or select the media size. The media size is specified in MiB.

When creating an SVTL, NetVault Backup uses a few megabytes of space to store some information about the SVTL on the disk. Take this requirement into consideration when you configure the media capacity.

5
To determine the disk space requirements for the SVTL, click Calculate Size Required. If the required disk size is larger than the actual disk size, reduce the Media Items and Media Capacity.
6
Click OK.
7
To create an SVTL, NetVault Backup formats the specified disk. To complete this step, provide the following details:
•
Password: Type the NetVault Backup password for the server.
•
Confirmation Phrase: Type the text FORMAT SVTL.
Click Format to format the disk and create the SVTL.
8
After the SVTL is created, and the tape drives are automatically discovered and assigned to the appropriate storage bays, a message is displayed.
You can use this default configuration if all drives are to be controlled by the client selected in Step 3. In this case, click Add Library. Information message appears. Close the message to exit the configuration wizard.
9
To assign the drives to different clients or to share the drive with multiple clients, click Add Drives Manually, and complete the following steps:
a
In the Choose Machine table, select the client to which the drive is attached. If the device is connected to multiple clients, select any one client. Click Next to scan the selected client and list the attached devices.
 
* 
NOTE: To skip any bay and configure the next bay, click Leave bay empty.
b
In the Choose drive for bay table, select the device that you want to add, and click Next.
c
If the device is connected to multiple clients (for example, in a SAN setup), all host clients are listed in the Choose Machines table. To share the drive with multiple clients, select the additional clients in the Choose Machines table, and click Next.
d
After the drive is successfully assigned to the selected clients, a message is displayed.
To assign additional drives for the library, click Add more devices, and repeat Step a through Step c.
If you do not want to add any other drives, exit the configuration wizard.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation