Using EMC Celerra with IBM Tivoli Storage Manager … EMC Celerra with IBM Tivoli Storage Manager Version 5.5 Applied Technology Abstract This white paper bridges the gap between the

Using EMC Celerra with IBM Tivoli Storage Manager Version 5.5

Applied Technology

Abstract

This white paper bridges the gap between the IBM Tivoli Storage Manager (TSM) user guides and the EMC® Celerra® Configuring NDMP Backups on Celerra technical module. It explains why configuration parameters are used to create connectivity between TSM and the Celerra Data Mover.

October 2009

Copyright © 2009 EMC Corporation. All rights reserved.

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 listing of EMC product names, see EMC Corporation Trademarks on EMC.com

All other trademarks used herein are the property of their respective owners.

Part Number h6637

Using EMC Celerra with IBM Tivoli Storage Manager Version 5.5 Applied Technology 2

Table of Contents Executive summary ............................................................................................4 Introduction.........................................................................................................4

Audience ...................................................................................................................................... 4 Terminology ................................................................................................................................. 4

IBM Tivoli Storage Manager version 5.5 ...........................................................4 Basic edition................................................................................................................................. 5 Extended edition .......................................................................................................................... 5

TSM topology ......................................................................................................5 TSM architecture.......................................................................................................................... 6

Storage pools ........................................................................................................................... 6 Device class ............................................................................................................................. 7 Policy and policy set................................................................................................................. 7 Path .......................................................................................................................................... 8 Virtual file spaces ..................................................................................................................... 9 Relationship between client nodes, storage pools, and policy sets ......................................... 9

Installing TSM....................................................................................................10 Configuring TSM for Celerra NDMP operations .............................................11 EMC Celerra NDMP features ............................................................................12

Integrated Checkpoint feature.................................................................................................... 12 Back up and restore NAS file servers using TSM..........................................13

Using the backup and restore client .......................................................................................... 13 Back up a client file system.................................................................................................... 13 Restore a client file system .................................................................................................... 16

Conclusion ........................................................................................................17 References ........................................................................................................17


Executive summary As an organization grows, so do its data storage requirements. However, storing data is not enough. Its protection is equally important. Protecting data is one of the foremost concerns of customers today. IBM Tivoli Storage Manager (TSM) protects an organization’s data by storing backup and archive copies offline.

Customers setting up and configuring TSM on EMC® Celerra® might find it difficult to understand IBM terminology, for example, terms like policy set, management class, and so on, and how they relate to the Celerra Data Mover and tape library unit (TLU). Therefore, it is important to understand the TSM architecture and how IBM terminologies translate to Celerra terminologies.

Introduction This white paper provides an overview of the TSM architecture and the components that make up this architecture. It discusses how these components relate to the Celerra NDMP environment. It also describes how you can install and configure TSM for Celerra. This white paper shows the relationship between client nodes, storage pools, and policy sets and briefly describes how to use the backup and restore client.

IBM TSM version 5.5 is described in this paper. It is supported with EMC Celerra Network Server versions 5.5 and 5.6.

Audience This white paper is intended to be used by EMC Professional Services and customers’ implementation services engineers.

Terminology Backup and restore — Technique for ensuring file system integrity and security by backing up to tape or disk a file system or incremental changes to a file system; this data can be restored later.

Checkpoint — Point-in-time, logical image of a PFS. A checkpoint is a file system and is also referred to as a checkpoint file system or a SnapSure™ file system.

Graphical user interface (GUI) — Software that uses graphical objects such as pull-down menus and operations such as drag-and-drop to allow the user to enter commands and execute functions.

Network Data Management Protocol (NDMP) — Open standard network protocol designed for enterprise-wide backup and recovery of heterogeneous network-attached storage.

Tape library unit (TLU) — Physical device that contains and manages sets of tape drives and cartridges.

Three-way backup — EMC’s definition of three-way NDMP backup: NDMP-protocol backup that directs data from one Data Mover through a network connection to a remote Data Mover to its attached tape library backup device.

Two-way backup — NDMP protocol backup that directs data from a Data Mover attached to a tape drive (NDMP server) to the tape library backup device.

IBM Tivoli Storage Manager version 5.5 IBM TSM is the core product in the Tivoli Storage Management suite. TSM protects an organization’s data by storing backup and archive copies offline. TSM is an enterprise-level storage protection system, and can scale to protect hundreds of computers, from laptops to mainframes running many different operating systems. What many customers like about TSM is that it uses a common graphical user interface (GUI) for


all its backup clients. This means that you can move to different operating systems and still be familiar with the backup and archive GUI on that platform.

TSM also implements a centralized in-built database in the backup server to keep track of what was stored, where the backups are stored, who are the clients, what are their business policies, and what are the backup schedules. The database is referenced when running backups, doing collocation and relocation to consolidate stored files onto fewer volumes. The centralized web-based management, smart data move and store techniques, and comprehensive policy-based automation work together to minimize data protection administration costs.

IBM TSM comes in two editions: Basic edition and Extended edition.

Basic edition IBM TSM 5.5 is an enterprise-class storage management application. It has many modules and supports about 30 different computer platforms. It can scale to protect hundreds of computers connected by LANs, WANs, or the Internet. The Basic edition does not support NDMP.

The Basic edition contains modules to perform tasks such as progressive incremental backups, tape resource sharing, dynamic multithreaded processes, and tape library support.

Extended edition The Extended edition of TSM contains all features in the Basic edition along with disaster planning capability, Network Data Management Protocol (NDMP) backup, and support for large tape libraries. For Celerra users using NDMP backup features, the Extended edition is necessary.

For Celerra and other NAS devices, TSM uses NDMP to perform high-performance, scalable backups and restores, keeping network traffic to a minimum. NDMP enables a full and differential file system image backup and restore of the Celerra systems. Multiple backup and restore operations can be performed simultaneously.

During the backup and restore operations, data flows directly between the tape drive and the Data Mover. NDMP for Celerra backup uses either a SCSI or fibre-attached tape library unit attached to the Celerra Data Mover. Data flows directly from the Data Mover to the TLU without going through the network, minimizing network traffic.

TSM topology IBM TSM is implemented as a client/server software application. This application consists of an IBM TSM server software component, a backup-archive client (baclient) component, and the IBM TSM storage agent component.

In this topology, the TSM client is used to display NAS nodes and file systems. The TSM client is also used to run the user interface for backup and restore (baclient), monitor the backup and restore progress on the client, and issue commands to start and stop the backup and restore operations. The client or user interface is uniform across all platforms. If you learn it on one platform, you can translate it across the other platforms.

When a TSM client starts a backup or restore operation, the backup or restore request is sent over the IP network to the TSM server. The TSM server accepts the requests from the client and runs a TSM process to initiate NDMP sessions. These commands are sent over the IP network to the NDMP server, which is also the Celerra Data Mover. The TSM server also keeps track of the metadata for the stored data and controls the tape library unit (TLU) operations.

The Celerra Data Mover is the NDMP server. It accepts the requests from the TSM server and issues NDMP commands to the TLU to initiate and perform tape and library operations. At the right moment, it retrieves data from the storage back end and sends it over a fibre connection to the TLU. This is a two-way NDMP backup and restore operation. TSM supports another configuration where the NDMP server sends Using EMC Celerra with IBM Tivoli Storage Manager Version 5.5 Applied Technology 5

data to another server that is connected to a TLU. IBM TSM calls it a three-way NDMP backup. This is not strictly the definition of three-way NDMP backup (which involves two Data Movers, one of which is the NDMP server) for Celerra. TSM with Celerra does not support three-way NDMP backup and restore operations.

Figure 1 shows the TSM topology.

Figure 1. TSM topology

TSM architecture

Storage pools IBM TSM stores all client data in storage repositories. Storage repositories are collections of similar storage devices called storage pools. The storage devices may be disks, tapes, or optical devices. The TSM server controls the storage pools by using its native model of storage to view, classify, and manage the storage devices.

TSM has a unique approach to manage client data. Most backup applications directly store the client data in the backup tapes. TSM manages the client data in storage pools. Data objects may be file system components such as files, directories, or even disk volumes that are backed up from the client systems. They may also be objects like database records or tables from database application backups.

Each data object has an associated management policy bound to it that defines what TSM does with that object. This is further explained in the following sections.

To manage the storage pools and their contents, TSM uses logical entities called storage pools, which describes a storage resource for a single type of storage media, for example, a disk partition or a set of tape cartridges. In any case, all client data is stored in some type of a storage pool.

TSM organizes storage pools in one or more hierarchical structures, which can span over several server instances. Within the TSM server, TSM implements management functions to migrate data objects automatically from one storage hierarchy to another. In other words, TSM can store client data in disk


http://celerra.emc.com/servlet/JiveServlet/showImage/102-2556-24-1530/topology4.JPG

storage pools and later move the data to tape cartridges. The actual location of the data objects at any time is automatically tracked within the built-in server database.

TSM also manages data with two important functions called relocation and collocation. After the data is stored in the storage repository, TSM may relocate data objects from one volume to another and collocate data objects that belong together. Collocation enables quick and efficient restoration of client data. The two management functions are done in the background and are transparent to the backup clients.

Another important TSM management function is the ability to copy client data objects and store them in different storage pools as shown in Figure 2. There are two kinds of storage pools: primary and copy storage pools. You can create primary storage pools such as disk pools, and copy storage pools such as local tape drives. The copy function can copy client data from the disk pool to local tape drives. You can then have the tapes taken offsite for long-term storage. This copy function is also performed and tracked automatically within the TSM server.

Figure 2. TSM copy storage pools

Client data can be sent to different disk pools, then copied to tape drives later.

Device class A device class is a basic building block for storage on a TSM server. It defines the type of storage hardware used for a particular storage pool. Each device that forms part of the storage pool belongs to one device class, which specifies the device type along with media management information such as recording format, capacity, and labeling prefixes.

TSM provides some predefined media types such as 8MM, UTLTRIUM3C for LT03 drives, and DISK.

Policy and policy set A TSM environment consists of three basic types of resources: client systems, rules, and data. The client systems contain the data to be managed and the rules that specify how the data must be managed. Examples


would be, say, during a backup, how many versions of the data must be kept, where they must be stored, how long they must be retained, and so on.

TSM uses policies to define the relationship between the three resources.

In TSM, rules that are created as a set of storage management parameters such as the number of copies retained, the retention period of the backup copies, the storage media or storage pool used, and so on are stored in an entity called a Management Class. A set of Management Classes are stored in a policy set. One of the Management Classes is designated as the default Management Class.

The client systems or nodes with common storage management requirements are grouped together with some common storage policies. This group is called a policy domain. Figure 3 shows the contents of a policy domain.

Figure 3. Policy domain

A policy domain contains a policy set consisting of at least one (default) Management Class, which contains:

• A backup copy group, that specifies: Where the data is stored How many versions are retained How long the data is stored

• An archive copy group, that specifies: Where the data is stored How long the data is stored

• Other Management Classes, each with their own backup and archive copy groups

Path In a TSM environment, you have logical entities such as storage pools and physical objects such as TLUs. A TLU represents a storage entity that contains drives and tapes to store data. A library always has drives defined to it. When a library is defined, a logical object is represented in the TSM environment. The direct link between the logical and the physical library is defined in a “path” object.

In an NDMP operation, the backup data flows across a path between the Data Mover and the destination, which is a tape drive. The restore data flows back across the path from the tape drive to the Data Mover.


http://celerra.emc.com/servlet/JiveServlet/showImage/102-2556-24-1539/PolicyDomain-Big.JPG

The Configuring NDMP Backups on Celerra technical module (available on Powerlink®) uses the following command to define the path between the Data Mover and the tape drive:

define path server_2 NDMPlib srctype=datamover desttype=library device=c2t0l0 The physical path is defined in the Data Mover name (server_2), and the device name (c2t0l0). At the Control Station, if you issue the following command server_devconfig server_2 –probe –scsi –all and if a TLU is attached and defined to the Data Mover server_2, you will be able to see the device name displayed. The format of the device name (c2t0l0) refers to the Controller 2 (c), target 0 (t), and lun 0 (l), and is sometimes referred to as the CTL number.

Virtual file spaces Use a virtual file space definition to perform NAS directory-level backups. This is like mapping a logical name to the NAS directory. To reduce the backup and restore time for large file systems, map a directory path from a NAS file server to a virtual file space name on the TSM server. To create a virtual file space name for the directory path on the NAS device, we use the define virtualfsmapping command:

define virtualfsmapping Celerra1 /mydir /fs1 /mine

This command defines a virtual file space name /mydir on the file system fs1, at the directory path of /mine on the NAS node Celerra1.

Relationship between client nodes, storage pools, and policy sets When clients are registered, they are associated with a policy domain. The policy domain contains the policy sets, Management Classes, and copy groups.

When a client backs up or migrates a file, it is bound to a Management Class. A Management Class and the backup and archive copy groups within it specify where the files are stored and how they are managed when they are backed up, archived, or migrated from the client.

Storage pools are the destinations for backed up, archived, or space-managed files. Copy groups specify storage pools for backed-up or archived files. Management Classes specify storage pools for space-managed files.

Storage pools are mapped to device classes, which represent devices. The storage pool contains volumes of the type indicated by the associated device class. For example, a storage pool that is mapped to a device class with a device type of *MM contains only 8 mm tapes.

Files that are initially stored on disk storage pools can migrate to tape or other types of storage pools if the pools are set up in a storage hierarchy. Figure 4 shows the relationship between the client nodes, storage pools, and policy sets.


Figure 4. Relationship between client nodes, storage pools, and policy sets

Installing TSM TSM uses a client/server paradigm and you need to install the server and client components. Although you do not need to install the server and client software on separate computers, it is recommended for performance reasons. The TSM server can consume a large amount of memory, network bandwidth, and processor resources, therefore, it is recommended that you install the server and the client components on separate machines. In many cases, the server performs best when other applications are not installed on the same system.

TSM can run on many (approximately 30) different operating systems. You can install the server software on a Sun server and the client software on a Windows machine, or install server software on a Windows server and client software on a Windows XP machine, and so on.

After the server and client software are installed, you need to configure the server software to recognize the TLU. Before you do this, you need to gather some information from the Celerra. Log in to the Control Station of the Celerra system that hosts the Data Mover connected to the TLU. You need to get some information about the TLU from the Control Station and use it when you configure the TLU and the Data Mover.

Here is a list of information you will need to gather:

• You need the IP address of the Data Mover hosting the TLU. Get the address from one of the interfaces. With CLI, you run the server_ifconfig server_x –all command. On the Celerra Manager, you can get this from the Networking screens.


• You need the output of the command server_devconfig server_x -probe -scsi –all. You need the CTL

value of the TLU and the tape drives. They are usually in the format cxtylz where x, y, and z are some positive integers.

• You need to create at least one user in each Data Mover that you want to connect to the TLU. In the Control Station, su to root and run the command /nas/sbin/server_user server_x -add -md5 -passwd <username>. When the prompt appears, type the password for this username. You need this username and password later.

To configure the server for NDMP, you need to run the dsmserv program. For Sun, it is in the /opt/Tivoli/tsm/server/bin directory. For Windows, it is in the /Program Files/Tivoli/TSM/server directory.

“Configuring TSM for Celerra NDMP operations ” next discusses the commands that you must run using dsmserv to configure the NDMP components.

Configuring TSM for Celerra NDMP operations Table 1 provides the commands for different NDMP operations.

Table 1 . Commands for NDMP operations

Operation Example command

Define the TLU Define library NDMPlib libtype=scsi shared=no

Define a device class for NDMP

Define devclass NDMPclass Library=NDMPlib devtype=NAS mountretention=0 estcapacity=30g

Define a storage pool Define stgpool NDMPpool NDMPclass Maxscratch=30 dataformat=Celerradump

Define a storage pool for table of contents Define stgpool tocpool disk

Define a Policy Domain Define domain NDMPdomain description = “policy domain for NDMP backup”

Create a policy set in the domain Define Policyset NDMPdomain NDMPpolicy

Define a Management Class Define Mgmtclass NDMPdomain NDMPpolicy NDMPmgmtclass

Assign it as a default Management Class Assign defmgmtclass NDMPdomain NDMPplicy NDMPmgmtclass

Define a backup copy group

Define Copygroup NDMPdomain NDMPpolicy nMPmgmtclass destination=NDMPpool Verexist=20 tocdestination=backuppool

Use a storage pool Define Volume backuppool bkpool F=3000

Activate the policy set Activate Policyset NDMPdomain NDMPpolicy

Register the NAS node Register NODE server_2 admin domain=NDMPdomain type=NAS

Define a Data Mover Define Datamover server_2 type=NAS hladdress=10.20.30.40 lladdress=10000 userid=NDMP password=NDMPpasswd dataformat=Celerradump

Define a path to the library

Define Path server_2 NDMPlib srctype=DATAMOVER DESTTYPE=Library DEVICE=c0t0l0

Show slots NDMPlib

Define Drive NDMPlib Drive1 element=128

Define Tape drive and Path

Define Drive NDMPlib Drive2 element=129


Operation Example command

Define Path server_2 Drive1 SRCTYPE=DATAMOVER desttype=DRIVE LIBRARY=NDMPlib Device=c0t0l1

Define Path server_2 Drive2SRCTYPE=DATAMOVER desttype=DRIVE LIBRARY=NDMPlib Device=c0t0l2

Label the tapes prior to use

Label LIBVOLUME NDMPlib SEARCH=yes labelsource=BARCODE checkin=scratch overwrite=yes

Define Virtual File Space Define VIRTUALFSMAPPING scarlos4 /domain /variety /junk

Copy to Backup data Move Data 000128

Copy to Move data Move Data 000128 Stgpool=newstgpool

EMC Celerra NDMP features Beginning with DART release 5.1, EMC Celerra added many enhancements to its NDMP backup and restore features. The current Celerra NDMP features are:

• Integrated Checkpoint for NDMP backup • NDMP volume backup (two-way and three-way support) • File Filtering for files and directories exclusion To run these NDMP features, the backup and restore operator has to define NDMP environment variables in their Data Management Applications (DMA) to activate the Celerra features. Because IBM TSM backup and archive client software do not accept environment variables, it is not possible to take advantage of these Celerra NDMP features by using environment variables.

To overcome this deficiency, EMC added a server parameter that will make it possible for DMAs that do not allow environment variables to use the Integrated Checkpoint feature. The following section explains how this is done. The Integrated Checkpoint feature is the only Celerra NDMP feature available to the TSM operations.

Integrated Checkpoint feature It is desirable to take backups from a stable image of the production file system. A production file system that is in flux may have too many files that are open during the backup process, leading to uncertain backup copies with files that have been modified during the backup. A checkpoint is a point-in-time view (snapshot) of the production file system and is consistent at the point in time it is snapped. Open files are ignored when the checkpoint file system is backed up

Operationally, to back up from a checkpoint, the backup operator must first create a checkpoint of the production file system, determine the checkpoint file system name, and enter the checkpoint file system mount point to the backup client program. However, the checkpoint file system name may change based on factors like the production file system name and the number of checkpoints already created. Therefore, it is inconvenient to use. The Integrated Checkpoint feature enables the operator to enter the production file system mount point in the backup client program. During the backup process, a temporary checkpoint file system name and mount point are created and used. When the backup process is completed, the temporary checkpoint file system is unmounted and deleted. Thus, the backup operator creates the same backup setup anytime, without changing the backup file system name.

To use this feature, the backup operator enters a Data Mover parameter by using the following command:

server_param server_x -facility NDMP -modify snapsure -value 1


This parameter notifies the Data Mover (NDMP server) that the Integrated Checkpoint feature is being requested and takes action to create the temporary checkpoint file system for backup.

Back up and restore NAS file servers using TSM After you install the server and client software, you are ready to run NDMP operations to back up and restore file systems from the Data Mover. The following sections describe the backup and restore client (baclient) interface to back up a NAS file system.

You can restore data from a NAS vendor system to another NAS vendor system when you use the NDMPDUMP data format. But you must verify compatibility between systems or maintain a separate storage pool for each NAS vendor.

Using the backup and restore client The TSM backup-archive client provides three operational interfaces: GUI, command line interface, and web user interface. The most commonly used interface is the GUI. It is available in almost all platforms. On those that do not have the GUI, you can use the Java-based web user interface, which has the same look and feel as that of the native GUI. On systems that require scripting for automation, the command line interface is a convenient tool to use instead.

Back up a client file system Before you start a large backup job, try backing up a small file system first. If it works for a small file system, it will work for a large file system. Therefore, rather than risking a backup job crash after waiting for many hours, it is better to see if the configuration you have set up works for you or not on a small file system. Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User’s Guide, available on the IBM website, provides more information on using the backup client.

To back up a remote or local client:

1. Start the client, type a user name and password, and then click Login.

Figure 5. Backup and restore client login dialog box

The backup-archive client window opens.


Figure 6. TSM backup and restore client user window

2. Click Backup. The Backup window appears.

3. Expand the directory tree and select the folder icon to display the files in the directory. Select the files or directories you want to back up. You will see a checkmark in the selection box.

4. From the list box, select the backup type, which may be one of the following (Figure 7):

Differential Full backup

Note: The first backup of a file is always a full backup, regardless of what you select.


Figure 7. Backup file systems

5. Click Backup. The backup processing status appears as shown in Figure 8. When the backup process is completed, a dialog box will appear to announce the completion of the backup job.

Figure 8. The backup Detailed Status Report


Restore a client file system Using the same backup and restore client interface, click the Restore button on the main interface screen. This will lead you into a tree structure that lists out the backup save-sets available for you to perform your file system restorations. For example, in Figure 9, the File Level branch of the tree structure lists several UNCs that point to files that have been backed up. Selecting the checkboxes on the left of the directory structure indicates that you want those files restored. The files will then be restored to their original location.

The Options button allows you to change the restore location to somewhere other than the original location.

Clicking Restore will start the restore process. When the file system restoration is completed, you will be shown a completion dialog box.

Figure 9. Restore client user window


Conclusion TSM is a scalable product that protects organizations from data loss. It tracks details of the data that it backs up and archives. This, along with its smart data move and store techniques and comprehensive policy-based automation, minimizes protection and administrative costs. TSM has two editions, Basic and Extended. Only the Extended edition of TSM can be used with Celerra NDMP. To make it possible for DMAs to leverage the Integrated Checkpoint feature of Celerra NDMP, EMC added a server parameter command. Understanding the TSM architecture is key to understanding why the Celerra commands are important for configuring the TLU.

References Name: EMC NDMP Features—A Detailed Review

Type: White paper

URL: http://powerlink.emc.com

Audience: Readers who are familiar with NDMP

Technical Depth: Medium

Name: Configuring NDMP Backups on Celerra

Type: Technical module

URL: http://powerlink.emc.com and the EMC Celerra Documentation CD Version 5.6

Audience: Implementation specialists, backup administrators

Technical Depth: Medium

Name: IBM Tivoli Storage Manager for Windows Administrator's Guide

Type: User Guide

URL: http://ibm.com

Audience: Technical consultants, implementation specialists, backup administrators

Technical Depth: High


Documents

Using EMC Celerra with IBM Tivoli Storage Manager … EMC Celerra with IBM Tivoli Storage Manager Version 5.5 Applied Technology Abstract This white paper bridges the gap between the