EMC® VNX™ Series

Release 7.1

Configuring NDMP Backups to Disk on VNX™

P/N 300-013-431 Rev 01

EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
 Copyright © 1998 - 2012 EMC Corporation. All rights reserved.
Published July 2012
EMC believes the information in this publication is accurate as of its publication date. The
information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION
MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO
THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an
applicable software license.
For the most up-to-date regulatory document for your product line, go to the Technical
Documentation and Advisories section on EMC Powerlink.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on
EMC.com.
All other trademarks used herein are the property of their respective owners.
Corporate Headquarters: Hopkinton, MA 01748-9103

2 Configuring NDMP Backup to Disk on VNX 7.1

 Contents

Preface.....................................................................................................5

Chapter 1: Introduction...........................................................................7
System requirements...............................................................................................8
Restrictions...............................................................................................................8
User interface choices.............................................................................................9
Related information................................................................................................9

Chapter 2: Concepts.............................................................................11
VTLU components................................................................................................12
VTLU device names..............................................................................................12
Configuring guidelines.........................................................................................13

Chapter 3: Configuring.........................................................................15
Configure a new VTLU........................................................................................16
Create a VTLU with default settings........................................................16
Create and customize a new VTLU..........................................................18
Configure a VTLU with Tivoli Storage Manager.............................................20
Add storage............................................................................................................22
Add storage with the default settings......................................................22
Add customized storage.............................................................................22
Configure your backup software........................................................................24

Chapter 4: Managing............................................................................27
Modify a VTLU configuration.............................................................................28
Modify properties........................................................................................28
Configure the chain ID...............................................................................31

Configuring NDMP Backup to Disk on VNX 7.1 3

Contents

Delete a VTLU..............................................................................................33
Manage storage......................................................................................................36
Export storage..............................................................................................36
Import storage..............................................................................................37
Delete storage...............................................................................................38
Extend storage..............................................................................................39
Manage virtual tapes............................................................................................39
Insert virtual tapes.......................................................................................40
Eject virtual tapes........................................................................................42
Unmount a virtual tape..............................................................................43
List VTLU information.........................................................................................46
List VTLUs on a Data Mover.....................................................................46
List VTLU information...............................................................................47
View the Chain ID.......................................................................................48
List VTLU tapes...........................................................................................49
View tape information................................................................................50
List the VTLU drives...................................................................................51
List drive information.................................................................................52

Chapter 5: Troubleshooting..................................................................55
EMC E-Lab Interoperability Navigator..............................................................56
VNX user customized documentation...............................................................56
Error messages.......................................................................................................56
EMC Training and Professional Services...........................................................57

Glossary..................................................................................................59

Index.......................................................................................................61

4 Configuring NDMP Backup to Disk on VNX 7.1

 Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines,
EMC periodically releases revisions of its hardware and software. Therefore, some functions described
in this document may not be supported by all versions of the software or hardware currently in use.
For the most up-to-date information on product features, refer to your product release notes.
If a product does not function properly or does not function as described in this document, please
contact your EMC representative.

Configuring NDMP Backup to Disk on VNX 7.1 5

 Preface

Special notice conventions

EMC uses the following conventions for special notices:

Note: Emphasizes content that is of exceptional importance or interest but does not relate to personal
injury or business/data loss.

Identifies content that warns of potential business or data loss.

Indicates a hazardous situation which, if not avoided, could result in minor or

moderate injury.

Indicates a hazardous situation which, if not avoided, could result in death or

serious injury.

Indicates a hazardous situation which, if not avoided, will result in death or serious
injury.

Where to get help

EMC support, product, and licensing information can be obtained as follows:

Product information — For documentation, release notes, software updates, or for

information about EMC products, licensing, and service, go to the EMC Online Support
website (registration required) at http://Support.EMC.com.
Troubleshooting — Go to the EMC Online Support website. After logging in, locate
the applicable Support by Product page.
Technical support — For technical support and service requests, go to EMC Customer
Service on the EMC Online Support website. After logging in, locate the applicable
Support by Product page, and choose either Live Chat or Create a service request. To
open a service request through EMC Online Support, you must have a valid support
agreement. Contact your EMC sales representative for details about obtaining a valid
support agreement or with questions about your account.

Note: Do not request a specific support representative unless one has already been assigned to
your particular system problem.

Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications.
Please send your opinion of this document to:

[email protected]

6 Configuring NDMP Backup to Disk on VNX 7.1

 1

Introduction

The EMC VNX virtual tape library unit (VTLU) for Network Data
Management Protocol (NDMP) allows VNX to back up data directly to
disk-based storage by means of the NDMP protocol. The EMC VTLU
feature expands the functionality of the industry-standard NDMP protocol
to include compatibility with disk-based storage, allowing you to manage
physical tape library units (TLUs) and VTLUs from the same
NDMP-compatible backup software.
A VTLU resides on a Data Mover and communicates with the backup
software in the same manner as a physical TLU. The backup software, for
example, EMC NetWorker, cannot distinguish between a VTLU and a
physical TLU. The EMC E-Lab Interoperability Navigator provides
information on qualified backup software vendors.
EMC NDMP backup-to-disk solution:
◆ Lowers the risk of mechanical failures, and has the reliability of VNX
file systems
◆ Eliminates the need to clean tapes to maintain performance levels
◆ Uses your existing NDMP infrastructure
This document is part of the VNX documentation set and is intended for
system administrators responsible for managing and performing NDMP
backups. Use this document and Configuring NDMP Backups on VNX to
perform NDMP backup and restore operations on VNX.
Topics included are:
◆ System requirements on page 8
◆ Restrictions on page 8
◆ User interface choices on page 9
◆ Related information on page 9

Configuring NDMP Backup to Disk on VNX 7.1 7

Introduction

System requirements
Table 1 on page 8 describes the EMC® VNX™ software, hardware, network, and storage
configurations required for backing up data to disk with NDMP as described in this
document.

Table 1. System requirements

Software VNX version 7.0

NDMP-compliant backup software that has been qualified with VNX

Hardware No specific hardware requirements

Network No specific network requirements

Storage EMC VNX for block or Symmetrix® system

Restrictions
The restrictions that apply to configuring a VTLU for NDMP backups are:

◆ A VTLU works only with NDMP.

◆ VNX Snapshots (for file) file systems cannot be imported into a VTLU.
◆ In an NDMP backup-to-disk solution, the primary disk storage to be backed up must be
attached to VNX and not to the backup server that is running the backup software.
◆ The server_archive and server_mt commands are not compatible with a VTLU.
◆ The server_devconfig command does not discover VTLUs; it discovers only physical
devices.
◆ Use dedicated file systems for VTLU storage.
◆ Auto extend should be set to "No".
◆ Tape cloning is supported; use your backup software to clone a tape, which moves it
from disk to tape.
◆ When a VTLU emulates a particular TLU, for example, in IBM Tivoli Storage Manager
backup software, the import or export slots must match what IBM would expect to see
if it were a real TLU instead of a VTLU. Also, import or export slots should never be
specified as 0 and must be in the range from 1 through 8. The default for import or export
slots is 8.
◆ When you create a new storage using IBM Tivoli and NDMP to disk with Celerra Network
Server version 5.6, do not specify the barcode prefix in lowercase letters. IBM Tivoli does
not support barcode prefix in lowercase.

8 Configuring NDMP Backup to Disk on VNX 7.1

 Introduction

If you do not specify the barcode prefix, it will be generated in uppercase letters.

User interface choices

VNX offers flexibility in managing networked storage that is based on your support
environment and interface preferences. This document describes how to configure NDMP
backups to disk by using the command line interface (CLI). You can also perform all of these
tasks by using one of VNX management applications:

◆ EMC Unisphere™
◆ Celerra Monitor
◆ Microsoft Management Console (MMC) snap-ins
◆ Active Directory Users and Computers (ADUC) extensions
For additional information about managing your VNX:

◆ Learning about VNX

◆ Unisphere online help
◆ Application’s online help system in the VNX Documentation on EMC Online Support
Installing Management Applications on VNX for File provides instructions on launching
Unisphere, and on installing the MMC snap-ins and the ADUC extensions.

Related information
For specific information related to the features and functionality described in this document:

◆ EMC VNX Command Line Interface Reference for File

◆ Parameters Guide for VNX for File
◆ VNX for File Man Pages

EMC VNX documentation on the EMC Online Support website

The complete set of EMC VNX series customer publications is available on the EMC
Online Support website. To search for technical documentation, go to
http://Support.EMC.com. After logging in to the website, click the VNX Support by
Product page to locate information for the specific feature required.

User interface choices 9

Introduction

10 Configuring NDMP Backup to Disk on VNX 7.1

 2

Concepts

To perform a backup to disk with NDMP, configure a VTLU on the Data

Mover. The VTLU allows VNX to back up data directly to disk-based
storage by means of the NDMP protocol. A VTLU emulates a physical
TLU by presenting to the backup software the same information as a
physical TLU. The backup software cannot distinguish between a physical
TLU and a VTLU.
When you configure a VTLU, space on the Data Mover is reserved for the
VTLU and its associated components. After the VTLU is created, associate
a file system with it. The file system must already be mounted on the
Physical Data Mover where the VTLU resides. After the VTLU is configured
and has an associated file system, you can manage it from the backup
software.
Topics included are:
◆ VTLU components on page 12
◆ VTLU device names on page 12
◆ Configuring guidelines on page 13

Configuring NDMP Backup to Disk on VNX 7.1 11

Concepts

VTLU components
The VTLU consists of the following components:
◆ Import or export slots: Hold virtual tapes and allow the user to move tapes from the
vault to the import or export slots and vice versa. In a physical TLU, import or export
slots offer a place to move tape cartridges without opening the TLU door. They are also
visible from the backup software. The VTLU is designed in the same way to be compatible
with the backup software.
◆ Robot: Mounts and unmounts cartridges to and from the tape drives.
◆ Slots: Hold virtual tapes and serve as the staging slots for moving tapes to drives by
means of the backup software.
◆ Vault: Holds virtual tapes that are hidden from the backup software.
◆ Virtual tapes: Represent a reserved space in a file system; data is read from and written
through virtual tapes.
◆ Virtual tape drives: Read from and write to the virtual tapes.
Figure 1 on page 12 shows a schematic view of a VTLU.
VTLU
Schematic view
Slots
0 000000 Tape drives
0
1 1 000001
0
2 000002
Import/export
slots 3 000003 1

7 2
16 000016
17 000017 3
18
20

31
32

CNS-000737

Figure 1. Schematic view of a VTLU

VTLU device names

When you create a VTLU, a device name is assigned to it. Device names represent the virtual
connection of the VTLU robot and drives. The device name format is c<x>t<y>l<z>, where
the variables represent the values used in a physical SCSI device name as follows:
<x> = SCSI chain number
<y> = SCSI ID
<z> = SCSI LUN

12 Configuring NDMP Backup to Disk on VNX 7.1

 Concepts

The chain number, or chain ID, is a user-addressable portion of the VTLU device name. You
will want to modify a chain ID if a conflict arises between virtual and physical devices. The
default chain ID is 0.

Configuring guidelines
Follow these general guidelines while configuring your environment for NDMP
backups-to-disk:
◆ For ATA-drive configurations, it is recommended to use RAID 3 logical unit numbers
(LUNs).
◆ In Fibre Channel environments, RAID 5 yields higher throughput for Fibre Channel
disks.
◆ For optimal three-way backup performance in a Gigabit Ethernet environment, enable
jumbo frames.
Managing Volumes and File Systems for VNX Manually and Managing Volumes and File Systems
with VNX Automatic Volume Management provide more information on file system
configuration and volume management.

Configuring guidelines 13
Concepts

14 Configuring NDMP Backup to Disk on VNX 7.1

 3

Configuring

When you configure a new VTLU, assign space on a Data Mover where
the virtual drives, slots, and tapes reside. A new VTLU is automatically
assigned an ID, which you use when configuring or managing the VTLU.
After creating the VTLU, add storage to it, which associates a file system
with the VTLU. And then, configure the VTLU device names in your
backup software.
Using a VTLU requires that VNX be configured for NDMP operations,
which involves these procedures:
◆ Configure Data Movers, if necessary for your backup software vendor.
Create a username and password on the Data Mover that will be used
for NDMP access. For the password, it is recommended that you use
the MD5 password encryption method for security reasons. The
username and password are case-sensitive.

◆ Configure the appropriate NDMP environment variables or parameters.

Configuring NDMP Backups on VNX contains information for performing
these procedures. If you have already configured the Data Movers for
NDMP, you do not need to change the configuration settings to use a
VTLU. The VNX configuration settings for NDMP are the same for
physical and virtual TLUs.

Topics included are:

◆ Configure a new VTLU on page 16
◆ Configure a VTLU with Tivoli Storage Manager on page 20
◆ Add storage on page 22
◆ Configure your backup software on page 24

Configuring NDMP Backup to Disk on VNX 7.1 15

Configuring

Configure a new VTLU

To configure a new VTLU, use one of these methods:
◆ Create a VTLU with default settings on page 16
◆ Create and customize a new VTLU on page 18

Create a VTLU with default settings

Action
To create a new VTLU with the default configuration settings, use this command syntax:
$ server_vtlu <movername> -tlu -new
where:
<movername> = name of the Data Mover

Example:
To create a new VTLU on server_2, type:
$ server_vtlu server_2 -tlu -new

Output

id = 1
slots = 32
import/export slots = 8
robot vendor = EMC
robot product = svltRobot
robot revision = 1.0
robot serial number = gkzp9492k5
robot device name = c0t0l0
drives = 4
drive vendor = EMC
drive product = svltDrive
drive revision = 1.0

Note: This output shows the VTLU default values.

The only values that cannot be modified are:

◆ VTLU ID
◆ Robot serial number
◆ Last two numbers in the device name: only the first number, the starting chain, can be modified. For the first VTLU,
the first number is 0.

16 Configuring NDMP Backup to Disk on VNX 7.1

 Configuring

Note
Output definitions:
id : VTLU ID, which is automatically assigned and cannot be modified

slots : number of slots on the VTLU; the sum of the slots, import or export slots, and drives cannot exceed 65,535

import/export slots : number of import or export slots; the sum of the slots, import or export slots, and drives
cannot exceed 65,535
robot vendor : name of the robot vendor, which can contain up to eight characters

robot product : product name of the robot, which can contain up to 16 characters

robot revision : robot revision number, which can contain up to four characters

robot serial number : robot serial number; this value is randomly generated and assigned

robot device name : robot device name in the format

c<x>t<y>l<z>
where:
<x> = SCSI starting chain number

<y> = SCSI ID

<z> = SCSI LUN

Note: Only the starting chain number can be modified.

drives : number of drives; the sum of the slots, import or export slots, and drives cannot exceed 65,535

drive vendor : drive vendor name, which can contain up to eight characters

drive product : drive product name, which can contain up to 16 characters

drive revision : drive revision number, which can contain up to four characters

Configure a new VTLU 17

Configuring

Create and customize a new VTLU

This task provides options to create a new VTLU. If you do not specify these options, the
default values are used, as shown in Create a VTLU with default settings on page 16. While
this example shows all options, you can configure a subset of these options while using the
default values for others.
With IBM Tivoli Storage Manager Backup software, the number of import or export slots
defined for a VTLU must be between one and eight. Also, the robot and drive information
must match the actual robot and tape drive information in your environment.

Action
To create and customize a new VTLU, use this command syntax:
$ server_vtlu <movername> -tlu -new [-robot {[-vendor <vendor>][-product
<product>][-revision <revision>]}][-slots <num_slots>][-impexp <num_
impexp_slots>][-drives <num_drives>][-drive {[-vendor <vendor>][-product
<product>][-revision <revision>]}]

where :
<movername> = name of the Data Mover

<vendor> = virtual robot vendor name, which can contain up to eight characters; the default value is EMC

<product> = virtual robot product name, which can contain up to 16 characters; the default value is svtlRobot

<revision> = virtual robot revision number, which can contain up to four characters; the default value is 1.0

<num_slots> = number of slots in the VTLU; the default value is 32; the sum of the slots, import or export slots, and
drives cannot exceed 65,535
<num_impexp_slots> = number of import or export slots in the VTLU; the default value is 8; the sum of the slots,
import or export slots, and drives cannot exceed 65,535
<num_drives> = number of drives in the VTLU; the default value is 4; the sum of the slots, import or export slots, and
drives cannot exceed 65,535
<vendor> = virtual drive vendor name, which can contain up to eight characters; the default value is EMC

<product> = virtual drive product name, which can contain up to 16 characters; the default value is svtlDrive

<revision> = virtual drive revision number, which can contain up to four characters; the default value is 1.0

Example:
To configure a VTLU and specify its configuration settings, type:
$ server_vtlu server_2 -tlu -new -robot -vendor legato -product vtlu -revision 2.0
-slots 256 -impexp 16 -drives 6 -drive -vendor emclegat -product vDrive -revision
2.0

18 Configuring NDMP Backup to Disk on VNX 7.1

 Configuring

Output

id = 1
slots = 256
import/export slots = 16
robot vendor = legato
robot product = vtlu
robot revision = 2.0
robot serial number = lX21uML2k5
robot device name = c0t0l0
drives = 6
drive vendor = emclegat
drive product = vDrive
drive revision = 2.0

Note
Output definitions:
id : VTLU ID, which is automatically assigned and cannot be modified

slots : number of slots on the VTLU; the sum of the slots, import or export slots, and drives cannot exceed 65,535

import/export slots : number of import or export slots; the sum of the slots, import or export slots, and drives
cannot exceed 65,535
robot vendor : name of the robot vendor, which can contain up to eight characters

robot product : product name of the robot, which can contain up to 16 characters

robot revision : robot revision number, which can contain up to four characters

robot serial number : robot serial number; this value is randomly generated and assigned

robot device name : robot device name in the format:

c<x>t<y>l<z>
where:
<x> = SCSI starting chain number

<y> = SCSI ID

<z> = SCSI LUN

Note: Only the starting chain number can be modified.

drives : number of drives; the sum of the slots, import or export slots, and drives cannot exceed 65,535

drive vendor : drive vendor name, which can contain up to eight characters

drive product : drive product name, which can contain up to 16 characters

drive revision : drive revision number, which can contain up to four characters

Configure a new VTLU 19

Configuring

Configure a VTLU with Tivoli Storage Manager

This is an example of a VTLU configured with Tivoli Storage Manager.
With IBM Tivoli Storage Manager backup software, the number of import or export slots
defined for a VTLU must be between one and eight. Also, the robot and drive information
must match the actual robot and tape drive information in your environment.

Note: You can configure a VTLU with Tivoli Storage Manager in different ways. This example shows
one of the configurations:

Action
To configure a VTLU with Tivoli Storage Manager and specify its configuration settings, type:
$ server_vtlu server_3 -tlu -new -robot -vendor ATL -product p1000 -drive -vendor
Quantum -product DLT7000

Output

id = 1
slots = 32
import/export slots = 8
robot vendor = ATL
robot product = P1000
robot revision = 1.01
robot serial number = JYK4YHP1k5
robot device name = c0t0l0
drives = 4
drive vendor = QUANTUM
drive product = DLT7000
drive revision = 1.01

20 Configuring NDMP Backup to Disk on VNX 7.1

 Configuring

Note
Output definitions:
id : VTLU ID, which is automatically assigned and cannot be modified

slots : number of slots on the VTLU; the sum of the slots, import or export slots, and drives cannot exceed 65,535

import/export slots : number of import or export slots; the sum of the slots, import or export slots, and drives
cannot exceed 65,535.
robot vendor : name of the robot vendor, which can contain up to eight characters

robot product : product name of the robot, which can contain up to 16 characters

robot revision : robot revision number, which can contain up to four characters

robot serial number : robot serial number; this value is randomly generated and assigned

robot device name : robot device name in the format:

c<x>t<y>l<z>
where:
<x> = SCSI starting chain number

<y> = SCSI ID

<z> = SCSI LUN

Note: Only the starting chain number can be modified.

drives : number of drives; the sum of the slots, import or export slots, and drives cannot exceed 65,535

drive vendor : drive vendor name, which can contain up to eight characters

drive product : drive product name, which can contain up to 16 characters

drive revision : drive revision number, which can contain up to four characters

Configure a VTLU with Tivoli Storage Manager 21

Configuring

Add storage
Adding storage to a VTLU associates a file system with it. To associate a file system with a
VTLU, the file system must be mounted on the Physical Data Mover where the VTLU resides.
It is recommended that you use dedicated file systems as VTLU storage. A VTLU can have
multiple file systems associated with it.
To add storage, use one of these methods:
◆ Add storage with the default settings on page 22
◆ Add customized storage on page 22

Add storage with the default settings

When you add new storage, you can use the default settings for the VTLU, as shown in this
section. Add customized storage on page 22 describes the procedure to customize the storage
settings.
Perform the following steps to add storage with default settings:
1. Add storage to a VTLU by using this command syntax:
$ server_vtlu <movername> -storage -new <fs_name> -tlu <tlu_id>
where:
<movername> = name of the Data Mover
<fs_name> = name of the file system
<tlu_id> = ID of the VTLU
Example:
To add storage to VTLU 1 on server_2, type:
$ server_vtlu server_2 -storage -new ufs1 -tlu 1

Output:

server_2 : done

Note: Add customized storage on page 22 provides the default VTLU configurations.

2. Run an inventory from the backup software.

Add customized storage

Perform the following steps to add customized storage:

22 Configuring NDMP Backup to Disk on VNX 7.1

 Configuring

1. Add storage to a VTLU by using this command syntax:

$ server_vtlu <movername> -storage -new <fs_name> -tlu <tlu_id>
-tapesize <size> G -tapes <num_tapes> -barcodeprefix <barcode
_prefix> -destination {slot|impexp|vault}

where:
<movername> = name of the Data Mover
<fs_name> = name of the file system to be associated with the VTLU
<tlu_id> = ID of the VTLU
<size> = size of the tape, in GB. The maximum value is 16384 GB; the default value of 50
GB is used if <size> and <num_tapes> are not defined. If <size> is not defined, then it is
calculated based on the amount of free space available on the file system.
<num_tapes> = number of tapes associated with the file system; the default is the maximum
number of tapes that can be created based on the file system size
<barcode_prefix> = barcode prefix for the virtual tapes that must be unique within the
VTLU. The default is a four-character hexadecimal value. It is recommended to use
between two and six characters so that the total barcode is between six and 10 characters.
Some backup software vendors use a limited number of characters, such as the first 10
or the last six characters.
{slot|impexp|vault} = destination of the new tapes; the default value is slot
Example:
To add the ufs1 file system to VTLU 1, type:
$ server_vtlu server_2 -storage -new ufs1 -tlu 1 -tapesize 1G -tapes 5
-barcodeprefix pre1 -destination slot

Output:

server_2 : done

Note: Add storage with the default settings on page 22 provides information about the default
storage settings.

2. Run an inventory from the backup software.

Add storage 23
Configuring

Configure your backup software

After you have created the VLTU, you need to configure the VTLU device names in your
backup software before you use the VTLU. The procedure in this section explains how to
find the device names you need for the backup software.
To configure the VTLU device names in the backup software, refer to your backup software
documentation.

Note: VTLU device names cannot be discovered by using the server_devconfig command. The
server_devconfig command discovers only physical devices.

Perform the following steps to configure your backup software:

1. View a list of VTLUs for the Data Mover by using this command syntax:
$ server_vtlu <movername> -tlu -list

where:
<movername> = name of the Data Mover
Example:
To list the VTLUs configured on server_2, type:
$ server_vtlu server_2 -tlu -list

Output:

id vendor product revision serial_number device_name

1 legato vtlu 2.0 lX21uML2k5 c0t0l0
2 EMC svltRobot 1.01 gkzp9492k5 c0t0l7
3 EMC svltRobot 1.01 P8gIgqs2k5 c0t0l12
Column definitions:
id : ID number for the VTLU
vendor : vendor name of the VTLU robot, which can contain up to eight characters; the
default value is EMC
product : VTLU product name, which can contain up to 16 characters; the default value
is svtlRobot
revision : VTLU revision number, which can contain up to four characters; the default
value is 1.0
serial_number : VTLU serial number, which the Data Mover automatically assigns
device_name : device name of the VTLU virtual robot in the following format:
c<x>t<y>l<z>
where:
<x> = SCSI starting chain number

24 Configuring NDMP Backup to Disk on VNX 7.1

 Configuring

<y> = SCSI ID
<z> = SCSI LUN
Only the chain ID can be modified; the default value is 0. Configure the chain ID on page
31 provides information on modifying the chain ID.

2. View the device names for the VTLU drives by using this command syntax:
$ server_vtlu <movername> -drive -list <tlu_id>

where:
<movername> = name of the Data Mover
<tlu_id> = ID of the VTLU
Example:
To view the drives on VTLU 1, which resides on server_2, type:
$ server_vtlu server_2 -drive -list 1

Output:

drive_id device_name serial_number status tape_barcode

0 c0t0l1 gMllGqf100 empty
1 c0t0l2 ziKtHqf100 empty
2 c0t0l3 PO8CIqf100 empty
3 c0t0l4 5lxKJqf100 empty
4 c0t0l5 lRVSKqf100 empty
5 c0t0l6 Bnk1Mqf100 empty
Column definitions:
drive_id : ID of the virtual tape drive; the default IDs are 0–3 for a VTLU with four drives

device_name : device name of the virtual drive in the following format:

c<x>t<y>l<z>
where:
<x> = SCSI starting chain number
<y> = SCSI ID
<z> = SCSI LUN
serial_number : drive serial number, which the Data Mover automatically assigns
status : status of the tape drive, options are:
•
empty : no tape is in the drive
•
full : a tape is in the drive, but the drive has been unloaded by the backup software
•
loaded : a tape is in the drive and the drive is loaded
•
in use : the drive is in use for a backup or restore
tape_barcode : barcode of the tape loaded in the tape drive, if any

Configure your backup software 25

Configuring

3. Configure the VTLU device names in the backup software. The backup software
documentation that your vendor provides gives specific instruction.

26 Configuring NDMP Backup to Disk on VNX 7.1

 4

Managing

Topics included are:

◆ Modify a VTLU configuration on page 28
◆ Manage storage on page 36
◆ Manage virtual tapes on page 39
◆ List VTLU information on page 46

Configuring NDMP Backup to Disk on VNX 7.1 27

Managing

Modify a VTLU configuration

The tasks to modify a VTLU configuration are:
◆ Modify properties on page 28
◆ Configure the chain ID on page 31
◆ Delete a VTLU on page 33

Modify properties

You can modify the robot and drive information if your backup software requires particular
information to recognize the VTLU. For example, if the backup software returns an error
when you run an inquiry command, such as unknown TLU or TLU not supported, then
you might need to change the VTLU robot and drive information. The information might
need to match what the backup software expects.
The options for modifying the configuration settings can be used individually or in
combination. The example in this section shows how to modify all options at once. You can
configure a subset of the options without configuring all of them.
The VTLU properties that you can modify are:
◆ Robot vendor name, product name, and revision number
◆ Virtual tape drive vendor name, product name, and revision number
◆ Number of tape drives, slots, and import or export slots
Most backup software applications do not require modifications to the VTLU properties.

Note: The sum of the slots, import or export slots, and drives cannot exceed 65,535.

With IBM Tivoli Storage Manager backup software, the number of import or export slots
defined for a VTLU must be between one and eight. Also, the robot and drive information
must match the actual robot and tape drive information in your environment.

Action
To modify a VTLU configuration, use this command syntax:
$ server_vtlu <movername> -tlu -modify <tlu_id> -robot -vendor <vendor>
-product <product> -revision <revision> -slots <num_slots> -impexp <num_
impexp_slots> -drives <num_drives> -drive -vendor -product <product>
-revision <revision> <vendor>
where:
<movername> = name of the Data Mover

28 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

Action
<tlu_id> = ID of the VTLU

<vendor> = virtual robot vendor name, which can contain up to eight characters; the default is EMC

<product> = virtual robot product name, which can contain up to 16 characters; the default value is svtlRobot

<revision> = virtual robot revision number, which can contain up to four characters; the default value is 1.0

<num_slots> = number of slots in the VTLU; the default value is 32; the sum of the slots, import or export slots, and
drives cannot exceed 65,535
<num_impexp_slots> = number of import or export slots in the VTLU; the default value is 8; the sum of the slots,
import or export slots, and drives cannot exceed 65,535
<num_drives> = number of drives in the VTLU; the default value is 4; the sum of the slots, import or export slots, and
drives cannot exceed 65,535
<vendor> = virtual drive product name, which can contain up to eight characters; the default value is EMC

<product> = virtual drive product name, which can contain up to 16 characters; the default value is svtlDrive

<revision> = virtual drive revision number, which can contain up to four characters; the default value is 1.0

Example:
To modify all configuration settings associated with a VTLU, type:
$ server_vtlu server_2 -tlu -modify 1 -robot -vendor EMC_1 -product vtlu_1 -revision
2.1 -slots 64 -impexp 16 -drives 8 -drive -vendor EMC_1 -product vDrive_1 -revision
2.1a

Output
server_2 : done

Verify the changes made to VTLU

Action
To verify that the desired changes were made to the VTLU configuration, use this command syntax:
$ server_vtlu <movername> -tlu -info <tlu_id>
where:
<movername> = name of the Data Mover

<tlu_id> = ID of the VTLU on which you want to view information

Example:
To verify the configuration settings on VTLU 1, type:
$ server_vtlu server_2 -tlu -info 1

Modify a VTLU configuration 29

Managing

Output

id = 1
slots = 64
import/export slots = 16
robot vendor = EMC_1
robot product = vtlu_1
robot revision = 2.1
robot serial number = lX21uML2k5
robot device name = c0t0l0
drives = 8
drive vendor = EMC_1
drive product = vDrive_1
drive revision = 2.1a

Note
Output definitions:
id : VTLU ID

slots : number of slots on the VTLU; the sum of the slots, import or export slots, and drives cannot exceed 65,535

import or export slots : number of import or export slots; the sum of the slots, import or export slots, and drives
cannot exceed 65,535
robot vendor : robot vendor name, which can contain up to eight characters

robot product : robot product name, which can contain up to 16 characters

robot revision : robot revision number, which can contain up to four characters

robot serial number : robot serial number; this value is randomly generated and assigned robot device name:
robot device name in the following format:
c<x>t<y>l<z>
where:
<x> = SCSI starting chain number (only this value can be modified)

<y> = SCSI ID

<z> = SCSI LUN

drives : number of tape drives; the sum of the slots, import or export slots, and drives cannot exceed 65,535

drive vendor : drive vendor name, which can contain up to eight characters

drive product : drive product name, which can contain up to 16 characters

drive revision : drive revision number, which can contain up to four characters

30 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

Configure the chain ID

When you create a VTLU or drive, a device name is assigned to represent the connection
between the device and the Data Mover.
The format of the device name is c<x>t<y>|<z>, the same as a physical device name, where
the variables represent:
<x> = SCSI starting chain number
<y> = SCSI ID
<z> = SCSI LUN
Only the starting chain number can be modified. When you modify the chain number, it
applies across the Data Mover, including all the VTLU device names on the Data Mover.

Action
To change the starting chain for a Data Mover, use this command syntax:
$ server_vtlu <movername> -service -set -chain <chain_id>
where:
<movername> = name of the Data Mover

<chain_id> = chain ID value, which is part of the device name

Example:
To assign the chain ID a value of 2, type:
$ server_vtlu server_2 -service -set -chain 2

Output
server_2 : done

Note
The starting chain number applies to all VTLU devices on the Data Mover, including the virtual tape drives.
A physical device chain ID cannot exceed 8192. If you set the VTLU chain ID to a value greater than 8192, such as 10000,
then there is no risk of contention among virtual and physical device names. However, the maximum allowable chain ID
value can be restricted to a value less than 10000 by your backup software.

Modify a VTLU configuration 31

Managing

Verify the chain number

Action
To verify that the chain number was modified, use this command syntax:
$ server_vtlu <movername> -service -info
where:
<movername> = name of the Data Mover

Example:
To query the VTLU on server_2 for the chain ID, type:
$ server_vtlu server_2 -service -info

Output

server_2 :
starting chain id = 2

Note
Output definition:
server_2 : Data Mover on which you are viewing information

starting chain id : starting chain of the VTLU device name

32 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

Delete a VTLU

When deleting a VTLU, you must first break the association between the storage and the
VTLU. You cannot delete a VTLU that has associated storage.

Note: Perform steps 1 and 2 if the VTLU has associated storage, otherwise, proceed to step 3.

Perform the following steps to delete a VTLU:

1. Identify the storage you want to free from association with the VTLU by using this
command syntax:
$ server_vtlu <movername> -storage -list <tlu_id>

Note: If the file system name is too long, it can be truncated. Use the -info option to obtain the
complete file system details.

or
$ server_vtlu <movername> -storage -info -tlu <tlu_id>

where:
<movername> = name of the Data Mover
<tlu_id> = ID of the VTLU
Example:
To list the storage associated with VTLU 1 on server_2, type:
$ server_vtlu server_2 -storage -list 1

Output:

tlu_id filesystem barcode_prefix

1 ufs1 pre1
or
$ server_vtlu server_2 -storage -info -tlu 3

Output:

Modify a VTLU configuration 33

Managing

server_2 :
tlu_id = 3
filesystem = fs_luy2_2
barcode_prefix = 0222

tlu_id = 3
filesystem = fs_delete_storage1
barcode_prefix = 0235

tlu_id = 3
filesystem = fs_phil6
barcode_prefix = 0243
Column definitions:
tlu_id : ID of the VTLU that you are viewing for information
filesystem : file system associated with the VTLU
barcode_prefix : barcode prefix associated with the file system

2. Break the association between the storage and the VTLU, which deletes any data on the
virtual tapes by using this command syntax:
$ server_vtlu <movername> -storage -delete {<fs_name>|-barcodeprefix
<barcode_prefix>} -tlu <tlu_id>

Note: You can also export the storage instead of deleting it if you want to move the VTLU to another
Data Mover. Export storage on page 36 provides more information. Deleting storage does not
delete the underlying file system; the file system remains mounted on the Data Mover.

where:
<movername> = name of the Data Mover
<fs_name> = name of the file system
<barcode_prefix> = barcode prefix associated with the file system you want to delete
<tlu_id> = ID of the VTLU
Example:
To delete the ufs1 file system from VTLU 1, type:
$ server_vtlu server_2 -storage -delete ufs1 -tlu 1

Output:

server_2 : done
3. Delete the VTLU by using this command syntax:
$ server_vtlu <mover_name> -tlu -delete <tlu_id>

where:
<movername> = name of the Data Mover
<tlu_id> = ID of the VTLU

34 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

Example:
To delete the VTLU 1 from server_2, type:
$ server_vtlu server_2 -tlu -delete 1

Output:

server_2 : done
4. Remove configuration references to this VTLU in your backup software.

5. Verify that VTLU 1 was deleted by using this command syntax:

$ server_vtlu <movername> -tlu -list

where:
<movername> = name of the Data Mover
Example:
To list the VTLUs configured on server_2, type:
$ server_vtlu server_2 -tlu -list

Output:

id vendor product revision serial_number device_name

2 EMC svltRobot 1.0 gkzp9492k5 c2t0l5
3 EMC svltRobot 1.0 lX21uML2k5 c2t0l10
4 EMC svltRobot 1.0 RLMgE853k5 c2t0l15
5 EMC svltRobot 1.01 nAwCOuo3k5 c2t1l4
6 EMCCorp vtluRobot 1.1a XEd8EhX4k5 c2t2l13
Column definitions:
id : ID number for the VTLU
vendor : VTLU robot vendor name, which can contain up to eight characters; EMC is the
default value
product : VTLU product name, which can contain up to 16 characters; svtlRobot is the
default value
revision : VTLU revision number, which can contain up to four characters; the default
value is 1.0
serial_number : VTLU serial number, which the Data Mover automatically assigns
device_name : device name of the VTLU virtual robot in the format:
c<x>t<y>l<z>
where:
<x> = SCSI starting chain number
<y> = SCSI ID
<z> = SCSI LUN
The default starting chain is 0.

Modify a VTLU configuration 35

Managing

Manage storage
The tasks to manage the storage associated with a VTLU are:
◆ Export storage on page 36
◆ Import storage on page 37
◆ Delete storage on page 38
◆ Extend storage on page 39

Export storage

You can export storage from a VTLU, which makes the storage inaccessible until it is imported
into another VTLU. When you export storage, the operation applies to a storage area, not
to individual tapes.

Note: You must unmount all associated tapes from their drives before you can export a VTLU storage.
Unmount a virtual tape on page 43 provides more information.

Steps to export storage are:

1. If you already know the name of the file system then proceed to step 2. Otherwise, query
the VTLU to identify the name of the file system you want to export by using this
command syntax:
$ server_vtlu <movername> -storage -list <tlu_id>

Note: If the file system name is too long, it can be truncated. Use the -info option to obtain the
complete file system details.

or
$ server_vtlu <movername> -storage -info -tlu <tlu_id>

where:
<movername> = name of the Data Mover
<tlu_id> = ID of the VTLU
Example:
To list the tape information for VTLU 1 on server_2, type:
$ server_vtlu server_2 -storage -list 1

Output:

tlu_id filesystem barcode_prefix

1 ufs1 pre1

36 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

or
$ server_vtlu server_2 -storage -info -tlu 3

Output:

server_2 :
tlu_id = 3
filesystem = fs_luy2_2
barcode_prefix = 0222

tlu_id = 3
filesystem = fs_delete_storage1
barcode_prefix = 0235

tlu_id = 3
filesystem = fs_phil6
barcode_prefix = 0243
Column definitions:
tlu_id : ID of the VTLU whose information you are viewing
filesystem : file system associated with the VTLU
barcode_prefix : barcode prefix associated with the file system

2. Export storage from the VTLU by using this command syntax:

$ server_vtlu <movername> -storage -export <fs_name> -tlu <tlu_id>

where:
<movername> = name of the Data Mover
<fs_name> = name of the file system
<tlu_id> = ID of the VTLU
Example:
To export a file system called ufs1 from VTLU 1, type:
$ server_vtlu server_2 -storage -export ufs1 -tlu 1

Note: After you export storage, use the backup software to inventory the VTLU.

Output

server_2 : done

Import storage

You can import storage that has been exported previously from a VTLU. You can import
the storage to the slots, the import or export slots, or to the vault.
Steps to import storage are:

Manage storage 37
Managing

1. Import a file system to an existing VTLU by using this command syntax:

$ server_vtlu <movername> -storage -import <fs_name> -tlu <tlu_id>
-destination {slot|impexp|vault}

where:
<movername> = name of the Data Mover
<fs_name> = name of the file system to import
<tlu_id> = ID of the VTLU
{slot | impexp | vault} = destination of the tapes; slot is the default value
Example:
To import the file system called ufs1 to the slots on VTLU 1, type :
$ server_vtlu server_2 -storage -import ufs1 -tlu 1 -destination slot

2. Run an inventory from your backup software.

Delete storage

Deleting a file system from a VTLU breaks the association between the file system and the
VTLU, as well as deletes a set of virtual tapes. Any data stored on the tapes is also deleted.
The file system itself is not deleted; it remains mounted on the Physical Data Mover.

Action
To delete storage from a VTLU, use this command syntax:
$ server_vtlu <movername> -storage -delete {<fs_name>|-barcodeprefix
<barcode_prefix>} -tlu <tlu_id>

where:
<movername> = name of the Data Mover

<fs_name> = name of the file system

<barcode_prefix> = barcode prefix associated with the file system that you want to delete

<tlu_id> = ID of the VTLU

Example:
To delete storage from ufs1 on VTLU 1, type:
$ server_vtlu server_2 -storage -delete ufs1 -tlu 1

Output
server_2 : done

38 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

Extend storage

When you extend storage, you add virtual tapes to a VTLU. The user should extend the file
system of the VTLU manually before extending the storage.
Steps to extend storage are:
1. Add storage to a VTLU by using this command syntax:
$ server_vtlu <movername> -storage -extend <fs_name> -tlu <tlu_id>
-tapesize <size>G -tapes <num_tapes> -destination {slot|impexp|vault}

where:
<movername> = name of the Data Mover
<fs_name> = name of the file system that has been extended
<tlu_id> = ID of the VTLU
<size> = size of the tape, in GB. The maximum value is 16384 GB; the default value of 50
GB is used if <size> and <num_tapes> are not defined. If <size> is not defined, then it is
calculated based on the amount of free space available on the file system.
<num_tapes> = number of tapes on the VTLU; the default is the maximum number of tapes
that can be created based on the file system size
{slot | impexp | vault} = destination of the tapes; slot is the default value
Example:
To add storage to VTLU 1 on server_2, type:
$ server_vtlu server_2 -storage -extend ufs1 -tlu 1 -tapesize 1G -tapes 5
-destination slot

Output:

server_2 : done
2. Run an inventory from your backup software.

Manage virtual tapes

The tasks to manage virtual tapes are:
◆ Insert virtual tapes on page 40
◆ Eject virtual tapes on page 42
◆ Unmount a virtual tape on page 43

Manage storage 39
Managing

Insert virtual tapes

When you insert a virtual tape, it is moved from the vault to an import or export slot.
Steps to insert virtual tapes are:
1. If you already know the tape barcode then proceed to step 2. Otherwise, query the VTLU
to identify the barcode of the tape that you want to insert by using this command syntax:
$ server_vtlu <movername> -tlu -tape -list <tlu_id>

where:
<movername> = name of the Data Mover
<tlu_id> = ID of the VTLU
Example:
To list the tape information for VTLU 1 on server_2, type:
$ server_vtlu server_2 -tlu -tape -list 1

Output:

barcode filesystem capacity(GB) location source_slot

pre10009 ufs2 50 slot:9 9
pre1000a ufs2 50 slot:10 10
pre1000b ufs2 40 vault
pre10004 ufs2 50 slot:4 4
pre10005 ufs2 50 slot:5 5
pre10006 ufs2 50 slot:6 6
pre10007 ufs2 50 slot:7 7
pre10008 ufs2 50 slot:8 8
pre10000 ufs2 50 slot:0 0
pre10002 ufs2 50 slot:2 2
pre10001 ufs2 50 slot:1 1
pre10003 ufs2 50 slot:3 3
Column definitions:
barcode : barcode associated with the virtual tape; the first part of the barcode, the prefix,
is constant across a file system. In this example, pre1 is the barcode prefix.
filesystem : name of the file system associated with the virtual tapes
capacity : virtual tape capacity in GB
location : element type and element ID of the virtual tape; possible element types are
slot, drive, import or export, robot, and vault
source_slot : original slot number

2. Insert a virtual tape from the vault into an import or export slot by using this command
syntax:
$ server_vtlu <movername> -tape -insert <tape_barcode> -tlu
<tlu_id>

40 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

where:
<movername> = name of the Data Mover
<tape_barcode> = barcode of the virtual tape
<tlu_id> = ID of the VTLU
Example:
To move a virtual tape from the vault to an import or export slot, type:
$ server_vtlu server_2 -tape -insert pre1000b -tlu 1

Output:

server_2 : done
3. Verify that the tape has been moved from the vault to an import or export slot. List the
tape information by using this command syntax:
$ server_vtlu <movername> -tlu -tape -list <tlu_id>

where:
<movername> = name of the Data Mover
<tlu_id> = ID of the VTLU
Example:
To list the tape information for VTLU 1 on server_2, type:
$ server_vtlu server_2 -tlu -tape -list 1

4. Output:

barcode filesystem capacity(GB) location source_slot

pre10009 ufs2 50 slot:9 9
pre1000a ufs2 50 slot:10 10
pre1000b ufs2 41 impexp:11
pre10004 ufs2 50 slot:4 4
pre10005 ufs2 50 slot:5 5
pre10006 ufs2 50 slot:6 6
pre10007 ufs2 50 slot:7 7
pre10008 ufs2 50 slot:8 8
pre10000 ufs2 50 slot:0 0
pre10002 ufs2 50 slot:2 2
pre10001 ufs2 50 slot:1 1
pre10003 ufs2 50 slot:3 3
Column definitions:
barcode : barcode associated with the virtual tape; the first part of the barcode, the prefix,
is constant across a file system. In this example, pre1 is the barcode prefix.
filesystem : name of the file system associated with the virtual tapes
capacity : virtual tape capacity in GB
location : element type and element ID of the virtual tape; possible element types are
slot, drive, import or export, robot, and vault

Manage virtual tapes 41

Managing

source_slot : original slot number

Eject virtual tapes

The eject operation moves a tape from an import or export slot to the vault. Tapes in the
VTLU vault are not visible to the backup software. In a physical TLU, you can move the
tape cartridges to the import or export slots without opening the TLU’s door. These cartridges
are still visible from the backup software. A VTLU emulates the infrastructure of a physical
TLU to ensure compatibility with the backup software and consistency with physical TLUs.
Steps to eject virtual tapes are:
1. If you already know the tape barcode, then proceed to step 2. Otherwise, query the VTLU
to identify the barcode of the tape that you want to eject by using this command syntax:
$ server_vtlu <movername> -tape -list <tlu_id>

where:
<movername> = name of the Data Mover
<tlu_id> = ID of the VTLU
Example:
To list the tape information for VTLU 1 on server_2, type:
$ server_vtlu server_2 -tape -list 1

Output:

barcode filesystem capacity(GB) location source_slot

pre10009 ufs2 50 slot:9
pre1000a ufs2 50 slot:10
pre1000b ufs2 41 vault
pre10004 ufs2 50 slot:4
pre10005 ufs2 50 impexp:5
pre10006 ufs2 50 slot:6
pre10007 ufs2 50 slot:7
pre10008 ufs2 50 slot:8
pre10000 ufs2 50 slot:0
pre10002 ufs2 50 slot:2
pre10001 ufs2 50 slot:1
pre10003 ufs2 50 slot:3
Column definitions:
barcode : barcode associated with the virtual tape; the first part of the barcode, the prefix,
is constant across a file system. In this example, pre1 is the barcode prefix.
filesystem : name of the file system
capacity : virtual tape capacity in GB
location : element type and element ID of the virtual tape; possible element types are
slot, drive, import or export, robot, and vault

42 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

source slot : original slot number

2. Eject a virtual tape from the VTLU and place it in the vault by using this command syntax:
$ server_vtlu <movername> -tape -eject <tape_barcode> -tlu <tlu_id>

where:
<movername> = name of the Data Mover
<tape_barcode> = barcode of the virtual tape
<tlu_id> = ID of the VTLU
Example:
To eject a virtual tape from the VTLU and place it in the vault, type:
$ server_vtlu server_2 -tape -eject pre10005 -tlu 1

Output:

server_2 : done

Unmount a virtual tape

Unmounting a tape removes it from a tape drive and places it in its original slot or in another
available slot. You should use this function only if the backup software encounters a problem
and cannot unmount a tape. It is not possible to unmount a tape from a drive that is in use.

Note: Mounting a tape is not possible from VNX. You must mount a tape from your backup software.

Steps to unmount a virtual tape are:

1. If you already know the drive ID, then proceed to step 2. Otherwise, identify the tape
drive ID for the tape that you want to unmount by using this command syntax:
$ server_vtlu <movername> -drive -list <tlu_id>

where:
<movername> = name of the Data Mover
<tlu_id> = ID of the VTLU
Example
To list the drive information for VTLU 1, type :
$ server_vtlu server_2 -drive -list 1

Output:

Manage virtual tapes 43

Managing

drive_id device_name serial_number status tape_barcode

0 c2t2l14 VtwsQVq300 loaded pre10001
1 c2t2l15 b0VARVq300 empty
2 c2t2l8 rwgJSVq300 empty
Column definitions:
drive_id : ID of the virtual tape drive. The default IDs are 0–3 for a VTLU with four drives

device_name : device name of the virtual drive in the format:

c<x>t<y>l<z>
where:
<x> = SCSI starting chain number
<y> = SCSI ID
<z> = SCSI LUN
Only the chain ID can be modified; the default chain ID is 0.
serial_number : drive serial number, which the Data Mover automatically assigns
status : status of the tape drive; options are:
•
empty : no tape is in the drive
•
full : a tape is in the drive, but the drive has been unloaded by the backup software
•
loaded : a tape is in the drive and the drive is loaded
•
in use : the drive is in use for a backup or restore
tape_barcode : barcode of the tape loaded in the tape drive, if any

2. Unmount a virtual tape drive by using this command syntax:

$ server_vtlu <movername> -drive -unmount <drive_id> -tlu <tlu_id>

where:
<movername> = name of the Data Mover
<drive_id> = ID of the virtual tape drive
<tlu_id> = ID of the VTLU
Example:
To unmount virtual tape 0 on VTLU 1, type:
$ server_vtlu server_2 -drive -unmount 0 -tlu 1

Output:

server_2 : done
3. Verify that the tape has been unmounted by using this command syntax:
$ server_vtlu <movername> -drive -list <tlu_id>

where:

44 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

<movername> = name of the Data Mover

<tlu_id> = ID of the VTLU
Example:
To list the drive information for VTLU 1, type:
$ server_vtlu server_2 -drive -list 1

Output:

drive_id device_name serial_number status tape_barcode

0 c2t2l14 VtwsQVq300 empty
1 c2t2l15 b0VARVq300 empty
2 c2t2l8 rwgJSVq300 empty
Column definitions:
drive_id : ID of the virtual tape drive; the default IDs are 0–3 for a VTLU with four drives

device_name : device name of the virtual drive in the following format:

c<x>t<y>l<z>
where:
<x> = SCSI starting chain number
<y> = SCSI ID
<z> = SCSI LUN
Only the chain ID can be modified; the default chain ID is 0.
serial_number : drive serial number, which the Data Mover automatically assigns
status : tape drive status; options are:
•
empty : no tape is in the drive
•
full : a tape is in the drive, but the drive has been unloaded by the backup software
•
loaded : a tape is in the drive and the drive is loaded
•
in use : the drive is in use for a backup or restore
tape_barcode : barcode of the tape loaded in the tape drive, if any

4. Run an inventory from your backup software.

Manage virtual tapes 45

Managing

List VTLU information

The tasks to query the VTLU for information on its configuration properties are:
◆ List VTLUs on a Data Mover on page 46
◆ List VTLU information on page 47
◆ View the Chain ID on page 48
◆ List VTLU tapes on page 49
◆ View tape information on page 50
◆ List the VTLU drives on page 51
◆ List drive information on page 52

List VTLUs on a Data Mover

Action
To view a list of VTLUs for the Data Mover, use this command syntax:
$ server_vtlu <movername> -tlu -list
where:
<movername> = name of the Data Mover

Example:
To list the VTLUs configured on server_2, type:
$ server_vtlu server_2 -tlu -list

Output

id vendor product revision serial_number device_name

1 EMC svtlRobot 1.0 NvP6ZHP1k5 c0t0l0
2 LEGATO svtlRobot 1.01 gkzp9492k5 c0t0l5
3 EMC svtlRobot 1.01 P8gIgqs2k5 c0t0l14
4 xyz vtlu 5.0 lX21uML2k5 c0t1l3
5 EMC svtlRobot 1.0 RLMgE853k5 c0t1l8
7 EMC svtlRobot 1.01 TogVYQH3k5 c0t1l11

46 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

Note
Column definitions:
id : ID number for the VTLU

vendor : vendor name associated with the VTLU

product : VTLU product name

revision : VTLU revision number

serial number : VTLU serial number, which the Data Mover automatically assigns

device name : device name of the virtual robot

List VTLU information

Action
To view information on the VTLU, robot, drives, slots, and import or export slots, use this command syntax:
$ server_vtlu <movername> -tlu -info <tlu_id>
where:
<movername> = name of the Data Mover

<tlu_id> = ID of the VTLU

Output

server_2 :
id = 1
slots = 48
import/export slots= 16
robot vendor = EMC
robot product = svtlRobot
robot revision = 1.0
robot serial number= NvP6ZHP1k5
robot device name = c0t0l0
drives = 8
drive vendor = EMC
drive product = svtlDrive
drive revision = 1.0

List VTLU information 47

Managing

Note
Output definition:
id : VTLU ID

slots : number of slots on the VTLU; sum of the slots, import or export slots, and drives cannot exceed 65,535

import/export slots : number of virtual import or export slots in the VTLU

robot vendor : vendor name associated with the virtual robot

robot product : product name associated with the virtual robot

robot revision : revision number of the virtual robot

robot serial number : serial number of the virtual robot

robot device name : device name of the VTLU robot

drives : number of virtual drives in the VTLU

drive vendor : vendor name associated with the virtual drive

drive product : drive product name that can contain up to 16 characters

drive revision : revision number associated with the virtual drive

View the Chain ID

Use this command to discover the chain ID associated with a VTLU. The chain ID is part of
the virtual device name associated with the VTLU. You can modify the chain ID if you have
a device name collision with a physical TLU’s device name. Configure the chain ID on page
31 describes how to modify the chain ID.

Action
To view the chain ID, use this command syntax:
$ server_vtlu <movername> -service -info
where:
<movername> = name of the Data Mover

Example:
To query the VTLU on server_2 for the chain ID, type:
$ server_vtlu server_2 -service -info

Output
server_2 : starting chain id = 0

48 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

Note
Output definition:
server_2 : Data Mover on which you are viewing information

starting chain id : starting chain of the VTLU device name; this value is the first number in the device name; it
applies to all VTLU devices on the Data Mover

List VTLU tapes

Action
To query the VTLU for virtual tape information, use this command syntax:
$ server_vtlu <movername> -tape -list <tlu_id>
where:
<movername> = name of the Data Mover

<tlu_id> = ID of the VTLU

Example:
To view tape information for VTLU 1, which resides on server_2, type:
$ server_vtlu server_2 -tape -list 1

Output

barcode filesystem capacity (GB) location source_slot

pre10008 ufs1 50 drive:2 8
pre1000a ufs1 50 slot:10 10
pre10002 ufs1 50 slot:2 2
pre10006 ufs1 50 drive:3 6
pre10004 ufs1 50 slot:4 4
pre10007 ufs1 50 slot:7 7
pre10001 ufs1 50 slot:1 1
pre10009 ufs1 50 drive:1 9
pre10003 ufs1 50 drive:0 3
pre1000b ufs1 40 impexp:0
pre10000 ufs1 50 slot:0 0
pre10005 ufs1 50 slot:5 5

List VTLU information 49

Managing

Note
Column definitions:
barcode : barcode associated with the virtual tape; the first part of the barcode, the prefix, is the same for tapes associ-
ated with the same file system. In this example, pre1 is the barcode prefix.
filesystem : name of the file system

capacity(GB) : virtual tape capacity in GB

location : element type and element ID of the virtual tape; possible element types are slot, drive, import or export,
robot, and vault
source slot : original slot number

View tape information

Use server_vtlu command to display information about the virtual tape. You need to know
the barcode of a tape to complete this command. List VTLU tapes on page 49 describes how
to discover a tape barcode.

Action
To query the VTLU for information on a particular tape, use this command syntax:
$ server_vtlu <movername> -tape -info {<tape_barcode>|-all} -tlu <tlu_id>
where:
<movername> = name of the Data Mover

<tape_barcode> = barcode of the tape on which you want information

<tlu_id> = ID of the VTLU

Example:
To query the VTLU for information on tape pre10008 on VTLU 1, type:
$ server_vtlu server_2 -tape -info pre10008 -tlu 1

Output

barcode = pre10008
filesystem = ufs1
capacity = 50GB
source_slot = 8
location = drive:2

50 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

Note
Output definitions:
barcode : barcode associated with the virtual tape; the first part of the barcode, the prefix, is constant for all tapes asso-
ciated with the same file system. (In this example, pre1 is the barcode prefix.)
filesystem : file system associated with the tape

capacity : capacity of the tape in GB

location : location of the tape

source_slot : slot where the tape resided before its current location

List the VTLU drives

Action
To view the drives associated with a VTLU, use this command syntax:
$ server_vtlu <movername> -drive -list <tlu_id>
where:
<movername> = name of the Data Mover

<tlu_id> = ID of the VTLU

Example:
To view the drives on VTLU 1, which resides on server_2, type:
$ server_vtlu server_2 -drive -list 1

Output

drive_id device_name serial_number status tape_barcode

0 c0t0l1 Lk8rbmg000 loaded pre10003
1 c0t0l2 1Rwzcmg000 loaded pre10009
2 c0t0l3 hnVHdmg000 loaded pre10008
3 c0t0l4 xTgQemg000 loaded pre10006

List VTLU information 51

Managing

Note
Column definitions:
drive_id : ID of the virtual tape drive; the default IDs are 0–3 for a VTLU with four drives

device_name : device name of the virtual drive in the following format:

c<x>t<y>l<z>
where:
<x> = SCSI starting chain number

<y> = SCSI ID

<z> = SCSI LUN

Only the chain ID can be modified; the default chain ID is 0.

serial_number : drive serial number, which the Data Mover automatically assigns

status : tape drive status; options are:

◆ empty : no tape is in the drive

◆ full : a tape is in the drive, but the drive has been unloaded by the backup software
◆ loaded : a tape is in the drive and the drive is loaded
◆ in use : the drive is in use for a backup or restore

tape_barcode : barcode of the tape loaded in the tape drive, if any

List drive information

Action
To view drive information, use this command syntax:
$ server_vtlu <movername> -drive -info <drive_id> -tlu <tlu_id>

where:
<movername> = name of the Data Mover

<drive_id> = ID of the drive on which you want to list information

<tlu_id> = ID of the VTLU

Example:
To view information on drive 2 on VTLU 1, type:
$ server_vtlu server_2 -drive -info 2 -tlu 1

52 Configuring NDMP Backup to Disk on VNX 7.1

 Managing

Output

server_2 :
id = 1
device_name = c0t0l8
status = loaded
serial_number = hnVHdmg000
status = loaded
tape_barcode = pre10008

Note
Output definitions:
id : ID of the virtual tape drive; the default IDs are 0-3 for a VTLU with four drives

device_name : device name of the virtual drive in the format:

c<x>t<y>l<z>
where:
<x> = SCSI starting chain number

<y> = SCSI ID

<z> = SCSI LUN

Only the chain ID can be modified; the default chain ID is 0.

serial_number : serial number of the drive, which is automatically assigned

status : drive status; options are:

◆ empty : no tape is in the drive

◆ full : tape is in the drive, but the drive has been unloaded by the backup software
◆ loaded : tape is in the drive and the drive is loaded
◆ in use : drive is in use for a backup or restore

tape_barcode : barcode of the tape loaded in the tape drive, if any

List VTLU information 53

Managing

54 Configuring NDMP Backup to Disk on VNX 7.1

 5

Troubleshooting

As part of an effort to continuously improve and enhance the performance

and capabilities of its product lines, EMC periodically releases new versions
of its hardware and software. Therefore, some functions described in this
document may not be supported by all versions of the software or
hardware currently in use. For the most up-to-date information on product
features, refer to your product release notes.
If a product does not function properly or does not function as described
in this document, contact your EMC Customer Support Representative.
Problem Resolution Roadmap for VNX contains additional information about
using the EMC Online Support website and resolving problems.
Topics included are:
◆ EMC E-Lab Interoperability Navigator on page 56
◆ VNX user customized documentation on page 56
◆ Error messages on page 56
◆ EMC Training and Professional Services on page 57

Configuring NDMP Backup to Disk on VNX 7.1 55

Troubleshooting

EMC E-Lab Interoperability Navigator

The EMC E-Lab™ Interoperability Navigator is a searchable, web-based application that
provides access to EMC interoperability support matrices. It is available on the EMC Online
Support website at http://Support.EMC.com. After logging in, locate the applicable Support
by Product page, find Tools, and click E-Lab Interoperability Navigator.

VNX user customized documentation

EMC provides the ability to create step-by-step planning, installation, and maintenance
instructions tailored to your environment. To create VNX user customized documentation,
go to: https://mydocs.emc.com/VNX.

Error messages
All event, alert, and status messages provide detailed information and recommended actions
to help you troubleshoot the situation.
To view message details, use any of these methods:

◆ Unisphere software:

• Right-click an event, alert, or status message and select to view Event Details, Alert
Details, or Status Details.

◆ CLI:

• Type nas_message -info <MessageID>, where <MessageID> is the message

identification number.

◆ Celerra Error Messages Guide:

• Use this guide to locate information about messages that are in the earlier-release
message format.

◆ EMC Online Support website:

• Use the text from the error message's brief description or the message's ID to search
the Knowledgebase on the EMC Online Support website. After logging in to EMC
Online Support, locate the applicable Support by Product page, and search for the
error message.

56 Configuring NDMP Backup to Disk on VNX 7.1

 Troubleshooting

EMC Training and Professional Services

EMC Customer Education courses help you learn how EMC storage products work together
within your environment to maximize your entire infrastructure investment. EMC Customer
Education features online and hands-on training in state-of-the-art labs conveniently located
throughout the world. EMC customer training courses are developed and delivered by EMC
experts. Go to the EMC Online Support website at http://Support.EMC.com for course and
registration information.
EMC Professional Services can help you implement your system efficiently. Consultants
evaluate your business, IT processes, and technology, and recommend ways that you can
leverage your information for the most benefit. From business plan to implementation, you
get the experience and expertise that you need without straining your IT staff or hiring and
training new personnel. Contact your EMC Customer Support Representative for more
information.

EMC Training and Professional Services 57

Troubleshooting

58 Configuring NDMP Backup to Disk on VNX 7.1

 Glossary

software virtual tape library (SVTL)

See VTLU.

virtual tape library unit (VTLU)

Software-based virtual tape library configured on a Data Mover that emulates a physical TLU.
A VTLU allows NDMP to work with disk-based storage.

Configuring NDMP Backup to Disk on VNX 7.1 59

Glossary

60 Configuring NDMP Backup to Disk on VNX 7.1

 Index

A file system (continued)

importing 37
adding
a file system 22
storage 22 G
GUI Unisphere 9
C
chain ID H
modifying 31 help system 9
viewing 48
configuration
options 18, 29 L
creating a new VTLU 15
listing
tape information 50
D VTLU properties 46
Data Mover, listing VTLUs on 46
device name, modifying 31 M
device names
configuring 24 messages, error 56
discovering device names 24 modifying
chain ID 31

E
EMC E-Lab Navigator 56
error messages 56
exporting storage 36

F
file system
adding 22
exporting 36

Configuring NDMP Backup to Disk on VNX 7.1 61

Index

modifying (continued) system requirements 8

device name 31
T
N
tapes
NDMP, configuration 15 ejecting 42
listing 50
unmounting 43
O troubleshooting 55
online help 9
U
Q Unisphere 9
querying a VTLU 46
V
R viewing
requirements chain ID 48
for NDMP 15 VTLU properties 46
for your system 8 virtual tapes
ejecting 42
unmounting 43
S VTLU
adding storage 22
starting chain components 12
modifying 31 configuration options 18, 29
viewing 48 configuring 16
storage creating 15
adding to VTLU 22 deleting 33
configuration options 23 device names 12
deleting 38 NDMP prerequisites 15
exporting 36 properties
importing 37 listing 46

62 Configuring NDMP Backup to Disk on VNX 7.1