Get more out of your san with ibm tivoli storage manager sg246687

ibm.com/redbooks

Front cover

Get More Out of Your SAN with IBM Tivoli Storage Manager

Charlotte BrooksMichel Baus

Denver DaleyRichard Lanicca

Provides detailed planning, installation, and configuration scenarios

Describes new features for Tivoli Storage Manager V5.3

Includes flowcharts for troubleshooting

http://www.redbooks.ibm.com/


International Technical Support Organization


June 2005

SG24-6687-00

© Copyright International Business Machines Corporation 2005. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.

First Edition (June 2005)

This edition applies to Version 5, Release 3 of IBM Tivoli Storage Manager and related products.

Note: Before using this information and the product it supports, read the information in “Notices” on page xv.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Chapter 1. Introduction to SANs and IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . 11.1 Overview of Storage Area Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 Introduction to Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.3 Tivoli Storage Manager SAN functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.4 Tivoli Storage Manager V5.3 latest SAN functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.5 Tivoli Storage Manager SAN functions and products . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2. Tape library sharing planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Library sharing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1.1 Library partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.1.2 Library sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2 Components of library sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.1 Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.2 Library Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.3 Library medium changer and library control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.4 Library drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2.5 Library control path failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2.6 Data path failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.3 Benefits of tape library sharing with Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . 182.4 Requirements for tape library sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.5 Tasks with Tivoli Storage Manager library sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.5.1 Library Manager as a single Tivoli Storage Manager Server without Tivoli Storage Manager client data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.5.2 Tivoli Storage Manager server maintenance planning . . . . . . . . . . . . . . . . . . . . . 202.5.3 Library drive reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5.4 Drive allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.5.5 Deleting a library volume on the Library Manager . . . . . . . . . . . . . . . . . . . . . . . . 22

2.6 Moving to a dedicated Tivoli Storage Manager Library Manager . . . . . . . . . . . . . . . . . 242.6.1 Preparing the new Tivoli Storage Manager Library Manager instance . . . . . . . . . 282.6.2 Checking the server-to-server communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.6.3 Stop all activities on all Tivoli Storage Manager servers. . . . . . . . . . . . . . . . . . . . 292.6.4 Backing up the Tivoli Storage Manager database for all Tivoli Storage Manager

servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.6.5 Listing all library volumes on the original Library Manager . . . . . . . . . . . . . . . . . . 302.6.6 Checking out library volumes on the original Library Manager . . . . . . . . . . . . . . . 302.6.7 Creating library definitions on the new Library Manager. . . . . . . . . . . . . . . . . . . . 312.6.8 Checking in library volumes on the new Library Manager . . . . . . . . . . . . . . . . . . 322.6.9 Deleting and defining the library on the old Library Manager . . . . . . . . . . . . . . . . 332.6.10 Deleting unneeded volume history entries on the old Library Manager . . . . . . . 34

© Copyright IBM Corp. 2005. All rights reserved. iii

2.6.11 Updating all libraries on all Library Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.7 Command differences in a library sharing environment . . . . . . . . . . . . . . . . . . . . . . . . 37

2.7.1 Auditing the library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.7.2 The QUERY MOUNT and QUERY DRIVE commands. . . . . . . . . . . . . . . . . . . . . 38

2.8 Interactions between Library Manager and Library Client. . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 3. SCSI tape library sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.1 Introduction to SCSI tape library sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.1.1 SCSI libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.1.2 Library medium changer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2 Library sharing with SCSI/FC tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.2.1 SAN zoning information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.2.2 Installing on IBM AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.2.3 Installing on Microsoft Windows 2000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.2.4 Installing on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.2.5 Installing on SUN Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3.3 Tivoli Storage Manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.3.1 With the Tivoli Storage Manager Administration Center . . . . . . . . . . . . . . . . . . . . 733.3.2 With the Tivoli Storage Manager command line interface. . . . . . . . . . . . . . . . . . . 90

Chapter 4. IBM 3494 tape library sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934.1 Introduction to the IBM 3494 tape library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

4.1.1 IBM 3494 Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944.1.2 Categories in an IBM 3494 library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4.2 Library Sharing with the IBM 3494 Tape Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954.2.1 Installing on IBM AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964.2.2 Installing on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034.2.3 Installing on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094.2.4 Installing on SUN Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

4.3 Tivoli Storage Manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224.3.1 Configuring server-to-server communication on the Library Manager . . . . . . . . 1234.3.2 Defining the library on the Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244.3.3 Defining the library path on the Library Manager . . . . . . . . . . . . . . . . . . . . . . . . 1244.3.4 Defining the drives for this library on the Library Manager . . . . . . . . . . . . . . . . . 1244.3.5 Defining the drive paths on the Library Manager . . . . . . . . . . . . . . . . . . . . . . . . 1244.3.6 Defining a device class using the library on the Library Manager. . . . . . . . . . . . 1244.3.7 Checking in library volumes on the Library Manager . . . . . . . . . . . . . . . . . . . . . 1244.3.8 Creating the server-to-server communication on the Library Client . . . . . . . . . . 1244.3.9 Defining the library on the Library Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254.3.10 Defining the drives path for the Library Client on the Library Manager. . . . . . . 1254.3.11 Defining a device class that uses the library on the Library Client . . . . . . . . . . 125

Chapter 5. Library sharing with the ACSLS Manager . . . . . . . . . . . . . . . . . . . . . . . . . 1275.1 Introduction to the ACSLS Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

5.1.1 Basic communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295.2 Tivoli Storage Manager library sharing with the STK ACSLS Manager . . . . . . . . . . . 130

5.2.1 Installing on IBM AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315.2.2 Installing on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345.2.3 Installing on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1395.2.4 Installing on SUN Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

5.3 Tivoli Storage Manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495.3.1 Defining server-to-server communication on the Library Manager . . . . . . . . . . . 1505.3.2 Setting the ACSLS options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1515.3.3 Defining the library on the Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

iv Get More Out of Your SAN with IBM Tivoli Storage Manager

5.3.4 Defining the drives for this library on the Library Manager . . . . . . . . . . . . . . . . . 1535.3.5 Defining the drives path on the Library Manager . . . . . . . . . . . . . . . . . . . . . . . . 1545.3.6 Defining a device class that uses the library on the Library Manager. . . . . . . . . 1545.3.7 Checking in library volumes on the Library Manager . . . . . . . . . . . . . . . . . . . . . 1545.3.8 Defining server-to-server communication on the Library Client . . . . . . . . . . . . . 1555.3.9 Defining the library on the Library Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1555.3.10 Defining the drive path for the Library Client on the Library Manager. . . . . . . . 1555.3.11 Defining a device class that uses the library on the Library Client . . . . . . . . . . 1565.3.12 Checking the setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Chapter 6. Planning for LAN-free. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1596.1 Details about LAN-free backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1606.2 When to use LAN-free data movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616.3 The ideal LAN-free client machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1626.4 Supported operating systems and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1646.5 Configuration preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

6.5.1 Obtaining the device name(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1666.6 Compatibility concerns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 7. LAN-free backup to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1717.1 Overview of the lab environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1727.2 Setting up a policy domain for LAN-free clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

7.2.1 Setting up a policy domain from the Administration Center . . . . . . . . . . . . . . . . 1747.2.2 Setting up a policy domain using the command line interface . . . . . . . . . . . . . . 179

7.3 Registering a new client node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1797.3.1 Registering the node from the Administration Center . . . . . . . . . . . . . . . . . . . . . 1797.3.2 Registering the node using the command line interface . . . . . . . . . . . . . . . . . . . 181

7.4 Enabling LAN-free data movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1827.4.1 Setting LAN-free from the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . 1827.4.2 Setting up LAN-free data movement using the command line interface. . . . . . . 1897.4.3 Configuring the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

7.5 Configuring the Storage Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1937.5.1 Configuring the Storage Agent from the Management Console . . . . . . . . . . . . . 1947.5.2 Configuring the Storage Agent using the command line interface . . . . . . . . . . . 199

7.6 Verifying the LAN-free path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2007.7 Communicating with and monitoring the Storage Agent . . . . . . . . . . . . . . . . . . . . . . . 203

7.7.1 Querying from the Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . . 2037.7.2 Using the command line interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

7.8 Configuring other Tivoli products for LAN-free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Chapter 8. LAN-free backup to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2078.1 Introduction to LAN-free backup to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2088.2 Preconfiguration: Setting up SANergy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2088.3 Overview of the lab environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2098.4 Summary of LAN-free disk configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2138.5 Setting up the SAN-attached disk device on the Tivoli Storage Manager server . . . . 213

8.5.1 Setting up the SAN disk device from the Administration Center . . . . . . . . . . . . . 2138.5.2 Setting up the SAN disk device using the command line interface. . . . . . . . . . . 219

8.6 Creating a policy domain for LAN-free clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2228.6.1 Creating a policy domain from the Administration Center. . . . . . . . . . . . . . . . . . 2228.6.2 Creating a policy domain using the command line interface. . . . . . . . . . . . . . . . 226

8.7 Registering client node(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2278.7.1 Registering the node from the Administration Center . . . . . . . . . . . . . . . . . . . . . 2278.7.2 Registering a node using the command line interface . . . . . . . . . . . . . . . . . . . . 229

Contents v

8.8 Setting up server-to-server communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2308.8.1 Setting up server-to-server communication from the Administration Center. . . . 2308.8.2 Setting up server-to-server communication using the command line interface. . 234

8.9 Installing and configuring the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2358.9.1 LAN-free options (used between the client and the Storage Agent) . . . . . . . . . . 235

8.10 Configuring the Storage Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2368.10.1 Setting up the Storage Agent from the Administration Center . . . . . . . . . . . . . 2378.10.2 Setting up the Storage Agent using the command line interface . . . . . . . . . . . 241

8.11 Enabling LAN-free data movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2438.11.1 Enabling LAN-free from the Administration Center . . . . . . . . . . . . . . . . . . . . . . 2438.11.2 Enabling LAN-free with the command line interface . . . . . . . . . . . . . . . . . . . . . 249

8.12 Verifying the LAN-free path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Chapter 9. Tivoli Storage Manager SAN Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . 2539.1 SAN device mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2549.2 New or updated Tivoli Storage Manager commands . . . . . . . . . . . . . . . . . . . . . . . . . 255

9.2.1 SANDISCOVERY server option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2559.2.2 QUERY SAN command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2559.2.3 DEFINE LIBRARY command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2569.2.4 DEFINE DRIVE serial number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2579.2.5 DEFINE DRIVE element number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2579.2.6 SAN Discovery error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2589.2.7 New Tivoli Storage Manager messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

9.3 Platform support and usage instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2599.3.1 Information for Windows systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2599.3.2 Information for AIX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2609.3.3 Information for Linux systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2609.3.4 Information for Solaris systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

9.4 Example of the automatic device mapping feature . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Chapter 10. Server-free data movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26710.1 Overview of server-free data movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

10.1.1 Related options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27010.1.2 Data format for server-free data movement . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

10.2 Requirements for server-free data movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27210.2.1 Preparing for server-free data movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

10.3 Server-free data movement in our lab environment . . . . . . . . . . . . . . . . . . . . . . . . . 27710.3.1 Server-free backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Chapter 11. Tivoli Storage Manager for Hardware — Data Protection for ESS for mySAP™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

11.1 Introduction to Data Protection for mySAP™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29411.2 Overview of the test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

11.2.1 Overview of the procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29611.3 Requirements and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

11.3.1 Hardware requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29711.3.2 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29711.3.3 Storage classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

11.4 Installation for this environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30011.4.1 mySAP™ and Oracle™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30011.4.2 Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30211.4.3 Tivoli Storage Manager for Hardware: Data Protection for IBM ESS for mySAP™

31911.4.4 Backup and restore commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

vi Get More Out of Your SAN with IBM Tivoli Storage Manager

11.5 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33011.5.1 FlashCopy Backup OFFLINE_MIRROR NOCOPY to Tivoli Storage Manager 33111.5.2 FlashCopy Backup ONLINE_MIRROR Disk-only INCR . . . . . . . . . . . . . . . . . . 343

11.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore35611.6.1 FlashBack Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

11.7 Special environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37211.7.1 AIX LVM mirroring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37211.7.2 AIX HACMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37311.7.3 Multiple backup generations on disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

11.8 Determining problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37611.8.1 Diagnostic commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37611.8.2 Summary of various logs and traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37611.8.3 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

Chapter 12. Backing up SAN File System with Tivoli Storage Manager . . . . . . . . . . 37912.1 SAN File System overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

12.1.1 SAN File System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38112.2 Backing up SAN File System with Tivoli Storage Manager. . . . . . . . . . . . . . . . . . . . 382

12.2.1 Benefits of Tivoli Storage Manager with SAN File System . . . . . . . . . . . . . . . . 38212.3 Backup and restore scenarios with Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . 383

12.3.1 Backing up user data in Windows filesets using Tivoli Storage Manager client for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

12.3.2 Backing up user data in UNIX filesets with Tivoli Storage Manager client for AIX . 387

12.3.3 Backing up FlashCopy images with Tivoli Storage Manager the -snapshotroot option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

12.4 Special environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39812.4.1 Large quantity of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39812.4.2 Large amounts of files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Chapter 13. General troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40113.1 Introduction to troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

13.1.1 Step 1.1: QUERY SAN command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40413.1.2 Step 1.2: Is the correct device driver installed . . . . . . . . . . . . . . . . . . . . . . . . . 40413.1.3 Step 1.3: Test the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40413.1.4 Step 1.4: Powercycle the device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40613.1.5 Step 1.5: Confirm that the path is online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40713.1.6 Step 1.6: Update the path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40713.1.7 Step 1.7: q path f=d. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40813.1.8 Step 1. 8: Confirm that the path points to the correct device . . . . . . . . . . . . . . 40813.1.9 Step 1. 9: Contact the vendor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

13.2 Library and SAN troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40913.2.1 Step 2.1: Is the device visible in SAN Nameserver. . . . . . . . . . . . . . . . . . . . . . 41013.2.2 Step 2.2: Check cables for drive etc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41013.2.3 Step 2.3: Is the zoning correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41113.2.4 Step 2.1: Is the server visible in SAN Nameserver . . . . . . . . . . . . . . . . . . . . . . 41113.2.5 Step 2.2: Check cables for server etc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41113.2.6 Step 2.6: Check HBA drivers and firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . 41113.2.7 Step 2.7: Contact the vendor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

13.3 Operating system and drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41213.3.1 Step 3.1: Is this an IBM device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41313.3.2 Step 3.2: Check the Tivoli Storage Manager device driver . . . . . . . . . . . . . . . . 41313.3.3 Step 3.3: Check the IBM tape device driver . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Contents vii

13.3.4 Step 3.4: Discover new devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41313.3.5 Step 3.5: Is the device visible to the operating system . . . . . . . . . . . . . . . . . . . 41313.3.6 Step 3.6: Contact the vendor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

13.4 Troubleshooting library sharing configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41813.4.1 Re-synchronizing server-to-server communication. . . . . . . . . . . . . . . . . . . . . . 41813.4.2 Define library path fails for IBM 3494 Tape Library. . . . . . . . . . . . . . . . . . . . . . 41913.4.3 ACSLS volume already locked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41913.4.4 ACSLS SSI Daemon requires correct name resolution . . . . . . . . . . . . . . . . . . 42013.4.5 Cannot connect to a Windows Tivoli Storage Manager server instance. . . . . . 420

Appendix A. Understanding TCP/IP ports for LAN-free in Tivoli Storage Manager . 421Introduction to TCP/IP ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422TCP/IP port definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423Server ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423Client ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424Storage Agent ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

viii Get More Out of Your SAN with IBM Tivoli Storage Manager

Figures

1-1 Common SAN components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2 Traditional LAN based backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41-3 LAN-free tape and disk backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51-4 Server-free data movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61-5 FlashCopy backup via a SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71-6 Typical tape library sharing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82-1 Library partitioning into multiple logical libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122-2 Library sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132-3 SCSI library control path failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162-4 Data path failover with one SAN fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172-5 Data path failover with two SAN fabrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182-6 Library Manager instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202-7 Before the Library Manager move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252-8 After the Library Manager move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273-1 SCSI/FC attached tape library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443-2 SCSI/FC attached tape library with control path failover . . . . . . . . . . . . . . . . . . . . . . 453-3 SCSI library sharing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463-4 SAN zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513-5 Device Manager: Without IBM tape driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543-6 Device Manager: Tape drive properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553-7 Device Manager: Tape drive update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553-8 Device Manager: Tape drive update - choose a specific driver . . . . . . . . . . . . . . . . . 563-9 Device Manager: Tape drive update - have a disk . . . . . . . . . . . . . . . . . . . . . . . . . . 563-10 Device Manager: Tape drive update - select inf file. . . . . . . . . . . . . . . . . . . . . . . . . . 573-11 Device Manager: Tape drive update - drive models . . . . . . . . . . . . . . . . . . . . . . . . . 573-12 Device Manager: Tape medium changer update. . . . . . . . . . . . . . . . . . . . . . . . . . . . 583-13 Device Manager: Tape medium changer update. . . . . . . . . . . . . . . . . . . . . . . . . . . . 593-14 Device Manager: Tape medium changer update - choose a specific driver . . . . . . . 593-15 Device Manager: Tape medium changer update - have a disk . . . . . . . . . . . . . . . . . 603-16 Device Manager: Tape medium changer update - choose directory . . . . . . . . . . . . . 603-17 Device Manager: Tape medium changer update - models . . . . . . . . . . . . . . . . . . . . 613-18 Device Manager: With the IBM device driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613-19 MMC: Tivoli Storage Manager Device Driver menu. . . . . . . . . . . . . . . . . . . . . . . . . . 623-20 MMC: Tivoli Storage Manager Device Driver - Drive information . . . . . . . . . . . . . . . 623-21 Lab configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733-22 Library Manager: Query Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743-23 Library Manager: enter name and type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753-24 Library Manager: Define library changer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753-25 Library Manager: Add drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763-26 Library Manager: Define path for drive one . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763-27 Library Manager: Define path for drive two . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773-28 Library Manager: Drives and paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773-29 Library Manager: Library wizard summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783-30 Library Manager: Shared library defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783-31 Library Manager: Query all device classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793-32 Library Manager: Defined device classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793-33 Library Manager: Wizard for the device class definition . . . . . . . . . . . . . . . . . . . . . . 793-34 Library Manager: Device class name and library assortment . . . . . . . . . . . . . . . . . . 80

© Copyright IBM Corp. 2005. All rights reserved. ix

3-35 Library Manager: All defined device classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803-36 Library Manager: Library settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813-37 Library Manager: Add volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813-38 Library Manager: Are the volumes labeled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823-39 Library Manager: Where are the volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823-40 Library Manager: Check in libvolumes options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833-41 Library Manager: Check in waittime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843-42 Library Manager: Check in summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843-43 Library Manager: Query libvolumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853-44 Library Client: Create the library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863-45 Library Client: Create library wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863-46 Library Client: Define the primary Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 873-47 Library Client: Define path for the shared drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873-48 Library Client: Define path for drive one . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883-49 Library Client: Path for both drives defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883-50 Library Client: Device class definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894-1 IBM 3494 Library sharing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964-2 Windows IBM Automated Tape Library Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044-3 Windows: Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054-4 Windows: HW update wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064-5 Windows: Driver search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064-6 Windows: Select driver directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074-7 Windows: Select tape driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074-8 Windows: Model select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084-9 Windows: Driver compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094-10 Windows: MMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094-11 3494 configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235-1 ACSLS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295-2 Tivoli Storage Manager SSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1305-3 Tape Library sharing with ACSLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315-4 STK LibAttach configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1355-5 STK Microsoft Windows service entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1355-6 Windows: Update drive driver step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365-7 Windows: Update drive driver step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375-8 Windows: Update drive driver step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375-9 Windows: Update drive driver step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1385-10 Windows: Update drive driver step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1385-11 Windows: Management Console, device information . . . . . . . . . . . . . . . . . . . . . . . 1395-12 Lab overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506-1 Steps for a LAN-free backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616-2 Small file effect on LAN-free backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1637-1 LAN-free environment in our lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1737-2 The Policy Domains screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1747-3 The current policy domains show up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1747-4 The Create Policy Domain General screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1757-5 Create Policy Domain Storage Pools screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1757-6 Create Policy Domain Assign Client Node Now? screen. . . . . . . . . . . . . . . . . . . . . 1767-7 Create Policy Domain, Summary screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1767-8 List of policy domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1777-9 Create Policy Domain Assign Client Node View Clients screen . . . . . . . . . . . . . . . 1777-10 Create Policy Domain, Assign Client Nodes, Select a client node to assign . . . . . . 1787-11 Create Policy Domain Summary after selecting a client to assign. . . . . . . . . . . . . . 1787-12 Tivoli Storage Manager servers and their policy domains . . . . . . . . . . . . . . . . . . . . 180

x Get More Out of Your SAN with IBM Tivoli Storage Manager

7-13 Policy domains for a Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . . . 1807-14 Newly defined node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1817-15 Start the Server-to-Server communication settings . . . . . . . . . . . . . . . . . . . . . . . . . 1827-16 Server-to-Server Settings input screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1827-17 Select node and Enable LAN-free Data Movement . . . . . . . . . . . . . . . . . . . . . . . . . 1837-18 LAN-Free client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1837-19 Verify Data Transfer Settings screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1847-20 Create or Select Storage Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1847-21 Create Storage Agent screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1857-22 Select Storage Pool screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1857-23 Create Drive Paths screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1867-24 Modify Drive Path screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1877-25 Create Drive Paths screen showing assigned device names . . . . . . . . . . . . . . . . . 1877-26 Configure Another Storage Pool? screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1887-27 LAN-free setup complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1887-28 LAN-free backup using a dedicated Storage Agent. . . . . . . . . . . . . . . . . . . . . . . . . 1927-29 Management console showing Tivoli Storage Manager StorageAgent1 expansion 1947-30 Start Storage Agent Initialization wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1947-31 The Welcome to the Storage Agent Initialization Wizard screen . . . . . . . . . . . . . . . 1957-32 The Tivoli Storage Manager Server Account Information screen filled in . . . . . . . . 1957-33 Tivoli Storage Manager Server Communication Information screen completed . . . 1967-34 Storage Agent Account Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1967-35 Completing the Storage Agent Initialization Wizard. . . . . . . . . . . . . . . . . . . . . . . . . 1977-36 The Storage Agent has been initialized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1977-37 Storage Agent service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1977-38 Example of Backup-Archive Client that shows bytes transferred using LAN-free . . 2028-1 The LAN-free to disk setup in our lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2098-2 SAN-attached disks to be accessed for LAN-free backup. . . . . . . . . . . . . . . . . . . . 2108-3 MDC shares the drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2108-4 SANergy managed buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2118-5 SANergy device assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2118-6 Volumes assigned to TONGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2128-7 SANergy shared disks accessed on SENEGAL . . . . . . . . . . . . . . . . . . . . . . . . . . . 2128-8 Servers screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2148-9 Device Classes screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2148-10 Select Device Type screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2148-11 Shared file device class definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2158-12 Create Device Summary screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2168-13 Newly created device class SANDISK, with file library called SANDISK. . . . . . . . . 2168-14 New library is listed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2178-15 Servers screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2178-16 Create Storage Pools screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2178-17 General Storage Pool Settings screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2188-18 Select a Device Class screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2188-19 Create Storage Pool Summary screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2198-20 New storage pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2198-21 Policy Domains screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2228-22 List of policy domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2228-23 Policy Domain General screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2238-24 Specify storage pool for the policy domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2238-25 Create Policy Domain Assign Client Nodes Now? screen. . . . . . . . . . . . . . . . . . . . 2248-26 Create Policy Domain Summary screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2248-27 Create Policy Domain Assign Client nodes screen . . . . . . . . . . . . . . . . . . . . . . . . . 225

Figures xi

8-28 Select client nodes to assign to the policy domain . . . . . . . . . . . . . . . . . . . . . . . . . 2258-29 The Create Policy Domain Summary screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2268-30 The newly created policy domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2268-31 Policy domain properties screen, after selecting Create a Client Node. . . . . . . . . . 2278-32 Create Client Node General screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2288-33 Create Client Node Security screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2288-34 Create Client Summary screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2298-35 The newly created node shows up under the policy domain . . . . . . . . . . . . . . . . . . 2298-36 Enterprise Management screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2308-37 Server-to-Server settings for the Library Manager server . . . . . . . . . . . . . . . . . . . . 2318-38 Servers and Server Groups Defined screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2318-39 Servers screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2318-40 Define Server Welcome screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2328-41 Define Server General screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2328-42 Server-to-server communication screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2338-43 Define a Server Virtual Volume screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2338-44 Define Server Summary screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2348-45 Newly created Storage Agent server appears . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2348-46 LAN-free to disk setup in our lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2368-47 Management console showing TSM StorageAgent1 expansion . . . . . . . . . . . . . . . 2378-48 Start the Storage Agent Initialization wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2378-49 The Welcome to the Storage Agent Initialization Wizard screen . . . . . . . . . . . . . . . 2388-50 The TSM Server Account Information screen filled in . . . . . . . . . . . . . . . . . . . . . . . 2388-51 TSM Server Communication Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2398-52 Storage Agent Account Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2398-53 Completing the Storage Agent Initialization Wizard. . . . . . . . . . . . . . . . . . . . . . . . . 2408-54 The Storage Agent has been initialized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2408-55 Storage Agent service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2408-56 Policy Domains screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2438-57 List of Policy Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2438-58 LANFREE_DISK Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2448-59 Client node used for LAN-free to disk use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2448-60 Enable LAN-free data movement Welcome screen. . . . . . . . . . . . . . . . . . . . . . . . . 2448-61 Verify Data Transfer Settings screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2458-62 Select an existing Storage Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2458-63 Select a Storage Pool screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2468-64 Specify the directories of the SAN-attached disks . . . . . . . . . . . . . . . . . . . . . . . . . . 2478-65 Select whether to configure another Storage Agent. . . . . . . . . . . . . . . . . . . . . . . . . 2478-66 The Enable LAN-free Data Movement Summary screen. . . . . . . . . . . . . . . . . . . . . 2488-67 Completing the setup on the client node overview . . . . . . . . . . . . . . . . . . . . . . . . . 2488-68 The Backup-Archive Detailed Status Report that shows LAN-free bytes . . . . . . . . 2519-1 Library Manager and client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26210-1 Image backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26810-2 Server-free backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26910-3 Specialist main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27310-4 Attention! message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27310-5 Upload completed message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27410-6 Warning! message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27410-7 Enable Data Mover window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27410-8 Fibre Channel selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27510-9 Fibre Channel parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27510-10 Visible devices for Fibre Channel - 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27610-11 Lab server-free setup 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

xii Get More Out of Your SAN with IBM Tivoli Storage Manager

10-12 Lab server-free setup 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27810-13 Device information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28110-14 Device information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28210-15 QUERY STATUS output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28310-16 Enabling server-free backups on the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28510-17 Warning if data mover not available on server-free backup. . . . . . . . . . . . . . . . . . . 28610-18 Server-free image backup in progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28610-19 Server-free backup status report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28710-20 Server-free image backup using command line interface . . . . . . . . . . . . . . . . . . . . 28810-21 Activity log extract showing server-free backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28810-22 Server-free restore selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28910-23 Warning on image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28910-24 Server-free image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29010-25 Server-free image restore using command line interface . . . . . . . . . . . . . . . . . . . . 29010-26 Activity log extract showing server-free restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29111-1 Test environment in the lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29511-2 Machine setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29611-3 Disk setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29911-4 Configuration files of Data Protection for mySAP . . . . . . . . . . . . . . . . . . . . . . . . . . 31811-5 mySAP backup environment: configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . 32811-6 FlashCopy backup scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33011-7 OFFLINE_MIRROR backup method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33111-8 FlashBack restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35711-9 LVM mirroring in mySAP ESS environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37211-10 HACMP mySAP environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37311-11 Use of two target sets as backup generations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37412-1 SAN File System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38112-2 Backing up SAN File System with Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . 38212-3 User files selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38412-4 Restore selective file selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38512-5 Select destination of restore file(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38612-6 Restore files selection for FlashCopy image backup . . . . . . . . . . . . . . . . . . . . . . . . 38612-7 Restore files destination path selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38712-8 Large amounts of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39913-1 General troubleshooting flow chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40313-2 Powercycle a drive in a 3584 library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40613-3 Library and SAN flow-chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40913-4 SAN switch nameserver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41013-5 Operating system and drivers flow-chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41213-6 List tape devices on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41613-7 Windows: Add new Tivoli Storage Manager Server. . . . . . . . . . . . . . . . . . . . . . . . . 420

Figures xiii

xiv Get More Out of Your SAN with IBM Tivoli Storage Manager

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

© Copyright IBM Corp. 2005. All rights reserved. xv

TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

Eserver®Eserver®Redbooks (logo) ™ibm.com®iSeries™pSeries®z/OS®zSeries®AIX 5L™

AIX®Domino®DB2®Enterprise Storage Server®FlashCopy®HACMP™IBM®Lotus®Magstar®

Redbooks™RS/6000®SANergy®Tivoli®TotalStorage®Wave®WebSphere®1-2-3®3090™

The following terms are trademarks of other companies:

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

Other company, product, and service names may be trademarks or service marks of others.

xvi Get More Out of Your SAN with IBM Tivoli Storage Manager

Preface

Storage Area Networks (SANs) have changed the way that data is moved, stored, and managed, allowing you to access your data faster and more efficiently. IBM Tivoli Storage Manager allows you to exploit your SAN infrastructure to potentially provide increased performance, greater flexibility in configurations, and more efficient use of your hardware resources.

This IBM Redbook describes the features of Tivoli Storage Manager, which can be deployed in a SAN. These features include LAN-free backup to tape and disk, tape library sharing, and server-free backup. It also discusses how to use Tivoli Storage Manager with other applications and hardware, such as STK libraries, mySAP™, and IBM TotalStorage® SAN File System. The emphasis of this information is on showing what can be done, why to do it, and how to do it.

This book is written for people who are working for IBM, our clients, vendors, and consulting organizations and who want to understand how Tivoli Storage Manager fits into and enhances a SAN environment, as well as for those wanting detailed assistance in implementing Tivoli Storage Manager using SAN-attached storage.

The team that wrote this redbookThis redbook was produced by a team of specialists from around the world working at the International Technical Support Organization (ITSO), San Jose Center.

Figure 1 The team: Richard, Denver, Michel, and Charlotte

Charlotte Brooks is an IBM Certified IT Specialist and Project Leader for Storage Solutions at the ITSO, San Jose Center. She has 15 years of experience with IBM in the fields of IBM TotalStorage hardware and software, IBM eserver pSeries® servers, and AIX®. She has written 12 Redbooks™ and has developed and taught IBM classes in all areas of storage and storage management. Before joining the ITSO in 2000, she was the Technical Support Manager for Tivoli Storage Manager in the Asia Pacific Region.

© Copyright IBM Corp. 2005. All rights reserved. xvii

Michel Baus is an IT Architect at System Vertrieb Alexander SVA GmbH, an IBM Premier Business Partner in Germany. He has 10 years of experience in the Tivoli Storage and Systems Management topics and is an IBM Certified Deployment Professional for various products. He holds a degree in Sensor Systems Technology from University of Applied Sciences in Karlsruhe, Germany. His areas of expertise include disk and tape subsystems, SAN, pSeries and xSeries. He has been co-author of three previous Redbooks.

Denver Daley is an Advisory IT Specialist within the Data Infrastructure Practice at IBM Global Services, in Canada. He has 8 years of experience with IBM Tivoli Storage Manager and other related storage products. He has worked at IBM for 7 1/2 years. His areas of expertise include consulting, planning and implementation of IBM Tivoli Storage Manager.

Richard Lanicca is a Technical Services Professional at IBM Global Services, Strategic Outsourcing in Switzerland. He has seven years of experience in IT field and has worked at IBM for three years. He holds a degree in telecommunications from University of Applied Sciences in Chur, Switzerland. His areas of expertise include planning, implementation and maintenance of Tivoli Storage products, high-end storage solutions, virtualization and SAN environments.

Thanks to the following people for their contributions to this project:

Emma Jacobs, Deanna PolmITSO, San Jose Center

Gerd Basel, John Marshall, Hans-Joachim Renger, Ernesto Puig Rodriguez, Andreas UhlIBM Boeblingen

Bruce Fong, Jo Lay, Tom Hepner, Claire RankinIBM San Jose

Randy Larson IBM Winston Salem

Bill Baxter, Janet Bolton, Rob Elder, Harry Husfelt, David Kosick, Kathy Mitton, Diem Nguyen, Charlie Nichols, Rosa Plaza, Harley PuckettIBM Tucson

Amit SinhaStorageTek

Christian GrafSAP

Become a published authorJoin us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners or customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

xviii Get More Out of Your SAN with IBM Tivoli Storage Manager

http://www.redbooks.ibm.com/residencies.html

http://www.redbooks.ibm.com/residencies.html

Comments welcomeYour comments are important to us!

We want our Redbooks to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways:

� Use the online Contact us review redbook form found at:

ibm.com/redbooks

� Send your comments in an email to:

[email protected]

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. QXXE Building 80-E2650 Harry RoadSan Jose, California 95120-6099

Preface xix



http://www.redbooks.ibm.com/contacts.html

xx Get More Out of Your SAN with IBM Tivoli Storage Manager

Chapter 1. Introduction to SANs and IBM Tivoli Storage Manager

This chapter discusses the following topics:

� Overview of Storage Area Network� Introduction to Tivoli Storage Manager� Tivoli Storage Manager SAN functions� Tivoli Storage Manager V5.3 latest SAN functions� Tivoli Storage Manager SAN functions and products

1

© Copyright IBM Corp. 2005. All rights reserved. 1

1.1 Overview of Storage Area NetworkA Storage Area Network (SAN) is a high speed network that allows computer systems, applications, and storage devices to be directly interconnected. A SAN allows businesses to consolidate computer systems, applications, and storages to reduce cost and increase availability, accessibility, and reliability.

Figure 1-1 illustrates the common components in a SAN configuration. In a SAN, Host Bus Adapters (HBAs) are installed on each system (server) and are connected to the shared storage devices via a SAN fabric of switches, directors, bridges, or hubs.

Figure 1-1 Common SAN components

A SAN configuration allows for improved methods to transfer data when compared with the traditional LAN infrastructure. Improvements include:

� Improved performance and data transfer flexibility

Transferring data over the SAN is faster because Fibre Channel (at 2 or 4 Gbps) is the typical means that is used for connection. SAN is also faster because the data transfer can bypass the bottleneck that can be experienced on traditional LANs.

The SAN allows data to be transferred from computers to other computers, from computers to storage devices, or from storage devices to other storage devices.

� Improved availability

SAN multiple data paths allow for better accessibility and reliability.

� Support for open system connectivity

Heterogeneous operating system platforms can share the same storage devices, which allows for better use of storage and reductions in storage costs.

� Highly scalable

SAN components, such as additional storage devices, can be added easily to meet growing needs.

Fibre Channel SANs are most commonly used. However, IP SANs are becoming popular. Some drawbacks of Fibre Channel SANs include its expensive costs and its complicated implementation, especially when businesses do not possess the necessary expertise.

Shared Storage Devices

Heterogeneous Servers

Bridge

Hub

SwitchDirector

zSeries

Windows

iSeries

UNIX

LINUX

pSeries

Tape

ESS

FastT SSA

JBOD

2 Get More Out of Your SAN with IBM Tivoli Storage Manager

For more detailed information about SAN, refer to Introduction to Storage Area Network, SG24-5470.

1.2 Introduction to Tivoli Storage ManagerTivoli Storage Manager is an enterprise-wide storage management and data recovery solution. It offers automated storage management services to a variety of operating systems and applications and multiple options for protecting data. Backup types include file system type backups, archives, space managed file system, data protection for application data, and more. Tivoli Storage Manager uses and takes advantage of many disk and tape devices that are available today. It consists of the following components:

� The server

The server is used to manage the storage services and includes the database and recovery log. It also manages and stores data that pertains to such things as, policy information, storage devices, client nodes, and scheduling.

The server is managed via the command line interface or the Administration Center.

� The client

When installed, the client software allows the server to protect and manage a machine’s data. The types of client software that are available include the backup and archive client, data protection for applications, application program interface (API), and use of Network Data Management Protocol (NDMP) for network attached storage (NAS) file servers

� Tivoli Storage Manager for Space Management

Used to manage space on workstations by migrating aged data to the Tivoli Storage Manager server automatically, based on criterias that are set.

� Storage Agent

Used in a LAN-free client configuration to allow client data to be transferred to the Tivoli Storage Manager server over a SAN path to tape storage or disk storage (using SANergy).

Chapter 1. Introduction to SANs and IBM Tivoli Storage Manager 3

1.3 Tivoli Storage Manager SAN functionsThe rapid advancement of SAN technology in recent years has corresponded in increasing adoption of SAN implementations. In keeping pace with the requirements to support SANs, Tivoli Storage Manager has been enhanced continually to provide customers with desired functions to manage their storage. Tivoli Storage Manager clients and servers can share and exploit SAN-attached devices to allow a consolidated and improved use of storage.

The currently available Tivoli Storage Manager SAN functions are:

� LAN-free backup to tape

With a LAN-free backups to tape, a SAN-attached client machine can send data directly to a SAN-attached tape device. This is made possible by the use of the Storage Agent. The Storage Agent acts as a miniature version of the Tivoli Storage Manager server and has the capability of writing or reading a client’s data to or from the SAN-attached tape device. The Storage Agent is installed on a SAN-attached Tivoli Storage Manager client machine that sends data directly or, optionally, acts as a proxy for LAN-free transfer from a LAN-attached system. With the use of the Storage Agent, data transfer workload is off-loaded from the LAN. Because the Storage Agent performs the direct writes and reads, there is also less work for the Tivoli Storage Manager server.

Figure 1-2 illustrates the data flow of a traditional LAN-based backup. The Tivoli Storage Manager backup and archive client initiates the backup, and the data is sent over the LAN via the Tivoli Storage Manager server to an attached storage device, disk or tape.

Figure 1-2 Traditional LAN based backup

Figure 1-3 on page 5 shows the data flow with LAN-free backup to tape. The Tivoli Storage Manager backup and archive client initiates the backup as before. The Storage Agent communicates with the Tivoli Storage Manager server to send metadata about the backup and to coordinate the use of the SAN-attached tape library. It then sends the data over the SAN directly to that tape library. You can find more details about LAN-free tape backup in Chapter 7, “LAN-free backup to tape” on page 171.

Client

LAN

Client Data

Tape Library

Disk STG Pool

Tivoli Storage Manager Server


Figure 1-3 LAN-free tape and disk backup

� LAN-free backup to disk

LAN-free backup to disk works similarly to LAN-free backup to tape, except that the data is written directly to or read from a SAN-attached disk device rather than a tape library. This configuration requires the use of the Tivoli SANergy file sharing software.

Figure 1-3 also shows the data flow with LAN-free backup to disk. The Tivoli Storage Manager backup and archive client initiates the backup as before. The Storage Agent communicates with the Tivoli Storage Manager server to send metadata about the backup and to coordinate the use of the SAN-attached disk device. It then sends the data over the SAN directly to the disk device. In this case, the disk emulates a sequential device and is known as a file library. You can find more details about LAN-free disk backup in Chapter 8, “LAN-free backup to disk” on page 207.

� Server-free backup

With server-free backup, client data is written from a SAN-attached disk device directly to a SAN-attached tape device. This is made possible through use of data movers, such as a SAN Data Gateway (SDG), that uses SCSI-3 extended copy functions to actually copy the data. With the data movement occurring from the SAN-attached disk device directly to the SAN-attached tape device, workload is reduced on both the Tivoli Storage Manager client and server.

Figure 1-4 on page 6 shows the data movement in a server-free setup. You can find more details about server-free backup in Chapter 10, “Server-free data movement” on page 267.

Tivoli Storage Manager Client and Storage Agent

SAN

Library ControlClient Data

Library ControlClient Metadata

LAN

Tape LibraryFile Library



Figure 1-4 Server-free data movement

� FlashCopy (split mirror) backups via the SAN

FlashCopy backups use a disk-based instant copy function, to copy a production host’s data to a less critical host. This less critical host then performs the backup, over the SAN, to the Tivoli Storage Manager server. This removes any performance impact of the backup from the production server.

This method is used by Data Protection for IBM Enterprise Storage Server® (ESS). With business’ critical databases residing on an ESS, Data Protection for ESS uses the ESS FlashCopy function to off-load the transfer of backup data from the production database server to a backup (secondary) database server. This method eliminates nearly all backup related performance impact from the production database server. Data Proctection for ESS is available for DB2® ,Oracle™, and mySAP databases.

Figure 1-5 on page 7 shows the data movement in FlashCopy as used with Data Protection for ESS. The production and backup server (system) both access disk space on the ESS. FlashCopy is used to create a copy of the production server database to the backup server. The Tivoli Storage Manager Backup-Archive Client and Storage Agent can then be used to perform a LAN-free backup of the database directly to the tape library. You can find an example of FlashCopy backup in Chapter 11, “Tivoli Storage Manager for Hardware — Data Protection for ESS for mySAP™” on page 293.

Tivoli Storage ManagerServer

LAN

Tivoli Storage Manager Servermanagedtape library

SAN

Tivoli Storage Manager

Client

LVSA

Data Mover

Control InformationData Flow


Figure 1-5 FlashCopy backup via a SAN

� Tape library sharing

Library sharing in a SAN is very popular, primarily because it exploits the performance and reliability gains that are associated with the use of a SAN.

There are three primary components in a typical tape library sharing environment:

– A Tivoli Storage Manager server that acts as the tape Library Manager.– One or more additional Tivoli Storage Manager servers that act as tape Library

Clients.– The tape library to be shared.

With library sharing, the Library Manager and Library Client(s) communicate with each other via server-to-server communication to coordinate the use of an automated tape library. The Library Manager controls all medium changer related functions, such as tape mounts, tape dismounts, volume ownership, and library inventory. When a Library Client needs to use the tape library for a backup or restore, it sends a request to the Library Manager, to mount a tape inside the tape library. When the tape is loaded, the Library Client accesses the media that is inside the tape drive to execute the necessary write or read. Figure 1-6 on page 8 shows a typical library sharing setup with two Tivoli Storage Manager servers.

In the case of LAN-free backups, the Storage Agent performs the tasks of a Library Client.

Tivoli Storage Manager provides library sharing for most SAN-attached tape libraries, as well as special configurations and features for IBM TotalStorage 3494 libraries and ACSLS-capable libraries from StorageTek. You can find details about these various library sharing environments in Chapter 3, “SCSI tape library sharing” on page 43, Chapter 4, “IBM 3494 tape library sharing” on page 93, and Chapter 5, “Library sharing with the ACSLS Manager” on page 127.

Backup

SANSAN

Tape Library

Restore

Client &Storage Agent installed

ProductionSystem

IBM EnterpriseStorage Server


backupBackupSystem

backup

restorerestore


Figure 1-6 Typical tape library sharing configuration

1.4 Tivoli Storage Manager V5.3 latest SAN functionsImprovements have been made to some key SAN-related components with the release of Tivoli Storage Manager V5.3. These improvements simplify the configuration of Tivoli Storage Manager in a SAN environment and maintenance of the setup.

The latest Tivoli Storage Manager SAN-related functions are:

� SAN device discovery, QUERY SAN command (supported on AIX, Linux®, and Solaris)

This server command displays information about SAN-attached devices. The output from this query can then be used to assist in defining a LAN-free client. This command was previously supported on Windows and is now available for AIX, Linux, and Solaris Tivoli Storage Manager servers. For more details about the QUERY SAN command, see Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.

� VALIDATE LANFREE command

This server command replaces the previously unsupported SHOW LANFREE command that was available in Tivoli Storage Manager V5.2. After a LAN-free client has been configured, this command can be used to verify the client, Storage Agent, and server definitions. The output shows any valid LAN-free capable definitions that are associating with a specific client and Storage Agent. The output also lists any invalid LAN-free definitions.

For more details about the VALIDATE LANFREE command, see Chapter 7, “LAN-free backup to tape” on page 171 and Chapter 8, “LAN-free backup to disk” on page 207.

� Accurate SAN device mapping

In a SAN environment, it is not uncommon for device names to change after the initial configuration is completed. This change can happen for different reasons, for example, hardware changes or bus resets. Such name changes can cause failed or improperly

Library ClientServer

Library ManagerServer

SAN

Data Flow

Library ControlData Flow

LibraryControl

LAN

Tape Library


defined paths, which can ultimately impact storage device operations. Tivoli Storage Manager assists in recovering from device name changes with the new server option SANDISCOVERY. For this feature to work, the device’s serial number should be used when defining each device, because the server relies on the serial number to confirm the device’s identity.

For further details about accurate SAN device mapping, see Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.

� ACSLS library support enhancements

ACSLS libraries can be shared across Tivoli Storage Manager servers in the same way as SCSI libraries. There is also support for LAN-free data movement using libraries that are controlled by StorageTek’s ACSLS. With this support, it is now optional to use third-party library manager products, such as Gresham’s EDT-DistribuTAPE, to work with these libraries.

For further details about ACSLS library support enhancements, see Chapter 5, “Library sharing with the ACSLS Manager” on page 127.

� LANFREETCPSERVERADDRESS client option

The LANFREETCPSERVERADDRESS option is used to specify the TCP/IP address of a Storage Agent machine when the client and the Storage Agent are not on the same system. In this way, a single Storage Agent can proxy LAN-free data movement for one or more LAN-attached Tivoli Storage Manager clients.

For further details about the LANFREETCPSERVERADDRESS, see Chapter 7, “LAN-free backup to tape” on page 171.

� Storage Agent and library sharing failover

Support for AIX HACMP failover has been enhanced to include failover in a Storage Agent and library sharing environment. Because the Tivoli Storage Manager server can determine which devices need to be reset during the start of the server or Storage Agent, a target reset is performed on only those devices to make them available.

For more information about Storage Agent and library sharing failover, see IBM Tivoli Storage Manager 5.3 Reference Guide for AIX, GC32-0768 and the IBM Redbook IBM Tivoli Storage Manager in a Clustered Environment, SG24-6679.

� Increased block size for writing to tape

Performance when writing to tape has been enhanced by increasing the maximum transfer length for all HBAs.

� Multi-session no-query restore from LAN-free path

If during a no-query restore, a volume is mounted on a shared device that can be accessed by the Storage Agent, then the server sends the data to the Storage Agent and the Storage Agent sends the data to the client to complete the LAN-free restore. Otherwise, if the volume cannot be mounted on a shared device to which the storage agent has access, the server sends the restore data directly to the client. The client then initiates additional sessions for the Storage Agent and server. In the case of the Storage Agent, these additional sessions are used to access volumes that are LAN-free enabled. The additional sessions to the server are used to access volumes that are not LAN-free enabled.


1.5 Tivoli Storage Manager SAN functions and productsThere are specific software components that are necessary to enable and support each Tivoli Storage Manager SAN function. Table 1-1 shows which products are required to support and enable each specific SAN related function.

Table 1-1 Tivoli Storage Manager products and functions

Tivoli Storage Manager products SAN functions

Tivoli Storage Manager Extended Edition Tape library sharing between multiple Tivoli Storage Manager serversServer-free backups and restores using Data Protection for NAS appliances through NDMP

Tivoli Storage Manager for Storage Area Network LAN-free backups and restoresLibrary sharingServer-free backups and restores

Tivoli Storage Manager for (WebSphere®) Application Servers LAN-free backups and restores

Tivoli Storage Manager for Enterprise Resource Planning (ERP) LAN-free backups and restores

Tivoli Storage Manager for Hardware FlashCopy over SAN

Tivoli Storage Manager for Mail LAN-free backups and restores

Tivoli Storage Manager for Space Management LAN-free migrations and recalls


Chapter 2. Tape library sharing planning

This chapter describes general considerations for planning tape library sharing with Tivoli Storage Manager and discusses the following topics:

� Library sharing overview� Components of library sharing� Benefits of tape library sharing with Tivoli Storage Manager� Requirements for tape library sharing� Tasks with Tivoli Storage Manager library sharing� Moving to a dedicated Tivoli Storage Manager Library Manager� Command differences in a library sharing environment� Interactions between Library Manager and Library Client

2


2.1 Library sharing overviewThere are two basic types of tape library sharing: library partitioning and library sharing.

2.1.1 Library partitioningIn library partitioning, the library is attached to two or more servers using different connections (Figure 2-1). Logically, the library must be split into partitions, each with their own drives and library slot ranges. Thus, each server only uses a small part of the library and is unable to access drives other than those that were defined to it. When this setup uses two host machines, it is often referred to as a twin-tail configuration. However, this method also applies to configurations with more than two hosts, as shown in Figure 2-1. When using library partitioning, the drives are not shared — only the library robotics are shared. This method is used for advanced security requirements, because it completely separates the drives, the storage slots, and the tapes within the library. Not all libraries support library partitioning.

Figure 2-1 Library partitioning into multiple logical libraries

Attention: All applications that use a partitioned library are affected if you change the partitioning at a later date.

Tip: The second generation of multipath architecture, also called Advanced Library Management System (ALMS), does not have the requirement to partition the library using static rules and contiguous resources. ALMS virtualizes the affinity to physical resources. ALMS is supported on the IBM 3584 tape library.

Storage Slots60 used20 free

Library controller

Logical Library 2

Logical Library 1

Logical Library 3



Host A

Drive

Drive

Drive

Drive

Host B

Host CDrive

Drive

Drive

Drive


2.1.2 Library sharingAs defined in the Tivoli Storage Manager library sharing implementation, library sharing means that all hosts attached to the library over a SAN fabric can share the entire library (Figure 2-2). This means that all hosts have access to all library slots and all library drives, but only one host has control of all drives and tapes. This host is known as the Tivoli Storage Manager Library Manager. All other hosts using the shared library must send a request to the Tivoli Storage Manager Library Manager for every tape operation. These hosts are referred to as the Tivoli Storage Manager Library Clients. The Library Manager and all the Library Clients all have Tivoli Storage Manager server code installed on them. So, this kind of library sharing is applicable to Tivoli Storage Manager configurations only.

Each tape in the library has a status of either scratch or private. A scratch tape is not assigned to any Tivoli Storage Manager server there is no data on it. A private tape has been assigned to a Tivoli Storage Manager server (Tivoli Storage Manager Library Client or Tivoli Storage Manager Library Manager). After a tape becomes private by the assignment, only this Tivoli Storage Manager server can access the tape; however the Library Manager is able to access all the tapes in the library. Tape volumes remain private once assigned, so that each Tivoli Storage Manager server (Library Client) sees only the volumes that have been assigned to it. When a Tivoli Storage Manager server needs a new tape volume, it can obtain them from the common scratch tape pool.

Figure 2-2 Library sharing

Library controller


Tivoli Storage ManagerLibraryManager

Tivoli Storage ManagerLibraryClients

Drive

Drive

Drive

Drive

Drive

Drive

Drive

Drive

SAN

Chapter 2. Tape library sharing planning 13

2.2 Components of library sharingThis section discusses the basic terms used for Tivoli Storage Manager library sharing configuration.

2.2.1 Library ManagerOne Tivoli Storage Manager server performs the function of Library Manager, whose task is to control the library physically. The Library Manager:

� Performs all communication with the library and serializes the access to the tape drives, so that only one Tivoli Storage Manager server is using a tape drive at a time.

� Checks volumes in and out of the library, and maintains the library inventory table for that library. This table keeps track of which tape belongs to which Library Client. Only the Library Manager knows all the volumes in the library (library volumes).

� Controls the pool of scratch tapes and allocates them to Library Clients as needed.

� Initializes the tape library during the Tivoli Storage Manager start process.

The Tivoli Storage Manager Library Manager can also use the library for normal Tivoli Storage Manager operations, without actually being a Tivoli Storage Manager Library Client. That is, the Tivoli Storage Manager Library Manager does not have to be configured as a Tivoli Storage Manager Library Client in order to use the library for Tivoli Storage Manager.

2.2.2 Library ClientThe Tivoli Storage Manager Library Client communicates with the Tivoli Storage Manager Library Manager for tape library operations on the physical hardware using Tivoli Storage Manager server-to-server communication. The Tivoli Storage Manager Library Client sends any tape device-related requests (for example, mount a particular volume or acquire a scratch volume) to the Tivoli Storage Manager Library Manager and then reads or writes data on the tape volume in the tape drive to which it was given access. After using the volume, the Tivoli Storage Manager Library Client tells the Library Manager that the read or write process is complete and that the drive is available for use by the Library Manager or other Library Clients. The Tivoli Storage Manager Library Client knows about only volumes it has been assigned, not all library volumes.

2.2.3 Library medium changer and library control

The library medium changer (also known as the library controller) gives the Tivoli Storage Manager Library Manager access to the functions that are required for basic tape operations such as backup and restore and medium changer operations such as mount and demount tape cartridges, as well as the advanced functions that are needed by full tape management systems. Depending on the library type, additional software might be required to use the library with the Tivoli Storage Manager server (for example, for the IBM 3494 tape library). Additional software requirements are discussed in Chapter 3, “SCSI tape library sharing” on page 43, Chapter 4, “IBM 3494 tape library sharing” on page 93, and Chapter 5, “Library sharing with the ACSLS Manager” on page 127.


Table 2-1 shows the library controller device special file for SCSI attached libraries. This special file is used when defining a library on the Library Manager.

Table 2-1 .Device special files for the library controller for SCSI tape libraries

The examples in this redbook use the IBM tape device driver for all IBM drives and the device driver that is supplied with Tivoli Storage Manager for all drives other than IBM drives. The library controller needs to be configured only on the Library Manager, not on the Library Clients.

2.2.4 Library drivesTo use a library drive with the Tivoli Storage Manager server, you must use the correct driver for the drive. The examples in this redbook use the IBM tape device driver for all IBM drives and the device driver that is supplied with Tivoli Storage Manager for all drives other than IBM drives.

You can download the latest version of the IBM tape device driver from:

ftp://ftp.software.ibm.com/storage/devdrvr/

Table 2-2 shows the drive device special files to use in the Tivoli Storage Manager drive path definition.

Table 2-2 Drive device file for SCSI tape libraries

2.2.5 Library control path failoverThe control path is the path to the library controller or medium changer. The library controller is required for using a tape library. Without the library controller, you cannot operate the library. Therefore, the library controller can be a single point of failure if there is only one path from the application to the library controller. To mitigate this failure, some libraries provide a library control path failover function. Figure 2-3 on page 16 shows an example with two physical paths to the library controller.

If the primary path is not available, you can switch to the alternate path. Depending on the device driver, the switch can be manual or automatic. Manual means there are two or more devices in the operating system for the same library controller. If one is not available, the

OS IBM tape device driver (IBM drives)

Tivoli Storage Manager device driver (drives other than IBM drives)

IBM AIX /dev/smcX /dev/lbX

Linux /dev/IBMchangerX /dev/lbX

SUN Solaris /dev/rmt/Xsmc /dev/rmt/Xlb

Microsoft Windows \\.\ChangerX lbX.X.X.X

OS IBM tape device driver(IBM drives)

Tivoli Storage Manager device driver (drives other than IBM drives)

IBM AIX /dev/rmtX /dev/mtX

Linux /dev/IBMtapeX /dev/mtX

SUN Solaris /dev/rmt/Xst /dev/rmt/Xmt

Microsoft Windows \\.\TapeX mtX.X.X.X



application switches to use the other device. Automatic means that the device driver switches automatically to the alternate path and that the application can use still the same device.

Figure 2-3 SCSI library control path failover

2.2.6 Data path failoverThe data path is the path to the actual library drive. It is common to use multipath connections for the data path. A multipath connection consists of two HBAs that are both zoned to a single port on an FC tape drive. Both HBAs are connected to the same SAN fabric (Figure 2-4 on page 17). This connection provides alternate paths to the same tape drive for redundancy if one path from an HBA to the drive fails. When the operating system starts, each HBA detects a drive, and two logical devices are configured (for example, in IBM AIX, devices rmt0 and rmt1 are configured). Each logical device is a physical path to the same tape drive. A backup and restore application can open and use only one logical device at a time (either rmt0 or rmt1), because they represent the same physical device. Without the IBM tape device driver alternate pathing support, if an application opens rmt0 and a permanent path error occurs (for example, because of an HBA or cable failure), then the application fails. You can initiate manual failover by updating the application to use the alternate logical device (rmt1).

SAN Fabric

1

HBA1

HBA2

Tape Library

Drive1

Drive2

SAN Fabric

2

Library controller

Device driver

Application

HOST

Primary path Alternate path


Figure 2-4 Data path failover with one SAN fabric

To enhance availability, some drives provide two FC ports (for example, the IBM TotalStorage Enterprise Tape System 3590 or 3592). In this case, two HBAs are used on the host. The first HBA is connected to port 0 of the drive, and the second HBA is connected to port 1 of the drive (Figure 2-5 on page 18). This connection provides two physical paths to the same tape drive for redundancy in the event of failure. Separate fabrics and two physical paths provide a higher degree of redundancy than the configuration that is shown in Figure 2-4.

When the operating system starts, each HBA detects a drive, and two logical devices are configured (for example, in IBM AIX, devices rmt0 and rmt1 are configured). Each logical device is a physical path to the same tape drive. A backup and restore application can open and use only one logical device at a time (either rmt0 or rmt1), because they represent the same physical device. Without the IBM tape device driver alternate pathing support, if an application opens rmt0 and a permanent path error occurs (for example, because of an HBA or cable failure), the application fails. It is possible to initiate manual failover by updating the application on the alternate logical device (rmt1).

SAN

HBA1

HBA2

Drive

Library controller

Device driver

Application

HOST


Tape Library


Figure 2-5 Data path failover with two SAN fabrics

2.3 Benefits of tape library sharing with Tivoli Storage ManagerBy sharing libraries among several Tivoli Storage Manager servers, higher overall tape drive usage should be achieved than in cases where every server has its own library. Tape library sharing can help reduce costs by reducing the total overall number of tape drives that are required. Before looking at how to improve the drive usage, you must decide which type of library sharing you will use.

Tivoli Storage Manager servers using non-shared (dedicated) tape libraries typically have a lower use rate for the tape devices. This lower use rate is because the required number of tape devices is usually driven by peak requirements rather than the required average need. A typical situation is where a restore must take place without disrupting server maintenance processes. This situation automatically requires three tape devices (two for server processes — for example, storage pool backups — and one for the restore session). If multiple concurrent restore sessions are required, this number increases even more. Another situation is where multiple concurrent backup sessions require a direct tape drive connection. You would need at least one drive for each of these sessions.

However, if the library is shared between different servers, you can reduce the total number of tape devices. This reduction is because usage becomes more distributed over time and peak requirements approach the average usage. For example, if you have two servers, each with the requirement that server maintenance operations and restore sessions must run concurrently, in a non-shared environment you would need at least three drives per library. In a shared environment, however, you could reduce this number first by reserving only one drive for restore. Therefore, you would need only five total drives. You could further reduce the number of drives that are required by staging the server maintenance processes so that they do not run at the same time. As a result, the two drives that are required for these

SAN Fabric

1

HBA1

HBA2

Drive

SAN Fabric

2

Library controller

Device driver

Application

HOST


Tape Library


operations could be shared among the servers. The resulting number of tape devices for the library would then be down to three drives instead of the original six. This example is just for illustration purposes. In real life, things might not be so cut and dried; however, the same principles apply.

Thus, library sharing gives you the flexibility to grow with the environment. So, if the requirement on one Tivoli Storage Manager server increases more than planned, all the connected servers share the library dynamically and can take advantage of the new capacity.

2.4 Requirements for tape library sharingThe requirements for tape library sharing are:

� Tivoli Storage Manager server-to-server communication must be configured between the Tivoli Storage Manager Library Manager and Tivoli Storage Manager Library Client.

� The library must be connected to the SAN to share the drives.

� Tivoli Storage Manager must support the tape library. You can find the list of supported libraries and drives at:

For IBM AIX, Microsoft Windows, HP UNIX®, and SUN Solaris:

http://www-306.ibm.com/software/sysmgmt/products/support/IBM_TSM_Supported_Devices_for_AIXHPSUNWIN.html

For Linux:

http://www-306.ibm.com/software/sysmgmt/products/support/IBM_TSM_Supported_Devices_for_Linux.html

� The Tivoli Storage Manager Library Manager level has equal or higher Tivoli Storage Manager server when compared to the Library Clients.

� The Tivoli Storage Manager Extended Edition must be licensed.

� Mixed Tivoli Storage Manager server levels are supported in the library sharing environment, as long as the Library Manager is at the same or a higher level than all the Library Clients.

For detailed setup instructions for various library sharing environments see Chapter 3, “SCSI tape library sharing” on page 43, Chapter 4, “IBM 3494 tape library sharing” on page 93, and Chapter 5, “Library sharing with the ACSLS Manager” on page 127.

The remainder of this chapter assumes that you have configured your library sharing environment and are familiar with its basic function.

Note: We recommend that you maintain consistent Tivoli Storage Manager server levels on the Tivoli Storage Manager Library Manager and all Tivoli Storage Manager Library Clients to simplify support issues.




2.5 Tasks with Tivoli Storage Manager library sharingThis section describes some tasks that are associated with Tivoli Storage Manager library sharing.

2.5.1 Library Manager as a single Tivoli Storage Manager Server without Tivoli Storage Manager client data

In case of a disaster, you need to be able to restore the Library Manager function quickly and simply, because you cannot start the Library Client restores until the Library Manager is working. To achieve this restore, we recommend using a dedicated Tivoli Storage Manager server instance used only for the Tivoli Storage Manager Library Manager. You can then install a separate Tivoli Storage Manager server instance to be a Library Client on this host if required (as shown in Figure 2-6). Then, if there is a multisystem failure, you can first restore the Library Manager, which would be relatively fast because there is no client data to restore. The Library Manager would then be available to provide shared library function to the Library Clients, which you can restore in order of priority.

Figure 2-6 Library Manager instance

2.5.2 Tivoli Storage Manager server maintenance planningIn a large Tivoli Storage Manager environment, you can use scheduling to spread the Tivoli Storage Manager housekeeping actions (such as Tivoli Storage Manager database backup, migration, and reclamation) equally over time. For example, if there are four drives that are shared by six Tivoli Storage Manager Library Clients, you can schedule the first three Tivoli Storage Manager database backups followed by the remaining three Tivoli Storage Manager database backups to always leave one drive free for Tivoli Storage Manager client data restores.

TSM_1Library Manager

TSM_2Library Client 1

Host ATSM_3

Library Client 2Host B

HostA HostB


2.5.3 Library drive resetWhenever the Tivoli Storage Manager server uses a tape drive or medium changer device, it issues a SCSI RESERVE command to the device. Every time a volume is mounted in a tape drive and when it is in the IDLE status, the SCSI reservation is still present. After the Tivoli Storage Manager Server finishes using a tape drive or medium changer device, it releases the SCSI reservation.

In the library definition, you can specify the RESETDRIVES option with the DEFINE LIBRARY command. This option specifies whether the server performs a target reset when the server is restarted or when a Library Client or storage agent reconnection is established. This parameter only applies to SCSI, 3494, Manual, and ACSLS type libraries. For this parameter, you can set the following:

� RESETDrives=Yes

Specifies to perform the target reset. This is the default for SCSI, 3494, Manual, and ACSLS libraries defined with SHARED=YES.

� RESETDrives=No

Specifies to not perform the target reset. This is the default for SCSI, 3494, Manual, and ACSLS libraries defined with SHARED=NO.

If the RESETDRIVES option is set to YES for a library, then the reset is performed by the Library Manager for the library and all drives that are defined to it. If a library is defined as SHARED, the RESETDRIVES option defaults to YES for the library automatically. Otherwise, you can run the UPDATE LIBRARY command with RESETDRIVES set to YES.

Table 2-3 shows the Tivoli Storage Manager server actions during initialization of the library.

Table 2-3 Tivoli Storage Manager Library actions during start

Note: If you are using HACMP and migrating to Tivoli Storage Manager V5.3 (from any previous version), you need to convert to the new startserver script. Device resets are done by the server during initialization of the library.

Previous Drive allocation Tivoli Storage Manager Library Manager action

Library Manager or not allocated Check for outstanding reserve and issue SCSI target reset if one exists

Library Client or Storage Agent Wait for session initialization� If reconnection, do nothing� If first connection, check for outstanding reserve and issue

SCSI target reset if one exists

Important: Device resets are done by the Tivoli Storage Manager server during initialization of the library.


2.5.4 Drive allocationWe recommend that you define paths to all the drives in a shared library on all Tivoli Storage Manager Library Clients. If you want to restrict usage by some Library Clients, you can use the MOUNTLIMIT parameter in the device class definition. Using the MOUNTLIMIT parameter increases the chances that a request for a drive from that Library Client can be fulfilled, because the Library Manager can allocate any of the drives to the Library Client. If you restrict the drives, you are more likely to be in a situation where a drive request has to wait for a free drive, because you limited the set of drives that are available for selection. Example 2-1 shows the use of the MOUNTLIMIT parameter in the DEFINE DEVCLASS command.

Example 2-1 Define device class with the MOUNTLIMIT is set

tsm: AZOV_1>DEFINE DEVCLASS LTO LIBRARY=3582 DEVTYPE=LTO MOUNTLIMIT=1ANR2203I Device class LTO defined.

2.5.5 Deleting a library volume on the Library ManagerIn some cases, it is possible that the Library Manager shows that a volume is used by a Library Client, when in reality, it is not. For example, if you remove an unused Tivoli Storage Manager Library Client without deleting its associated database backup volumes, to clean up the volume table on the Library Manager, you do the following:

1. Find all library volumes that are assigned to the Tivoli Storage Manager Library Client.2. Delete all volume history entries for this library volume.3. Update the status of this library volume.

Finding all library volumes that are assigned to the Tivoli Storage Manager Library Client

You use the QUERY LIBVOLUMES command on the Library Manager to display the library volumes, as shown in Example 2-2. You can check the Owner column to see which library volumes are associated with the particular Library Client.

Example 2-2 Query library volumes on the Library Manager

tsm: POCO_1>q libv

Library Name Volume Name Status Owner Last Use Home Device Element Type------------ ----------- ---------- ---------- --------- ------- ------3494 J11771 Scratch3494 J11772 Private SCAMP_1 DbBackup3494 J11773 Scratch3494 J11774 ScratchACSLS CB5382 Scratch

Tip: You can set MOUNTLIMIT to 0 to prevent the access to the storagepool or library. You might set this to disable temporarily access to a library that needs to be offline for maintenance.


Alternatively, you can use the Tivoli Storage Manager SQL syntax to find library volumes, as shown in Example 2-3.

Example 2-3 Tivoli Storage Manager SQL command on the Library Manager

tsm: POCO_1>SELECT Library_Name, Volume_Name, Status, Owner from libvolumes where owner='SCAMP_1'

LIBRARY_NAME VOLUME_NAME STATUS OWNER------------------ ------------------ ---------- ------------------3494 J11772 Private SCAMP_1

Deleting the volume history entry for the library volumeAll volumes that are used on the Library Client have an entry in the volume history on the Library Manager. The type is REMOTE in the volume history. First, you have to show all information about this volume. Then, you can delete them.

To delete the volume history, use these commands:

QUERY VOLHISTORY TYPE=RemoteDELETE VOLHISTORY TYPE=Remote VOLUME=VolumeName TODATE=mm/dd/yyyy FORCE=YES

Example 2-4 and Example 2-5 show examples of the output from these commands.

Example 2-4 Query the volume history

tsm: POCO_1>QUERY VOLHISTORY TYPE=Remote

Date/Time: 24.03.2005 12:20:08 Volume Type: REMOTE Backup Series:Backup Operation: Volume Seq: Device Class: 3494_3592C Volume Name: J11772 Volume Location: SCAMP_1 Command:

Example 2-5 Delete a volume in the volume history

tsm: POCO_1>DELETE VOLHISTORY t=remote vol=J11772 todate=03/24/2005 force=yes

Do you wish to proceed? (Yes (Y)/No (N)) yANR2467I DELETE VOLHISTORY: 1 sequential volume history entries were successfully deleted.

Attention: Confirm that you have the right volume name before deleting it!


Updating the status of this library volumeAfter using the DELETE VOLHISTORY command, the Tivoli Storage Manager library volume table is the same as before (as shown in Example 2-6).

Example 2-6 Query library volumes

tsm: POCO_1>query libvolumes

Library Name Volume Name Status Owner Last Use Home Device Element Type------------ ----------- ---------- ---------- --------- ------- ------3494 J11771 Scratch3494 J11772 Private SCAMP_1 DbBackup3494 J11773 Scratch3494 J11774 ScratchACSLS CB5382 Scratch

To update the library volume table on the Tivoli Storage Manager Library Manager, you use the UPDATE LIBVOLUME command, as shown in Example 2-7.

Example 2-7 Update a library volume

tsm: POCO_1>UPDATE LIBVOLUME 3494 J11772 STATUS=Scratch OWNER=''ANR8445I Volume J11772 in library 3494 updated.

tsm: POCO_1>Q LIBV

Library Name Volume Name Status Owner Last Use Home Device Element Type------------ ----------- ---------- ---------- --------- ------- ------3494 J11771 Scratch3494 J11772 Scratch3494 J11773 Scratch3494 J11774 ScratchACSLS CB5382 Scratch

The library volume is now scratch and can be reused for other purposes.

2.6 Moving to a dedicated Tivoli Storage Manager Library Manager

This example illustrates how to move the Tivoli Storage Manager Library Manager to a new Tivoli Storage Manager server instance where it functions only as the Library Manager (that is, this Tivoli Storage Manager server instance will not have any Tivoli Storage Manager clients). This action is recommended in large environments. This section assumes that you are familiar with library sharing configuration as described in Chapter 3, “SCSI tape library sharing” on page 43, Chapter 4, “IBM 3494 tape library sharing” on page 93, and Chapter 5, “Library sharing with the ACSLS Manager” on page 127.

Figure 2-7 shows the original implementation with two Tivoli Storage Manager servers.


Figure 2-7 Before the Library Manager move

Example 2-8 shows configuration information about the original Tivoli Storage Manager Library Manager. The QUERY LIBRARY command shows the definition of the tape library, the QUERY LIBVOLUMES command shows all library volumes, and the QUERY VOLHISTORY command collects more information about the used volumes.

Example 2-8 Library Manager configuration information

tsm: POCO_1>query library f=d

Library Name: 3494 Library Type: 349X ACS Id: Private Category: 701 Scratch Category: 700 WORM Scratch Category: External Manager: Shared: Yes LanFree: ObeyMountRetention: Primary Library Manager: WWN: Serial Number: AutoLabel: Reset Drives: YesLast Update by (administrator): ADMIN Last Update Date/Time: 22.03.2005 13:18:36

tsm: POCO_1>query libvolumes

Library Name Volume Name Status Owner Last Use

------------ ----------- ---------- ---------- ---------3494 J11771 Private POCO_1 DbBackup3494 J11772 Scratch3494 J11773 Private SCAMP_1 Data3494 J11774 Scratch

tsm: POCO_1>query volhistory


SCAMP_1Library Client 1

Host Poco Host Scamp

Tivoli Storage ManagerPOCO_1

Library Manager


Date/Time: 28.03.2005 17:54:54 Volume Type: BACKUPFULL Backup Series: 4Backup Operation: 0 Volume Seq: 1 Device Class: 3494_3592C Volume Name: J11771 Volume Location: Command:

Date/Time: 29.03.2005 17:47:24 Volume Type: REMOTE Backup Series:Backup Operation: Volume Seq: Device Class: 3494_3592C Volume Name: J11773Volume Location: SCAMP_1 Command:

Example 2-9 shows the same commands on the Tivoli Storage Manager Library Client.

Example 2-9 Library Client

tsm: SCAMP_1>query library f=d

Library Name: 3494 Library Type: SHARED ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: RSM Media Type: Shared: No LanFree: ObeyMountRetention: Primary Library Manager: POCO_1 WWN: Serial Number: AutoLabel: Reset Drives: NoLast Update by (administrator): ADMIN Last Update Date/Time: 24.03.2005 12:05:57

tsm: SCAMP_1>query volumes

Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status----------------- ----------- ---------- --------- ----- -------J11773 TAPE_3494 3494_3592C 900'000,0 0,4 Filling

tsm: SCAMP_1>query volhistory

Date/Time: 29.03.2005 17:50:24 Volume Type: STGNEW Backup Series:Backup Operation: Volume Seq:


Device Class: 3494_3592C Volume Name: J11773 Volume Location: Command:

Figure 2-8 on page 27 shows the target implementation. The host Scamp now has the Tivoli Storage Manager Library Manager and a Tivoli Storage Manager Library Client on separate server instances. The Tivoli Storage Manager instance on host Poco now acts only as a Tivoli Storage Manager Library Client.

Figure 2-8 After the Library Manager move

The remainder of this section describes in detail how to move the Library Manager to another Tivoli Storage Manager server instance. Briefly, the steps are:

1. Preparing the new Tivoli Storage Manager Library Manager instance.

2. Checking the server-to-server communication.

3. Stop all activities on all Tivoli Storage Manager servers.

4. Backing up the Tivoli Storage Manager database for all Tivoli Storage Manager servers.

5. Listing all library volumes on the original Library Manager.

6. Checking out library volumes on the original Library Manager.

7. Creating library definitions on the new Library Manager.

8. Checking in library volumes on the new Library Manager.

9. Deleting and defining the library on the old Library Manager.

10.Deleting unneeded volume history entries on the old Library Manager.

11.Updating all libraries on all Library Clients.

Tivoli Storage ManagerLM

Library Manager

Tivoli Storage ManagerSCAMP_1

Library Client 1

Poco Scamp

Tivoli Storage ManagerPOCO_1

Library Client 2


2.6.1 Preparing the new Tivoli Storage Manager Library Manager instanceOn the host Scamp, we created a new Tivoli Storage Manager instance called LM. This instance will become the new Library Manager. (For information about how to install a new Tivoli Storage Manager instance on the same host, See the Tivoli Storage Manager documentation.) We then defined the server-to-server communication to the other Tivoli Storage Manager server instances (POCO_1 and SCAMP_1), as shown in Example 2-10.

Example 2-10 Setting up server-to-server communication

tsm: LM>SET SERVERPASSWORD secretANR2131I Server password set.

tsm: LM>SET SERVERNAME LMANR2094I Server name set to LM.

tsm: LM>SET SERVERHLADDRESS 9.11.213.9ANR2132I Server hladdress set to 9.11.213.9.

tsm: LM>SET SERVERLLADDRESS 1501ANR2133I Server lladdress set to 1501.

tsm: LM>DEFINE SERVER LM serverpassword=secret HLADDRESS=9.11.213.9 lladdress=1501ANR1660I Server LM defined successfully.

tsm: LM>DEFINE SERVER POCO_1 serverpassword=secret HLADDRESS=9.11.213.110 lladdress=1500ANR1660I Server POCO_1 defined successfully.

tsm: LM>DEFINE SERVER SCAMP_1 serverpassword=secret HLADDRESS=9.11.213.9 lladdress=1500ANR1660I Server SCAMP_1 defined successfully.

2.6.2 Checking the server-to-server communicationTo check the server-to-server communication, use the PING SERVER command. Example 2-11 shows the commands on all three Tivoli Storage Manager servers. We can communicate to the two Library Clients from the new Library Manager (LM) and from both Library Clients (POCO_1 and SCAMP_1) to the Library Manager.

Example 2-11 Ping server on all Tivoli Storage Manager servers

tsm: LM>PING SERVER LMANR1706I Ping for server 'LM' was able to establish a connection.

tsm: LM>PING SERVER POCO_1ANR1706I Ping for server 'POCO_1' was able to establish a connection.

tsm: LM>PING SERVER SCAMP_1ANR1706I Ping for server 'SCAMP_1' was able to establish a connection.

tsm: POCO_1>PING SERVER LMANR1706I Ping for server 'LM' was able to establish a connection.

tsm: SCAMP_1>PING SERVER LMANR1706I Ping for server 'LM' was able to establish a connection.


2.6.3 Stop all activities on all Tivoli Storage Manager serversNext, you disable sessions on all Tivoli Storage Manager servers and wait until all sessions are closed. You also need to stop all administrative schedules and wait until all volumes are unmounted. Example 2-12 shows the DISABLE SESSION command on POCO_1. You need to repeat this command for the other Tivoli Storage Manager servers (SCAMP_1 and LM).

Example 2-12 Disable session

tsm: POCO_1>DISABLE SESSIONANR2553I Server now disabled for Client access.

2.6.4 Backing up the Tivoli Storage Manager database for all Tivoli Storage Manager servers

You next need to backup the server database, volume history, and device configuration on all the Tivoli Storage Manager servers. Do not continue until all processes have completed successfully. Example 2-13 shows the commands on POCO_1. You need to repeat the commands for the other Tivoli Storage Manager servers (SCAMP_1 and LM).

Example 2-13 Backing up the configuration

tsm: POCO_1>BACKUP DB devclass=3494_3592c type=fullANR2280I Full database backup started as process 5.ANS8003I Process number 5 started.

tsm: POCO_1>BACKUP VOLHISTORY filename=volhist

Do you wish to proceed? (Yes (Y)/No (N)) yANR2462I BACKUP VOLHISTORY: Server sequential volume history information was written to volhist.

tsm: POCO_1>BACKUP DEVCONFIG filename=device

Do you wish to proceed? (Yes (Y)/No (N)) yANR2393I BACKUP DEVCONFIG: Server device configuration information was written to device.

Tip: The ENABLE SESSION and DISABLE SESSION commands have been enhanced to allow greater flexibility in which session types are affected.

ENable SESSions CLIent/ALL/SERVer/ADMinDISAble SESSions CLIent/ALL/SERVer/ADMin

� CLIent, backup-archive client sessions (default).� ALL, all session types.� SERVer, server-to-server sessions.� ADMin, administrative sessions.

Attention: With the new commands, it is possible to lock out the administrative session itself. If this happens, you must kill the Tivoli Storage Manager server process and restart it in console mode.


2.6.5 Listing all library volumes on the original Library ManagerYou use a Tivoli Storage Manager SQL command to create a list of all library volumes that are currently defined on the original Library Manager POCO_1. Example 2-14 shows the SQL command and how to redirect the output to a file.

Example 2-14 Tivoli Storage Manager SQL command

tsm: POCO_1>select LIBRARY_NAME,VOLUME_NAME,STATUS,OWNER,LAST_USE from libvolumes

LIBRARY_NAME VOLUME_NAME STATUS OWNER LAST_USE------------- -------------- ---------- ------------ ----------3494 J11771 Private POCO_1 DbBackup3494 J11772 Scratch3494 J11773 Private SCAMP_1 Data3494 J11774 Private POCO_1 DbBackup

tsm: POCO_1>select LIBRARY_NAME,VOLUME_NAME,STATUS,OWNER,LAST_USE from libvolumes > c:\poco_1_libvolumes.txt Output of command redirected to file 'C:\POCO_1_LIBVOLUMES.TXT'

2.6.6 Checking out library volumes on the original Library ManagerYou use the output file that was created in Example 2-14 to create a macro for the CHECKOUT LIBVOLUMES command. The best way for this conversion is to use a spreadsheet program such as Lotus® 1-2-3®.

Example 2-15 Tivoli Storage Manager macro for the CHECKOUT LIBVOLUMES command

checkout libv 3494 J11771 remove=no checkl=nocheckout libv 3494 J11772 remove=no checkl=nocheckout libv 3494 J11773 remove=no checkl=nocheckout libv 3494 J11774 remove=no checkl=no

Then, you start the macro on the old Library Manager, as shown in Example 2-16.

Example 2-16 Start the macro for the CHECKOUT LIBVOLUMES command

tsm: POCO_1>macro c:\Poco_1_checkout.mac > poco_1_checkout_output.txtOutput of command redirected to file 'POCO_1_CHECKOUT_OUTPUT.TXT'

You next check the Tivoli Storage Manager activity log to confirm that all the volumes were checked out successfully. Example 2-17 shows the Tivoli Storage Manager activity log for the CHECKOUT LIBVOLUMES command.

Example 2-17 Activity log for the CHECKOUT LIBVOLUMES command

ANR2017I Administrator ADMIN issued command: CHECKOUT libv 3494 J11771 remove=no checkl=noANR0984I Process 6 for CHECKOUT LIBVOLUME started in the BACKGROUND at 15:10:25.ANR8434I CHECKOUT LIBVOLUME: Operation for volume J11771 in library 3494 started as process 6.ANR2017I Administrator ADMIN issued command: CHECKOUT libv 3494 J11772 remove=no checkl=noANR0984I Process 7 for CHECKOUT LIBVOLUME started in the BACKGROUND at 15:10:25.ANR8434I CHECKOUT LIBVOLUME: Operation for volume J11772 in library 3494 started as process 7.ANR2017I Administrator ADMIN issued command: CHECKOUT libv 3494 J11773 remove=no checkl=noANR0984I Process 8 for CHECKOUT LIBVOLUME started in the BACKGROUND at 15:10:25.ANR8434I CHECKOUT LIBVOLUME: Operation for volume J11773 in library 3494 started as process 8.ANR2017I Administrator ADMIN issued command: CHECKOUT libv 3494 J11774 remove=no checkl=noANR0984I Process 9 for CHECKOUT LIBVOLUME started in the BACKGROUND at 15:10:25.ANR8434I CHECKOUT LIBVOLUME: Operation for volume J11774 in library 3494 started as process 9.


ANR2017I Administrator ADMIN issued command: COMMITANR2017I Administrator ADMIN issued command: COMMITANR8438I CHECKOUT LIBVOLUME for volume J11771 in library 3494 completed successfully.ANR0985I Process 6 for CHECKOUT LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 15:10:26.ANR8438I CHECKOUT LIBVOLUME for volume J11772 in library 3494 completed successfully.ANR0985I Process 7 for CHECKOUT LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 15:10:27.ANR8438I CHECKOUT LIBVOLUME for volume J11773 in library 3494 completed successfully.ANR0985I Process 8 for CHECKOUT LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 15:10:28.ANR8438I CHECKOUT LIBVOLUME for volume J11774 in library 3494 completed successfully.ANR0985I Process 9 for CHECKOUT LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 15:10:29.

All library volumes are now checked out. You can confirm this with the QUERY LIBVOLUMES command. There should be no library volumes, as shown in Example 2-18.

Example 2-18 The QUERY LIBVOLUMES command

tsm: POCO_1>q libv ANR2034E QUERY LIBVOLUME: No match found using this criteria.ANS8001I Return code 11.

2.6.7 Creating library definitions on the new Library ManagerYou are now ready to define the libraries, the drives, and all paths on the new Tivoli Storage Manager Library Manager, LM. Example 2-19 shows the steps in our environment. You use the same name for the library as before. In our case, this name is 3494.

Example 2-19 Define library, drive, and paths for all Tivoli Storage Manager servers

tsm: LM>DEFINE LIBRARY 3494 LIBTYPE=349X SHARED=YES SCRATCHCATegory=700 PRIVATECATegory=701ANR8400I Library 3494 defined.

tsm: LM>DEFINE PATH LM 3494 SRCTYPE=SERVER AUTODETECT=YES DESTTYPE=LIBRARY DEVICE=3494cANR1720I A path from LM to 3494 has been defined.

tsm: LM>DEFINE DRIVE 3494 3494_01ANR8404I Drive 3494_01 defined in library 3494.

tsm: LM>DEFINE DRIVE 3494 3494_02ANR8404I Drive 3494_02 defined in library 3494.

tsm: LM>DEFINE PATH LM 3494_01 srct=server autodetect=yes destt=drive libr=3494 device=\\.\Tape2ANR1720I A path from LM to 3494 3494_01 has been defined.

tsm: LM>DEFINE PATH LM 3494_02 srct=server autodetect=yes destt=drive libr=3494 device=\\.\Tape3ANR1720I A path from LM to 3494 3494_02 has been defined.

tsm: LM>DEFINE PATH POCO_1 3494_01 srct=server autodetect=yes destt=drive libr=3494 device=/dev/rmt2ANR1720I A path from POCO_1 to 3494 3494_01 has been defined.

tsm: LM>DEFINE PATH POCO_1 3494_02 srct=server autodetect=yes destt=drive libr=3494 device=/dev/rmt3ANR1720I A path from POCO_1 to 3494 3494_02 has been defined.


tsm: LM>DEFINE PATH SCAMP_1 3494_01 srct=server autodetect=yes destt=drive libr=3494 device=\\.\Tape2ANR1720I A path from SCAMP_1 to 3494 3494_01 has been defined.

tsm: LM>DEFINE PATH SCAMP_1 3494_02 srct=server autodetect=yes destt=drive libr=3494 device=\\.\Tape3ANR1720I A path from SCAMP_1 to 3494 3494_02 has been defined.

tsm: LM>DEFINE DEVCLASS 3494_3592C LIBRARY=3494 DEVTYPE=3592ANR2203I Device class 3494_3592C defined.

2.6.8 Checking in library volumes on the new Library ManagerThe tape library is now defined, and you can check in the library volumes. To check in library volumes, you use the output file that is shown in Example 2-14 on page 30 to create a Tivoli Storage Manager macro. The best way for this conversion is to use a spreadsheet program such as Lotus 1-2-3. The command format that you use depends on the library type. (For more information, see the Tivoli Storage Manager manual for the CHECKIN LIBVOLUMES command.) Example 2-20 shows our macro. Running it ensures that the volumes remain assigned to the same Tivoli Storage Manager server.

Example 2-20 Tivoli Storage Manager macro for the CHECKIN LIBVOLUMES command

checkin libv 3494 J11771 status=Private owner=POCO_1 checkl=nocheckin libv 3494 J11772 status=Scratch owner="" checkl=nocheckin libv 3494 J11773 status=Private owner=SCAMP_1 checkl=nocheckin libv 3494 J11774 status=Private owner=SCAMP_1 checkl=no

Next, you run the macro to check in the library volumes on the new Library Manager, as shown in Example 2-21.

Example 2-21 Start the macro for the CHECKIN LIBVOLUMES command

tsm: LM>macro c:\LM_checkin.mac > c:\LM_checkin_output.txtOutput of command redirected to file 'C:\LM_CHECKIN_OUTPUT.TXT'

Check the Tivoli Storage Manager activity log after the command to confirm that all processes completed successfully. Example 2-22 shows the activity log for the CHECKIN LIBVOLUMES command.

Example 2-22 Activity log for the CHECKIN LIBVOLUMES command

ANR2017I Administrator ADMIN issued command: CHECKIN libv 3494 J11771 status=Private owner=POCO_1 checkl=noANR0984I Process 3 for CHECKIN LIBVOLUME started in the BACKGROUND at 16:10:49.ANR8422I CHECKIN LIBVOLUME: Operation for library 3494 started as process 3.ANR2017I Administrator ADMIN issued command: CHECKIN libv 3494 J11772 status=Scratch owner= checkl=noANR0984I Process 4 for CHECKIN LIBVOLUME started in the BACKGROUND at 16:10:50.ANR8422I CHECKIN LIBVOLUME: Operation for library 3494 started as process 4.ANR2017I Administrator ADMIN issued command: CHECKIN libv 3494 J11773 status=Private owner=SCAMP_1 checkl=noANR0984I Process 5 for CHECKIN LIBVOLUME started in the BACKGROUND at 16:10:50.ANR8422I CHECKIN LIBVOLUME: Operation for library 3494 started as process 5.ANR2017I Administrator ADMIN issued command: CHECKIN libv 3494 J11774 status=Private owner=SCAMP_1 checkl=noANR0984I Process 6 for CHECKIN LIBVOLUME started in the BACKGROUND at 16:10:50.ANR8422I CHECKIN LIBVOLUME: Operation for library 3494 started as process 6.


ANR2017I Administrator ADMIN issued command: COMMITANR2017I Administrator ADMIN issued command: COMMITANR8427I CHECKIN LIBVOLUME for volume J11771 in library 3494 completed successfully.ANR0985I Process 3 for CHECKIN LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 16:11:08.ANR8427I CHECKIN LIBVOLUME for volume J11772 in library 3494 completed successfully.ANR0985I Process 4 for CHECKIN LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 16:11:11.ANR8427I CHECKIN LIBVOLUME for volume J11773 in library 3494 completed successfully.ANR0985I Process 5 for CHECKIN LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 16:11:15.ANR8427I CHECKIN LIBVOLUME for volume J11774 in library 3494 completed successfully.ANR0985I Process 6 for CHECKIN LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 16:11:18.

All library volumes should be available now on the new Library Manager. You can confirm their availability with the QUERY LIBVOLUMES command on the Tivoli Storage Manager server. Compare the results (Example 2-23) with the output on the previous Library Manager (Example 2-14 on page 30). The results should be the same, except for the column Last Use, which is filled when each volume is accessed again.

Example 2-23 QUERY LIBVOLUMES after CHECKIN LIBVOLUMES

tsm: LM>q libv

Library Name Volume Name Status Owner Last Use Home Device Element Type------------ ----------- ---------- ---------- --------- ------- ------3494 J11771 Private POCO_13494 J11772 Scratch3494 J11773 Private SCAMP_13494 J11774 Private SCAMP_1

2.6.9 Deleting and defining the library on the old Library ManagerTo this point, the libraries, drives, and paths are defined on the old Library Manager. You can now delete these definitions, because you have a new Library Manager. Example 2-24 shows the deletion.

Example 2-24 Deleting all paths, drives, and libraries on the old Library Manager

tsm: POCO_1>DELETE PATH SCAMP_1 3494_01 srct=server destt=drive libr=3494ANR1721I A path from SCAMP_1 to 3494 3494_01 has been deleted.tsm: POCO_1>DELETE PATH SCAMP_1 3494_02 srct=server destt=drive libr=3494ANR1721I A path from SCAMP_1 to 3494 3494_02 has been deleted.tsm: POCO_1>DELETE PATH POCO_1 3494_01 srct=server destt=drive libr=3494ANR1721I A path from POCO_1 to 3494 3494_01 has been deleted.tsm: POCO_1>DELETE PATH POCO_1 3494_02 srct=server destt=drive libr=3494ANR1721I A path from POCO_1 to 3494 3494_02 has been deleted.tsm: POCO_1>DELETE PATH POCO_1 3494 srct=server destt=libraryANR1721I A path from POCO_1 to 3494 has been deleted.tsm: POCO_1>DELETE DRIVE 3494 3494_01ANR8412I Drive 3494_01 deleted from library 3494.tsm: POCO_1>DELETE DRIVE 3494 3494_02ANR8412I Drive 3494_02 deleted from library 3494.tsm: POCO_1>DELETE LIBRARY 3494ANR8410I Library 3494 deleted.


Next, because the former Library Manager is now a Library Client, you need to redefine the shared library so that it points to the new Library Manager, as shown in Example 2-25.

Example 2-25 Defining the shared Library on the former Library Manager

tsm: POCO_1>DEFINE LIBRARY 3494 libtype=shared primarylibmanager=LMANR8400I Library 3494 defined.

tsm: POCO_1>q libr f=d

Library Name: 3494 Library Type: SHARED ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: Shared: No LanFree: ObeyMountRetention: Primary Library Manager: LM WWN: Serial Number: AutoLabel: Reset Drives: NoLast Update by (administrator): ADMIN Last Update Date/Time: 30.03.2005 16:25:57

2.6.10 Deleting unneeded volume history entries on the old Library ManagerNext, you need to delete all volume history entries with the type remote on the previous Library Manager. To find these entries, query the volume history table on the old Library Manager, as shown in Example 2-26.

Example 2-26 Query volume history with type=remote

tsm: POCO_1>QUERY VOLHISTORY type=remote Date/Time: 28.03.2005 18:00:31 Volume Type: REMOTE Backup Series:Backup Operation: Volume Seq: Device Class: 3494_3592C Volume Name: J11774 Volume Location: SCAMP_1 Command: Date/Time: 29.03.2005 17:47:24 Volume Type: REMOTE Backup Series:Backup Operation: Volume Seq: Device Class: 3494_3592C Volume Name: J11773 Volume Location: SCAMP_1 Command:

Important: If you do not delete these entries, if the previous Library Manager requests a scratch volume from the new Library Manager, and if the volume granted is still in its volume history, the volume will be rejected (for example, ANR8448E Scratch volume J11772 from library 3494 rejected because the volume name is already in use).


To delete these entries, you make a Tivoli Storage Manager macro, use a Tivoli Storage Manager SQL command to query the volume history, and then use a spreadsheet program to create the macro, as shown in Example 2-27.

Example 2-27 Tivoli Storage Manager SQL command

tsm: POCO_1>select VOLUME_NAME,DATE_TIME from volhistory where type='REMOTE'

VOLUME_NAME: J11774 DATE_TIME: 2005-03-28 18:00:31.000000



tsm: POCO_1>select VOLUME_NAME,DATE_TIME from volhistory where type='REMOTE' > c:\poco_1_volh_remote.txtOutput of command redirected to file 'C:\POCO_1_VOLH_REMOTE.TXT'

Example 2-28 shows the macro.

Example 2-28 Macro to delete the entry in the volume history on the old Library Manager

DELETE VOLHISTORY t=remote vol=J11774 todate=03/28/2005 force=yesDELETE VOLHISTORY t=remote vol=J11772 todate=03/29/2005 force=yesDELETE VOLHISTORY t=remote vol=J11773 todate=03/29/2005 force=yes

You can now run the macro and check the Tivoli Storage Manager activity log for errors (Example 2-29).

Example 2-29 Activity log of DELETE VOLHISTORY on old Library Manager

ANR2017I Administrator ADMIN issued command: DELETE VOLHISTORY t=remote vol=J11774 todate=03/28/2005 force=yesANR2467I DELETE VOLHISTORY: 1 sequential volume history entries were successfully deleted.ANR2017I Administrator ADMIN issued command: DELETE VOLHISTORY t=remote vol=J11772 todate=03/29/2005 force=yesANR2467I DELETE VOLHISTORY: 1 sequential volume history entries were successfully deleted.ANR2017I Administrator ADMIN issued command: DELETE VOLHISTORY t=remote vol=J11773 todate=03/29/2005 force=yesANR2467I DELETE VOLHISTORY: 1 sequential volume history entries were successfully deleted.ANR2017I Administrator ADMIN issued command: COMMITANR2017I Administrator ADMIN issued command: COMMIT


2.6.11 Updating all libraries on all Library ClientsThe last step is to update the libraries on all Library Clients to use the new Library Manager. In our environment, we updated the Library Client SCAMP_1 (Example 2-30).

Example 2-30 Update shared library on Library Client

tsm: SCAMP_1>QUERY LIBRARY 3494 f=d

Library Name: 3494 Library Type: SHARED ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: RSM Media Type: Shared: No LanFree: ObeyMountRetention: Primary Library Manager: POCO_1 WWN: Serial Number: AutoLabel: Reset Drives: NoLast Update by (administrator): ADMIN Last Update Date/Time: 24.03.2005 12:05:57

tsm: SCAMP_1>UPDATE LIBRARY 3494 primarylibmanager=LMANR8465I Library 3494 updated.

tsm: SCAMP_1>QUERY LIBRARY 3494 f=d

Library Name: 3494 Library Type: SHARED ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: RSM Media Type: Shared: No LanFree: ObeyMountRetention: Primary Library Manager: LM WWN: Serial Number: AutoLabel: Reset Drives: NoLast Update by (administrator): ADMIN Last Update Date/Time: 30.03.2005 16:33:06

You are now ready to use the new Library Manager. You can enable all sessions on all Tivoli Storage Manager servers.


2.7 Command differences in a library sharing environmentThere are some commands which execute differently when issued in a library sharing environment (that is, the results are different depending on whether they are run at the Library Manager or a Library Client). This section describes those command differences.

2.7.1 Auditing the libraryThe AUDIT LIBRARY command works differently in a Tivoli Storage Manager library sharing environment compared to a non-shared environment.

On the Library ManagerWhen the AUDIT LIBRARY command is issued on a Library Manager for a shared library, the Library Manager updates ownership of its volumes if it detects inconsistencies and synchronizes its inventory with the inventory of the library device. If the Library Manager detects inconsistencies, it deletes missing volumes from its inventory. In addition, the Library Manager:

� In SCSI libraries, updates the locations of volumes in its inventory that have been moved since the last audit.

� In 349X libraries, ensures that scratch volumes are in the scratch category and that private volumes are in the private category.

Example 2-31 shows the use of the AUDIT LIBRARY command on a Library Manager.

Example 2-31 AUDIT LIBRARY on the Library Manager with a 3494 library

ANR2017I Administrator ADMIN issued command: AUDIT LIBR 3494 ANR0984I Process 2 for AUDIT LIBRARY started in the BACKGROUND at 15:10:20.ANR8457I AUDIT LIBRARY: Operation for library 3494 started as process 2.ANR8461I AUDIT LIBRARY process for library 3494 completed successfully.ANR0985I Process 2 for AUDIT LIBRARY running in the BACKGROUND completed with completion state SUCCESS at 15:10:21.

For a SCSI library, the AUDIT LIBRARY command mounts and reads the label on each tape to verify its identity. Depending on the library capacity, this process can take a long time. Use the CHECKLABEL=BARCODE parameter (as shown in Example 2-32) so that Tivoli Storage Manager uses the barcode reader to read the storage label. This parameter decreases the audit processing time, compared with loading and reading each label from the tape.

Example 2-32 AUDIT LIBRARY with CHECKLABEL=BARCODE

ANR2017I Administrator ADMIN issued command: AUDIT LIBR 3582 checkl=barcode ANR0984I Process 3 for AUDIT LIBRARY started in the BACKGROUND at 15:35:46.ANR8457I AUDIT LIBRARY: Operation for library 3582 started as process 3.ANR8461I AUDIT LIBRARY process for library 3582 completed successfully.ANR0985I Process 3 for AUDIT LIBRARY running in the BACKGROUND completed with completion state SUCCESS at 15:35:53.

Note: Issuing the AUDIT LIBRARY command does not add new volumes to a library automatically. To add new volumes, you must use the CHECKIN LIBVOLUME command.

Note: If the scanner cannot read the barcode label or the barcode label is missing, Tivoli Storage Manager loads that tape in a drive to read the label.


On the Library ClientWhen the AUDIT LIBRARY command is issued on a Library Client, the client synchronizes its inventory with the inventory on the Library Manager. If the Library Client detects inconsistencies, it corrects them by changing the ownership of the volume on the Library Manager. Example 2-33 contains sample output and shows that a server-to-server session is started with the Library Manager.

Example 2-33 AUDIT LIBRARY on the Library Client

ANR2017I Administrator ADMIN issued command: AUDIT LIBR 3494 ANR0984I Process 21 for AUDIT LIBRARY started in the BACKGROUND at 15:26:30.ANR8457I AUDIT LIBRARY: Operation for library 3494 started as process 21.ANR0408I Session 70 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 70 ended for server POCO_1 (AIX-RS/6000).ANR8461I AUDIT LIBRARY process for library 3494 completed successfully.ANR0985I Process 21 for AUDIT LIBRARY running in the BACKGROUND completed with completion state SUCCESS at 15:26:30.

2.7.2 The QUERY MOUNT and QUERY DRIVE commandsThese two commands are used to display the tapes that are mounted currently and the drives that are defined on a Tivoli Storage Manager server.

On the Library ManagerWith the QUERY MOUNT command, you see the status of all sequential access volumes that are mounted. On the Library Manager, this command shows information for mounts by both the Library Manager and all Library Clients. Example 2-34 shows some examples.

Example 2-34 QUERY MOUNT on the Tivoli Storage Manager Library Manager

tsm: LM>q mo ANR8379I Mount point in device class 3494_3592C is waiting for the volume mount to complete, status: WAITING FOR VOLUME.ANR8334I 1 matches found.tsm: LM>q mo ANR8330I 3592 volume J11772 is mounted R/W in drive 3494_01 (\\.\Tape2), status: IN USE.ANR8334I 1 matches found.tsm: LM>q mo ANR8331I 3592 volume J11772 is mounted R/W in drive 3494_01 (\\.\Tape2), status: DISMOUNTING.ANR8334I 1 matches found.

tsm: LM>q mo ANR2034E QUERY MOUNT: No match found using this criteria.

Attention: Running the AUDIT LIBRARY command prevents any other library activity from starting until the audit completes. For example, Tivoli Storage Manager does not process restore or retrieve requests that involve the library while the AUDIT LIBRARY command is running.

Attention: If other activity is occurring in the library, do not issue the AUDIT LIBRARY command. In this case, issuing the AUDIT LIBRARY command can produce unpredictable results (for example, a hang condition) if a process that is accessing the library attempts to acquire a new tape mount.


The QUERY DRIVE command shows all information about a drive, including the drive state, name of volume (if loaded), and which Tivoli Storage Manager server is using this drive (Example 2-35).

Example 2-35 QUERY DRIVE on the Tivoli Storage Manager Library Manager

tsm: LM>query drive 3494 3494_01 f=d Library Name: 3494 Drive Name: 3494_02 Device Type: 3592 On-Line: Yes Read Formats: 3592C,3592 Write Formats: 3592C,3592 Element: Drive State: LOADED Volume Name: J11772 Allocated to: POCO_1 WWN: 5005076300000000 Serial Number: 000001300114 Last Update by (administrator): ADMIN Last Update Date/Time: 30.03.2005 15:31:02Cleaning Frequency (Gigabytes/ASNEEDED/NONE):

On the Library ClientWith the QUERY MOUNT command, you see the status of all sequential access volumes that are mounted for this Tivoli Storage Manager Library Client only. Example 2-36 shows some examples.

Example 2-36 QUERY MOUNT on the Tivoli Storage Manager Library Client

tsm: POCO_1>q mo ANR8379I Mount point in device class 3494_3592C is waiting for the volume mount to complete, status: WAITING FOR VOLUME.ANR8334I 1 matches found.

tsm: POCO_1>q mo ANR8330I 3592 volume J11772 is mounted R/W in drive 3494_01 (/dev/rmt2), status: IN USE.ANR8334I 1 matches found.

tsm: POCO_1>q mo ANR8331I 3592 volume J11772 is mounted R/W in drive 3494_01 (/dev/rmt2), status: DISMOUNTING.ANR8334I 1 matches found.

tsm: POCO_1>q mo ANR2034E QUERY MOUNT: No match found using this criteria.

The QUERY DRIVE command cannot be used on the Tivoli Storage Manager Library Client (Example 2-37), because there are no drives defined.

Example 2-37 QUERY DRIVE on the Tivoli Storage Manager Library Manager

tsm: POCO_1>query drive 3494 3494_01 f=d ANR2034E QUERY DRIVE: No match found using this criteria.ANS8001I Return code 11.


2.8 Interactions between Library Manager and Library ClientA Library Client contacts the Library Manager, when:

� The Library Manager starts.� A shared storage device initializes.� After a Library Manager is defined to a Library Client.

The Tivoli Storage Manager Library Client confirms that the contacted server is the Tivoli Storage Manager Library Manager for the named library device. The Library Client also compares drive definitions with the Library Manager for consistency. The Library Client contacts the Library Manager for each of the following operations:

� Volume Mount

A Library Client sends a request to the Library Manager for access to a particular volume in the shared library device. For a scratch volume, the Library Client does not specify a volume name. If the Library Manager cannot access the requested volume or if a scratch volume is not available, the Library Manager denies the mount request. If the mount is successful, the Library Manager returns the name of the drive where the volume is mounted.

� Volume Release (free to scratch)

When a Library Client no longer needs a volume (for example, after reclamation), it notifies the Library Manager that the volume should be returned to scratch. The Library Manager’s database is updated with the volume’s new location. The volume is deleted from the volume inventory of the Library Client.


Table 2-4 shows some Tivoli Storage Manager commands and associated actions that are performed on the Tivoli Storage Manager Library Manager or Tivoli Storage Manager Library Client.

Table 2-4 Interactions between Library Manager and Library Client

Operation (command) Tivoli Storage Manager Library Manager Tivoli Storage Manager Library Client

Query library volumes(QUERY LIBVOLUME)

Displays the volumes that are checked into the library. For private volumes, the owner server is also displayed

Not applicable.

Check in and check out library volumes(CHECKIN LIBVOLUME, CHECKOUT LIBVOLUME)

Performs the commands to the library device.

Not applicable. When a check-in operation must be performed because of a client restore, a request is sent to the Library Manager server.

Move media and move DRM media (MOVE MEDIA, MOVE DRMEDIA)

Only valid for volumes that are used by the Library Manager.

Requests that the Library Manager perform the operations. Generates a checkout process on the Library Manager.

Audit library inventory(AUDIT LIBRARY)

Performs inventory synchronization with the library device.

Performs inventory synchronization with the Library Manager.

Label a library volume(LABEL LIBVOLUME)

Performs the labeling and check in of media.

Not applicable.

Dismount a volume(DISMOUNT VOLUME)

Sends the request to the library device. Requests that the Library Manager perform the operation.

Query a volume(QUERY VOLUME)

Checks whether the volume is owned by the requesting Library Client and checks whether the volume is in the library device.

Requests that the Library Manager perform the operation



Chapter 3. SCSI tape library sharing

This chapter describes Tivoli Storage Manager library sharing with direct or Fibre Channel attached SCSI libraries and how to implement library sharing in a typical environment. This chapter contains the following topics:

� Introduction to SCSI tape library sharing

� Library sharing with SCSI/FC tape libraries

– SAN zoning information– Installing on IBM AIX– Installing on Microsoft Windows 2000– Installing on Linux– Installing on SUN Solaris

� Tivoli Storage Manager configuration

3


3.1 Introduction to SCSI tape library sharingThis section introduces some important concepts related to SCSI tape library sharing.

3.1.1 SCSI librariesA SCSI library is controlled through a SCSI interface that is attached either directly to the server's host using SCSI cabling or by a SAN. A robot or other mechanism handles volume mounts and dismounts automatically. The drives in a SCSI library might be of different types. This chapter considers only SAN-attached SCSI libraries. IBM Linear Tape Open (LTO) libraries (for example, 3582, 3583, and 3584) are SCSI libraries.

3.1.2 Library medium changerThe library medium changer gives the Library Manager access to the functions that are required for basic tape operations such as backup and restore and medium changer operations such as mount and demount the cartridges, as well as the advanced functions that are needed by full tape management systems.

Tivoli Storage Manager supports the use of the Tivoli Storage Manager device driver, which is supplied with Tivoli Storage Manager for non-IBM devices. Tivoli Storage Manager supports the IBM device driver for IBM devices.

On the Tivoli Storage Manager Library Client, you do not use or configure the library medium changer device. You use and configure the library medium only on the Library Manager.

For SCSI/FC attached drives, we do not need a special connection to the tape library controller, because the tape library controller can be accessed through one of the SCSI/FC attached drives. Figure 3-1 shows a library with eight drives. It is configured to access the controller through the first drive.

Figure 3-1 SCSI/FC attached tape library

SAN

Tivoli Storage Managerserver

Library controller

Drive

Drive

Drive

Drive

Drive

Drive

Drive

Drive

Function NumberLibrary Medium Changer

1

Drive 8

Device special file


For this configuration on the Library Manager, we have one operating system device special file for the library medium changer (for example, for IBM AIX /dev/smc0) and eight device special files for the drives that are available (for example, /dev/rmt0). If the drive that is used for the control path is not available, you lose access to the tape library medium changer. To circumvent this loss of access, some tape libraries offer library control path failover.

Control path and data path failoverIf your library offers this feature, you can enable more than one drive to connect to the library controller (as shown in Figure 3-2). In this configuration, you setup paths to the controller on the first two drives. The operating system now sees two device special files for the same physical tape library controller. If one drive is not available, you can access the library via the path on the second drive.

Figure 3-2 SCSI/FC attached tape library with control path failover

Important: It is highly recommended to use dedicated HBAs for attachment to the tape drives and libraries — that is, do not also access non-tape devices on the same Host Bus Adapter (HBA). In the case of IBM devices, sharing tape and non-tape devices on the same HBA is not a supported configuration.

SAN

Tivoli Storage Managerserver

Library controller

Drive

Drive

Drive

Drive

Drive

Drive

Drive

Drive

Function NumberLibrary Medium Changer

2

Drive 8

Device special file

Chapter 3. SCSI tape library sharing 45

3.2 Library sharing with SCSI/FC tape librariesThis section describes how to install the IBM device driver for IBM AIX, Microsoft Windows, Linux, and SUN Solaris. Figure 3-3 shows the interrelationship between the Tivoli Storage Manager Library Manager, Tivoli Storage Manager Library Client, and the tape library.

Figure 3-3 SCSI library sharing overview

3.2.1 SAN zoning informationZoning allows you to partition your SAN into logical groupings of devices so that each group is isolated from each other and can only access the devices in their own group. Using zoning, you can arrange fabric-connected devices into logical groups, or zones, over the physical configuration of the fabric. Zones can be configured dynamically. They can vary in size depending on the number of fabric connected devices, and devices can belong to more than one zone. Because zone members can access only other members of the same zone, a device not included in a zone is not available to members of that zone.

All Tivoli Storage Manager Library Clients and the Tivoli Storage Manager Library Manager must have access to all shared drives to use the Tivoli Storage Manager Library Sharing function. It is recommended that you allow all Tivoli Storage Manager Library Clients to use all tape drives. For more information, see 2.5.4, “Drive allocation” on page 22.

Table 3-1 on page 47 shows an example of SAN zoning that you can use. In this configuration, there is a Library Manager (LM) and two Library Clients (LC1 and LC2). Each host has two HBAs (fcs1 and fcs2). The library is an IBM 3584 with two fibre drives.

Tivoli Storage Manager Library Client

Library ControlSCSI

Data Flow

Server-to-Server communication

LAN

Tape Library

SAN

Data Flow

Tivoli Storage Manager Library Manager


Table 3-1 SAN zoning

For further information about SAN zoning, see the IBM Redbook IBM TotalStorage: Implementing an Open IBM SAN, SG24-6116.

3.2.2 Installing on IBM AIXThis section shows the steps that are required to create the tape library medium changer and the drive special files on IBM AIX. It uses the host AZOV with two HBAs as the Library Manager. The library is an IBM 3582 with two FC Ultrium drives.

This example creates zones so that each HBA on AZOV can see both the drives. After configuring this zoning on the IBM AIX server, you see the connected drives as shown in Example 3-1. Because there are two HBAs, you see two device files for each drive.

Example 3-1 AIX: lsdev -Cctape before IBM tape driver installation

azov.almaden.ibm.com:/# lsdev -Cctapermt0 Available 1Z-08-02 Other FC SCSI Tape Drivermt1 Available 1Z-08-02 Other FC SCSI Tape Drivermt2 Available 1D-08-02 Other FC SCSI Tape Drivermt3 Available 1D-08-02 Other FC SCSI Tape Drive

The drives show as generic Other FC SCSI Tape Drive because the correct device driver has not yet been installed. Because this example uses an IBM tape library and drives, you install the IBM device driver (Atape). This driver is designed specifically to take advantage of the features that are provided by the IBM Ultrium tape drives and medium changer devices. For more information, see Part 2 in IBM Ultrium Device Drivers Installation and User’s Guide, GA32-0430. You can download the Atape driver package from:

ftp://ftp.software.ibm.com/storage/devdrvr/AIX/

For non-IBM drives, you would use the Tivoli Storage Manager device driver instead.

Name of Zone Zone Members Purpose

z_LM_fa1 a_LM_fcs1a_3584_dr1a_3584_dr2

Tivoli Storage Manager Library Manager zone for SAN Fabric 1 with the first HBA.

z_LM_fa2 a_LM_fcs2a_3584_dr3a_3584_dr4

Tivoli Storage Manager Library Manager zone for SAN Fabric 2 with the second HBA.

z_LC1_fa1 a_LC1_fcs1a_3584_dr1a_3584_dr2

Tivoli Storage Manager Library Client 1 zone for SAN Fabric 1 with the first HBA.


Tivoli Storage Manager Library Client 1 zone for SAN Fabric 2 with the second HBA.


Tivoli Storage Manager Library Client 2 zone for SAN Fabric 1 with the first HBA.


Tivoli Storage Manager Library Client 2 zone for SAN Fabric 2 with the second HBA.



Use the SMIT command to install the packages, as shown in Example 3-2. After the driver installation, you should reboot the server as soon as possible, because the installation updates the system boot image.

Example 3-2 AIX: Atape installation with SMIT

COMMAND STATUS

Command: OK stdout: yes stderr: no

Before command completion, additional instructions may appear below.

[TOP]geninstall -I "a -cgNQqwX -J" -Z -d . -f File 2>&1

File: I:Atape.driver 9.3.3.0+-----------------------------------------------------------------------------+ Pre-installation Verification...+-----------------------------------------------------------------------------+Verifying selections...doneVerifying requisites...doneResults...

SUCCESSES--------- Filesets listed in this section passed pre-installation verification and will be installed.

Selected Filesets -----------------Atape.driver 9.3.3.0 # IBM AIX Enhanced Tape and Me...

<< End of Success Section >>

FILESET STATISTICS------------------ 1 Selected to be installed, of which: 1 Passed pre-installation verification ---- 1 Total to be installed

0503-409 installp: bosboot verification starting...installp: bosboot verification completed.+-----------------------------------------------------------------------------+ Installing Software...+-----------------------------------------------------------------------------+

installp: APPLYING software for: Atape.driver 9.3.3.0

. . . . . << Copyright notice for Atape >> . . . . . . .

IBM AIX Enhanced Tape and Medium Changer Device Driver

(C) COPYRIGHT International Business Machines Corp. 1993 1997 All Rights Reserved Licensed Materials - Property of IBM

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.


. . . . . << End of copyright notice for Atape >>. . . .

Checking for existing Atape devices...Installing AIX Version 5.2 Atape.driver...Adding device prototype...Adding odm and smit entries...Adding catalogs...Adding trace template...Adding error template...5 entries added.0 entries deleted.0 entries updated.Adding utility programs...Finished processing all filesets. (Total time: 10 secs).

0503-409 installp: bosboot verification starting...installp: bosboot verification completed.0503-408 installp: bosboot process starting...

bosboot: Boot image is 19708 512 byte blocks.0503-292 This update will not fully take effect until after a system reboot.

* * * A T T E N T I O N * * * System boot image has been updated. You should reboot the system as soon as possible to properly integrate the changes and to avoid disruption of current functionality.

installp: bosboot process completed.+-----------------------------------------------------------------------------+ Summaries:+-----------------------------------------------------------------------------+

Installation Summary--------------------Name Level Part Event Result-------------------------------------------------------------------------------Atape.driver 9.3.3.0 USR APPLY SUCCESS

[BOTTOM]

F1=Help F2=Refresh F3=Cancel F6=CommandF8=Image F9=Shell F10=Exit /=Findn=Find Next


After rebooting, check the drives again with the lsdev command, as shown in Example 3-3. Now, the correct device type is shown because the drives are configured with the IBM tape device driver.

Example 3-3 AIX: lsdev -Cctape after IBM tape driver installation

azov.almaden.ibm.com:/# lsdev -Cctapermt0 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt1 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt2 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt3 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)smc0 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc1 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc2 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)smc3 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)

Example 3-4 AIX: cfgmgr

azov.almaden.ibm.com:/# lsdev -Ccadapterent0 Available 1L-08 10/100 Mbps Ethernet PCI Adapter II (1410ff01)ent1 Available 1n-08 IBM 10/100/1000 Base-T Ethernet PCI Adapter (14100401)ent2 Available 14-08 10/100 Mbps Ethernet PCI Adapter II (1410ff01)fcs0 Available 1Z-08 FC Adapterfcs1 Available 1D-08 FC Adapterfda0 Available 01-D1 Standard I/O Diskette Adapteride0 Available 1G-19 ATA/IDE Controller Devicelai0 Available 12-00 GXT135P Graphics Adapterppa0 Available 01-R1 CHRP IEEE1284 (ECP) Parallel Port Adaptersa0 Available 01-S1 Standard I/O Serial Portsa1 Available 01-S2 Standard I/O Serial Portsa2 Available 01-S3 Standard I/O Serial Portscsi0 Available 1S-08 Wide/Ultra-3 SCSI I/O Controllerscsi1 Available 1S-09 Wide/Ultra-3 SCSI I/O Controllerscsi2 Available 1c-08 Wide/Fast-20 SCSI I/O Controllersioka0 Available 01-K1-00 Keyboard Adaptersiokma0 Available 01-K1 Keyboard/Mouse Adaptersioma0 Available 01-K1-01 Mouse Adapterazov.almaden.ibm.com:/# cfgmgr -l fcs0azov.almaden.ibm.com:/# cfgmgr -l fcs1azov.almaden.ibm.com:/#

Example 3-3 shows four rmt devices have been made available. However, there are only two tape drives in the tape library. The extra rmt devices appear because AZOV has two HBAs installed, and both are zoned for both tape drives using just one SAN fabric, as shown in Figure 3-4 on page 51. Therefore, there are two paths that are available to each drive and, consequently, two devices configured for each physical device.

Example 3-3 also shows four library medium changers for only one physical library. The extra medium changers appear because of the two SAN paths to each drive and the library control path failover feature on the IBM 3582 tape library is used. This means each drive is enabled for the control path, and there are two paths to each drive, making four medium changer devices in all. With this feature, if one library control path failed, the library can be accessed via the other control path.

Tip: If the drives do not appear, run configuration manager (cfgmgr) to rescan for devices on the FC HBAs, as shown in Example 3-4.


Figure 3-4 SAN zoning

In Example 3-3 on page 50, the devices /dev/rmt0 and /dev/rmt2 point to the same target drive. You can check this with the lsattr command on AIX (Example 3-5). Note that the node names and World Wide Node Name are the same for both devices.

In the Tivoli Storage Manager drive path definition, this example uses either /dev/rmt0 or /dev/rmt2 for this drive but not both at the same time. If you lose one path to the drive, you can either update the Tivoli Storage Manager drive path manually or use the new Tivoli Storage Manager V5.3 SANDISCOVERY feature. (For more information about SANDISCOVERY, see Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.) Similarly, /dev/rmt1 and /dev/rmt3 point to the same target drive.

Example 3-5 AIX: lsattr

azov.almaden.ibm.com:/# lsattr -El rmt0alt_pathing no Enable Alternate Pathing Support Trueautoload no Use Autoloading Feature at End-of-Tape Trueblock_size 0 Block Size (0=Variable Length) Truecompress yes Use Hardware Compression on Tape Truedebug_trace no Debug Trace Logging Enabled Truedev_status N/A Falsedevtype ULT3580- Device Type Falselocation Location Truelogging no Activate volume information logging Truelun_id 0x0 Logical Unit Number Truemax_log_size 500 Maximum size of log file (in # of entries) Truenew_name New Logical Name Truenode_name 0x500308c140067006 World Wide Node Name Falseprimary_device rmt0 Primary Logical Device Falseretain_reserve no Retain Reservation Falserew_immediate no Use Immediate Bit in Rewind Commands Truescsi_id 0x502cb SCSI Target ID Truespace_mode SCSI Backward Space/Forward Space Record Mode Truetrace_logging no Trace Logging Enabled Truetrailer_labels no Trailer Label Processing Trueww_name 0x500308c140467006 World Wide Port Name False

SAN Fabric

Host AZOV

HBAfcs0

HBAfcs1

Tape Library3582

Drive1

Drive2

Name of Zone Zone Members

z_azov_fcs0a_azov_fcs0a_3582_dr1a_3582_dr2

z_azov_fcs1a_azov_fcs1a_3582_dr1a_3582_dr2

SAN Zoning


azov.almaden.ibm.com:/# lsattr -El rmt2alt_pathing no Enable Alternate Pathing Support Trueautoload no Use Autoloading Feature at End-of-Tape Trueblock_size 0 Block Size (0=Variable Length) Truecompress yes Use Hardware Compression on Tape Truedebug_trace no Debug Trace Logging Enabled Truedev_status N/A Falsedevtype ULT3580- Device Type Falselocation Location Truelogging no Activate volume information logging Truelun_id 0x0 Logical Unit Number Truemax_log_size 500 Maximum size of log file (in # of entries) Truenew_name New Logical Name Truenode_name 0x500308c140067006 World Wide Node Name Falseprimary_device rmt2 Primary Logical Device Falseretain_reserve no Retain Reservation Falserew_immediate no Use Immediate Bit in Rewind Commands Truescsi_id 0x502cb SCSI Target ID Truespace_mode SCSI Backward Space/Forward Space Record Mode Truetrace_logging no Trace Logging Enabled Truetrailer_labels no Trailer Label Processing Trueww_name 0x500308c140467006 World Wide Port Name False

Another elegant method is to use the Atape device driver alternate pathing support for AIX. The alternate pathing support configures multiple physical paths to the same device within the device driver and provides two basic functions:

� Automatic failover to an alternate physical path when a permanent error occurs on one path.

� Dynamic load balancing for devices using multiple HBAs.

The automatic failover support provides error recovery on an alternate path when a permanent error occurs on one path. This recovery is transparent to the running application.

Alternate pathing support can be enabled on all configured devices at once (as shown in Example 3-6), or it can be enabled or disabled individually by logical device (as shown in Example 3-7 on page 53). It might be desirable to configure some, but not all, logical paths to a device with the support enabled.

Example 3-6 AIX: enable alternate pathing support - all

azov.almaden.ibm.com:/tmp# lsdev -Cctapermt0 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt1 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt2 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt3 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)smc0 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc1 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc2 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)smc3 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)

azov.almaden.ibm.com:/tmp# /usr/lpp/Atape/instAtape -aSetting alternate pathing support on rmt0...rmt0 changedSetting alternate pathing support on smc0...smc0 changedSetting alternate pathing support on rmt1...rmt1 changedSetting alternate pathing support on smc1...


smc1 changedSetting alternate pathing support on rmt2...rmt2 changedSetting alternate pathing support on smc2...smc2 changedSetting alternate pathing support on rmt3...rmt3 changedSetting alternate pathing support on smc3...smc3 changedazov.almaden.ibm.com:/tmp# lsdev -Cctapermt0 Available 1Z-08-02-PRI IBM 3580 Ultrium Tape Drive (FCP)rmt1 Available 1Z-08-02-PRI IBM 3580 Ultrium Tape Drive (FCP)rmt2 Available 1D-08-02-ALT IBM 3580 Ultrium Tape Drive (FCP)rmt3 Available 1D-08-02-ALT IBM 3580 Ultrium Tape Drive (FCP)smc0 Available 1Z-08-02-PRI IBM 3582 Library Medium Changer (FCP)smc1 Available 1Z-08-02-ALT IBM 3582 Library Medium Changer (FCP)smc2 Available 1D-08-02-ALT IBM 3582 Library Medium Changer (FCP)smc3 Available 1D-08-02-ALT IBM 3582 Library Medium Changer (FCP)azov.almaden.ibm.com:/tmp#

The /usr/lpp/Atape/instAtape -a command unconfigures all devices that have alternate pathing set to No and reconfigures all devices, setting alternate pathing to Yes. After running the command, you see that rmt0 and rmt1 are set to the primary path (PRI) to the drives, and rmt2 and rmt3 are alternate (ALT) paths. Similarly, for the medium changer, smc0 is the primary path and the others are alternate.

Example 3-7 AIX: enable alternate pathing support

azov.almaden.ibm.com:/tmp# lsdev -Cctapermt0 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt1 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt2 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt3 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)smc0 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc1 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc2 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)smc3 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)azov.almaden.ibm.com:/tmp# chdev -l rmt0 -aalt_pathing=yesrmt0 changedazov.almaden.ibm.com:/tmp# lsdev -Cctapermt0 Available 1Z-08-02-PRI IBM 3580 Ultrium Tape Drive (FCP)rmt1 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt2 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt3 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)smc0 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc1 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc2 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)smc3 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)azov.almaden.ibm.com:/tmp# chdev -l rmt2 -aalt_pathing=yesrmt2 changedazov.almaden.ibm.com:/tmp# lsdev -Cctapermt0 Available 1Z-08-02-PRI IBM 3580 Ultrium Tape Drive (FCP)rmt1 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt2 Available 1D-08-02-ALT IBM 3580 Ultrium Tape Drive (FCP)rmt3 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)smc0 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc1 Available 1Z-08-02 IBM 3582 Library Medium Changer (FCP)smc2 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)smc3 Available 1D-08-02 IBM 3582 Library Medium Changer (FCP)azov.almaden.ibm.com:/tmp#


Example 3-8 shows the devices files for all drives and all library medium changers. In the Tivoli Storage Manager path definitions, you can use all the primary devices files — /dev/smc0 for the library medium changer and /dev/rmt0 and /dev/rmt1 for the drives.

Example 3-8 AIX: lsdev

rmt0 Available 1Z-08-02-PRI IBM 3580 Ultrium Tape Drive (FCP)rmt1 Available 1Z-08-02-PRI IBM 3580 Ultrium Tape Drive (FCP)rmt2 Available 1D-08-02-ALT IBM 3580 Ultrium Tape Drive (FCP)rmt3 Available 1D-08-02-ALT IBM 3580 Ultrium Tape Drive (FCP)smc0 Available 1Z-08-02-PRI IBM 3582 Library Medium Changer (FCP)smc1 Available 1Z-08-02-ALT IBM 3582 Library Medium Changer (FCP)smc2 Available 1D-08-02-ALT IBM 3582 Library Medium Changer (FCP)smc3 Available 1D-08-02-ALT IBM 3582 Library Medium Changer (FCP)

3.2.3 Installing on Microsoft Windows 2000This section describes the steps that are required to install the IBM tape library medium changer and the driver on Microsoft Windows. For more information, see Part 7 in IBM Ultrium Device Drivers Installation and User’s Guide, GA32-0430.

To install the IBM tape library medium changer and driver on Microsoft Windows:

1. You can download the IBM tape device driver from:

ftp://ftp.software.ibm.com/storage/devdrvr/Windows/

2. After downloading the package, unzip all files into a directory.

After SAN zoning is configured so that the host has access to the drives, on the Windows 2000 server, you see the connected drives (IBMULT3580) and the library medium changer (IBM ULT3582) as shown in Figure 3-5.

Figure 3-5 Device Manager: Without IBM tape driver

Note: Beginning with V6.0.4.4, the IBM tape device drivers for Windows 2000 and Windows 2003 have been converged into a single install package with common inf files. Use this single package to install a driver on either operating system. The system detects which version of the driver binary files it needs to install. For Windows 2000 users, the Magstar® and Ultrium drivers have also been converged.



3. To use the IBM tape device driver, you need to update the driver for each drive. Right click the drive and select Properties, as shown in Figure 3-6.

Figure 3-6 Device Manager: Tape drive properties

4. Select the Driver tab and click Update Driver (as shown in Figure 3-7).

Figure 3-7 Device Manager: Tape drive update

5. Choose the option Display a list of known drivers for the device so that I can choose a specific driver (Figure 3-8 on page 56).


Figure 3-8 Device Manager: Tape drive update - choose a specific driver

6. On the next screen, as shown in Figure 3-9, select the option Have Disk.

Figure 3-9 Device Manager: Tape drive update - have a disk

7. Choose the exctape.inf in the directory that contains the unzipped files of the IBM tape device driver (Figure 3-10 on page 57) and click Open.


Figure 3-10 Device Manager: Tape drive update - select inf file

8. The output lists all available tape drive models. Select the required model. In this example, you would select the IBM 3580 Ultrium II drive with the extension for Tivoli Storage Manager, as shown in Figure 3-11.

9. Click Next.

Figure 3-11 Device Manager: Tape drive update - drive models


10.After the device driver update completes, repeat these steps, beginning with step 3 on page 55 to update all remaining tape drives.

After you have updated all the tape drive, you need to update the library medium changer. This example has two library medium changers devices, because we enabled the control path on both library drives.

To update the library medium changer:

1. Right click the medium changer and select Properties, as shown in Figure 3-12.

Figure 3-12 Device Manager: Tape medium changer update

2. Choose the Driver tab and select Update Driver (Figure 3-13 on page 59).

Important: With the introduction of V6.0.2.4 and later, two versions of the device driver are made available: one that prohibits multiple opens on a single tape drive and one that will allow multiple opens on a single tape drive. Drivers that prohibit multiple opens on a single tape drive are indicated (when presented by the Windows Plug and Play Device Manager during device configuration) with the text string '(for Tivoli Storage Manager)' in them. These drivers will use the file exctape.inf from the install package during installation. Drivers that allow multiple opens on a tape drive do not have the text string '(for Tivoli Storage Manager)' in them. These drivers will use the file magtape.inf from the install package during the installation.

IBM strongly recommends that you use the "for Tivoli Storage Manager" drivers whether or not you are a Tivoli customer to prevent a tape drive from being accessed by more than one process and potentially causing data to be corrupted or lost. However, if you are a customer that uses RSM, you will need to use the other driver and take steps to ensure that multiple uncoordinated opens to a tape drive do not occur.


Figure 3-13 Device Manager: Tape medium changer update

3. Choose the option Display a list of known drivers for the device so that I can choose a specific driver (Figure 3-14).

Figure 3-14 Device Manager: Tape medium changer update - choose a specific driver

4. On the screen that is shown in Figure 3-15 on page 60, select the option Have Disk.


Figure 3-15 Device Manager: Tape medium changer update - have a disk

5. Choose the exctape.inf in the directory that contains the unzipped files of the IBM tape device driver and click Open, as shown in Figure 3-16.

Figure 3-16 Device Manager: Tape medium changer update - choose directory

6. The output lists all the available tape library models. Select the required model. In this example, you would select IBM 3582 LTO Library, as shown in Figure 3-17 on page 61.


Figure 3-17 Device Manager: Tape medium changer update - models

7. After the device driver update completes, repeat this process to update all the remaining library medium changers.

8. When you have updated all library medium changers, reboot the server to activate the new device driver. After the reboot, check the Device Manager to verify that all devices are correctly configured, as shown in Figure 3-18.

Figure 3-18 Device Manager: With the IBM device driver

If the Tivoli Storage Manager device driver is also installed, you can open the Tivoli Storage Manager Management Console to display more information about the tape drives, as shown in Figure 3-19 on page 62.


Figure 3-19 MMC: Tivoli Storage Manager Device Driver menu

Figure 3-20 shows information about the two drives and two library medium changers. The tape \\.\Tape0 and the medium changer Changer0 have the same World Wide Name and the same SCSI ID (0). Only the LUN is different. This nomenclature is because the library medium changer is accessed through the tape drive

Figure 3-20 MMC: Tivoli Storage Manager Device Driver - Drive information

You use the device names (\\.\Tape0, \\.\Tape1) in the Tivoli Storage Manager drive path definition and \\.\Changer0 or \\.\Changer1 for the library definition.

You also use the Tivoli Storage Manager QUERY SAN command to check the library drives and medium changers (supported only with Tivoli Storage Manager V5.3). For more information, see Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.

Example 3-9 Query SAN

tsm: TONGA_1>q san

Device Vendor Product Serial Number DeviceType-------- -------- ---------------- ---------------- ------------------DRIVE IBM ULT3580-TD2 1110177214 Tape0LIBRARY IBM ULT3582-TL 0000013108231000 Changer0DRIVE IBM ULT3580-TD2 1110176223 Tape1LIBRARY IBM ULT3582-TL 0000013108231000 Changer1


3.2.4 Installing on LinuxThis section describes the steps that are required to create the tape library medium changer and the drive special files on Linux. For more information, see Part 5 in IBM Ultrium Device Drivers Installation and User’s Guide, GA32-0430.

If the drives are non-IBM drives, you need to use the Tivoli Storage Manager device driver. If they are IBM drives, use the IBMtape driver. In our IBM 3582 tape library are IBM drives, so we have to install the IBMtape driver. The IBMtape device driver for Linux is an installable kernel module that is supplied in an rpm package. The utility tools for IBMtape are supplied in a tar file. The IBMtapeutil package consists of IBMtapeutil, IBMtapeconfig, and the source files for IBMtapeutil. You can download the software from:

ftp://ftp.software.ibm.com/storage/devdrvr/Linux/

For Linux, download the IBMtape and the IBMtapeutil packages, and then follow these steps:

1. Install the packages as shown in Example 3-10 and Example 3-11.

Example 3-10 Linux: IBMtapeutil install

cadi:/tmp # tar -xvf ./IBMtapeutil.1.3.1.i386.tar.binIBMtapeutil.1.3.1/IBMtapeutil.1.3.1/IBMtapeconfigIBMtapeutil.1.3.1/IBMtapeutil.cIBMtapeutil.1.3.1/IBMtapeutil.hIBMtapeutil.1.3.1/makefileIBMtapeutil.1.3.1/IBMtapeutil.ReadMeIBMtapeutil.1.3.1/IBMtapeutilcadi:/tmp # cd IBMtapeutil.1.3.1/cadi:/tmp/IBMtapeutil.1.3.1 # make installcp -f IBMtapeutil /usr/bin/.cp -f IBMtapeconfig /usr/bin/.

Example 3-11 Linux: IBM tape driver install

cadi:/tmp # rpm -i ./IBMtape-2.0.5-2.6.5-7.147.i386.rpm.binInstalling IBMtapeIBMtape loaded

2. After the installation, check whether the devices are detected (Example 3-12).

Example 3-12 Linux: ls -l /dev/IBMtape*

cadi:~ # ls -l /dev/IBMtap*crw-rw-rw- 1 root root 253, 0 Apr 8 05:04 /dev/IBMtape0crw-rw-rw- 1 root root 253, 256 Apr 8 05:04 /dev/IBMtape0ncrw-rw-rw- 1 root root 253, 1 Apr 8 05:04 /dev/IBMtape1crw-rw-rw- 1 root root 253, 257 Apr 8 05:04 /dev/IBMtape1ncadi:~ #

3. Check the library medium changer, as shown in Example 3-13.

Example 3-13 Linux: ls -l /dev/IBMchanger*

cadi:~ # ls -l /dev/IBMchanger*[root@diomede root]# ls -l /dev/IBMchanger*crw-rw-rw- 1 root root 252, 128 Mar 8 16:15 /dev/IBMchanger0cadi:~ #



4. To enable the alternate pathing support on Linux, stop the IBMtape daemon (IBMtaped stop) and remove the IBMtape modules from the kernel with the rmmod IBMtape command.

Add the following lines:

– options IBMtape alternate_pathing=1 to enable the alternate pathing support for the library controller

– options IBMtape alternate_pathing=1 dpf_keys="abcdefghijklmnop" to enable the alternate pathing support for the drives into the /etc/modules.conf file.

Figure 3-14 shows these steps.

Example 3-14 Linux: /etc/modules.conf

cadi:~ # IBMtaped stopcadi:~ # rmmod IBMtapecadi:~ # vi /etc/modules.confalias eth0 e1000alias eth1 tulipalias scsi_hostadapter0 qla2300_confalias scsi_hostadapter1 qla2300alias sound-slot-0 i810_audiopost-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :alias usb-controller usb-uhcialias usb-controller1 ehci-hcdpost-remove qla2200 rmmod qla2200_confpost-remove qla2300 rmmod qla2300_confoptions scsi_mod max_scsi_luns=128options IBMtape alternate_pathing=1options IBMtape alternate_pathing=1 dpf_keys="abcdefghijklmnop"

5. Load the updated IBMtape module into the running kernel (Figure 3-15).

Example 3-15 Linux: IBMtape daemon start

cadi:~ # depmoddepmod: *** Unresolved symbols in /lib/modules/2.4.21-15.ELsmp/kernel/drivers/scsi/IBMtape.ocadi:~ # modprobe IBMtapeWarning: loading /lib/modules/2.4.21-15.ELsmp/kernel/drivers/scsi/IBMtape.o will taint the kernel: non-GPL license - USER LICENSE AGREEMENT FOR IBM DEVICE DRIVERS See http://www.tux.org/lkml/#export-tainted for information about tainted modulesModule IBMtape loaded, with warningscadi:~ # IBMtapedcadi:~ #

You can ignore the following message after the depmod command.

Unresolved symbols in /lib/modules/2.4.21-15.ELsmp/kernel/drivers/scsi/IBMtape.o


6. To check if the IBMtape driver has recognized multiple control paths for the library, view the /proc/scsi/IBMchanger file (Figure 3-16). If Primary and Alternate are listed in the FO Path column, you have successfully enabled control path failover feature for your library. If the column shows NA, then control path failover is not enabled.

Example 3-16 Linux: /proc/scsi/IBMchanger

cadi:~ # cat /proc/scsi/IBMchangerIBMtape version: 1.5.3IBMtape major number: 252Attached Changer Devices:Number Model SN HBA FO Path0 ULT3582-TL 0000013108231000 QLogic Fibre Channel 2300 Primary1 ULT3582-TL 0000013108231000 QLogic Fibre Channel 2300 Alternatecadi:~ #

Example 3-17 shows two library medium changers. However, this example has only one physical library controller because the control path was enabled on both tape drives as shown in Figure 3-2 on page 45. The Linux IBMtape device driver alternate pathing support configures multiple physical control paths to the same logical library within the device driver and provides automatic failover to an alternate control path when a permanent error occurs on one path.

Example 3-17 Linux: ls -l /dev/IBMchanger*

cadi:~ # ls -l /dev/IBMchanger*[root@diomede root]# ls -l /dev/IBMchanger*crw-rw-rw- 1 root root 252, 128 Mar 8 16:15 /dev/IBMchanger0crw-rw-rw- 1 root root 252, 128 Mar 8 16:15 /dev/IBMchanger1cadi:~ #

If there are no /dev/IBMtape* devices or /dev/IBMchanger*, reboot the server. After the reboot, check the files /proc/scsi/IBMtape (Example 3-18) and /proc/scsi/IBMchanger to see if the drives/medium changer are correctly detected. Otherwise, check the SAN connections and the SAN zoning.

Example 3-18 Linux: /proc/scsi/IBMtape

cadi:~ # more /proc/scsi/IBMtapeIBMtape version: 2.0.5IBMtape major number: 253Attached Tape Devices:Number Model SN HBA FO Path0 03592J1A 000001300117 qla2xxx NA1 03592J1A 000001300114 qla2xxx NA

Important: The library control path failover feature code must be installed on the library before enabling the alternate pathing support in the Linux IBMtape device driver.


7. You can reconfigure the IBM tape devices with the IBMtapeconfig script. This removes all the existing /dev/IBMtape and /dev/IBMchanger special files, and creates new ones based on the information in /proc/scsi/IBMtape and /proc/scsi/IBMchanger. Example 3-19 shows the command output.

Example 3-19 Linux: IBMtapeconfig

cadi:~ # IBMtapeconfig

Creating IBMtape special files major number: 253 Attached devices: 0 1 mknod -m 0666 /dev/IBMtape0 c 253 0 mknod -m 0666 /dev/IBMtape0n c 253 256 mknod -m 0666 /dev/IBMtape1 c 253 1 mknod -m 0666 /dev/IBMtape1n c 253 257

Creating IBMchanger special files major number: 253 No attached devices.

Each tape device has a set of special files that provides access to the same physical drive but provides different attributes. Table 3-2 shows the attributes of the special files.

Table 3-2 Linux: Special files for IBM tape devices

You use these /dev/IBMtape* special devices files in the Tivoli Storage Manager server drive path definition, as discussed in 3.3, “Tivoli Storage Manager configuration” on page 73.

Example 3-20 Linux: IBMtapeutil

cadi: # IBMtapeutil

IBMtapeutil for Linux, Version 1.3.1, Sept. 14, 2004========================================= 1. Tape 2. Changer 3. Quit=========================================

Enter your choice: 1-------------------------- General Commands: ----------------------------- 1. Open a Device 9. Mode Sense Pag 2. Close a Device 10. Switch Tape/Changer Devic 3. Inquiry 11. Create Special Files 4. Test Unit Ready 12. Query Driver Version 5. Reserve Device 13. Query Device Path 6. Release Device 14. Display All Paths

Important: If a new device is attached to a running system, reboot before running the IBMtapeconfig script.

Special file name Rewind on close

/dev/IBMtape* Yes

/dev/IBMtape*n No

Tip: You can test your drives with the IBMtapeutil program, as shown in Example 3-20.


7. Request Sense 15. Enable A Path 8. Log Sense Page 16. Disable A Path Q. Quit IBMtapeutil--------------------------- Tape Commands: -------------------------------- 20. Rewind 33. Set Block Size 21. Forward Space Filemarks 34. Retension Tape 22. Backward Space Filemarks 35. Query/Set Tape Position 23. Forward Space Records 36. Query Tape Status 24. Backward Space Records 37. Load Tape 25. FSFM 38. Unload Tape 26. BSFM 39. Lock Tape Drive Door 27. Space to End of Data 40. Unlock Tape Drive Door 28. Read and Write Tests 41. Take Tape Offline 29. Write Filemarks 42. Enable/Disable Compression 30. Read or Write Files 43. Flush Drive's Buffer 31. Erase 44. Self Test 32. Reset Drive 45. Display Message--------------------------- IBMtape Commands: ------------------------------- 46. Query Sense 52. Locate Tape Position 47. Query Inquiry 53. Read Tape Position 48. Query/Set Tape Parameters 54. Query Mtdevice Number 49. Query/Set Tape Position 55. Synchronize Buffers 50. Query/Set MT/ST Mode 56. List Tape Filemarks 51. Report Density Support--------------------------- Service Aid Commands: ------------------------- 70. Dump Device 74. Read Persistent Reservation Keys 71. Force Dump 75. Read Persistent Reservations 72. Load Ucode 76. Register Persistent Reservation Key 73. Reset Drive 77. Remove Persistent Reservation 78. Clear All Persistent Registrations--------------------------------------------------------------------------- 99. Back To Main Menu

Enter Selection: 1

Enter device name (<enter> for /dev/IBMtape0):Select mode (<enter> or 1=Read/Write, 2=Read Only, 3=Write Only, 4=Append):

Opening device......

Note: Beginning with IBMtape V1.2.5, the IBMtape device driver provides an error diagnostic daemon (IBMtaped) that provides error logging and tracing of the IBMtape device driver. When drive dumps, log sense data, or SIM/MIMM error information are created by the tape drive, the daemon retrieves that data automatically and saves it to disk on the Linux system.

We recommend that you leave this daemon enabled at all times.


3.2.5 Installing on SUN SolarisThis section describes the steps that are required to create the tape library medium changer and the drive special files on SUN Solaris. For more information, see Part 6 of IBM Ultrium Device Drivers Installation and User’s Guide, GA32-0430.

If you have non-IBM drives, you would use the Tivoli Storage Manager device driver. If you have IBM drives, use the IBMtape driver. We have IBM drives in our IBM 3494 library, so we have to install the IBM tape driver. You can download the package from:

ftp://ftp.software.ibm.com/storage/devdrvr/Solaris/

1. Install the IBMtape package as shown in Example 3-22 and record this information. You will need this information later in the installation.

Example 3-21 Solaris: ls -l /dev/rmt/*st before IBMtape installation

bash-2.03# ls -l /dev/rmt/*stlrwxrwxrwx 1 root other 57 Apr 8 13:49 /dev/rmt/0st -> ../../devices/pci@1f,4000/fibre-channel@2/st@36,0:stlrwxrwxrwx 1 root other 57 Apr 8 13:49 /dev/rmt/1st -> ../../devices/pci@1f,4000/fibre-channel@2/st@37,0:st

2. Install the IBMtape package as shown in Example 3-22.

Example 3-22 Solaris: IBM tape driver install process

bash-2.03# pkgadd -d ./IBMtape.4.1.1.4.bin

The following packages are available: 1 IBMtape IBM Tape & Medium Changer Device Driver 4.1.1.4 (sparc) 4.1.1.4

Select package(s) you wish to process (or 'all' to processall packages). (default: all) [?,??,q]: 1

Processing package instance <IBMtape> from </tmp/IBMtape.4.1.1.4.bin>

IBM Tape & Medium Changer Device Driver 4.1.1.4(sparc) 4.1.1.4

IBM Tape & Medium Changer Device Driver for Sun Solaris 7, 8, 9 and 10 Version 4.1.1.4

Contains Licensed Internal Code Licensed Materials - Property of IBM

(C) Copyright 1994-. IBM Corporation All Rights Reserved Portions (C) 1994 Sun Microsystems

US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM

(R) IBM is a registered trademark of IBM Corporation (R) Solaris is a registered trademark of Sun Microsystems

Attention: Before installing, make a backup of the system, list all current device special files, and find the SCSI addressees with which they are associated.



Using </opt> as the package base directory.## Processing package information.## Processing system information. 1 package pathname is already properly installed.## Verifying disk space requirements.## Checking for conflicts with packages already installed.## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-userpermission during the process of installing this package.

Do you want to continue with the installation of <IBMtape> [y,n,?] y

Installing IBM Tape & Medium Changer Device Driver 4.1.1.4 as <IBMtape>

## Installing part 1 of 1./opt/IBMtape/IBMtape.conf/opt/IBMtape/diags_info/opt/IBMtape/tapelist/opt/IBMtape/tapeutil/opt/IBMtape/tapeutil.c/opt/IBMtape/tmd/opt/IBMtape/tmd.conf/usr/include/sys/oldtape.h/usr/include/sys/smc.h/usr/include/sys/st.h/usr/include/sys/svc.h/usr/kernel/drv/IBMtape/usr/kernel/drv/sparcv9/IBMtape[ verifying class <none> ]## Executing postinstall script.## The /usr/kernel/drv/IBMtape.conf file already exists.## It will be preserved as the current configuration file## for the IBM Tape & Medium Changer Device Driver.

## Stopping any running instances of tape monitor daemon...

## Installing the /etc/tmd.conf file.

## Creating the directory of /var/opt/IBMtape.

## The /usr/kernel/drv/IBMtape.conf already contains## a control node entry. It will be preserved.

## Adding new tmd entry to /etc/inittab...## Loading IBM Tape & Medium Changer Device Driver.

## Starting IBMtape Monitor Daemon (tmd)...

Installation of <IBMtape> was successful.

3. Edit the file the /usr/kernel/drv/IBMtape.conf to include the drive information (Example 3-23). You can use the information from Example 3-21 on page 68.

Example 3-23 Solaris: /usr/kernel/drv/IBMtape.conf

bash-2.03# cat /usr/kernel/drv/IBMtape.conf

##############################################################################################################################################################


## #### IBM SCSI Tape & Medium Changer Device Driver for Solaris 7, 8, 9 and 10 #### (C) COPYRIGHT IBM Corporation, 1994 - #### #### IBMtape.conf - Configuration File #### Licensed Materials - Property of IBM #### All Rights Reserved #### #### US Government Users Restricted Rights - Use, duplication, or #### disclosure restricted by GSA ADP Schedule Contract with IBM Corp. #### ################################################################################################################################################################

#name="IBMtape"# class="scsi"# target=0 lun=0# block_size=0# buffering=1# immediate=0# trailer=0# sili=0;

...



name="IBMtape" parent="pseudo" instance=16383;

# An example entry for high numbers of target and lun# name="IBMtape" class="scsi" target=200 lun=3;

# An example entry for QLogic HBA running qla HBA driver# name="IBMtape" parent="qla2100" target=0; for qla2100 only# name="IBMtape" parent="qla2200" target=0; for qla2200 only# name="IBMtape" parent="qla2300" target=0; for qla2300 only

# An example entry for AMCC JNI HBA# name="IBMtape" parent="jnic146x" target=0;

# An example entry for Emulex HBA# name="IBMtape" parent="lpfc" target=0;

# An example entry for Sun Branded FC HBA


# name="IBMtape" parent="fp" lun=0 fc-port-wwn="xxxxxxxxxxxxxxxx";# name="IBMtape" parent="fp" lun=1 fc-port-wwn="xxxxxxxxxxxxxxxx";

name="IBMtape" parent="qla2300" target=36;name="IBMtape" parent="qla2300" target=37;

4. If you do not know the SCSI information, create an IBMtape.conf as shown in Example 3-24 with all SCSI target and LUN combinations (0-255).

Example 3-24 Solaris: IBMtape.conf with all targets/luns

....name="IBMtape" class="scsi" target=8 lun=19 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;name="IBMtape" class="scsi" target=8 lun=20 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;name="IBMtape" class="scsi" target=8 lun=21 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;....name="IBMtape" class="scsi" target=8 lun=255 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;name="IBMtape" class="scsi" target=9 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;name="IBMtape" class="scsi" target=9 lun=1 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;...

5. Configuration settings are applied only at boot time or when IBMtape is unloaded manually and then reloaded into memory. After changing the configuration settings in IBMtape.conf, reboot the system to activate the changes. Alternatively, make sure that no IBMtape-owned devices are in use and run the commands that are shown in Example 3-25.

Example 3-25 Solaris: Reload IBMtape

/opt/IBMtape/tmd -s/usr/sbin/rem_drv IBMtape /usr/sbin/add_drv -m ’* 0666 bin bin’ IBMtape/opt/IBMtape/tmd

6. The drives are now configured. You can view the device special files with the ls command (Example 3-26).

Example 3-26 Solaris: ls -l /dev/rmt/*st after IBMtape installation

bash-2.03# ls -l /dev/rmt/*stlrwxrwxrwx 1 root other 57 Apr 8 13:49 /dev/rmt/0st -> ../../devices/pci@1f,4000/fibre-channel@2/IBMtape@36,0:stlrwxrwxrwx 1 root other 57 Apr 8 13:49 /dev/rmt/1st -> ../../devices/pci@1f,4000/fibre-channel@2/IBMtape@37,0:stbash-2.03#

Note: IBM requires that the Solaris native SCSI tape device driver st be configured (/kernel/drv/st.conf) so that it does not attempt to allocate SCSI targets that are controlled by IBMtape (/usr/kernel/drv/IBMtape.conf). See “Preventing Conflicts with Other Device Drivers” in IBM TotalStorage Tape Device Drivers Installation and User’s Guide, GC35-0154.


This command indicates that the IBMtape device driver is now in use for these devices, compared with Example 3-21 on page 68. To view the special file for the library medium changer, you can also use the ls command (Example 3-27).

Example 3-27 Solaris: ls -l /dev/rmt/*smc after IBMtape installation

bash-2.03# ls -l /dev/rmt/*smclrwxrwxrwx 1 root other 57 Apr 8 13:49 /dev/rmt/0smc -> ../../devices/pci@1f,4000/fibre-channel@2/IBMtape@36,1:stbash-2.03#

7. You can now define the drive paths using these device special files (/dev/rmt/0st, /dev/rmt/1st) and the device special file for the library medium changer (/dev/rmt/0smc) on the Tivoli Storage Manager Server.

8. To display more information about the drives, use the tapelist command (Example 3-28).

Example 3-28 Solaris: tapelist

bash-2.03# /usr/bin/tapelistIBM Tape Device Information : Instance : 6248 Special File : /dev/rmt/0st Device : 03592J1A Serial Number : 000001300117 TGT/LUN : 54/0 Ucode : 04E6 World Wide NN : 50050763020000C5 World Wide PN : 50050763024000C5 Dev Phy Path : /devices/pci@1f,4000/fibre-channel@2/IBMtape@36,0 Path Type : N/A

--- more ---

Instance : 6254 Special File : /dev/rmt/1st Device : 03592J1A Serial Number : 000001300114 TGT/LUN : 55/0 Ucode : 04E6 World Wide NN : 50050763020000C7 World Wide PN : 50050763028000C7 Dev Phy Path : /devices/pci@1f,4000/fibre-channel@2/IBMtape@37,0 Path Type : N/A

Note: By default, alternate pathing support is enabled automatically on installation of the IBMtape Solaris device driver. The Solaris IBMtape device driver also provides a driver configuration parameter to enable or disable the library control path failover (CPF) support. For more information, see Part 6 in IBM Ultrium Device Drivers Installation and User’s Guide, GA32-0430.


3.3 Tivoli Storage Manager configurationThis section shows how to set up library sharing with an IBM 3582 Tape Library. In our test environment, the Tivoli Storage Manager Library Manager is installed on the AIX server AZOV and the Library Client on the Windows server TONGA (as shown in Figure 3-21). We assume the Tivoli Storage Manager server is installed and operational on both the Library Client and Library Manager.

For more information about this topic, see:

� IBM Tivoli Storage Manager for AIX Installation Guide V5.3, GC32-1597

� IBM Tivoli Storage Manager Implementation Guide, SG24-5416

Figure 3-21 Lab configuration overview

3.3.1 With the Tivoli Storage Manager Administration CenterBecause we are using Tivoli Storage Manager V5.3, we can use the Tivoli Storage Manager Administration Center for the configuration.

Configuring the Tivoli Storage Manager Library Manager

Server-to-server communication is required between the Library Manager and Library Client. If you have not already previously configured these settings, use the commands discussed in “Configuring server-to-server communication on the Library Manager” on page 91.

SAN

LAN

Server-to-servercommunication

Data Flow

Library Control

Data Flow

Tivoli Storage ManagerLibrary Manager

Tivoli Storage ManagerLibrary Client

SCSITapeLibrary

WindowsTONGAIBM 3582

2 * LTO2 FC drives

AIXAZOV


From the Administration Center:

1. Choose Storage Devices from the work items menu. You see all installed Tivoli Storage Manager servers and libraries (Figure 3-22, “Library Manager: Query Library” on page 74). Our installed Tivoli Storage Manager servers, AZOV_1 and TONGA_1, are the Library Manager and Library Client, respectively. Select the Tivoli Storage Manager server that will act as the Library Manager. In this example, choose AZOV.

Figure 3-22 Library Manager: Query Library

2. A wizard is provided to define the library, library paths, tape drives, and the tape drive paths. To start the wizard, choose Create a Library and click Go.

We recommend using a Tivoli Storage Manager Administrative Interface session (dsmadmc) in console mode to monitor Tivoli Storage Manager activities as they occur, as shown in Example 3-29.

Example 3-29 Tivoli Storage Manager console window

azov.almaden.ibm.com:/usr/tivoli/tsm/client/ba/bin# dsmadmc -consolemodeIBM Tivoli Storage ManagerCommand Line Administrative Interface - Version 5, Release 3, Level 0.0(c) Copyright by IBM Corporation and other(s) 1990, 2004. All Rights Reserved.Enter your user id: adminEnter your password:Session established with server AZOV_1: AIX-RS/6000 Server Version 5, Release 3, Level 0.0 Server date/time: 03/17/05 15:24:15 Last access: 03/17/05 15:14:43

ANR2017I Administrator ADMIN issued command: QUERY SESSION

3. On the first screen, choose a name for the library. (We use 3582 in this example.) Specify the library type, which in this case is SCSI, as shown in Figure 3-23 on page 75.

Tip: When using the Administration Center, click Next to progress through the steps after you have completed the options for each screen. In general, our instructions omit this step.


Figure 3-23 Library Manager: enter name and type

4. Enter the device special file name for the library medium changer (Figure 3-24).

Figure 3-24 Library Manager: Define library changer

5. To find this device file name, you can use the QUERY SAN command, as shown in Example 3-30, or use an operating system command to find the name of this device file. Note that two library medium changer devices are displayed, because the alternate control path feature is enabled on each drive, which sets up an alternate path to the library.

Example 3-30 QUERY SAN on the Library Manager

tsm: AZOV_1>query san

Device Vendor Product Serial Number DeviceType-------- -------- ---------------- ---------------- ------------------DRIVE IBM ULT3580-TD2 1110176223 /dev/rmt0LIBRARY IBM ULT3582-TL 0000013108231000 /dev/smc0DRIVE IBM ULT3580-TD2 1110177214 /dev/rmt1LIBRARY IBM ULT3582-TL 0000013108231000 /dev/smc1


6. Add the drives, as shown in Figure 3-25.

Figure 3-25 Library Manager: Add drive

7. Enter the drive name and the device special file name for each drive (Figure 3-26). Either use the Tivoli Storage Manager QUERY SAN command (Example 3-30 on page 75) or use an operating system command to find the name of this device file.

Figure 3-26 Library Manager: Define path for drive one

In most cases, the element address is detected automatically, so you need not specify it for all supported SAN-attached libraries (Figure 3-27 on page 77).

Restriction: The QUERY SAN command requires Tivoli Storage Manager V5.3 and the Tivoli Storage Manager server option SANDISCOVERY. For more details, see Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.

Attention: Be sure to enable the option Allow other servers and storage agents to use this library.


Figure 3-27 Library Manager: Define path for drive two

Now, both drives are now defined and displayed (Figure 3-28). If the device name (special device file name) is incorrect, you can change it now.

Figure 3-28 Library Manager: Drives and paths

8. The wizard shows information about the defined library and drives (Figure 3-29 on page 78). If the configuration is correct, return to the main screen, which now displays the newly added library, as shown in Figure 3-30 on page 78.


Figure 3-29 Library Manager: Library wizard summary

Figure 3-30 Library Manager: Shared library defined

9. To use this library, you have to define a new device class. To display the existing device classes, select View Device Classes and click Go as shown in Figure 3-31 on page 79.


Figure 3-31 Library Manager: Query all device classes

10.The available device classes for the Tivoli Storage Manager server AZOV_1 are displayed. You have to create a new one for the library. Select Create a Device Class, as shown in Figure 3-32.

Figure 3-32 Library Manager: Defined device classes

11.This action starts another wizard. Select the device type. We are using an LTO library with Ultrium cartridges, so select this entry from the list (Figure 3-33).

Figure 3-33 Library Manager: Wizard for the device class definition

12.Enter a name for this device class (LTO2C in this example) and select the library for the device class. In this example, it is 3582, as shown in Figure 3-34 on page 80.


Figure 3-34 Library Manager: Device class name and library assortment

The device class is now defined and ready for use, as shown in Figure 3-35.

Figure 3-35 Library Manager: All defined device classes


You can now check in the library volumes.

1. Select the library and choose Modify Library (Figure 3-36).

Figure 3-36 Library Manager: Library settings

2. Click Volumes on the left-hand side, and select Add Volumes, as shown in Figure 3-37.

Figure 3-37 Library Manager: Add volumes

3. You might have to scroll down on the browser window to see the next panel. Choose whether the volumes are labeled. If you do not know whether the volumes have labels, you can specify this, and Tivoli Storage Manager will read each volume to see if it has a label (Figure 3-38 on page 82).


Figure 3-38 Library Manager: Are the volumes labeled

4. Specify location of the volumes (Figure 3-39). In this configuration, all volumes are already loaded in the library’s slots. So, you can choose the second option. If the volumes are in the library’s I/O port or if you want to add only one volume, select the corresponding option.

Figure 3-39 Library Manager: Where are the volumes


5. In Figure 3-40 you define the label source to write the label on the tape. Typically, you can use the barcode reader to detect the volume labels as shown. If the volumes have previously been used or mislabeled, you should specify to Overwrite existing volume labels. If you do not use this option and the volumes are already labeled, the Tivoli Storage Manager ANR8807W message occurs, as shown in Example 3-31, and the volume is not checked in.

Example 3-31 Library volumes are already labeled

LABEL libvol 3582 search=yes labelsource=barcode overwrite=NO checkin=SCRATCH WAITTIME=0Process 7 for LABEL LIBVOLUME started in the BACKGROUND at 09:57:52. ANR8807W Could not write label 020AKK on the volume in drive DRIVE1 (/dev/rmt0) of library 3582 because volume is already labelled 020AKK.

6. Figure 3-40 shows the output after labelling the volume. Typically a new or empty volume can be checked in as a scratch volume. Private specifies that the volume is a private volume that is mounted only when it is requested by name. Scratch specifies that the volume is a new scratch volume. This volume can be mounted to satisfy scratch mount requests during either data storage or export operations.

Figure 3-40 Library Manager: Check in libvolumes options

Attention: If a volume already has an entry in the volume history, you cannot check it in as a scratch volume.


7. Figure 3-41 shows the wait time option, which specifies the number of minutes that the server waits for a response to a library request. Specify a value in the range of 0 to 9999. If you want to be prompted by the server, specify a wait time greater than zero. The default value is 60 minutes.

For example, suppose the server prompts you to insert a tape into the entry or exit port of a library. If you specified a wait time of 60 minutes, the server issues a request and waits 60 minutes for you to reply. Suppose, on the other hand, you specify a wait time of zero. If you have already inserted a tape, a wait time of zero causes the operation to continue without prompting. If you have not inserted a tape, a wait time of zero causes the operation to fail.

Figure 3-41 Library Manager: Check in waittime

After all the options are completed, the check in process starts automatically, as shown in Figure 3-42.

Figure 3-42 Library Manager: Check in summary

Attention: Each volume that is used by a Tivoli Storage Manager server for any purpose must have a unique name. This requirement applies to all volumes, whether the volumes are used for storage pools or used for operations such as database backup or export. In a library sharing environment, this applies to all connected libraries and Tivoli Storage Manager servers.

Tip: A REPLY command is no longer required (Tivoli Storage Manager V5.3) if you specify a wait time of zero using the optional WAITTIME parameter on the CHECKIN LIBVOLUME or LABEL LIBVOLUME command. The default wait time is 60 minutes.


8. Monitor the progress of the process on the administrative console window, as shown in Example 3-32.

Example 3-32 Output of the label libvolume command

ANR2017I Administrator ADMIN issued command: LABEL libvol 3582 search=yes labelsource=barcode overwrite=YES checkin=SCRATCH WAITTIME=0 (SESSION: 381)ANR0984I Process 7 for LABEL LIBVOLUME started in the BACKGROUND at 10:45:02. (SESSION: 381, PROCESS: 7)ANR8799I LABEL LIBVOLUME: Operation for library 3582 started as process 11. (SESSION: 381, PROCESS: 7)ANR8810I Volume 020AKK has been labeled in library 3582. (SESSION: 381, PROCESS: 7)ANR8810I Volume 021AKK has been labeled in library 3582. (SESSION: 381, PROCESS: 7)ANR8810I Volume 023AKK has been labeled in library 3582. (SESSION: 381, PROCESS: 7)ANR8810I Volume 026AKK has been labeled in library 3582. (SESSION: 381, PROCESS: 7)ANR8810I Volume 028AKK has been labeled in library 3582. (SESSION: 381, PROCESS: 7)ANR8810I Volume 029AKK has been labeled in library 3582. (SESSION: 381, PROCESS: 7)ANR8810I Volume 030AKK has been labeled in library 3582. (SESSION: 381, PROCESS: 7)ANR8810I Volume 031AKK has been labeled in library 3582. (SESSION: 381, PROCESS: 7)ANR8810I Volume 034AKK has been labeled in library 3582. (SESSION: 381, PROCESS: 7)ANR8801I LABEL LIBVOLUME process 11 for library 3582 completed; 9 volume(s) labelled, 9 volume(s) checked-in. (SESSION: 381, PROCESS: 7)ANR0985I Process 11 for LABEL LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 10:54:07. (SESSION: 381, PROCESS:7)

Figure 3-43 shows the newly checked in volumes.

Figure 3-43 Library Manager: Query libvolumes

Configuring the Tivoli Storage Manager Library ClientThe library is now defined for the Library Manager and can be used for normal operations on that Tivoli Storage Manager server. You now have to define the same library to the Library Client, so that it can be shared.

Server-to-server communication is required between the Library Manager and Library Client. If you have not already previously configured these settings, use the commands that are described in “Configuring server-to-server communication on the Library Client” on page 92.


To begin the library configuration:

1. Select the Library Client, TONGA_1, and choose Create a Library, as shown in Figure 3-44.

Figure 3-44 Library Client: Create the library

2. Use the same library name as defined on the Library Manager (3582 in this case, as in Figure 3-23 on page 75), and select Shared Library type, as shown in Figure 3-45.

Figure 3-45 Library Client: Create library wizard


3. Select the name of the Library Manager, AZOV_1, as shown in Figure 3-46.

Figure 3-46 Library Client: Define the primary Library Manager

4. Add the drives using the device names as they appear to the Library Client.

Figure 3-47 shows all the available drives for this library. For every drive, you have to enter the Device Name (device special file name) for the Library Client. To find this name, we can use the QUERY SAN command (as shown in Example 3-33). This example uses a Windows Tivoli Storage Manager Library Client. Thus, the device name is in a different format from AIX. You use the same drive names, matching up the serial numbers, as discussed in the section on AIX (Example 3-30 on page 75).

Example 3-33 QUERY SAN on the Library Client

tsm: TONGA_1>query san

Device Vendor Product Serial Number DeviceType-------- -------- ---------------- ---------------- ------------------DRIVE IBM ULT3580-TD2 1110176223 Tape0LIBRARY IBM ULT3582-TL 0000013108231000 Changer0DRIVE IBM ULT3580-TD2 1110177214 Tape1LIBRARY IBM ULT3582-TL 0000013108231000 Changer1

Figure 3-47 Library Client: Define path for the shared drives


Figure 3-48 shows the wizard to update the device name for one drive.

Figure 3-48 Library Client: Define path for drive one

Figure 3-49 shows the drives with the device names entered.

Figure 3-49 Library Client: Path for both drives defined

5. Before you can use the drives in this shared library, you have to define a device class to point to this library. The Library Client’s device class definition has to be compatible with the device class definition on the Library Manager. The device type and recording format need to be the same on both Tivoli Storage Manager servers. Figure 3-50 on page 89 shows the device class that we defined for the Tivoli Storage Manager Library Client TONGA_1. It matches the device class that was defined for our Library Manager in Figure 3-35 on page 80.

Tip: If SAN Discovery is enabled (see Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253), you can enter any name for the device name. On the first use of this drive, Tivoli Storage Manager tries to find the correct drive for you and changes the device name to the correct one.


Figure 3-50 Library Client: Device class definitions

6. You can now check the library on the Library Client. For this test, backup the Library Client’s Tivoli Storage Manager database on this shared library using the BACKUP DB command. Example 3-34 shows the activity log on the Library Client and Example 3-35 on page 90 shows the activity log on the Library Manager. You can see the processes initiated on both servers, using server-to-server communication.

Example 3-34 Library Client: activity log during a backup database on the Library Client

ANR2017I Administrator ADMIN issued command: BACKUP DB dev=LTO2C t=f (SESSION: 390)ANR0984I Process 14 for DATABASE BACKUP started in the BACKGROUND at 11:21:51. (SESSION: 390, PROCESS: 14)ANR2280I Full database backup started as process 14. (SESSION: 390, PROCESS: 14)ANR0408I Session 391 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 390)ANR0409I Session 391 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 390)ANR0408I Session 392 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 390)ANR0409I Session 392 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 390)ANR8337I LTO volume 021AKK mounted in drive DRIVE1 (\\.\Tape0). (SESSION: 390)ANR0511I Session 390 opened output volume 021AKK. (SESSION: 390)ANR1360I Output volume 021AKK opened (sequence number 1). (SESSION: 390)ANR1361I Output volume 021AKK closed. (SESSION: 390)ANR0514I Session 390 closed volume 021AKK. (SESSION: 390)ANR0408I Session 393 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 390)ANR0409I Session 393 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 390)

Important: The device type and recording format of the device class needs to be the same on Library Manager and Library Client.


ANR0408I Session 395 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 395)ANR0408I Session 394 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 390)ANR0409I Session 394 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 390)ANR4550I Full database backup (process 14) complete, 396 pages copied. (SESSION: 390, PROCESS: 14)ANR0985I Process 14 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 11:22:29. (SESSION: 390, PROCESS: 14)ANR8336I Verifying label of LTO volume 021AKK in drive DRIVE1 (\\.\Tape0). (SESSION: 390)ANR8468I LTO volume 021AKK dismounted from drive DRIVE1 (\\.\Tape0) in library 3582. (SESSION: 390)ANR0409I Session 395 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 395)

Example 3-35 Library Manager: activity log during a backup database on the Library Client

ANR0408I Session 390 started for server TONGA_1 (Windows) (Tcp/Ip) for library sharing. (SESSION: 390)ANR0409I Session 390 ended for server TONGA_1 (Windows). (SESSION: 390)ANR0408I Session 391 started for server TONGA_1 (Windows) (Tcp/Ip) for library sharing. (SESSION: 391)ANR8337I LTO volume 021AKK mounted in drive DRIVE1 (/dev/rmt0). (SESSION: 391)ANR9791I Volume 021AKK in library 3582 ownership is changing from AZOV_1 to TONGA_1. (SESSION: 391)ANR0409I Session 391 ended for server TONGA_1 (Windows). (SESSION: 391)ANR0408I Session 392 started for server TONGA_1 (Windows) (Tcp/Ip) for library sharing. (SESSION: 392)ANR0408I Session 393 started for server TONGA_1 (Windows) (Tcp/Ip) for library sharing. (SESSION: 393)ANR0409I Session 392 ended for server TONGA_1 (Windows). (SESSION: 392)ANR0408I Session 394 started for server TONGA_1 (Windows) (Tcp/Ip) for library sharing. (SESSION: 392)ANR0409I Session 393 ended for server TONGA_1 (Windows). (SESSION: 393)ANR0409I Session 394 ended for server TONGA_1 (Windows). (SESSION: 392)ANR8336I Verifying label of LTO volume 021AKK in drive DRIVE1 (/dev/rmt0). (SESSION: 391)ANR8468I LTO volume 021AKK dismounted from drive DRIVE1 (/dev/rmt0) in library 3582. (SESSION: 391)

3.3.2 With the Tivoli Storage Manager command line interfaceThis section summarizes the commands that are required to achieve the configuration using the command line interface. The steps to set up library sharing are:

1. Configuring server-to-server communication on the Library Manager.2. Defining the library on the Library Manager.3. Defining the library path on the Library Manager.4. Defining the drives for this library on the Library Manager.5. Defining the drive paths on the Library Manager.6. Defining a device class that uses the library on the Library Manager.7. Checking in library volumes on the Library Manager.8. Configuring server-to-server communication on the Library Client.9. Defining the library on the Library Client.10.Defining the drives path for the Library Client on the Library Manager.11.Defining a device class that uses the library on the Library Client.


Configuring server-to-server communication on the Library ManagerTo configure server-to-server communication, run these commands:

SET SERVERHLADDRESS 9.1.39.89SET SERVERLLADDRESS 1500SET SERVERNAME AZOV_1SET SERVERPASSWORD secretSET CROSSDEFINE ONDEFINE SERVER AZOV_1 serverpassword=secret HLADDRESS=9.1.38.89 lladdress=1500DEFINE SERVER TONGA_1 serverpassword=secret HLADDRESS=9.1.38.168 lladdress=1500

Defining the library on the Library ManagerTo define the library, run this command:

DEFINE LIBRARY 3582 libtype=SCSI shared=YES

Defining the library path on the Library ManagerTo define the library path on the Library Manager, run this command:

DEFINE PATH AZOV_1 3582 srctype=server desttype=library device=/dev/smc0

Defining the drives for this library on the Library ManagerTo define the for this library, run these commands:

DEFINE DRIVE 3582 3582_1DEFINE DRIVE 3582 3582_2

Defining the drive paths on the Library ManagerTo define the drive paths, run these commands:

DEFINE PATH AZOV_1 3582_1 SRCTYPE=SERVER AUTODETECT=YES DESTTYPE=DRIVE LIBRARY=3582 DEVICE=/dev/rmt0DEFINE PATH AZOV_1 3582_2 SRCTYPE=SERVER AUTODETECT=YES DESTTYPE=DRIVE LIBRARY=3582 DEVICE=/dev/rmt1

Defining a device class that uses the library on the Library ManagerTo define a device class that uses the library, run this command:

DEFINE DEVCLASS 3582_ULT3C LIBRARY=3582 DEVTYPE=LTO FORMAT=ULTRIUM2C MOUNTRETENTION=5 MOUNTWAIT=60 MOUNTLIMIT=DRIVES

Checking in library volumes on the Library ManagerTo check in library volumes, use this command:

CHECKIN LIBVOLUMES 3582 SEARCH=YES STAT=SCRATCH CHECKLABEL=YES

Tip: You should use a low value for the MOUNTRETENTION option. The bigger the environment (number of Tivoli Storage Manager nodes, library size, and number of Tivoli Storage Manager servers) the lower the MOUNTRETENTION value.

Tip: You can decrease the check in time by using the CHECKLABEL=BARCODE parameter. This parameter applies only to SCSI libraries.

Tip: If you use the SEARCH=BULK option and do not want to be prompted by the server, add the WAITTIME=0 option to the command


Configuring server-to-server communication on the Library ClientTo configure server-to-server communication, run these commands:

SET SERVERHLADDRESS 9.1.39.168SET SERVERLLADDRESS 1500SET SERVERNAME TONGA_1SET SERVERPASSWORD secretSET CROSSDEFINE ONDEFINE SERVER AZOV_1 serverpassword=secret HLADDRESS=9.1.38.89 lladdress=1500DEFINE SERVER TONGA_1 serverpassword=secret HLADDRESS=9.1.38.168 lladdress=1500

Defining the library on the Library ClientTo define the library on the Library Client, run this command:

DEFINE LIBRARY 3582 LIBTYPE=SHARED PRIMARYLIBMANAGER=AZOV_1

Defining the drives path for the Library Client on the Library ManagerTo define the drives path for the Library Client, run these commands:

DEFINE PATH TONGA_1 3582_1 SRCTYPE=SERVER AUTODETECT=YES DESTTYPE=DRIVE LIBRARY=3582 DEVICE=\\.\TAPE0DEFINE PATH TONGA_1 3582_2 SRCTYPE=SERVER AUTODETECT=YES DESTTYPE=DRIVE LIBRARY=3582 DEVICE=\\.\TAPE1

Defining a device class that uses the library on the Library ClientTo define a device class that uses the library, run this command:

DEFINE DEVCLASS 3582_ULT3C LIBRARY=3582 DEVTYPE=LTO FORMAT=ULTRIUM2C MOUNTRETENTION=5 MOUNTWAIT=60 MOUNTLIMIT=DRIVES


Chapter 4. IBM 3494 tape library sharing


� Introduction to the IBM 3494 tape library

� Library Sharing with the IBM 3494 Tape Library

– Installing on IBM AIX– Installing on Microsoft Windows– Installing on Linux– Installing on SUN Solaris


For more information about the IBM TotalStorage Enterprise Automated Tape Library (3494), see:

� IBM TotalStorage Tape Device Drivers Installation and User’s Guide, GC35-0154

� IBM TotalStorage Enterprise Automated Tape Library (3494) Introduction and Planning Guide, GA32-0448

4


4.1 Introduction to the IBM 3494 tape libraryThe IBM TotalStorage Enterprise Automated Tape Library (3494) provides a modular tape automation solution for multiple computing environments. It provides cost-effective, reliable, and space-efficient tape automation. The 3494:

� Provides a data storage capacity of up to 1 872 terabytes (TB) of uncompacted data and up to 5616 TB of compacted data.

� Supports the following subsystems:

– Tape drives: • 3490E Models C1A, C2A, and F1A • 3590 Models B1A, E1A, and H1A • 3592 Model J1A

– Tape drive controllers:• 3590 Models A00, A50, and A60• 3592 Model J70

– Media cartridges:• Cartridge System Tape (3490E)• Enhanced Capacity Cartridge System Tape (3490E)• High Performance Cartridge Tape (3590)• Extended High Performance Cartridge Tape (3590)• Enterprise Tape Cartridge (3592)• Enterprise Economy Tape Cartridge (3592)• Enterprise WORM Tape Cartridge (3592)• Enterprise Economy WORM Tape Cartridge (3592)

The 3494 provides a High Availability model that contains dual Library Managers and dual accessors for reduced service interventions and greater availability. Also, an optional feature enables two active accessors for increased performance.

4.1.1 IBM 3494 Library ManagerThe IBM 3494 Library Manager, or the remote console, controls all of the operations in the 3494 tape library, including the interaction between the library and its operators. The Library Manager hardware consists of a controller, display unit, keyboard and pointing device, and the hardware to support communication with the other units in the library.

During normal operations, the controls on the operator panel are sufficient to operate the library. The Library Manager is used for error recovery, for service, and for displaying operational status.

The 3494 Model HA1 provides a second set of hardware (controller, display unit, and keyboard with its pointing device) to improve Library Manager availability. The second Library Manager takes control of the library automatically if the first Library Manager fails.

The Tivoli Storage Manager Library Manager requires a connection to the 3494 Library Manager for the library control.


4.1.2 Categories in an IBM 3494 library The Library Manager that is built into the IBM 3494 library tracks the category number of each volume in the library. A single category number identifies all volumes that are used for the same purpose or application. These category numbers are useful when multiple systems share the resources of a single library.

Typically, a software application that uses a 3494 library uses volumes in one or more categories that are reserved for that application. To avoid loss of data, each application sharing the library must have unique categories. When you define a 3494 library to a Tivoli Storage Manager server, you can use the PRIVATECATEGORY and SCRATCHCATEGORY parameters for the DEFINE LIBRARY command to specify the category numbers for private and scratch Tivoli Storage Manager volumes in that library. If the volumes are IBM 3592 WORM (write once, read many) volumes, you can use the WORMSCRATCHCATEGORY parameter to specify category numbers for scratch WORM volumes in the library.

When a volume is first inserted into the library, either manually or automatically at the convenience I/O station, the volume is assigned to the insert category (X'FF00'). A software application such as Tivoli Storage Manager can contact the Library Manager to change a volume’s category number. For Tivoli Storage Manager, you use the CHECKIN LIBVOLUME command.

A Tivoli Storage Manager server reserves at least two category numbers in each 3494 library that it accesses: one for private volumes and one for scratch volumes. For example, suppose that you want to define a library object for your 3592 drives:

define library my3494 libtype=349x privatecategory=400 scratchcategory=401 wormscratchcategory=402

This command reserves the following categories for the new library, called my3494:

� 400 (X'190') Private volumes � 401 (X'191') Scratch volumes � 402 (X'192') WORM scratch volumes

4.2 Library Sharing with the IBM 3494 Tape LibraryTo use the IBM 3494 Tape Library, the Tivoli Storage Manager Library Manager needs either a LAN or serial connection to the tape library. A LAN connection is most common. The Tivoli Storage Manager Library Manager host also requires an interface between the Tivoli Storage Manager Server and the IBM 3494 Tape Library Manager. This section describes this interface for Microsoft Windows, IBM AIX, Linux, and SUN Solaris. The Tivoli Storage Manager Library Manager and Library Clients communicate, as usual, via server-to-server

Note: A 349X library object defend to Tivoli Storage Manager only contains one device type (3490, 3590, or 3592) of drives. Thus, if you have 3590s and 3592s in your 349X library, you need to define two library objects to Tivoli Storage Manager: one for your 3590 drives and one for your 3592 drives. Each of these library objects has the same device parameter when defining their paths.

Note: The default values for the categories might be acceptable in most cases. However, if you connect other systems or Tivoli Storage Manager servers to a single 3494 library, ensure that each uses unique category numbers. Otherwise, two or more systems might try to use the same volume, and cause a corruption or loss of data.

Chapter 4. IBM 3494 tape library sharing 95

communication. Figure 4-1 summarizes the connections that are required for sharing a 3494 library.

Figure 4-1 IBM 3494 Library sharing overview

4.2.1 Installing on IBM AIXThis section discusses the steps required for sharing with AIX.

Installing library controlThis library control (medium changer) needs to be installed only on the Tivoli Storage Manager Library Manager. The IBM 3494 Library device driver is an AIX device driver for the 3494 and VTS to an RS/6000®, RS/6000 SP, or pSeries host. The Library device driver, together with the IBM AIX Enhanced Tape Device Driver (Atape), provides support for the tape subsystem in the IBM TotalStorage 3494 Enterprise Tape Library.

The library control software consists of an Automated Tape Library Device Driver (atldd), an application daemon (lmcpd) that communicates with the 3494 Library Manager (LM), and a utility program (mtlib), which provides a command line interface to the library. An Ethernet, token-ring, or RS-232 serial connection can be used for the physical connection between the host and the 3494 Library Manager.

The daemon, known to AIX specifically as the IBM Library Manager Control Point Daemon (lmcpd), communicates with the tape libraries that are defined in a configuration file, /etc/ibmatl.conf, which is created when the software package is installed. The LMCP is used to perform library functions such as mounting and unmounting volumes. To send commands to the 3494, at least one LMCP device must be defined for use on the library. Multiple LMCP devices can be defined for use on the same 3494.

On AIX, you need the IBM TotalStorage Enterprise Tape Library Driver, also called IBM Automated Tape Library Device Driver (atldd). Use SMIT used to install the latest version of the driver. For more information about the driver and installation process, see IBM TotalStorage Tape Device Drivers Installation and User's Guide, GC35-0154 and the atldd.Readme file. You can download the latest version of the atldd install package from:


Tivoli Storage Manager Library Client Tivoli Storage Manager Library Manager

SAN

Data Flow

Library Control


LAN

3494 Tape Library

LAN

Data Flow



After installing, you need to update the /etc/ibmatl.conf file with the library name, TCP/IP address, and host name, as shown in Example 4-1. Our Library Manager is called poco, and we have assigned it a symbolic name of 3494.

Example 4-1 AIX ibmatl.conf

## (C) COPYRIGHT International Business Machines Corp. 1993, 1998# All Rights Reserved# Licensed Materials - Property of IBM## US Government Users Restricted Rights - Use, duplication or# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.### This is the file which defines the 3494 libraries and how they are attached.# The format of this file is:## Library name address identifier <address2>## Where library name is a symbolic name of the library, the address# is a value which represents either a direct rs232 connection or an# internet address of the Library Manager for a TCP/IP connection, and# the identifier to be used in conjuction with the Library Manager. It# is common practice to use the hostname of the machine for the identfier.# The address2 field after the identifier is the second internet address# for a 3494 HA (High Availability) library.## Notes: There is a 32 character limit for symbolic names.# There is an 8 character limit for the identifier.# Any line beginning with # is treated as a comment.## Example for rs232 connected library:## 3494a /dev/tty0 myhost## Example for TCP/IP connected library:## 3494b 9.115.32.21 myhost## Example for TCP/IP connected 3494 HA library:## 3494c 9.115.64.15 myhost 9.115.64.16#3494 9.11.213.8 poco

To activate the new configuration file ibmatl.conf, restart the Library Manager Control Point Daemon (lmcpd), as shown in Example 4-2.

Example 4-2 /etc/lmcpd restart

(root@poco) /> ps -ef | grep lmcpd root 122974 1 0 17:23:44 - 0:00 /etc/lmcpd root 397560 352292 0 12:54:35 pts/4 0:00 grep -i lmcpd(root@poco) /> kill -9 122974(root@poco) /> /etc/lmcpd(root@poco) /> ps -ef | grep lmcpd root 122978 352292 0 12:57:58 pts/4 0:00 grep -i lmcpd root 372786 1 0 12:57:53 - 0:00 /etc/lmcpd


Next, you configure the LMCP instances. Use the defatl command to define and configure the LMCP. This command creates the new LAN/TTY Library Management Control Point

/etc/methods/defatl -ctape -slibrary -tatl -a library_name='3494'

The device /dev/lmcp0 is now defined. To make it available, use the mkdev command.

mkdev -l 'lmcp0'

Now, you can define the library and the path to this library in the Tivoli Storage Manager LIbrary Manager, as shown in Example 4-3. Specify LIBTYPE=349x, and specify the correct /dev/lcmpx device.

Example 4-3 Define library and path on the Library Manager on AIX

tsm: POCO_1>DEFINE LIBRARY 3494 LIBTYPE=349X SHARED=YESANR8400I Library 3494 defined.

tsm: POCO_1>DEFINE PATH poco_1 3494 SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=/dev/lmcp0ANR1720I A path from POCO_1 to 3494 has been defined.

Installing the driveThe device driver for the tape drives has to be installed on both the Tivoli Storage Manager Library Manager and the Tivoli Storage Manager Library Client(s). If they are non-IBM drives, use the Tivoli Storage Manager device driver. If they are IBM drives, you can use the IBM tape driver. We have IBM drives in our IBM 3494 library, so we have to install the IBM tape driver. For AIX this is the Atape package. You can download this package at:


Install the package using SMIT and then reboot the server, because the installation updates the system boot image. Example 4-4 shows the installation process output.

Example 4-4 AIX: Atape installation with SMIT

COMMAND STATUS

Command: OK stdout: yes stderr: no

Before command completion, additional instructions may appear below.

[TOP]geninstall -I "a -cgNqwX -J" -Z -d . -f File 2>&1

File: Atape.driver 9.3.3.0+-----------------------------------------------------------------------------+ Pre-installation Verification...+-----------------------------------------------------------------------------+Verifying selections...doneVerifying requisites...doneResults...

SUCCESSES--------- Filesets listed in this section passed pre-installation verification and will be installed.

Important: The library_name parameter must be set to the same name as is defined in the ibmatl.conf file, which is 3494 in our example.



Selected Filesets ----------------- Atape.driver 9.3.3.0 # IBM AIX Enhanced Tape and Me...

<< End of Success Section >>

FILESET STATISTICS------------------ 1 Selected to be installed, of which: 1 Passed pre-installation verification ---- 1 Total to be installed

0503-409 installp: bosboot verification starting...installp: bosboot verification completed.+-----------------------------------------------------------------------------+ Installing Software...+-----------------------------------------------------------------------------+installp: APPLYING software for: Atape.driver 9.3.3.0

. . . . . << Copyright notice for Atape >> . . . . . . .

IBM AIX Enhanced Tape and Medium Changer Device Driver

(C) COPYRIGHT International Business Machines Corp. 1993 1997 All Rights Reserved Licensed Materials - Property of IBM

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

. . . . . << End of copyright notice for Atape >>. . . .

Checking for existing Atape devices...There are 2 Atape devices configured: rmt2 Available rmt3 AvailableUnconfiguring Atape devices...Unconfiguring rmt2...

rmt2 DefinedUnconfiguring rmt3...rmt3 DefinedInstalling AIX Version 5.2 Atape.driver...Adding device prototype...Adding odm and smit entries...Adding catalogs...Adding trace template...Adding error template...5 entries added.0 entries deleted.0 entries updated.

Adding utility programs...Reconfiguring Atape devices...Configuring rmt2...rmt2 AvailableConfiguring rmt3...rmt3 Available


Finished processing all filesets. (Total time: 13 secs).

0503-409 installp: bosboot verification starting...installp: bosboot verification completed.0503-408 installp: bosboot process starting...

bosboot: Boot image is 22643 512 byte blocks.0503-292 This update will not fully take effect until after a system reboot.

* * * A T T E N T I O N * * * System boot image has been updated. You should reboot the system as soon as possible to properly integrate the changes and to avoid disruption of current functionality.

installp: bosboot process completed.+-----------------------------------------------------------------------------+ Summaries:+-----------------------------------------------------------------------------+

Installation Summary--------------------Name Level Part Event Result-------------------------------------------------------------------------------Atape.driver 9.3.3.0 USR APPLY SUCCESS

[BOTTOM]

F1=Help F2=Refresh F3=Cancel F6=CommandF8=Image F9=Shell F10=Exit /=Findn=Find Next

The devices should be now configured. You can check the configuration with the lsdev command (Example 4-5).

Example 4-5 AIX: lsdev

(root@poco) /tmp/tsm>lsdev -Cctapelmcp0 Available LAN/TTY Library Management Control Pointrmt0 Available 1V-08-01 Other FC SCSI Tape Drivermt1 Available 1V-08-01 Other FC SCSI Tape Drivermt2 Available 1V-08-01 IBM 3592 Tape Drive (FCP)rmt3 Available 1V-08-01 IBM 3592 Tape Drive (FCP)

In our setup, there are two other non-IBM drives that are attached to the server (rmt0 and rmt1) and our two IBM 3592 drives (rmt2 and rmt3). We use these device special files (/dev/rmt2 and /dev/rmt3) for our Tivoli Storage Manager drive path definition.


Example 4-6 AIX: cfgmgr

(root@poco) /usr/tivoli/tsm/server/bin>lsdev -Ccadapterent0 Available 1L-08 10/100 Mbps Ethernet PCI Adapter II (1410ff01)ent1 Available 14-08 10/100 Mbps Ethernet PCI Adapter II (1410ff01)fcs0 Available 1V-08 FC Adapterfda0 Available 01-D1 Standard I/O Diskette Adapteride0 Available 1G-19 ATA/IDE Controller Devicelai0 Available 1p-00 GXT135P Graphics Adapterppa0 Available 01-R1 CHRP IEEE1284 (ECP) Parallel Port Adaptersa0 Available 01-S1 Standard I/O Serial Portsa1 Available 01-S2 Standard I/O Serial Portsa2 Available 01-S3 Standard I/O Serial Portscsi0 Available 1S-08 Wide/Ultra-3 SCSI I/O Controllerscsi1 Available 1S-09 Wide/Ultra-3 SCSI I/O Controllerscsi2 Available 1c-08 Wide/Fast-20 SCSI I/O Controllersioka0 Available 01-K1-00 Keyboard Adaptersiokma0 Available 01-K1 Keyboard/Mouse Adaptersioma0 Available 01-K1-01 Mouse Adapter

(root@poco) /usr/tivoli/tsm/server/bin>cfgmgr -l fcs0 -v----------------attempting to configure device 'fcs0'Time: 0 LEDS: 0x2600invoking /usr/lib/methods/cfgefc -l fcs0Number of running methods: 1----------------Completed method for: fcs0, Elapsed time = 0return code = 0****************** stdout ***********fscsi0****************** no stderr ***********----------------Time: 0 LEDS: 0x539Number of running methods: 0----------------attempting to configure device 'fscsi0'Time: 0 LEDS: 0x569invoking /usr/lib/methods/cfgefscsi -l fscsi0Number of running methods: 1----------------Completed method for: fscsi0, Elapsed time = 0return code = 0****************** stdout ***********rmt0 rmt1 rmt2 rmt3****************** no stderr ***********----------------Time: 0 LEDS: 0x539Number of running methods: 0----------------attempting to configure device 'rmt0'Time: 0 LEDS: 0x973invoking /etc/methods/cfgscsitape -l rmt0Number of running methods: 1----------------

Tip: If the drives do not appear, run configuration manager (cfgmgr), as shown in Example 4-6, to rescan your devices.


Completed method for: rmt0, Elapsed time = 0return code = 0****************** no stdout ***************************** no stderr ***********----------------Time: 0 LEDS: 0x539Number of running methods: 0----------------attempting to configure device 'rmt1'Time: 0 LEDS: 0x973invoking /etc/methods/cfgscsitape -l rmt1Number of running methods: 1----------------Completed method for: rmt1, Elapsed time = 0return code = 0****************** no stdout ***************************** no stderr ***********----------------Time: 0 LEDS: 0x539Number of running methods: 0----------------attempting to configure device 'rmt2'Time: 0 LEDS: 0x899invoking /etc/methods/cfgAtape -l rmt2Number of running methods: 1----------------Completed method for: rmt2, Elapsed time = 0return code = 0****************** no stdout ***************************** no stderr ***********----------------Time: 0 LEDS: 0x539Number of running methods: 0----------------attempting to configure device 'rmt3'Time: 0 LEDS: 0x899invoking /etc/methods/cfgAtape -l rmt3Number of running methods: 1----------------Completed method for: rmt3, Elapsed time = 0return code = 0****************** no stdout ***************************** no stderr ***********----------------Time: 0 LEDS: 0x539Number of running methods: 0----------------calling savebasereturn code = 0****************** no stdout ***************************** no stderr ***********Configuration time: 0 seconds(root@poco) /usr/tivoli/tsm/server/bin>


4.2.2 Installing on Microsoft WindowsThis section discusses the steps that are required for sharing on Windows.

Installing library controlThis library control (medium changer) needs to be installed only on the Tivoli Storage Manager Library Manager. This software provides attachment for the 3494 to a server running Microsoft Windows NT® 4.0, Windows 2000 or 2003. This product supports the tape subsystems in the 3494 Tape Library with either the IBM Windows Tape Device Driver (magstar.sys) or the Tivoli Storage Manager for Microsoft Windows NT Server Device Driver (adsmscsi.sys).

The software consists of a tape library service that communicates directly with the Library Manager of the 3494 via the LAN, a utility program that provides a command line interface to the service as well as a static library and a DLL that can be used to provide a communication interface with the service.

The IBM Automated Tape Library service is provided in the installation package. The service is set to automatic start, so that it initiates automatically when the Windows system is booted.

When configuring the Tivoli Storage Manager Library Manager on a Windows server, you need to install the IBM Automated Tape Library driver. The IBM Tape Library service for Microsoft Windows is installed by executing the install binary, which has the format ibmatl.x.x.x.x.exe or ibmatl64.x.x.x.x.exe, where x is the current level of the package and 64 is for 64-bit Windows 2003. You can download the Automated Tape Library driver from:

ftp://ftp.software.ibm.com/storage/devdrvr/Windows/ibmatl/

After installing, update the file C:\WINNT\ibmatl.conf. Example 4-7 shows our file for the 3494 Tape Library with the TCP/IP address 9.11.213.8.

Example 4-7 Windows ibmatl.conf

## (C) COPYRIGHT International Business Machines Corp. 1993, 1998# All Rights Reserved# Licensed Materials - Property of IBM## US Government Users Restricted Rights - Use, duplication or# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.### This is the file which defines the 3494 libraries and how they are attached.# The format of this file is:## Library name address identifier <address2>## Where library name is a symbolic name of the library, address is the# internet address of the Library Manager for a TCP/IP connection, and# the identifier to be used in conjuction with the Library Manager. It# is common practice to use the hostname of the machine for the identfier.# The address2 field after the identifier is the second internet address

Note: After installing the ibmatl on Windows 2003, the InstallShield can create a hidden directory (InstallShield Installation Information) in the Program Files folder, where it saves its own log file. This log file is a record of script functions that have changed the state of the machine during the installation. Do not delete this folder or run the setup.exe in the folder, or you will not be able to uninstall ibmatl.


ftp://ftp.software.ibm.com/storage/devdrvr/Windows/ibmatl/

# for a 3494 HA (High Availability) library.## Notes: There is a 32 character limit for symbolic names.# There is an 8 character limit for the identifier.# Any line beginning with # is treated as a comment.### Example for TCP/IP connected library:## 3494a 9.115.32.21 myhost## Example for TCP/IP connected 3494 HA library:## 3494b 9.115.64.15 myhost 9.115.64.16#3494c 9.11.213.8 scamp

Next, start the IBM Automated Tape Library Service (Figure 4-2).

Figure 4-2 Windows IBM Automated Tape Library Service

You can now define the library and the path to this library in Tivoli Storage Manager, as shown in Example 4-8.

Example 4-8 Define library and path on the Library Manager on Microsoft Windows

tsm: SCAMP_1>DEFINE LIBRARY 3494c LIBTYPE=349X SHARED=YESANR8400I Library 3494C defined.

tsm: SCAMP_1>DEFINE PATH scamp_1 3494c SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=3494cANR1720I A path from SCAMP_1 to 3494C has been defined.

Installing the driveThe device driver has to be installed on both the Tivoli Storage Manager Library Manager and the Tivoli Storage Manager Library Client(s). If they are non-IBM drives, use the Tivoli Storage Manager device driver. If they are IBM drives, use the IBM tape device driver. We have IBM drives in our IBM 3494 library, so we install the IBM tape device driver. You can download the software from:


Important: For the DEFINE PATH command, the DEVICE parameter must match exactly the name used in the ibmatl.conf file (Example 4-7), which is 3494c in this example.



After downloading the package:

1. Unzip the file and update the driver for all the drives. Figure 4-3 shows the Microsoft Windows device manager and how to start the driver update.

Figure 4-3 Windows: Device Manager

2. On the next screen, Figure 4-4 on page 106, select the option Install from a list or specific location (Advanced). Click Next.

Note: Beginning with V6.0.4.4, the IBM Tape device drivers for Windows 2000 and Windows 2003 are converged into a single install package with common inf files. Use this single package to install a driver on either operating system. The system detects which version of the driver binary files to install. For Windows 2000 users, the Magstar and Ultrium drivers have also been converged.


Figure 4-4 Windows: HW update wizard

3. Select Don’t search. I will choose the driver to install, as shown in Figure 4-5.

Figure 4-5 Windows: Driver search

4. Click Have Disk and browse to the directory where you extracted the contents of the IBM tape device driver zipped file (Figure 4-6 on page 107).


Figure 4-6 Windows: Select driver directory

5. Choose the magtape.inf file and click Open (Figure 4-7).

Figure 4-7 Windows: Select tape driver

6. You have now two models to select, Figure 4-8 on page 108. Choose the model with the extension for Tivoli Storage Manager.


Figure 4-8 Windows: Model select

7. Ignore the warning that the driver is not tested by Microsoft. Click Continue Anyway (Figure 4-9 on page 109).

Important: Beginning with V6.0.2.4, two versions of the device driver are made available: one that prohibits multiple opens on a single tape drive and one that will allow multiple opens on a single tape drive. Drivers that prohibit multiple opens on a single tape drive are indicated (when presented by the Windows Plug and Play Device Manager during device configuration) with the text string (for Tivoli Storage Manager) in them. These drivers use the file exctape.inf from the install package during installation. Drivers that allow multiple opens on a tape drive do not have this text string in them. These drivers use the file magtape.inf from the install package during the installation.

IBM strongly recommends that you use the for Tivoli Storage Manager drivers whether or not you are a Tivoli customer to prevent a tape drive from being accessed by more than one process and potentially causing data to be corrupted or lost. However, if you are a customer that uses RSM, you need to use the other driver and take steps to ensure that multiple uncoordinated opens to a tape drive do not occur.


Figure 4-9 Windows: Driver compatibility

8. Repeat these steps for all IBM drives. Reboot the server to activate the new driver.

After rebooting, in the Microsoft Windows Management Console, you can see all drives (Figure 4-10). You will use these device names (for example, \\.\Tape0) for the Tivoli Storage Manager server drive path definition as discussed in 4.3, “Tivoli Storage Manager configuration” on page 122.

Figure 4-10 Windows: MMC

4.2.3 Installing on LinuxThis section discusses the steps for setup with Linux.

Installing library controlThis library control (medium changer) needs to be installed only on the Tivoli Storage Manager Library Manager. The Linux Tape Library Driver (ibmatl) is software for attaching a 3494 to a Linux server. Use the Tape Library Driver in conjunction with the IBM SCSI Tape and Medium Changer Device Driver for Linux to provide support for 3590 and 3592 tape systems with the Fibre Channel Attachment in the 3494.

Important: For Windows 2003, the previous Tivoli Storage Manager device was replaced with a standard Windows device driver. The new device driver does not run as a service.


The software consists of a daemon that communicates directly with the Library Manager of the 3494 through Ethernet or Token Ring LAN, a utility program that provides a command-line interface to the daemon, and a C object module that can be linked with user applications to provide a communication interface with the daemon.

This software is termed as a driver throughout this document, because it provides the software and interface necessary to drive the 3494 Tape Library. However, the product does not include a device driver in the true sense of the term. That is, it is not an extension of the operating system kernel, such as a tape device driver.

The Library Manager control point daemon (lmcpd) is provided in the package. It provides direct communication with the Library Manager. An application links with the supplied C object module using the interface described in the IBM TotalStorage Tape Device Drivers: Programming Reference. The subroutines in this module communicate with the lmcpd to perform the various library operations using standard UNIX name space sockets.

The lmcpd communicates with the Library Manager through TCP/IP. The /etc/ibmatl.conf configuration file is used to define the attachment for each library.

The installation medhot for lmcpd depends on the Linux distribution. We used the YAST tool in SUSE LINUX Enterprise Server 9 for this installation.

After the installation, you need to update the /etc/ibmatl.conf file with the library name, TCP/IP address, and host name, as shown in Example 4-9.

Example 4-9 Linux ibmatl.conf

## (C) COPYRIGHT International Business Machines Corp. 1993, 1998# All Rights Reserved# Licensed Materials - Property of IBM## US Government Users Restricted Rights - Use, duplication or# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.### This is the file which defines the 3494 libraries and how they are attached.# The format of this file is:## Library name address identifier <address2>## Where library name is a symbolic name of the library, the address# is a value which represents either a direct rs232 connection or an# internet address of the Library Manager for a TCP/IP connection, and# the identifier to be used in conjuction with the Library Manager. It# is common practice to use the hostname of the machine for the identfier.# The address2 field after the identifier is the second internet address# for a 3494 HA (High Availability) library.## Notes: There is a 32 character limit for symbolic names.# There is an 8 character limit for the identifier.# Any line beginning with # is treated as a comment.## Example for rs232 connected library:## 3494a /dev/tty0 myhost## Example for TCP/IP connected library:## 3494b 9.115.32.21 myhost


## Example for TCP/IP connected 3494 HA library:## 3494c 9.115.64.15 myhost 9.115.64.16 3494b 9.11.213.8 cadi

Whenever the /etc/ibmatl.conf file is changed, you have to restart the lmcpd, as shown in Example 4-10.

Example 4-10 Linux /etc/lmcpd restart

cadi:/tmp # ps -ef | grep lmcpdroot 9798 1 0 05:58 ? 00:00:00 /etc/lmcpdroot 9805 9003 0 05:59 pts/4 00:00:00 grep lmcpdcadi:/tmp # kill -9 9798cadi:/tmp # ps -ef | grep lmcpdroot 9807 9003 0 05:59 pts/4 00:00:00 grep lmcpdcadi:/tmp # /etc/lmcpdcadi:/tmp # ps -ef | grep lmcpdroot 9810 1 0 06:00 ? 00:00:00 /etc/lmcpdroot 9814 9003 0 06:00 pts/4 00:00:00 grep lmcpd

We can now define the library and the path to this library in Tivoli Storage Manager, as shown in Example 4-11.

Example 4-11 Define library and path on the Library Manager on Linux

tsm: CADI_1>DEFINE LIBRARY 3494lib LIBTYPE=349X SHARED=YESANR8400I Library 3494LIB defined.

tsm: CADI_1>DEFINE PATH cadi_1 3494lib SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=3494bANR1720I A path from CADI_1 to 3494LIB has been defined.

Specify LIBTYPE=349x on the DEFINE LIBRARY command. The DEVICE parameter in the DEFINE PATH command must match the entry made in /etc/ibmatl.conf.

Installing the driveThe device driver has to be installed on both the Tivoli Storage Manager Library Manager and the Tivoli Storage Manager Library Client. If they are non-IBM drives, use the Tivoli Storage Manager device driver. If they are IBM drives, you can use the IBM tape driver. We have IBM drives in our IBM 3494 library, so we have to install the IBM tape driver. You can download the software from




For Linux, you download the IBMtape and the IBMtapeutil packages. Example 4-12 shows the install process for IBMtapeutil, and Example 4-13 shows the process for IBMtape.

Example 4-12 Linux: IBMtapeutil install

cadi:/tmp # tar -xvf ./IBMtapeutil.1.3.1.i386.tar.binIBMtapeutil.1.3.1/IBMtapeutil.1.3.1/IBMtapeconfigIBMtapeutil.1.3.1/IBMtapeutil.cIBMtapeutil.1.3.1/IBMtapeutil.hIBMtapeutil.1.3.1/makefileIBMtapeutil.1.3.1/IBMtapeutil.ReadMeIBMtapeutil.1.3.1/IBMtapeutilcadi:/tmp # cd IBMtapeutil.1.3.1/cadi:/tmp/IBMtapeutil.1.3.1 # make installcp -f IBMtapeutil /usr/bin/.cp -f IBMtapeconfig /usr/bin/.

Example 4-13 Linux: IBM tape driver install

cadi:/tmp # rpm -i ./IBMtape-2.0.5-2.6.5-7.147.i386.rpm.binInstalling IBMtapeIBMtape loaded

After the installation, you can check whether the devices were detected (Example 4-14).

Example 4-14 Linux: ls -l /dev/IBMtape*

cadi:~ # ls -l /dev/IBMtap*crw-rw-rw- 1 root root 253, 0 Apr 8 05:04 /dev/IBMtape0crw-rw-rw- 1 root root 253, 256 Apr 8 05:04 /dev/IBMtape0ncrw-rw-rw- 1 root root 253, 1 Apr 8 05:04 /dev/IBMtape1crw-rw-rw- 1 root root 253, 257 Apr 8 05:04 /dev/IBMtape1ncadi:~ #

If there are no /dev/IBMtapeX devices, reboot the server. After the reboot, check the file /proc/scsi/IBMtape (Example 4-15) to see whether the drives were correctly detected. Otherwise, check the SAN connections and the SAN zoning.

Example 4-15 Linux: /proc/scsi/IBMtape

cadi:~ # more /proc/scsi/IBMtapeIBMtape version: 2.0.5IBMtape major number: 253Attached Tape Devices:Number Model SN HBA FO Path0 03592J1A 000001300117 qla2xxx NA1 03592J1A 000001300114 qla2xxx NA

You can reconfigure the IBM tape devices with the IBMtapeconfig script. IBMtapeconfig removes all the existing /dev/IBMtape and /dev/IBMchanger special files and creates new ones based on the information in /proc/scsi/IBMtape and /proc/scsi/IBMchanger. Example 4-16 shows the output from this command.

Example 4-16 Linux: IBMtapeconfig

cadi:~ # IBMtapeconfig

Creating IBMtape special files major number: 253


Attached devices: 0 1 mknod -m 0666 /dev/IBMtape0 c 253 0 mknod -m 0666 /dev/IBMtape0n c 253 256 mknod -m 0666 /dev/IBMtape1 c 253 1 mknod -m 0666 /dev/IBMtape1n c 253 257

Creating IBMchanger special files major number: 253 No attached devices.

Each tape device has a set of special files that provides access to the same physical drive but provides different attributes. Table 4-1 shows the attributes of the special files.

Table 4-1 Linux: Special files for IBM tape devices

You will use these /dev/IBMtape* special devices files in the Tivoli Storage Manager server drive path definition as discussed in 4.3, “Tivoli Storage Manager configuration” on page 122.

Example 4-17 Linux: IBMtapeutil

cadi: # IBMtapeutil

IBMtapeutil for Linux, Version 1.3.1, Sept. 14, 2004========================================= 1. Tape 2. Changer 3. Quit=========================================

Enter your choice: 1

-------------------------- General Commands: ----------------------------- 1. Open a Device 9. Mode Sense Pag 2. Close a Device 10. Switch Tape/Changer Devic 3. Inquiry 11. Create Special Files 4. Test Unit Ready 12. Query Driver Version 5. Reserve Device 13. Query Device Path 6. Release Device 14. Display All Paths 7. Request Sense 15. Enable A Path 8. Log Sense Page 16. Disable A Path Q. Quit IBMtapeutil--------------------------- Tape Commands: -------------------------------- 20. Rewind 33. Set Block Size 21. Forward Space Filemarks 34. Retension Tape 22. Backward Space Filemarks 35. Query/Set Tape Position 23. Forward Space Records 36. Query Tape Status 24. Backward Space Records 37. Load Tape 25. FSFM 38. Unload Tape 26. BSFM 39. Lock Tape Drive Door 27. Space to End of Data 40. Unlock Tape Drive Door 28. Read and Write Tests 41. Take Tape Offline 29. Write Filemarks 42. Enable/Disable Compression

Special file name Rewind on close

/dev/IBMtape* Yes

/dev/IBMtape*n No

Tip: You can test your drives with the program IBMtapeutil, as shown in Example 4-17.


30. Read or Write Files 43. Flush Drive's Buffer 31. Erase 44. Self Test 32. Reset Drive 45. Display Message--------------------------- IBMtape Commands: ------------------------------- 46. Query Sense 52. Locate Tape Position 47. Query Inquiry 53. Read Tape Position 48. Query/Set Tape Parameters 54. Query Mtdevice Number 49. Query/Set Tape Position 55. Synchronize Buffers 50. Query/Set MT/ST Mode 56. List Tape Filemarks 51. Report Density Support--------------------------- Service Aid Commands: ------------------------- 70. Dump Device 74. Read Persistent Reservation Keys 71. Force Dump 75. Read Persistent Reservations 72. Load Ucode 76. Register Persistent Reservation Key 73. Reset Drive 77. Remove Persistent Reservation 78. Clear All Persistent Registrations--------------------------------------------------------------------------- 99. Back To Main Menu

Enter Selection: 1

Enter device name (<enter> for /dev/IBMtape0):Select mode (<enter> or 1=Read/Write, 2=Read Only, 3=Write Only, 4=Append):

Opening device......

4.2.4 Installing on SUN SolarisThis section describes the steps for setup on SUN Solaris.

Installing library controlThis library control (medium changer) needs to be installed only on the Tivoli Storage Manager Library Manager. The Sun Solaris Tape Library Driver is software for attaching the 3494 to a Sun server. Use the Tape Library Driver together with the IBM SCSI Tape and Medium Changer Device Driver for Solaris to provide support for the SCSI tape subsystems in the 3494.

The software consists of a daemon that communicates directly with the Library Manager of the 3494 Tape Library through RS-232 or LAN, a utility program that provides a command-line interface to the daemon, and a C object module that can be linked with user applications to provide a communication interface with the daemon.

This software is known as a driver because it provides the software and interface necessary to drive the Tape Library. However, the product does not consist of a device driver in the true sense of the term. That is, it is not an extension of the operating system kernel, such as a SCSI tape device driver.

Note: Beginning with IBMtape V1.2.5, the IBMtape device driver provides an error diagnostic daemon (IBMtape) that provides error logging and tracing of the IBMtape device driver. When drive dumps, log sense data, or SIM/MIMM error information are created by the tape drive, the daemon retrieves that data automatically and saves it to disk on the Linux system.

We recommend that you leave this daemon enabled at all times.


The Library Manager control point daemon (lmcpd) is provided in the package. The lmcpd is a process that is always running on the system which provides direct communication with the 3494 Library Manager. An application (such as Tivoli Storage Manager) links with the supplied C object module using the interface described in the IBM TotalStorage Tape Device Drivers: Programming Reference. The subroutines in this module communicate with the lmcpd to perform the various library operations using standard UNIX namespace sockets.

The lmcpd communicates with the Library Manager either through a standard 25-pin null modem D-shell RS-232 cable or through TCP/IP. The /etc/ibmatl.conf configuration file is used to define the type of attachment for each library.

The IBM Tape Library driver (the lmcpd package) for Solaris is installed using the standard Sun package facility. The IBM Tape Library Driver for Solaris is the package. Example 4-18 shows the installation process. You can download the Tape Library driver from:


Example 4-18 Solaris lmcpd install

bash-2.03# pkgadd -d ./lmcpd.6.0.6.0.bin

The following packages are available: 1 lmcpd IBM Automated Tape Library Daemon (sparc) 6.0.6.0


Processing package instance <lmcpd> from </tmp/lmcpd.6.0.6.0.bin>

IBM Automated Tape Library Daemon(sparc) 6.0.6.0IBM (R)Solaris (R)IBM Automated Tape Library DaemonVersion 6.0.6.0

Contains Licensed Internal CodeLicensed Materials - Property of IBM

(C) COPYRIGHT 1995. IBM CorporationAll Rights ReservedPortions (C) 1994 Sun Microsystems

US Government Users Restricted Rights -Use, duplication, or disclosure restrictedby GSA ADP Schedule Contract with IBM

(R) IBM is a registered trademark of IBM Corporation(R) Solaris is a registered trademark of Sun MicrosystemsUsing </opt> as the package base directory.## Processing package information.## Processing system information.## Verifying disk space requirements.## Checking for conflicts with packages already installed.## Checking for setuid/setgid programs.




Do you want to continue with the installation of <lmcpd> [y,n,?] y

Installing IBM Automated Tape Library Daemon as <lmcpd>

## Installing part 1 of 1./etc/lmcpd/opt/lmcpd/ibmatl.conf/usr/bin/mtevent/usr/bin/mtlib/usr/bin/mtlib64/usr/bin/trcatl/usr/include/sys/mtlibio.h/usr/lib/libibm.o/usr/lib/libibm64.o/usr/lib/libibm64k.o/usr/lib/libibmk.o[ verifying class <none> ]## Executing postinstall script.The ibmatl.conf file already exists in the /etc directory...Using existing ibmatl.conf as current configuration file.Adding lmcpd 3494 port to /etc/services file...Adding new lmcpd entry to /etc/inittab file...

Installation of <lmcpd> was successful.

After installing, update the /etc/ibmatl.conf file with the library name, TCP/IP address, and host name, as shown in Example 4-19.

Example 4-19 Solaris ibmatl.conf

## (C) COPYRIGHT International Business Machines Corp. 1993, 1998# All Rights Reserved# Licensed Materials - Property of IBM## US Government Users Restricted Rights - Use, duplication or# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.## This is the file which defines the 3494 libraries and how they are attached.# The format of this file is:## Library name address identifier <address2>## Where library name is a symbolic name of the library, the address# is a value which represents either a direct rs232 connection or an# internet address of the Library Manager for a TCP/IP connection, and# the identifier to be used in conjuction with the Library Manager. It# is common practice to use the hostname of the machine for the identfier.# The address2 field after the identifier is the second internet address# for a 3494 HA (High Availability) library.## Notes: There is a 32 character limit for symbolic names.# There is an 8 character limit for the identifier.# Any line beginning with # is treated as a comment.## Example for rs232 connected library:## 3494a /dev/tty0 myhost dst3494b 9.11.213.8 sunset


To activate the new configuration file ibmatl.conf, restart the Library Manager Control Point daemon (lmcpd), as shown in Example 4-20.

Example 4-20 Solaris /etc/lmcpd restart

bash-2.03# ps -ef | grep lmcpd root 521 1 0 Jan 06 ? 0:09 /etc/lmcpd root 3600 3090 0 10:33:33 pts/2 0:00 grep lmcpdbash-2.03# kill -9 521bash-2.03# ps -ef | grep lmcpd root 3602 3090 0 10:33:41 pts/2 0:00 grep lmcpdbash-2.03# /etc/lmcpdbash-2.03# ps -ef | grep lmcpd root 3616 3090 0 10:33:51 pts/2 0:00 grep lmcpd root 3605 1 0 10:33:44 ? 0:00 /etc/lmcpd

You can now define the library and the path to this library in Tivoli Storage Manager, as shown in Example 4-21.

Example 4-21 Define library and path on the Library Manager on Solaris

tsm: SUNSET_1>DEFINE LIBRARY 3494lib LIBTYPE=349X SHARED=YESANR8400I Library 3494LIB defined.

tsm: SUNSET_1>DEFINE PATH sunset_1 3494lib SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=dst3494bANR1720I A path from SUNSET_1 to 3494LIB has been defined.

Use LIBTYPE of 349x in the DEFINE LIBRARY command. The DEVICE parameter in the DEFINE PATH command must match the name defined in ibmatl.conf, dst3494b in our example.

Installing the driveThe device driver has to be installed on both the Tivoli Storage Manager Library Manager and the Tivoli Storage Manager Library Client. If they are non-IBM drives, use the Tivoli Storage Manager device driver. If they are IBM drives, you can use the IBM tape driver. We have IBM drives in our IBM 3494 library, so we have to install the IBM tape driver. You can download the package from:


Before installing the IBMtape driver, you should display the device special files (as shown in Example 4-22) and record this information. You will need this information later in the installation.

Example 4-22 Solaris: ls -l /dev/rmt/*st before IBMtape installation

bash-2.03# ls -l /dev/rmt/*stlrwxrwxrwx 1 root other 57 Apr 8 13:49 /dev/rmt/0st -> ../../devices/pci@1f,4000/fibre-channel@2/st@36,0:stlrwxrwxrwx 1 root other 57 Apr 8 13:49 /dev/rmt/1st -> ../../devices/pci@1f,4000/fibre-channel@2/st@37,0:st

Attention: Before installing, make a backup of the system, list all current device special files, and find the SCSI addressees with which they are associated.



Example 4-23 shows the IBMtape installation process.

Example 4-23 Solaris: IBM tape driver installation process

bash-2.03# pkgadd -d ./IBMtape.4.1.1.4.bin

The following packages are available: 1 IBMtape IBM Tape & Medium Changer Device Driver 4.1.1.4 (sparc) 4.1.1.4


Processing package instance <IBMtape> from </tmp/IBMtape.4.1.1.4.bin>

IBM Tape & Medium Changer Device Driver 4.1.1.4(sparc) 4.1.1.4

IBM Tape & Medium Changer Device Driver for Sun Solaris 7, 8, 9 and 10 Version 4.1.1.4

Contains Licensed Internal Code Licensed Materials - Property of IBM

(C) Copyright 1994-. IBM Corporation All Rights Reserved Portions (C) 1994 Sun Microsystems

US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM

(R) IBM is a registered trademark of IBM Corporation (R) Solaris is a registered trademark of Sun Microsystems

Using </opt> as the package base directory.## Processing package information.## Processing system information. 1 package pathname is already properly installed.## Verifying disk space requirements.## Checking for conflicts with packages already installed.## Checking for setuid/setgid programs.


Do you want to continue with the installation of <IBMtape> [y,n,?] y

Installing IBM Tape & Medium Changer Device Driver 4.1.1.4 as <IBMtape>

## Installing part 1 of 1./opt/IBMtape/IBMtape.conf/opt/IBMtape/diags_info/opt/IBMtape/tapelist/opt/IBMtape/tapeutil/opt/IBMtape/tapeutil.c/opt/IBMtape/tmd/opt/IBMtape/tmd.conf/usr/include/sys/oldtape.h/usr/include/sys/smc.h/usr/include/sys/st.h


/usr/include/sys/svc.h/usr/kernel/drv/IBMtape/usr/kernel/drv/sparcv9/IBMtape[ verifying class <none> ]## Executing postinstall script.## The /usr/kernel/drv/IBMtape.conf file already exists.## It will be preserved as the current configuration file## for the IBM Tape & Medium Changer Device Driver.

## Stopping any running instances of tape monitor daemon...

## Installing the /etc/tmd.conf file.

## Creating the directory of /var/opt/IBMtape.

## The /usr/kernel/drv/IBMtape.conf already contains## a control node entry. It will be preserved.

## Adding new tmd entry to /etc/inittab...## Loading IBM Tape & Medium Changer Device Driver.

## Starting IBMtape Monitor Daemon (tmd)...

Installation of <IBMtape> was successful.

Next, edit the file the /usr/kernel/drv/IBMtape.conf to include drive information. You can use the information from Example 4-22 on page 117. Example 4-24 shows our entries.

Example 4-24 Solaris: /usr/kernel/drv/IBMtape.conf

bash-2.03# cat /usr/kernel/drv/IBMtape.conf

################################################################################################################################################################ #### IBM SCSI Tape & Medium Changer Device Driver for Solaris 7, 8, 9 and 10 #### (C) COPYRIGHT IBM Corporation, 1994 - #### #### IBMtape.conf - Configuration File #### Licensed Materials - Property of IBM #### All Rights Reserved #### #### US Government Users Restricted Rights - Use, duplication, or #### disclosure restricted by GSA ADP Schedule Contract with IBM Corp. #### ################################################################################################################################################################


...

#name="IBMtape"


# class="scsi"# target=15 lun=0# block_size=0# buffering=1# immediate=0# trailer=0# sili=0;


name="IBMtape" parent="pseudo" instance=16383;

# An example entry for high numbers of target and lun# name="IBMtape" class="scsi" target=200 lun=3;

# An example entry for QLogic HBA running qla HBA driver# name="IBMtape" parent="qla2100" target=0; for qla2100 only# name="IBMtape" parent="qla2200" target=0; for qla2200 only# name="IBMtape" parent="qla2300" target=0; for qla2300 only

# An example entry for AMCC JNI HBA# name="IBMtape" parent="jnic146x" target=0;

# An example entry for Emulex HBA# name="IBMtape" parent="lpfc" target=0;

# An example entry for Sun Branded FC HBA# name="IBMtape" parent="fp" lun=0 fc-port-wwn="xxxxxxxxxxxxxxxx";# name="IBMtape" parent="fp" lun=1 fc-port-wwn="xxxxxxxxxxxxxxxx";

name="IBMtape" parent="qla2300" target=36;name="IBMtape" parent="qla2300" target=37;

Note: IBM requires that the Solaris native SCSI tape device driver st be configured (/kernel/drv/st.conf) so that it does not attempt to support SCSI targets that are controlled by IBMtape (/usr/kernel/drv/IBMtape.conf). For more information, see “Preventing Conflicts with Other Device Drivers” in IBM TotalStorage Tape Device Drivers Installation and User’s Guide, GC35-0154


If you do not know the SCSI information, you can create an IBMtape.conf that is similar to Example 4-25 with all SCSI target and LUN combinations (0 to 255).

Example 4-25 Solaris: IBMtape.conf with all targets/luns

....name="IBMtape" class="scsi" target=8 lun=19 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;name="IBMtape" class="scsi" target=8 lun=20 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;name="IBMtape" class="scsi" target=8 lun=21 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;....name="IBMtape" class="scsi" target=8 lun=255 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;name="IBMtape" class="scsi" target=9 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;name="IBMtape" class="scsi" target=9 lun=1 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;...

Changes to configuration settings require either a system reboot or manual unload and reload of the IBMtape driver. Because you changed IBMtape.conf, you can either reboot or run the commands that are shown in Example 4-26. Make sure that no devices that are owned by IBMtape are in use before rebooting or using these commands.

Example 4-26 Solaris: Reload IBMtape

/opt/IBMtape/tmd -s/usr/sbin/rem_drv IBMtape /usr/sbin/add_drv -m ’* 0666 bin bin’ IBMtape/opt/IBMtape/tmd

The drives are now configured, and you can view the device special files with the ls command, as shown in Example 4-27.

Example 4-27 Solaris: ls -l /dev/rmt/*st after IBMtape installation

bash-2.03# ls -l /dev/rmt/*stlrwxrwxrwx 1 root other 57 Apr 8 13:49 /dev/rmt/0st -> ../../devices/pci@1f,4000/fibre-channel@2/IBMtape@36,0:stlrwxrwxrwx 1 root other 57 Apr 8 13:49 /dev/rmt/1st -> ../../devices/pci@1f,4000/fibre-channel@2/IBMtape@37,0:stbash-2.03#

The IBMtape device driver is in use for these devices, compared with previously in Example 4-22 on page 117.

You can now define the drive paths using these device special files on the Tivoli Storage Manager Server (Example 4-28).

Example 4-28 Solaris: Tivoli Storage Manager drive path definition

tsm: SUNSET_1>def path SUNSET_1 3494_01 srct=server destt=drive libr=3494LIB device=/dev/rmt/0stANR1720I A path from SUNSET_1 to 3494LIB 3494_01 has been defined.tsm: SUNSET_1>def path SUNSET_1 3494_02 srct=server destt=drive libr=3494LIB device=/dev/rmt/1stANR1720I A path from SUNSET_1 to 3494LIB 3494_02 has been defined.


You can display more information about the drives with the tapelist command (Example 4-29).

Example 4-29 Solaris: tapelist

bash-2.03# /usr/bin/tapelistIBM Tape Device Information : Instance : 6248 Special File : /dev/rmt/0st Device : 03592J1A Serial Number : 000001300117 TGT/LUN : 54/0 Ucode : 04E6 World Wide NN : 50050763020000C5 World Wide PN : 50050763024000C5 Dev Phy Path : /devices/pci@1f,4000/fibre-channel@2/IBMtape@36,0 Path Type : N/A

--- more ---


4.3 Tivoli Storage Manager configurationThis section summarizes the Tivoli Storage Manager commands that are required to create library sharing with the IBM 3494 Tape Library. In our test environment, the Tivoli Storage Manager Library Manager was installed on the AIX server POCO and the Library Client on the Windows server SCAMP (as illustrated in Figure 4-11 on page 123). For more information about basic installation and setup of a Tivoli Storage Manager Server, see the following:

� IBM Tivoli Storage Manager for AIX Installation Guide V5.3, GC32-1597



Figure 4-11 3494 configuration overview

The steps to configure Tivoli Storage Manager are:

1. Configuring server-to-server communication on the Library Manager2. Defining the library on the Library Manager3. Defining the library path on the Library Manager4. Defining the drives for this library on the Library Manager5. Defining the drive paths on the Library Manager6. Defining a device class using the library on the Library Manager7. Checking in library volumes on the Library Manager8. Creating the server-to-server communication on the Library Client9. Defining the library on the Library Client10.Defining the drives path for the Library Client on the Library Manager11.Defining a device class that uses the library on the Library Client

4.3.1 Configuring server-to-server communication on the Library ManagerTo use library sharing, you have to set up server-to-server communication between the Library Manager POCO and the Library Client SCAMP, as shown in Example 4-30.

Example 4-30 Server-to-server communication

SET SERVERPASSWORD secretSET SERVERNAME POCO_1 SET SERVERHLADDRESS 9.11.213.9 SET SERVERLLADDRESS 1500DEFINE SERVER POCO_1 serverpassword=secret HLADDRESS=9.11.213.110 lladdress=1500DEFINE SERVER SCAMP_1 serverpassword=secret HLADDRESS=9.11.213.9 lladdress=1500

SAN

LAN

Library Control

Data path Data path



Tivoli Storage

ManagerLibraryClient

IBM 3494TapeLibrary

SCAMPPOCO


4.3.2 Defining the library on the Library ManagerTo define the library, use this command and set the LIBTYPE parameter to 349x:

DEFINE LIBRARY 3494 LIBTYPE=349X SHARED=YES SCRATCHCATegory=700 PRIVATECATegory=701

4.3.3 Defining the library path on the Library ManagerTo define the library path on the LIbrary Manager, use this command:

DEFINE PATH POCO_1 3494 SRCTYPE=SERVER AUTODETECT=YES DESTTYPE=LIBRARY DEVICE=/dev/lmcp0

4.3.4 Defining the drives for this library on the Library ManagerTo define the drives for this library on the Library Manager, use these commands:

DEFINE DRIVE 3494 3494_01DEFINE DRIVE 3494 3494_02

4.3.5 Defining the drive paths on the Library ManagerTo define the drive paths on the Library Manager, use these commands:

DEFINE PATH POCO_1 3494_01 srct=server autodetect=yes destt=drive libr=3494 device=/dev/rmt2DEFINE PATH POCO_1 3494_02 srct=server autodetect=yes destt=drive libr=3494 device=/dev/rmt3

4.3.6 Defining a device class using the library on the Library ManagerTo define a device class using the library, use this command:

DEFINE DEVCLASS 3494_3592C LIBRARY=3494 DEVTYPE=3592 FORMAT=DRIVE MOUNTRETENTION=5 MOUNTWAIT=60 MOUNTLIMIT=DRIVES

4.3.7 Checking in library volumes on the Library ManagerTo check in library volumes:

CHECKIN LIBVOLUMES 3494 SEARCH=yes VOLRANGE=J11771,J11774 STATUS=scr DEVTYPE=3592

If the volumes are unlabled, use the LABEL LIBVOLUME command as follows:

LABEL LIBVOLUME 3494 SEARCH=YES CHECKIN=SCRATCH

4.3.8 Creating the server-to-server communication on the Library ClientTo create the server-to-server communication, run these commands:

SET SERVERPASSWORD secretSET SERVERNAME scamp_1SET SERVERHLADDRESS 9.11.213.9 SET SERVERLLADDRESS 1500DEFINE SERVER POCO_1 serverpassword=secret HLADDRESS=9.11.213.110 lladdress=1500DEFINE SERVER SCAMP_1 serverpassword=secret HLADDRESS=9.11.213.9 lladdress=1500

Attention: Be sure to use appropriate categories for scratch and private volumes. For more information see IBM TotalStorage Enterprise Automated Tape Library (3494) Introduction and Planning Guide, GA32-0448.


4.3.9 Defining the library on the Library ClientTo define the library on the Library Client, run this command:

DEFINE LIBRARY 3494 LIBTYPE=shared PRIMARYLIBMANAGER=poco_1

4.3.10 Defining the drives path for the Library Client on the Library ManagerTo define the drives path for the Library Client, run these commands:

DEFINE PATH scamp_1 3494_01 srct=server destt=drive libr=3494 device=whatever1DEFINE PATH scamp_1 3494_02 srct=server destt=drive libr=3494 device=whatever2

Here, you avoid having to identify the Library Client’s device special file for the drives and instead use a dummy device parameter. Because of the SAN Discovery feature of Tivoli Storage Manager, it uses serial number that match when the client first tries to open the device in order to detect the device special file. For more information about SAN Discovery, see Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.

4.3.11 Defining a device class that uses the library on the Library ClientTo define a device class that uses the library, run this command:

DEFINE DEVCLASS 3494_3592C LIBRARY=3494 DEVTYPE=3592

The library sharing for the 3494 library is now ready and you can test it (for example, by making a Tivoli Storage Manager server database backup). Example 4-31 shows the activity log on the Library Client, and Example 4-32 on page 126 shows the activity log on the Library Manager.

Example 4-31 Tivoli Storage Manager activity log on the Library Client

ANR2017I Administrator ADMIN issued command: BACKUP DB devcl=3494_3592C t=fANR0984I Process 6 for DATABASE BACKUP started in the BACKGROUND at 15:00:22.ANR2280I Full database backup started as process 6.ANR0408I Session 13 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 13 ended for server POCO_1 (AIX-RS/6000).ANR0408I Session 14 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0408I Session 15 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 15 ended for server POCO_1 (AIX-RS/6000).ANR0408I Session 16 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 16 ended for server POCO_1 (AIX-RS/6000).ANR8974I Found new path for SCAMP_1 and target name 3494_01 old path whatever1 new path \\.\Tape2. Path information will be updated remotely.ANR0409I Session 14 ended for server POCO_1 (AIX-RS/6000).ANR8337I 3592 volume J11774 mounted in drive 3494_01 (\\.\Tape2).ANR0511I Session 7 opened output volume J11774.ANR1360I Output volume J11774 opened (sequence number 1).ANR1361I Output volume J11774 closed.ANR0514I Session 7 closed volume J11774.ANR0408I Session 17 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 17 ended for server POCO_1 (AIX-RS/6000).ANR0408I Session 18 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0408I Session 19 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 19 ended for server POCO_1 (AIX-RS/6000).ANR4550I Full database backup (process 6) complete, 156 pages copied.ANR0985I Process 6 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 15:01:06.ANR8336I Verifying label of 3592 volume J11774 in drive 3494_01 (\\.\Tape2).ANR8468I 3592 volume J11774 dismounted from drive 3494_01 (\\.\Tape2) in library 3494.ANR0409I Session 18 ended for server POCO_1 (AIX-RS/6000).


Example 4-32 Tivoli Storage Manager activity log on the Library Manager

ANR0408I Session 7 started for server SCAMP_1 (Windows) (Tcp/Ip) for library sharing.ANR0409I Session 7 ended for server SCAMP_1 (Windows).ANR0408I Session 8 started for server SCAMP_1 (Windows) (Tcp/Ip) for library sharing.ANR0408I Session 9 started for server SCAMP_1 (Windows) (Tcp/Ip) for library sharing.ANR0409I Session 9 ended for server SCAMP_1 (Windows).ANR8337I 3592 volume J11774 mounted in drive 3494_01 (/dev/rmt2).ANR9791I Volume J11774 in library 3494 ownership is changing from POCO_1 to SCAMP_1.ANR0408I Session 10 started for server SCAMP_1 (Windows) (Tcp/Ip) for library sharing.ANR0409I Session 10 ended for server SCAMP_1 (Windows).ANR0409I Session 8 ended for server SCAMP_1 (Windows).ANR0408I Session 11 started for server SCAMP_1 (Windows) (Tcp/Ip) for library sharing.ANR0409I Session 11 ended for server SCAMP_1 (Windows).ANR0408I Session 13 started for server SCAMP_1 (Windows) (Tcp/Ip) for library sharing.ANR0409I Session 13 ended for server SCAMP_1 (Windows).ANR0408I Session 12 started for server SCAMP_1 (Windows) (Tcp/Ip) for library sharing.ANR0409I Session 12 ended for server SCAMP_1 (Windows).ANR8336I Verifying label of 3592 volume J11774 in drive 3494_01 (/dev/rmt2).ANR8468I 3592 volume J11774 dismounted from drive 3494_01 (/dev/rmt2) in library 3494.

You can check the library volumes on the Library Manager. The output (as shown in Example 4-33) shows that the database backup volume is now owned by the Library Client SCAMP_1.

Example 4-33 Tivoli Storage Manager library volumes after the database backup

tsm: POCO_1>q libv

Library Name Volume Name Status Owner Last Use Home Device Element Type------------ ----------- ---------- ---------- --------- ------- ------3494 J11771 Private POCO_1 DbBackup3494 J11772 Scratch3494 J11773 Scratch3494 J11774 Private SCAMP_1 DbBackup

Note: In the middle of the Example 4-31, in message ANR8974I, the device special file is updated with the correct value (SAN Discovery).


Chapter 5. Library sharing with the ACSLS Manager


� Introduction to the ACSLS Manager

� Tivoli Storage Manager library sharing with the STK ACSLS Manager

– Installing on IBM AIX– Installing on Microsoft Windows– Installing on Linux– Preparation for SUN Solaris


5


5.1 Introduction to the ACSLS ManagerManagement of distributed tape libraries is both time-consuming and costly. Multiple libraries, multiple backup applications, multiple administrators, and poor resource use can add up to a high cost of ownership. The Automated Cartridge System Library Software (ACSLS Manager) offering from StorageTek centralizes the management of your tape libraries — for easier administration, increased use, and a lower cost of ownership. In short, ACSLS Manager software helps you unleash trapped profits.

ACSLS Manager allows you to implement a strategic, centralized library management solution. It functions as a central service provider for StorageTek library operations in heterogeneous environments. It allows you to collapse disparate, application dedicated libraries to one centralized library or string of libraries that are accessed via a single point of control.

Features of ACSLS Manager include:

� Tape library management

ACSLS Manager can act as the central library service provider for one or several libraries, allowing you to manage library resources from a single location.

� Centralize storage

ACSLS Manager enables a centralized storage operations model that allows you to manage more with less.

� Reduce costs

Library resource sharing reduces capital equipment, maintenance, and operating costs while simplifying library management.

� Increase availability

ACSLS Manager helps you keep your business up and running. The ACSLS High Availability solution goes even further, providing dual-server, fault-tolerant protection.

� Prevent downtime

The ACSLS High Availability solution provides serviceability and redundancy features to minimize scheduled and unscheduled downtime.

� Protect your investments

A highly flexible client/server architecture supports your mature systems to protect capital investments in libraries, drives, and software applications.

� Rich management capabilities

Fully optimize your libraries with advanced features such as auditing, reporting, event-log recording, querying, issuing service requests, and automated drive cleaning.

� Robust cartridge and volume support

Cartridges that cannot be found in the library due to ejection or absence are marked absent rather than being deleted. These cartridges are easily reactivated.

� Cartridge exchange support

ACSLS Manager software uses the pass-through port feature of StorageTek tape libraries. This feature enables the libraries to exchange cartridges between Library Storage Modules.


� Access control

Administrators can limit client access to ACSLS Manager software commands selectively through passwords and permissions. The ACSLS server itself can be protected behind a firewall.

� Dynamic resource management

The media pool feature allows you to assign each application or user its own pool of tapes to manage.

5.1.1 Basic communicationThis section describes how the Tivoli Storage Manager server communicates with the ACSLS server.

ACSLS serverThe ACSLS server manages the library control for multiple Library Clients. All Library Clients need to be connected to the ACSLS server. The library drives are attached over a SAN to all Library Clients and the library control path is attached to the ACSLS server (Figure 5-1). This is a similar setup to the IBM 3494 Library Manager.

Figure 5-1 ACSLS configuration

Important: Tivoli Storage Manager V5.3 Extended Edition provides the basic support to share ACSLS libraries across Tivoli Storage Manager servers in the same way that SCSI libraries are shared. Support for LAN-free data movement using libraries that are controlled by StorageTek’s ACSLS interface has also been provided. As a result, the use of a third party product is now optional.

SAN

LAN

ACSLSServer

STKLibrary

Control path

Data path

Application A Application B Application C

Chapter 5. Library sharing with the ACSLS Manager 129

Tivoli Storage Manager server subsystem interfaceTo control an ACSLS tape library, the Tivoli Storage Manager server communicates via a server subsystem interface (SSI), which is a daemon running on the same host as the Tivoli Storage Manager server itself. This SSI daemon then communicates to a client subsystem interface (CSI) daemon running on the ACSLS server host (as shown in Figure 5-2). The SSI can communicate with only one ACSLS server. If you have multiple ACSLS servers, you can use third-party products which can access several ACSLS servers, or you can have a dedicated Tivoli Storage Manager Library Manager for each ACSLS server. Tivoli Storage Manager V5.3 Extended Edition is required for this support.

Figure 5-2 Tivoli Storage Manager SSI

5.2 Tivoli Storage Manager library sharing with the STK ACSLS Manager

The SSI daemon is used by the Tivoli Storage Manager Library Manager over the LAN to communicate with the STK ACSLS managed tape library. The SSI is not used by Tivoli Storage Manager Library Clients. They simply use the device driver (Figure 5-3 on page 131).

This section describes how to install the SSI software and Tivoli Storage Manager device driver installation on Microsoft Windows, IBM AIX, Linux, and SUN Solaris.

Host A

ACSLS Server

CSI

Host A Host B

TSM Library Manager

SSILAN

Important: With Tivoli Storage Manager V5.3, use of a third-party product is now optional. Prior to Tivoli Storage Manager V5.3, each Tivoli Storage Manager Library Manager, Tivoli Storage Manager Library Client, and Tivoli Storage Manager Storage Agent needed a product (such as Gresham Enterprise DistribuTape).


Figure 5-3 Tape Library sharing with ACSLS

The library is attached to the ACSLS server, and the drives are attached to the Tivoli Storage Manager server. The ACSLS server and the Tivoli Storage Manager server must be on different systems. Refer to the ACSLS installation documentation for details about how to set up the library.

The ACSLS library server manages the physical aspects of tape cartridge storage and retrieval. The ACSLS client application communicates with the ACSLS library server to access tape cartridges in an automated library. Tivoli Storage Manager, as an application, gains access to tape cartridges by interacting with ACSLS through its client, which is known as the control path. The Tivoli Storage Manager server reads and writes data on tape cartridges by interacting directly with tape drives through the data path. The control path and the data path are two different paths.

5.2.1 Installing on IBM AIXThis section describes the steps for setting up ACSLS communication with Tivoli Storage Manager on AIX.

Installing library controlIf the Tivoli Storage Manager Library Manager is on an IBM AIX server, you have to install the Tivoli Storage Manager SSI. On AIX, the SSI is the Tivoli Storage Manager package tivoli.tsm.devices.acsls. You install the package using SMIT, and the installation process creates an /etc/inittab entry (as shown in Example 5-1) to start the daemon at boot time.

Example 5-1 AIX: /etc/inittab entry

autoacs:2:once:/usr/tivoli/tsm/devices/bin/rc.acs_ssi quiet >/dev/console 2>&1 #Start the ssi agent

SAN

LAN

Data Flow

Data Flow

ACSLSServer

STKLibrary

Tivoli Storage ManagerLibraryClient

LibraryControl

Server-to-servercommunication



The installation process also puts files in the /usr/tivoli/tsm/devices/bin directory. The rc.acs_ssi script is in this directory. This script starts the STK ACSLS client SSI daemon. There are two start options:

� rc.acs_ssi� rc.acs_ssi quiet

If you use the rc.acs_ssi option, you are prompted to enter the ACSLS server host name (Example 5-2). You must be able to resolve this host name to its TCP/IP address. In our case, the ACSLS manager is called ICARUS.

Example 5-2 AIX: rc.acs_ssi

(root@poco) /usr/tivoli/tsm/devices/bin>./rc.acs_ssi

****** rc.acs_ssi *******This routine initiates Event Logger (mini_el) and Server SubsystemInterface (ssi) daemons to establish ACSLS client/server interaction.It will first check if these daemons are already running and optionto kill if they are.The following environmental variables will be set to: CSI_TCP_RPCSERVICE=TRUE CSI_UDP_RPCSERVICE=TRUE CSI_CONNECT_AGETIME=172800 CSI_RETRY_TIMEOUT=4 CSI_RETRY_TRIES=5 ACSAPI_PACKET_VERSION=4

The short description of these variables can be found in rc.acs_ssi.Press any key to continue or Ctrl-c to terminate.

Enter the host name of the ACSLS server:

icarus

event.log and trace.log in the current directory containthe previous status and errors of the csi and ssi components.Do you want to NULL these files first? (y/n)

yStarting Event Logger daemon ... /usr/tivoli/tsm/devices/bin/mini_elStarting SSI daemon ... /usr/tivoli/tsm/devices/bin/ssiSIGHUP receivedParent Process ID is: 340082SIGHUP receivedParent Process #340082 EXITING NORMALLY

Initialization Done.Do you want to see the processes get started? (y/n)

y root 368702 360452 0 14:51:55 pts/2 0:00 /usr/tivoli/tsm/devices/bin/mini_el root 282824 360452 0 14:52:02 pts/2 0:00 /usr/tivoli/tsm/devices/bin/ssi 340082 50004 23#

If you use the rc.acs_ssi quiet option, you need to specify the ACSLS server host name in advance. You can edit the script and replace the $ACSLS_SERVER_HOSTNAME entry with the host name of the ACSLS server. Alternatively, you can define the environment variable


ACSLS_SERVER_HOSTNAME in the /etc/environment or /etc/profile files, as shown in Example 5-3. If the variable is defined in /etc/profile, you must export the variable.

Example 5-3 AIX: /etc/environment variable for the rc.acs_ssi

ACSLS_SERVER_HOSTNAME=icarus

After starting the SSI daemon, either manually or automatically from /etc/inittab, you can check the processes as shown in Example 5-4.

Example 5-4 AIX: SSI and event logger daemon

(root@poco) /usr/tivoli/tsm/devices/bin>ps -ef | grep ssi root 331972 1 0 Mar 22 pts/0 4:08 /usr/tivoli/tsm/devices/bin/ssi 147606 50004 23

(root@poco) /usr/tivoli/tsm/devices/bin>ps -ef | grep mini_el root 164078 1 0 Mar 22 pts/0 0:00 /usr/tivoli/tsm/devices/bin/mini_el

The mini_el program is the Event Logger daemon. This daemon writes all events that are received to the event.log and trace.log files in the same directory.

You can now define this library on the Tivoli Storage Manager server. For more information, see 5.3, “Tivoli Storage Manager configuration” on page 149.

Installing the device driverYou must install the device driver on both the Tivoli Storage Manager Library Manager and the Tivoli Storage Manager Library Client. If they are non-IBM drives, use the Tivoli Storage Manager device driver package. If they are IBM drives, you can use the IBM tape driver (Atape). Check the following Web site for the supported hardware:


We have non-IBM drives in our STK library, so we have to install the Tivoli Storage Manager device driver. The AIX package is tivoli.tsm.devices.aix5.rte. After you install the device driver with SMIT, you must configure the drives.

Using SMIT, choose Devices → Tivoli Storage Manager Devices. Our drives are connected over the SAN, so we select Fibre Channel SAN Attached Devices → Discover Devices Supported by TSM. This action starts the discovery process and creates new devices for the drives, as shown in Example 5-5.

Example 5-5 AIX: smitty TSM device, discover

Fibre Channel SAN Attached DevicesMove cursor to desired item and press Enter.

List Attributes of a Discovered Device Discover Devices Supported by TSM Remove All Defined Devices Remove a Device

F1=Help F2=Refresh F3=Cancel F8=ImageF9=Shell F10=Exit Enter=Do

Attention: Do not define the SSI_HOSTNAME environment variable. In our test environment, we were not able to use the STK ACSLS managed library with this variable.



We also have two IBM drives that are attached as well as the STK drives. The discover process creates two new devices for these drives. However, their status shows as Defined. Because we are not using the Tivoli Storage Manager device driver for the IBM drives, we delete them using the SMIT entry, as shown in Example 5-5 on page 133.

Check the devices with the lsdev command (Example 5-6). With the lsdev -Cc adsmtape command, you can view just the Tivoli Storage Manager devices.

Example 5-6 AIX: list devices

(root@poco) /tmp/tsm/5310>lsdev -Cctapelmcp0 Available LAN/TTY Library Management Control Pointrmt0 Available 1V-08-01 Other FC SCSI Tape Drivermt1 Available 1V-08-01 Other FC SCSI Tape Drivermt2 Available 1V-08-01 IBM 3592 Tape Drive (FCP)rmt3 Available 1V-08-01 IBM 3592 Tape Drive (FCP)

(root@poco) /tmp/tsm/5310>lsdev -Ccadsmtapemt0 Available 1V-08-01 Tape Drivemt1 Available 1V-08-01 Tape Drive

You can now use these two special device files (/dev/mt0 and /dev/mt1) in the Tivoli Storage Manager server drive path definitions. (For more information, see 5.3, “Tivoli Storage Manager configuration” on page 149.) Do not use the special device file /dev/rmtX for the non-IBM drives. For more information, see Chapter 5, “Determining Device Special File Names” in IBM Tivoli Storage Manager AIX Administrator’s Guide, GC32-0768.

5.2.2 Installing on Microsoft WindowsThis section describes the steps for setting up ACSLS communication with Tivoli Storage Manager on Microsoft Windows 2003.

Installing library controlIf the Tivoli Storage Manager Library Manager is on a Windows server, install an external program to communicate with the STK ACSLS server. This program is called StorageTek Library Attach (LibAttach) and is provided by StorageTek. After installing LibAttach, you can configure and start the program.

To configure, run Configurator.exe in the LibAttach directory (Figure 5-4 on page 135).


Figure 5-4 STK LibAttach configurator

Enter the STK ACSLS server host name, icarus, in the Library server host name field. After the update, restart the service to activate the new configuration. Figure 5-5 shows the service entry.

Figure 5-5 STK Microsoft Windows service entry

You can now define this library on the Tivoli Storage Manager server. (For more information see 5.3, “Tivoli Storage Manager configuration” on page 149.)

Installing the device driverYou must install the device driver on both the Tivoli Storage Manager Library Manager and the Tivoli Storage Manager Library Client. If they are non-IBM drives, use the Tivoli Storage Manager device driver package. If they are IBM drives, you can use the Atape driver. Check the following Web site for Tivoli Storage Manager supported hardware:





We have non-IBM drives in our STK library, so we install the Tivoli Storage Manager device driver. The default Microsoft Windows driver does not support all the functions that are needed to use it with Tivoli Storage Manager. The Tivoli Storage Manager device driver is provided with the Tivoli Storage Manager server code. After the install process, change the driver for the non-IBM drives so that they use the Tivoli Storage Manager device driver.

To update the tape device driver:

1. Right click the STK drive and select Update driver (Figure 5-6).

Figure 5-6 Windows: Update drive driver step 1

2. On the next screen (Figure 5-7 on page 137), select Install from a list or specific location (Advanced). Click Next.



3. Select Don’t search. I will choose the driver to install (Figure 5-8).


4. Make sure the Tivoli Storage Manager device driver is selected (Figure 5-9 on page 138).



5. Ignore the warning that the driver is not tested by Microsoft. Click Continue Anyway (Figure 5-10).


6. Repeat these steps for all non-IBM drives.

7. Reboot the server to activate the new driver.

After the reboot, in the Microsoft Windows Management Console, you we can see all the drives and the new Tivoli Storage Manager device names, such as mt0.0.0.2 or mt1.0.0.2 (Figure 5-11 on page 139). You will use these device names for the Tivoli Storage Manager server drive path definition (see 5.3, “Tivoli Storage Manager configuration” on page 149).


Figure 5-11 Windows: Management Console, device information

5.2.3 Installing on LinuxThis section describes the steps for setting up ACSLS communication with Tivoli Storage Manager on Linux.

Installing library controlA Tivoli Storage Manager on Linux cannot use the STK ACSLS, because it is not supported at the time of writing. However, we can use the STK ACSLS managed library as a LInux Tivoli Storage Manager Library Client when the Tivoli Storage Manager Library Manager is on AIX, SUN Solaris, or on Microsoft Windows.

Installing the driveYou must install the device driver on the Tivoli Storage Manager Library Client. If they are non-IBM drives, use the Tivoli Storage Manager device driver package. If they are IBM drives, you can use the Atape driver. Check the following for Tivoli Storage Manager supported hardware:


We have non-IBM drives in our STK library, so we have to install the Tivoli Storage Manager device driver, which is in the rpm package, TIVsm-tsmscsi. Example 5-7 shows the installation process.

Example 5-7 Linux: Install the Tivoli Storage Manager device driver

cadi:/tmp/5302/i686 # rpm -Uvh TIVsm-tsmscsi-5.3.0-2.i386.rpmPreparing... ########################################### [100%] 1:TIVsm-tsmscsi ########################################### [100%]cadi:/tmp/5302/i686 #

Important: For Windows 2003, the previous Tivoli Storage Manager device was replaced with a standard Windows device driver. The new device driver does not run as a service.



After the installation, configure the drives. First, check in the file /proc/scsi/scsi to verify that the devices were correctly detected by the system, as shown in Example 5-7 on page 139. You can see the two STK 9480 drives are present, as well as the other IBM 3592 drives.

Example 5-8 Linux: /proc/scsi/scsi

cadi:/opt/tivoli/tsm/devices/bin # more /proc/scsi/scsiAttached devices:Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: STK Model: 9840 Rev: 1.34 Type: Sequential-Access ANSI SCSI revision: 03Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: STK Model: 9840 Rev: 1.34 Type: Sequential-Access ANSI SCSI revision: 03Host: scsi2 Channel: 00 Id: 02 Lun: 00 Vendor: IBM Model: 03592J1A Rev: 04E6 Type: Sequential-Access ANSI SCSI revision: 03Host: scsi2 Channel: 00 Id: 03 Lun: 00 Vendor: IBM Model: 03592J1A Rev: 04E6 Type: Sequential-Access ANSI SCSI revision: 03cadi:/opt/tivoli/tsm/devices/bin #

If this /proc/scsi/scsi file is empty or not present, check that the HBA module is loaded. You can use the lsmod command to show the loaded modules (Example 5-9). To load the module, you can use the modprobe command. In this example, the QLogic HBA modules were correctly loaded.

Example 5-9 Linux: lsmod

cadi:/opt/tivoli/tsm # lsmodModule Size Used bysg 41760 0IBMtape 252988 2snd_pcm_oss 65704 0snd_pcm 112900 1 snd_pcm_osssnd_page_alloc 16264 1 snd_pcmsnd_timer 32260 1 snd_pcmsnd_mixer_oss 24448 1 snd_pcm_osssnd 71012 4 snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_osssoundcore 13536 1 sndedd 13720 0joydev 14528 0st 45212 0sr_mod 21028 0ide_cd 42628 0cdrom 43036 2 sr_mod,ide_cdnvram 13448 0thermal 16648 0processor 21568 1 thermalfan 8196 0button 10384 0battery 12804 0ac 8964 0usbserial 36080 0parport_pc 41280 0lp 15492 0parport 44232 2 parport_pc,lpipv6 275580 43sworks_agp 13472 0agpgart 36140 1 sworks_agp


ohci_hcd 24452 0evdev 13952 0usbcore 116700 4 usbserial,ohci_hcdtg3 80516 0subfs 12160 2dm_mod 59904 0reiserfs 264016 1qla2300 126592 0qla2xxx 224580 1 qla2300scsi_transport_fc 11008 1 qla2xxxsd_mod 25088 0scsi_mod 120132 7 sg,IBMtape,st,sr_mod,qla2xxx,scsi_transport_fc,sd_mod

Next, you create the /opt/tivoli/tsm/devices/bin/mt.conf file and update this file with the information from the /proc/scsi/scsi file (Example 5-10). A sample mt.conf.smp file is provided in the bin directory that you can copy and modify. Add stanzas for the two drives and provide the matching host, channel, ID, and LUN fields from the /proc/scsi/scsi file.

Example 5-10 Linux: mt.conf

cadi:/opt/tivoli/tsm/devices/bin # cp ./mt.conf.smp ./mt.confcadi:/opt/tivoli/tsm/devices/bin # vi ./mt.conf## For each stanza, a device special file will be created with# the name /dev/tsmscsi/mtn, where n corresponds to the index# specified in the stanza. For example, /dev/tsmscsi/mt0 will# correspond to a tape with SCSI ID 3, LUN 0, as specified in# the stanza below.## HOST[0]=0# CHANNEL[0]=0# ID[0]=3# LUN[0]=0#HOST[0]=scsi2CHANNEL[0]=0ID[0]=0LUN[0]=0

HOST[1]=scsi2CHANNEL[1]=0ID[1]=1LUN[1]=0


You can now start the /opt/tivoli/tsm/devices/bin/autoconf program to configure the two STK drives (Example 5-11).

Example 5-11 Linux: autoconf

cadi:/opt/tivoli/tsm/devices/bin # ./autoconfThe total numbers of devices on the system are 4./bin/mknod: `/dev/sg0': File exists/bin/mknod: `/dev/sg1': File exists/bin/mknod: `/dev/sg2': File exists/bin/mknod: `/dev/sg3': File exists

Tivoli Tape Drives:===================Index Minor Host CHN ID LUN Type Vendor_ID S/N Product_ID Rev.000 000 002 000 000 000 001 STK 331002037903 9840 1.34001 001 002 000 001 000 001 STK 331000048026 9840 1.34

cadi:/opt/tivoli/tsm/devices/bin # ls -l /dev/tsmscsi/mt*lrwxrwxrwx 1 root root 8 Apr 5 03:16 /dev/tsmscsi/mt0 -> /dev/sg0lrwxrwxrwx 1 root root 8 Apr 5 03:16 /dev/tsmscsi/mt1 -> /dev/sg1-rw-r--r-- 1 root root 238 Apr 5 03:16 /dev/tsmscsi/mtinfocadi:/opt/tivoli/tsm/devices/bin #

The two new special device files, /dev/tsmscsi/mt0 and /dev/tsmscsi/mt1, are now created. You will use these special device files in the Tivoli Storage Manager server drive path definition (see 5.3, “Tivoli Storage Manager configuration” on page 149).

5.2.4 Installing on SUN SolarisThis section describes the steps for setting up ACSLS communication with Tivoli Storage Manager on SUN Solaris.

Installing library controlIf the Tivoli Storage Manager Library Manager is on a SUN Solaris server, install the Tivoli Storage Manager SSI. This interface is shipped in the Tivoli Storage Manager software package, TIVsmSdev. Use the pkgadd command to install the software, as shown in Example 5-12 on page 143.

Note: Tivoli Storage Manager Version 5.3 supports the Passthru driver, which replaces the Tivoli Storage Manager Linux SCSI device driver. The Tivoli Storage Manager Passthru drivers require the Linux SCSI generic (sg) driver along with the Linux operating system to install the kernels. The IBM Tivoli Storage Manager Linux Administrator’s Guide, GC23-4690, Chapter 5, “Configuring Tivoli Storage Manager Passthru Drivers for Tape Drives and Libraries” describes this process.

Tip: You can test your drives with the /opt/tivoli/tsm/devices/bin/mttest program.


Example 5-12 Solaris: TIVsmSdev install

bash-2.03# pkgadd -d .

The following packages are available: 1 TIVsmS Tivoli Storage Manager/Sun Server (sparc) Version 5 Release 3 Level 0.2 2 TIVsmSdev Tivoli Storage Manager/Sun Solaris Device Drivers (sparc) Version 5 Release 3 Level 0.2


Processing package instance <TIVsmSdev> from </tmp/5302>

Tivoli Storage Manager/Sun Solaris Device Drivers(sparc) Version 5 Release 3 Level 0.2Licensed Materials - Property of IBM

5608-ISM5608-ISX

(C) Copyright International Business Machines Corp. 1990, 2004.All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corp.## Executing checkinstall script.Using </opt> as the package base directory.## Processing package information.## Processing system information. 4 package pathnames are already properly installed.## Verifying package dependencies.## Verifying disk space requirements.## Checking for conflicts with packages already installed.## Checking for setuid/setgid programs.


Do you want to continue with the installation of <TIVsmSdev> [y,n,?] y

Installing Tivoli Storage Manager/Sun Solaris Device Drivers as <TIVsmSdev>

## Installing part 1 of 1./opt/tivoli/tsm/devices/README.DEVICES/opt/tivoli/tsm/devices/bin/autoconf/opt/tivoli/tsm/devices/bin/ddtrace/opt/tivoli/tsm/devices/bin/kill.acs_ssi/opt/tivoli/tsm/devices/bin/lb/opt/tivoli/tsm/devices/bin/lb.conf/opt/tivoli/tsm/devices/bin/lbtest/opt/tivoli/tsm/devices/bin/mini_el/opt/tivoli/tsm/devices/bin/mt/opt/tivoli/tsm/devices/bin/mt.conf/opt/tivoli/tsm/devices/bin/mttest/opt/tivoli/tsm/devices/bin/op/opt/tivoli/tsm/devices/bin/op.conf/opt/tivoli/tsm/devices/bin/optest/opt/tivoli/tsm/devices/bin/rc.acs_ssi/opt/tivoli/tsm/devices/bin/ssi


/opt/tivoli/tsm/devices/bin/t_parent/opt/tivoli/tsm/devices/bin/tsmdlist/opt/tivoli/tsm/devices/bin/tsmtrc[ verifying class <none> ]## Executing postinstall script.

Installation of <TIVsmSdev> was successful.

The following packages are available: 1 TIVsmS Tivoli Storage Manager/Sun Server (sparc) Version 5 Release 3 Level 0.2 2 TIVsmSdev Tivoli Storage Manager/Sun Solaris Device Drivers (sparc) Version 5 Release 3 Level 0.2

Select package(s) you wish to process (or 'all' to processall packages). (default: all) [?,??,q]: qbash-2.03#

After installation, the script rc.acs_ssi is available in the /opt/tivoli/tsm/devices/bin directory. This script starts the STK ACSLS client SSI daemon. There are two start options:

� rc.acs_ssi� rc.acs_ssi quiet

If you use the rc.acs_ssi option, you are prompted to enter the ACSLS server host name (Example 5-13). You must be able to resolve the host name to its TCP/IP address. In our case, the ACSLS server is on the host icarus.

Example 5-13 Solaris: rc.acs_ssi

bash-2.03# ./rc.acs_ssi****** rc.acs_ssi *******This routine initiates Event Logger (mini_el) and Server SubsystemInterface (ssi) daemons to establish ACSLS client/server interaction.It will first check if these daemons are already running and optionto kill if they are.The following environmental variables will be set to: CSI_TCP_RPCSERVICE=TRUE CSI_UDP_RPCSERVICE=TRUE CSI_CONNECT_AGETIME=172800 CSI_RETRY_TIMEOUT=4 CSI_RETRY_TRIES=5 ACSAPI_PACKET_VERSION=4

The short description of these variables can be found in rc.acs_ssi.Press any key to continue or Ctrl-c to terminate.

Event Logger already running, mini_el pid=534Do you want to kill this process to continue? (y/n)ykilling 534

SSI already running, ssi pid=606Do you want to kill this process to continue? (y/n)ykilling 606

SSI already running, ssi pid=624Do you want to kill this process to continue? (y/n)y


killing 624

Enter the host name of the ACSLS server:

icarus

event.log and trace.log in the current directory containthe previous status and errors of the csi and ssi components.Do you want to NULL these files first? (y/n)

yStarting Event Logger daemon ... /opt/tivoli/tsm/devices/bin/mini_elStarting SSI daemon ... /opt/tivoli/tsm/devices/bin/ssiSIGHUP receivedParent Process ID is: 7736SIGHUP receivedParent Process #7736 EXITING NORMALLY

Initialization Done.Do you want to see the processes get started? (y/n)y root 7734 7684 0 15:16:14 pts/3 0:00 /opt/tivoli/tsm/devices/bin/mini_el root 7738 7684 0 15:16:21 pts/3 0:00 /opt/tivoli/tsm/devices/bin/ssi 7736 50004 23bash-2.03#

If you use the rc.acs_ssi quiet option, you must replace $ACSLS_SERVER_HOSTNAME with the name of the ACSLS server in this file. Alternatively, you can define the environment variable ACSLS_SERVER_HOSTNAME in the /etc/environment or /etc/profile files (Example 5-3 on page 133). If the variable is defined in /etc/profile, you must export the variable, as shown in Example 5-14.

Example 5-14 Solaris: /etc/environment variable for the rc.acs_ssi

ACSLS_SERVER_HOSTNAME=icarus

You can now define this library on the Tivoli Storage Manager server (see 5.3, “Tivoli Storage Manager configuration” on page 149).

Installing the driveYou must install the device driver on both the Tivoli Storage Manager Library Manager and the Tivoli Storage Manager Library Client. If they are non-IBM drives, use the Tivoli Storage Manager device driver package. If they are IBM drives, you can use the Atape driver. See the following for Tivoli Storage Manager supported hardware:


Attention: Do not define the SSI_HOSTNAME environment variable. In our test environment, we were not able to use the STK ACSLS managed library with this variable.




We have non-IBM drives in our STK library, so we need to use the Tivoli Storage Manager device driver. This driver is in the same package that is installed for the Tivoli Storage Manager SSI (TIVsmSdev). The device driver configuration file is /opt/tivoli/tsm/devices/bin/mt.conf. Edit this file with the values for the drives (Example 5-15).

Example 5-15 Solaris: mt.conf

## ---------------------------------------------------------# Tivoli Storage Manager Server for Sun Solaris# Licensed Materials - Property of IBM# 5765-303 (C) Copyright IBM Corporation 1999.# All rights reserved.# Refer to Copyright Instructions Form Number G120-2083# ---------------------------------------------------------## ---------------------------------------------------------# TSM SCSI tape device driver configuration file# ---------------------------------------------------------## This file should contain one stanza of the following form# for each SCSI tape drive that the IBM Tivoli Storage# Manager server is to use:## name="mt" class="scsi"# target=$X$ lun=$Y$;## ---------------------------------------------------------# TSM Fibre tape device driver configuration file# ---------------------------------------------------------## This file should contain one stanza of the following form# for each Fibre tape drive that the IBM Tivoli Storage# Manager server is to use:## name="mt" class="scsi"# target=$X$ lun=$Y$ hba="Z" wwpn="W";## The $X$ string should be replaced with the SCSI ID of# the tape drive. This will be a number in the range# 0-6 (7 is reserved for the SCSI adapter and cannot be# used for devices), and possibly 8-15, depending on the# type of the SCSI adapter. In a configuration where# devices attached to multiple initiators with the same# SCSI id, only one target/lun id has to be specified. The# "add_drv" command will probe all devices as specified in# the mt.conf file and create separate device special file# for each entity.## The $Y$ string should be replaced with the SCSI logical# unit number (LUN) of the device. This is usually zero.# All other fields should be left as they appear in the# above example.## The "Z" string should be replaced with the HBA pci bus# number. It can be determined on the boot up screen.## The "W" string should be replaced with the HBA world wide# port number. It can be determined on the boot up screen.#


# Note: Both "Z" and "W" strings are optional. IBM Tivoli# Storage Manager does not support and implement them.# Those strings are going to help Solaris machine to have# better ability to determine and add the fibre device.# ---------------------------------------------------------# Special case for Fibre devices on SUN HBA# ---------------------------------------------------------## IBM Tivoli Storage Manager only supports the SUN Storage# certified devices on "Sun StorEdge 2G Fibre Channel PCI# Single Channel Network Adapter".## name="mt" parent="fp" target=0 lun=0# fc-port-wwn="U";## The "U" string should be replaced by fc-port-wwn.# For example, "500104f00048b9c9".## The following line is required for IBM Tivoli Storage# Manager version 5.3.0 or later.# name="mt" parent="pseudo" instance=16383;# name="mt" class="scsi" target=8 lun=0; name="mt" class="scsi" target=9 lun=0;

To find the target and LUN ID, view the file /var/adm/messages (as shown in Example 5-16) or use the dmesg command.

Example 5-16 Solaris: /var/adm/messages

...Apr 4 15:14:50 sunset mt: [ID 436682 kern.notice] adsm scsi_probe: Target 8 Lun 0, STK 9840Apr 4 15:14:50 sunset scsi: [ID 193665 kern.info] mt3203 at qla23000: target 8 lun 0Apr 4 15:14:50 sunset genunix: [ID 936769 kern.info] mt3203 is /pci@1f,4000/fibre-channel@2/mt@8,0...Apr 4 15:14:50 sunset mt: [ID 436682 kern.notice] adsm scsi_probe: Target 9 Lun 0, STK 9840Apr 4 15:14:50 sunset scsi: [ID 193665 kern.info] mt3204 at qla23000: target 9 lun 0Apr 4 15:14:50 sunset genunix: [ID 936769 kern.info] mt3204 is /pci@1f,4000/fibre-channel@2/mt@9,0...

To create the special device file for the drives, you can use the autoconf script in the same directory, as shown in Example 5-17 on page 148. This script deletes all previously defined Tivoli Storage Manager devices for tape drives (/dev/rmt/*mt*), optical drives (/dev/rmt/*op*), and libraries (/dev/rmt/*lb*). In then configures all tape drives, optical drives, and libraries. Finally, the script creates three special files for tracing the Tivoli Storage Manager device driver which are used by Tivoli Storage Manager support if required.


Example 5-17 Solaris: autoconf

bash-2.03# /opt/tivoli/tsm/devices/bin/autoconfSetting up aliasesAll alias set-----exit status = 0devfsadm[7850]: verbose: mknod /devices/pci@1f,4000/fibre-channel@2/mt@8,0:mt 2l/2l/20666devfsadm[7850]: verbose: symlink /dev/rmt/1mt -> ../../devices/pci@1f,4000/fibre-channel@2/mt@8,0:mtdevfsadm[7850]: verbose: mknod /devices/pci@1f,4000/fibre-channel@2/mt@8,0:mtn 2l/2l/20666devfsadm[7850]: verbose: symlink /dev/rmt/1mtn -> ../../devices/pci@1f,4000/fibre-channel@2/mt@8,0:mtndevfsadm[7850]: verbose: mknod /devices/pci@1f,4000/fibre-channel@2/mt@8,0:mtt 2l/2l/20666devfsadm[7850]: verbose: symlink /dev/rmt/1mtt -> ../../devices/pci@1f,4000/fibre-channel@2/mt@8,0:mttdevfsadm[7850]: verbose: mknod /devices/pci@1f,4000/fibre-channel@2/mt@9,0:mt 2l/2l/20666devfsadm[7850]: verbose: symlink /dev/rmt/2mt -> ../../devices/pci@1f,4000/fibre-channel@2/mt@9,0:mtdevfsadm[7850]: verbose: mknod /devices/pci@1f,4000/fibre-channel@2/mt@9,0:mtn 2l/2l/20666devfsadm[7850]: verbose: symlink /dev/rmt/2mtn -> ../../devices/pci@1f,4000/fibre-channel@2/mt@9,0:mtndevfsadm[7850]: verbose: mknod /devices/pci@1f,4000/fibre-channel@2/mt@9,0:mtt 2l/2l/20666devfsadm[7850]: verbose: symlink /dev/rmt/2mtt -> ../../devices/pci@1f,4000/fibre-channel@2/mt@9,0:mttDriver (mt) installed.

exit status = 0devfsadm: driver failed to attach: opexit status = 11Warning: Driver (op) successfully added to system but failed to attachDriver (op) installed.

exit status = 0devfsadm: driver failed to attach: lbexit status = 11Warning: Driver (lb) successfully added to system but failed to attachDriver (lb) installed.

IBM TIVOLI STORAGE MANAGER by IBMDevice List Utility Program for Sun SolarisLicensed Materials - Property of IBM

5698-ISE (C) Copyright IBM Corporation 2004. All rights reserved.U.S. Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corporation.

Inst Special File Vendor Product Serial Target LUN World Wide Name Firmware---- ------------ ------ ------- ------------ ------ --- ---------------- --------3204 /dev/rmt/2mt STK 9840 331000048026 9 0 500104f00043eaa7 1.343203 /dev/rmt/1mt STK 9840 331002037903 8 0 500104f00045cb26 1.34

o Tape drive configuration information has been saved in mtinfo

bash-2.03#


To show drive information, view the mtinfo file (Example 5-18) or start the tsmdlist program (Example 5-19), which are both in the /opt/tivoli/tsm/devices/bin directory.

Example 5-18 Solaris: /opt/tivoli/tsm/devices/bin/mtinfo

bash-2.03# cat /opt/tivoli/tsm/devices/bin/mtinfoInst Special File Vendor Product Serial Target LUN World Wide Name Firmware---- ------------ ------ ------- ------------ ------ --- ---------------- --------3203 /dev/rmt/1mt STK 9840 331002037903 8 0 500104f00045cb26 1.343204 /dev/rmt/2mt STK 9840 331000048026 9 0 500104f00043eaa7 1.34

Example 5-19 Solaris: /opt/tivoli/tsm/devices/bin/tsmdlist

bash-2.03# /opt/tivoli/tsm/devices/bin/tsmdlist

IBM TIVOLI STORAGE MANAGER by IBMDevice List Utility Program for Sun SolarisLicensed Materials - Property of IBM

5698-ISE (C) Copyright IBM Corporation 2004. All rights reserved.U.S. Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corporation.

Inst Special File Vendor Product Serial Target LUN World Wide Name Firmware---- ------------ ------ ------- ------------ ------ --- ---------------- --------3203 /dev/rmt/1mt STK 9840 331002037903 8 0 500104f00045cb26 1.343204 /dev/rmt/2mt STK 9840 331000048026 9 0 500104f00043eaa7 1.34


The drives are ready to be defined in the Tivoli Storage Manager Server.

5.3 Tivoli Storage Manager configurationThis section summarizes the Tivoli Storage Manager commands that are required to set up library sharing with an STK ACSLS managed tape library. In our test environment, the Tivoli Storage Manager Library Manager (LM) was e installed on the AIX server poco and the Library Client (LC) was installed on the Sun Solaris server sunset. The ACSLS server is named icarus. We are using an STK L180 library with two STK 9840 drives.

For detailed information about installing the Tivoli Storage Manager server, see:

� IBM Tivoli Storage Manager for AIX Installation Guide V5.3, GC32-1597� IBM Tivoli Storage Manager Implementation Guide, SG24-5416

Figure 5-12 on page 150 shows our test environment.


Figure 5-12 Lab overview

The setup steps are:

1. Defining server-to-server communication on the Library Manager.2. Setting the ACSLS options.3. Defining the library on the Library Manager.4. Defining the drives for this library on the Library Manager.5. Defining the drives path on the Library Manager.6. Defining a device class that uses the library on the Library Manager.7. Checking in library volumes on the Library Manager.8. Defining server-to-server communication on the Library Client.9. Defining the library on the Library Client.10.Defining the drive path for the Library Client on the Library Manager.11.Defining a device class that uses the library on the Library Client.12.Checking the setup.

5.3.1 Defining server-to-server communication on the Library ManagerTo use the library sharing, we have to set up server-to-server communication between the Library Manager, poco, and the Library Client, sunset. Example 5-20 shows the required commands.

Example 5-20 Server-to-Server communication

SET SERVERPASSWORD secretSET SERVERNAME POCO_1 SET SERVERHLADDRESS 9.11.213.9 SET SERVERLLADDRESS 1500DEFINE SERVER POCO_1 serverpassword=secret HLADDRESS=9.11.213.110 lladdress=1500DEFINE SERVER SUNSET_1 serverpassword=secret HLADDRESS=9.11.213.107 lladdress=1500

SAN

LAN

Data Flow

Data Flow

ACSLSServer

STKLibrary

Tivoli Storage ManagerLibraryClient

LibraryControlServer-to-server

communication


SUNSET POCO ICARUS


5.3.2 Setting the ACSLS optionsThere are four Tivoli Storage Manager server options for the ACSLS libraries which are defined in dsmserv.opt on the Tivoli Storage Manager Library Manager:

� AcsAccessId

Specifies the ID for the Automatic Cartridge System (ACS) access control. The default ID is your local host name.

� AcsTimeoutX

Specifies the multiple for the built-in timeout value for ACSLS APIs. The built-in timeout value for the ENTER, EJECT, and AUDIT ACS API is 1800 seconds; for all other ACSLS APIs it is 600 seconds. For example, if the multiple value specified is five (5), the timeout value for audit API becomes 9000 seconds, and all other APIs become 3000 seconds. The default is one (1).

� AcsLockDrive

Specifies if the drives within the ACSLS libraries are locked. Drive locking ensures the exclusive use of the drive in the ACSLS library in a shared environment. However, there is some performance gain if libraries are not locked. If other applications are not sharing the Tivoli Storage Manager drives, drive locking is not required. The default is NO.

� AcsQuickInit

Specifies whether, at server start, the initialization of the ACSLS library is a quick or full initialization. When a full initialization of the library occurs, the initialization matches the ACSLS inventory with the Tivoli Storage Manager inventory and validates the locking of each server-owned volume. It also validates that drives within the ACSLS libraries are locked. The full initialization takes about one to two seconds per volume. If your library inventory is large, it could take a long time to fully initialize the library during server start. The default is NO.

For this example, we leave all these Tivoli Storage Manager server options at their default values (Example 5-21).

Example 5-21 dsmserv.opt: acs options

...*======================================================================** ACSTIMEOUTX (not available on z/OS, HP & Linux)** Specifies the multiple for the build-in timeout value for ACSLS API.* The build-in timeout value for ACS audit API is 1800 seconds, for* all other APIs are 600 seconds. If the multiple value specified is 5,* the timeout value for audit API becomes 9000 seconds and all other* APIs becomes 3000 seconds.** Syntax* +------------------+----------------------------------------------+* | ACSTIMEOUTX | value |* +------------------+----------------------------------------------+** Parameters* value Specifies the multiple for the build-in timeout* value for ACSLS API. The minimum value is 1, the* maximum value is 100 and the default is 1.

Note: Ask your STK ACSLS administrator for further informations.


** Examples* ACSTIMEOUTX 5**========================================================================** ACSACCESSID (not available on z/OS, HP & Linux)** Specifies the id for the ACS access control.** Syntax* +------------------+----------------------------------------------+* | ACSACCESSID | name |* +------------------+----------------------------------------------+** Parameters* name Specifies the id for the ACS access control.** The default id is hostname. When specified the* name must be between 1 to 64 in length.** Examples* ACSACCESSID startrek*=======================================================================*** ACSLOCKDRIVE (not available on z/OS, HP & Linux)** Specifies if the drives within the ACSLS libraries to be locked.* Drive locking ensures the exclusive use of the drive within the* ACSLS library in a shared environment. However, there are some* performance improvements if locking is not performed. If the TSM* drives are not shared with other applications in the configuration* then drive locking are not required.** The default is NO** +------------------+----------------------------------------------+* | ACSLOCKDRIVE | [YES | NO] |* +------------------+----------------------------------------------+**=======================================================================*** ACSQUICKINIT (not available on z/OS, HP & Linux)** Specifies if the initialization of the ACSLS library should be quick* or full initialization during the server startup.** The full initialization matches the ACSLS inventory with the server* inventory and validate the locking for each TSM owned volume. It* also validates the drive locking and dismount all volumes currently* in the ADSM drive. The full initialization takes about 1-2 seconds* per volume and can take a long time during the server startup if* the library inventory is large.** ACSQUICKINIT bypasses all the inventory matching, lock validation and* volume dismounting from the drive. The user must ensure the integrity* of the TSM inventory and drive availability, all TSM volumes* or drives are assumed locked by the same lock_id and available.* This option is useful for server restart, and should only be used* if all TSM inventory and resources remain the same while the server


* is down.** The default is NO** +------------------+----------------------------------------------+* | ACSQUICKINIT | [YES | NO] |* +------------------+----------------------------------------------+**=========================================================================...

5.3.3 Defining the library on the Library ManagerTo define the library, run this command:

DEFINE LIBRARY ACSLS LIBTYPE=acsls SHARED=yes ACSID=0

Example 5-22 ACSLS: query acs

(root@icarus) /> /STKhome/ACSSS/bin/cmd_proc

This material is confidential and proprietary to StorageTek and may be licensed only under a valid StorageTek license. Do not copy or distribute unless authorized in writing by StorageTek.

If this software is used by the Government, use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.7-7013.

---------------------------------ACSLS 6.1.1--------------------------------------------ACSSA> query acs all2005-03-14 14:48:56 ACS Status Identifier State Free Cell Audit Mount Dismount Enter Eject Count C/P C/P C/P C/P C/P 0 online 79 0/0 0/0 0/0 0/0 0/0ACSSA>

5.3.4 Defining the drives for this library on the Library ManagerTo define the drives for this library, run these commands:

DEFINE DRIVE ACSLS ACSLS_01 ACSDRVID=0,0,0,1DEFINE DRIVE ACSLS ACSLS_02 ACSDRVID=0,0,0,6

Important: Be sure to use the right ACSID. Example 5-22 shows the query on the ACSLS server icarus to find the ACSID or you can ask the ACSLS administrator. This example, and remaining examples on the ACSLS server, use the ACSSA prompt, which you start with the /STKhome/ACSSS/bin/cmd_proc command.

Attention: You do not need to define a path for the STK ACSLS managed library, because the control path is via SSI to the ACSLS server.


To find the ACSDRVID, you can use the ACSLS query drive command, as shown in Example 5-23.

Example 5-23 ACSLS: query drive

---------------------------------ACSLS 6.1.1--------------------------------------------ACSSA> query drive all2005-03-14 14:47:46 Drive Status Identifier State Status Volume Type 0, 0, 0, 0 online available HP-LTO-2 0, 0, 0, 1 online available 9840 0, 0, 0, 2 online available SDLT-320 0, 0, 0, 3 online available SDLT-320 0, 0, 0, 4 online available HP-LTO-2 0, 0, 0, 5 online available HP-LTO-2 0, 0, 0, 6 online available 9840ACSSA>

This command reports several drives. However, for our testing, we used just the two 9840 drives.

5.3.5 Defining the drives path on the Library ManagerTo define the drives path, run these commands:

DEFINE PATH POCO_1 ACSLS_01 SRCTYPE=server DESTTYPE=drive LIBRARY=ACSLS DEVICE=/dev/mt0DEFINE PATH POCO_1 ACSLS_02 SRCTYPE=server DESTTYPE=drive LIBRARY=ACSLS DEVICE=/dev/mt1

5.3.6 Defining a device class that uses the library on the Library ManagerTo define a device class that uses the library, run this command:

DEFINE DEVCLASS 9840 LIBRARY=ACSLS DEVTYPE=ecartridge FORMAT=drive

5.3.7 Checking in library volumes on the Library ManagerTo check in library volumes, run these commands:

CHECKIN LIBV ACSLS SEARCH=yes VOLRANGE=CB5381,CB5382 STATUS=scratchCHECKIN LIBV ACSLS CB5384 STAT=scratch

Use the LABEL LIBVOLUME command, if the library volumes are unlabeled.

LABEL LIBVOLUME acsls CB5384 CHECKIN=SCRATCH

Attention: Avoid specifying FORMAT=DRIVE when a mixture of drives is used within the same library. For example, do not use this option for a library that contains some drives that support higher recording formats than other drives.


To determine the library volumes to check in, you can use the query scratch command on the ACSLS server, as shown in Example 5-24.

Example 5-24 ACSLS: query scratch

---------------------------------ACSLS 6.1.1--------------------------------------------ACSSA> q scratch all 2005-03-14 15:14:05 Scratch Status Scratch Pool Identifier Home Location Status Type 9840 CB5381 0, 0, 1, 1, 0 home STK1R 9840 CB5384 0, 0, 1, 2, 0 home STK1R 9840 CB5382 0, 0, 1, 3, 0 home STK1RACSSA>

After the library volumes are checked in, you can query whether the library volumes are visible on the Tivoli Storage Manager server using the QUERY LIBVOLUME command, as shown in Example 5-25.

Example 5-25 LM: query library volumes

tsm: POCO_1>q libv

Library Name Volume Name Status Owner Last Use Home Device Element Type------------ ----------- ---------- ---------- --------- ------- ------ACSLS CB5381 ScratchACSLS CB5382 ScratchACSLS CB5384 Scratch

5.3.8 Defining server-to-server communication on the Library ClientExample 5-26 shows the required commands to define server-to-server communication.

Example 5-26 Server-to-Server definition on the Library Client

SET SERVERPASSWORD secretSET SERVERNAME SUNSET_1 SET SERVERHLADDRESS 9.11.213.107 SET SERVERLLADDRESS 1500DEFINE SERVER POCO_1 serverpassword=secret HLADDRESS=9.11.213.110 lladdress=1500DEFINE SERVER SUNSET_1 serverpassword=secret HLADDRESS=9.11.213.107 lladdress=1500

5.3.9 Defining the library on the Library ClientTo define the library, run this command:

DEFINE LIBRARY ACSLS LIBTYPE=shared PRIMARYLIBMANAGER=poco_1

This command refers back to the Library Manager, poco.

5.3.10 Defining the drive path for the Library Client on the Library ManagerThese use the Solaris device names as shown in Example 5-17 on page 148.

DEF PATH sunset_1 ACSLS_01 SRCT=server DESTT=drive LIBR=acsls DEVICE=/dev/rmt/1mtDEF PATH sunset_1 ACSLS_02 SRCT=server DESTT=drive LIBR=acsls DEVICE=/dev/rmt/2mt


5.3.11 Defining a device class that uses the library on the Library ClientTo define a device class that uses the library, run this command:

DEFINE DEVCLASS 9840 LIBRARY=ACSLS DEVTYPE=ecartridge FORMAT=drive

5.3.12 Checking the setupLibrary sharing for the STK library is now ready and we can take a Tivoli Storage Manager database backup on the Library Client. Example 5-27 shows the activity log on the Library Client, and Example 5-28 on page 157 shows the activity log on the Library Manager.

Example 5-27 Tivoli Storage Manager activity log on the Library Client

ANR2017I Administrator ADMIN issued command: BACKUP DB devcl=9840 t=fANR0984I Process 2 for DATABASE BACKUP started in the BACKGROUND at 03:45:29 PM.ANR2280I Full database backup started as process 2.ANR0408I Session 4 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 4 ended for server POCO_1 (AIX-RS/6000).ANR0408I Session 5 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 5 ended for server POCO_1 (AIX-RS/6000).ANR8337I ECARTRIDGE volume CB5381 mounted in drive ACSLS_02 (/dev/rmt/2mt).ANR0511I Session 1 opened output volume CB5381.ANR1360I Output volume CB5381 opened (sequence number 1).ANR1361I Output volume CB5381 closed.ANR0514I Session 1 closed volume CB5381.ANR0408I Session 6 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0408I Session 7 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 6 ended for server POCO_1 (AIX-RS/6000).ANR0408I Session 8 started for server POCO_1 (AIX-RS/6000) (Tcp/Ip) for library sharing.ANR0409I Session 8 ended for server POCO_1 (AIX-RS/6000).ANR4502W No files have been defined for automatically storing sequential volume history information.ANR4550I Full database backup (process 2) complete, 174 pages copied.ANR0985I Process 2 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 03:47:19 PM.ANR8336I Verifying label of ECARTRIDGE volume CB5381 in drive ACSLS_02 (/dev/rmt/2mt).ANR8468I ECARTRIDGE volume CB5381 dismounted from drive ACSLS_02 (/dev/rmt/2mt) in library ACSLS.

Tip: With the SAN Discovery feature, the Tivoli Storage Manager server identifies the correct device special file for the Library Client using the serial number of the tape drive. For more information, see Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.


Example 5-28 Tivoli Storage Manager activity log on the Library Manager

ANR0408I Session 52 started for server SUNSET_1 (Solaris 8/9) (Tcp/Ip) for library sharing.ANR0409I Session 52 ended for server SUNSET_1 (Solaris 8/9).ANR0408I Session 53 started for server SUNSET_1 (Solaris 8/9) (Tcp/Ip) for library sharing.ANR2017I Administrator ADMIN issued command: QUERY LIBRANR2017I Administrator ADMIN issued command: QUERY PATHANR0405I Session 51 ended for administrator ADMIN (WinNT).ANR0407I Session 54 started for administrator ADMIN (WinNT) (Tcp/Ip 9.1.38.61(3844)).ANR8337I ECARTRIDGE volume CB5381 mounted in drive ACSLS_02 (/dev/mt1).ANR9791I Volume CB5381 in library ACSLS ownership is changing from POCO_1 to SUNSET_1.ANR0409I Session 53 ended for server SUNSET_1 (Solaris 8/9).ANR0408I Session 55 started for server SUNSET_1 (Solaris 8/9) (Tcp/Ip) for library sharing.ANR0409I Session 55 ended for server SUNSET_1 (Solaris 8/9).ANR0408I Session 57 started for server SUNSET_1 (Solaris 8/9) (Tcp/Ip) for library sharing.ANR0409I Session 57 ended for server SUNSET_1 (Solaris 8/9).ANR0408I Session 56 started for server SUNSET_1 (Solaris 8/9) (Tcp/Ip) for library sharing.ANR0409I Session 56 ended for server SUNSET_1 (Solaris 8/9).ANR8336I Verifying label of ECARTRIDGE volume CB5381 in drive ACSLS_02 (/dev/mt1).ANR8468I ECARTRIDGE volume CB5381 dismounted from drive ACSLS_02 (/dev/mt1) in library ACSLS.

You can check the library volumes on the Library Manager to confirm that the database backup volume is now used on the Library Client SUNSET_1. Example 5-29 shows that the owner of the CB5381 volume is now the Library Client SUNSET_1 and that it has been used for a database backup.

Example 5-29 Tivoli Storage Manager library volumes after the database backup

tsm: POCO_1>q libv

Library Name Volume Name Status Owner Last Use Home Device Element Type------------ ----------- ---------- ---------- --------- ------- ------ACSLS CB5381 Private SUNSET_1 DbBackupACSLS CB5382 ScratchACSLS CB5384 Scratch



Chapter 6. Planning for LAN-free

This chapter covers the preliminary stages that are involved in preparing a LAN-free backup environment. There are a number of different elements involved in performing backups in a SAN environment, and configuration of all of them can become confusing. Therefore, we recommend that you take the time for careful planning to allow for a smooth setup experience.


� Details about LAN-free backup� When to use LAN-free data movement� The ideal LAN-free client machine� Supported operating systems and requirements� Configuration preparations� Compatibility concerns

6


6.1 Details about LAN-free backupWe discussed the basics of LAN-free backup in 1.3, “Tivoli Storage Manager SAN functions” on page 4. This section now provides the detail that can help you plan an effective configuration. First, we’ll discuss the flow of control during a LAN-free backup.

The steps involved in performing a Tivoli Storage Manager LAN-free backup are:

1. The Backup-Archive Client begins a backup operation. The Tivoli Storage Manager server reports policy information to the client, including whether a destination is LAN-free. As the client assigns policy settings for files during backup processing, it uses the Storage Agent to send the data via LAN-free when the destination for that policy is LAN-free enabled.

2. The Storage Agent receives data for those files backed up by the client and assigned to policy settings that use a LAN-free enabled storage pool. The Storage Agent sends a request for a volume mount to the Library Manager server.

3. A request is sent from the Library Manager to the storage device to mount the appropriate media.

4. The Library Manager notifies the Storage Agent of the location where the mounted media resides.

5. The client, by means of the Storage Agent, writes the backup data directly to the device over the SAN.

6. The Storage Agent sends metadata information to the Tivoli Storage Manager server over the LAN, and the server stores the information in its database.

Figure 6-1 on page 161 gives a further breakdown of a typical client backup process. The tasks that are performed on the LAN-free (that is, the SAN path) are indicated by the thick red arrow, while the other tasks (with black arrows) use the LAN path. As you can see, of the whole backup processes, only one actually uses the LAN-free path for actual transfer of backup data. All the other tasks, which are metadata related, use the LAN path. Therefore, depending on the profile of the backup to be performed, the proportion of time spent transferring over the LAN versus the SAN will be different.

Note: A storage pool is a LAN-free destination when the storage pool is associated with a device that is shared on the SAN. That device must also have a defined path between the device and the Storage Agent machine, using the DEFINE PATH command.


Figure 6-1 Steps for a LAN-free backup

6.2 When to use LAN-free data movementDetermining when to use LAN-free data movement as opposed to traditional LAN backup can be confusing. To achieve the best overall performance, you should consider the type of data on the client. As discussed in 6.1, “Details about LAN-free backup” on page 160, LAN-free backup makes substantial use of the LAN for control and other information exchange. Different backup types will generate a different profile of LAN versus SAN usage and might be better suited to one type of backup rather than the other.

When trying to decide what is appropriate for your environment, consider the following common factors that could predicate use of a LAN-free backup:

� A congested network

This factor includes overall network congestion as well as any network limitations between the client and the server machines.

� Constrained server

The Tivoli Storage Manager server system’s resources are a factor. Perhaps there are already a large number of clients backing up to a single server.

� Available SAN storage resources

Streaming data to tape over the SAN can be faster than using the network, providing that client systems have access to the SAN storage resources.

� Type of data to be backed up

Because the LAN-free path is used for sending the actual data, and not the metadata, a client workload, which has proportionately more metadata than data to send, will in general see less benefit from using the LAN-free path. Conversely, a client workload which spends most of its time sending data will see a greater benefit from using LAN-free backup. From this, you can extrapolate that large file sizes are better suited for LAN-free backup. (Further discussion on this topic is in 6.3, “The ideal LAN-free client machine” on page 162.)

Chapter 6. Planning for LAN-free 161

� When not to use LAN-free

Generally, when doing traditional Tivoli Storage Manager progressive incremental backups, consider multithreading many clients with many small files to a shared random disk storage pool using the LAN. In this type of backup, each client typically spends more time selecting the actual files to be backed up and other processing rather than in actual data transmission. Therefore, you will see little or no benefit from using the LAN-free path. In some cases, LAN-free to disk is appropriate.

6.3 The ideal LAN-free client machineLAN-free performance continues to improve through subsequent releases of Tivoli Storage Manager, due in part to improved default options and other algorithmic factors. However, one of the most common misconceptions when backing up over the SAN is the expected performance.

SAN-based (or LAN-free) backup performance will decrease when many smaller objects are transferred, because more time is spent in non-SAN communications. In some cases, a LAN-based backup might even be faster than a SAN-based one for the same workload. Most typically, using LAN-free for backing up larger objects, such as database files or full volume image backups, yields the best performance. Traditional Tivoli Storage Manager progressive incremental backups usually perform better over the LAN than LAN-free, because this type of backup typically does not exploit fully the speed of the SAN or allow a tape drive to operate at streaming speeds. LAN-free to disk backup might also be appropriate for these type of environments.

To illustrate this point, we performed some simple backup tests in our lab to show the effects of transferring larger and fewer objects when compared to transferring smaller and many objects. The results of the test are shown in Figure 6-2 on page 163 and Table 6-1 on page 163.

The test results show the effects of backing up many smaller files using LAN-free when compared to backing up larger and fewer files. Information about the infrastructure used during the testing is intentionally omitted in order to focus entirely on the relative effect of file size on performance, rather than the performance numbers themselves.

The test environment used a Tivoli Storage Manager V5.3 server, Storage Agent, and Backup-Archive Client. All backups (LAN and LAN-free) were sent to tape. All client and server options were left at the default. No modifications were made to any performance related options. Other than the bare minimum for establishing communication with the server and configuring LAN-free, no other options were modified.

We performed multiple LAN-free backup tests of data that equaled 2 GB total. We started with backing up a single 2 GB file and recorded the aggregate transfer rate. We then increased the number of files to 10, with each file being 200 MB in size, to give us a total of 2 GB. We continued increasing the number of files and running backups until the test consisted of one million files, each 2 KB in size. We ran four backup tests for each data set, and we averaged the results. We then repeated the scenario using a LAN path to the tape device. We removed the LAN-free configuration and reran the same set of backup tests to tape, this time over the LAN. Table 6-1 on page 163 includes the metrics that we gathered from the tests.


Figure 6-2 Small file effect on LAN-free backups

Table 6-1 LAN-free versus LAN 2 GB backup comparison results

Data path Number of files Average file size Aggregate transfer rate

LAN-free 1 2 GB 40.36 MB/s

LAN 1 2 GB 11.27 MB/s

LAN-free 10 200 MB 33.83 MB/s

LAN 10 200 MB 10.34 MB/s


LAN 20 100 MB 9.73 MB/s


LAN 40 50 MB 8.80 MB/s


LAN 50 40 MB 8.27 MB/s


LAN 100 20 MB 6.36 MB/s

LAN-free 1,000 2 MB 9.17 MB/s

LAN 1,000 2 MB 6.74 MB/s

LAN-free 10,000 200 KB 8.11 MB/s

LAN 10,000 200 KB 6.10 MB/s

LAN-free 100,000 20 KB 1.05 MB/s

LAN 100,000 20 KB 1.61 MB/s

LAN-free 1,000,000 2 KB 0.17 KB/s

LAN 1,000,000 2 KB 0.13 KB/s

LAN-free

0

5

10

15

20

25

30

35

40

45

2GB 1

200MB 10

100MB 20

50MB 40

40MB 50

20MB 100

2 MB 1,000

200KB 10,000

20KB 100,000

2KB 1,000,000

Average File Size Number of Files

Aggr

egat

e Tr

ansf

er R

ate

(MB/

s)

LAN


The results show that as the number of files increases and, at the same time, the average file size decreases, the LAN-free and LAN backup performance converges. The line graph and table illustrate that the best LAN-free backup performance is achieved when backing up larger and fewer objects. In this set of tests, the best LAN-free throughput (40 MB per second) was achieved when the average file size was 2 GB. As the average file size decreased to 200 MB, the throughput dropped to 33.83 MB per second. The LAN-free throughput drops more rapidly when the average file size is reduced to 20 MB in size and the number of files is reduced to 100 files. From this data, we can determine that in this particular test environment an average file size of about 100 MB can yield fairly decent LAN-free performance, before performance begins to decline. With that said, such backups results can be useful in helping you to decide whether a client machine is ideal for LAN-free data movements.

The average file size information might be gathered from all your client machines and then you can use that information to determine which client machines are ideal for LAN-free movement. Various tools are available that you can use to gather such information, for example, TotalStorage Productivity Center for Data (TPC for Data).You could also calculate the average file size for a client machine manually by determining the total amount of data (in GB) on that machine, then by dividing that total by the total number of files.

Often, client machines have a mix of both large and small files. Where these files can be identified (for example, by the directory in which they reside or the file extension), you can use Tivoli Storage Manager client options to send the larger objects over the SAN path while sending the smaller objects over the LAN path.

To use different paths for larger and smaller files, first configure storage pools that reside on both LAN and SAN-accessible devices. Then, configure management classes to use those storage pools. Use INCLUDE statements in the client options file to bind the smaller objects to a management class for a LAN-accessible storage pool and to bind larger objects to a management class for a LAN-free pool. For further information about using the INCLUDE client statement to bind objects to a management class, see the Backup-Archive Clients Installation and User’s Guide for your client platform.

6.4 Supported operating systems and requirementsThis section covers the LAN-free system components and their requirements. In general, we recommend using the latest versions of each component. Before you set up LAN-free data movement, ensure the following:

� SAN hardware components are in place

Ensure that all the required SAN hardware components are in place and functioning properly. All hardware components such as SAN switches and HBAs should have the most current firmware levels applied, unless otherwise noted by the manufacturer. For more details about where to acquire the latest device driver and firmware level for each hardware component, consult with the hardware’s accompanied documentation. If no documentation were provided, consult with the hardware’s manufacturer’s support center or Web page.

Important: This example is intended merely to show general trends of LAN-free versus LAN performance when considering file size. It is not a formal benchmark and is not intended to be used to extrapolate actual performance figures for any particular environment. For this reason, we have not given specifics of the particular SAN and network topologies, the storage devices, or servers which were a part of this test.


� Tivoli Storage Manager for SAN (Storage Agent) License is current

The Tivoli Storage Manager for SAN license and software is required. Review the Storage Agent, client, and server readme files for the necessary platform for possible updated information about HBA and device driver support.

The Tivoli Storage Manager software components typically involved in LAN-free data movement are the server, the backup-archive client, and the storage agent. The server and backup-archive client are supported on the common platforms. For specific details about which platform the server and clients support, see:

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The Storage Agent plays an essential role in a LAN-free setup. The Storage Agent is a miniature version of the Tivoli Storage Manager server and takes on the functions of a Library Client in order to control the writing and reading of tapes in a LAN-free setup. The Storage Agent is supported on the following operating systems at the time of writing:

� AIX 5.1, 5.2 and 5.3 (both 32 and 64 bit)

� HP-UX 11iv1, 11iv2 (both 32 and 64 bit)

� Solaris 8, 9 (64 bit)

� Windows 2000, Server 2003

� Linux IA32: Red Hat Enterprise Linux 3, update 2 or later, SLES 8 sp3 or later, SLES 9

� Linux on pSeries: SuSE Enterprise Server 8 sp3 or later, SLES 9, Red Hat Enterprise Linux 3 update 2 or later

� Linux Power5 iSeries™ and pSeries: Red Hat Enterprise Linux 3 update 2 or later, SLES 9

� Linux on zSeries®: SuSE Linux Enterprise Server 8 sp3 or later, SLES 9, Red hat Enterprise Linux 3 update 2 or later

� Linux 390 (31 bit) Read Hat 3 update 2 or later, SLES 8, sp3 or later, SLES 9

6.5 Configuration preparationsThere are some essential pieces of information and components of which you should have a good understanding before setting up a LAN-free configuration. This section discusses these pieces. It also gives more details on how the LAN-free backup works to provide a better understanding of the process.

To assist you in setting up LAN-free data movement , you should identify or be aware of the following:

� The client machine on which the LAN-free is to be set up

We have already discussed the importance of deciding when LAN-free backup is appropriate. Having decided to use LAN-free backup, you must then consider where to install the Storage Agent. The Storage Agent is installed most usually on the actual client machine, although it is also possible to have the Storage Agent running on a separate system. For details on having the Storage Agent run on a separate machine, see 7.4.3, “Configuring the client” on page 191 .

� The Tivoli Storage Manager server to be used

The Tivoli Storage Manager server in a LAN-free environment can play different roles. It can act as the Library Manager or as a Library Client or even both in more complex environments. (For a discussion of these terms, see Chapter 2, “Tape library sharing



planning” on page 11.) In many small and mid-size businesses, it is most typical to have a single Tivoli Storage Manager server. In that case, the server acts as the Library Manager. However, in more complex environments consisting of multiple Tivoli Storage Manager servers, the Library Manager and Library Client architecture must be determined.

� The type of library sharing method to be used

The SAN-attached storage devices that you have (or plan to have) in your environment most likely determines the type of library sharing method you will use. IBM tape devices or non-IBM storage devices that are supported by the Tivoli Storage Manager device driver can be used for sharing. These device types include SCSI, file (for disk), ACSLS, external, and 349x tape libraries. For more details on the different library sharing methods, see Chapter 3, “SCSI tape library sharing” on page 43, Chapter 4, “IBM 3494 tape library sharing” on page 93, and Chapter 5, “Library sharing with the ACSLS Manager” on page 127.

� The device names

The device names for the SAN-attached storage devices are required when defining the path on the server. SAN-attached devices might appear with different device names on each host which is attached to the same SAN. For instance a SAN-attached 3580 LTO drive might show up as device name /dev/rmt0 on one AIX system, while on another AIX machine it will show up as /dev/rmt1. Different operating systems also use different device naming conventions. It is important to know the naming convention when defining the device path. The correct device driver must be installed in order for the devices to show up and be available for further configuration. For information about finding device names, see 6.5.1, “Obtaining the device name(s)” on page 166.

� A proper management class destination

In order for a client node to use the Storage Agent to perform LAN-free data movements, the client node must be bound to a management class that uses the SAN-attached storage device. This management class can be set as the default to allow any client node that is created within the policy domain to use it automatically for all backup operations. Alternatively you can explicitly specify to use the management class using INCLUDE statements within the client options file or client option set that point to the LAN-free management class.

6.5.1 Obtaining the device name(s)You must obtain the device names for each SAN-attached device, because that information is required when defining the path(s) for that device on the Tivoli Storage Manager server. To obtain the device names for each device, you need to execute the following tasks on the system(s) that will be running the Storage Agent.

Installing the Storage Agent and device driverOn the Storage Agent machine, you must install the Storage Agent software and the appropriate device driver(s). In most cases, for IBM tape drives, you use an IBM tape device driver. For other non-IBM tape drives, use the Tivoli Storage Manager device driver (ADSMSCSI/ TSMSCSI). We recommend using the latest device drivers in any case.

For complete details on selecting and installing device drivers, refer to the Attaching Devices section of the IBM Tivoli Storage Manager Administrator V5.3 Administrator’s Guide for your Tivoli Storage Manager server platform.

You can download the latest version of the IBM tape device driver from :




The Tivoli Storage Manager device driver is shipped with the Storage Agent software in the Tivoli Storage Manager for Storage Area Networks package. You can download the latest version of the Tivoli Storage Manager Storage Agent and device driver from:

ftp://ftp.software.ibm.com/storage/tivoli-storage-management/

Install the Storage Agent software from the Tivoli Storage Manager for Storage Area Networks package or from the latest downloaded patch. Follow the instructions on the screen to complete the software install. Review the readme files for important information about installation, as well as known issues and limitations.

After the Storage Agent and device drivers are installed successfully, you can then determine the device names using the tsmdlst utility.

In our lab, we installed the Storage Agent on the Windows platform. To install the Storage Agent on the Windows platform, you need to start the Tivoli Storage Manager device driver.

� On Windows 2000 at a command prompt, enable the Tivoli Storage Manager device driver (TSMSCSI). Change to the C:\Program Files\Tivoli\TSM\console directory and run the following command:

tsmscsi /enable

You should received a message similar to Example 6-1, which indicates that the device support is enabled on the system.

Example 6-1 Starting the Tivoli Storage Manager device driver

C:\Program Files\Tivoli\Tsm\console>tsmscsi /enable

TSM Windows 2000 / Optical support is enabled on SENEGAL.

C:\Program Files\Tivoli\Tsm\console>

Note: In Tivoli Storage Manager V5.3 the new SAN Discovery feature allows Tivoli Storage Manager to assist with recovering from device name changes. If you plan on taking advantage of this feature, ensure that you use the latest device driver for your HBAs. More information is available in Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.

Note: On Windows systems, both the Storage Agent and Tivoli Storage Manager device driver installs require a system reboot. To avoid rebooting twice, when prompted to reboot after the Storage Agent install, select no and then install the Tivoli Storage Manager device driver and reboot afterwards.

Note: On Windows, when using the Tivoli Storage Manager device driver or the IBM tape device driver to control all devices, ensure that the Removable Storage Manager (RSM) service is disabled, to avoid conflicts with the intended device drivers.

Note: If you are using IBM tape drives or libraries, the Tivoli Storage Manager device driver is not required and does not need to be started. Skip this step and proceed to “Query the device name(s)” on page 168.


ftp://ftp.software.ibm.com/storage/tivoli-storage-management/

Reboot the Storage Agent system. The device driver is now set to start at system start up. It controls the devices if the devices are available and if they are not controlled by any other device drivers.

� On Windows Server 2003, devices are controlled by the Windows device driver by default, even after installing the Tivoli Storage Manager device driver (TSMSCSI). You must update each device manually so that each is controlled by the TSMSCSI device driver. To update each device manually, start the Windows Device Manager and then:

a. Right click the device and select Properties. Select the Driver tab and Driver File Details to see the driver that is currently controlling your device.

b. You must configure the device to be used by tsmscsi.sys by right clicking the device and selecting Update Driver or by selecting Action and then Update Driver. The Hardware Update Wizard appears.

c. Select Install from a list or specific location (Advanced) and click Next.

d. Click Next.

e. Select Don't search. I will choose to install and click Next.

f. From the Hardware Installation panel, click Continue Anyway.

g. Verify that the device has been configured correctly for tsmscsi:

i. Right click the device and select Properties.

ii. Select the driver tab and driver details.

For completed details about controlling devices in a Windows 20003 system, refer to IBM Tivoli Storage Manager for Windows Administrator’s Guide, GC35-4010.

Query the device name(s)At a command prompt, change to the C:\Program Files\Tivoli\TSM\console directory and enter the command:

tsmdlst

The output should show the all the devices that are attached to the system, including the SAN-attached devices, as shown in Example 6-2. The example shows that there are two disk devices, one tape library, and two tape drives visible from this client’s Storage Agent.

Example 6-2 Example of tsmdlst output.

Computer Name: SENEGALTSM Device Driver: Not Running (TSM information may not be accurate)

TSM Name ID LUN Bus Port SSN WWN TSM Type Device Identifier-----------------------------------------------------------------------------------------------------------n/a 0 12 0 2 1T44668011 200400A0B8174432 DISK IBM 1742-900 0520n/a 0 13 0 2 1T44668011 200400A0B8174432 DISK IBM 1742-900 0520mt2.0.0.2 2 0 0 2 1110176223 500308C140467003 LTO IBM ULT3580-TD2 4772lb2.1.0.2 2 1 0 2 0000013108231000 500308C140467003 LIBRARY IBM ULT3582-TL 237Bmt3.0.0.2 3 0 0 2 1110177214 500308C140467006 LTO IBM ULT3580-TD2 477

Note: The message indicates that Optical support is enabled. However, Tivoli Storage Manager does not currently support the use of optical devices in a LAN-free environment.


Make a note of the special device names for the SAN-attached devices that you plan on using in the LAN-free configuration. For example, the tape related devices are lb2.1.0.2 (library medium changer), mt2.0.0.2 (first tape drive), and mt3.0.0.2 (second tape drive). You will need these device names when defining the path to these devices.

In Example 6-2 on page 168, note the following message:

TSM Device Driver: Not Running (TSM information may not be accurate)

This message is expected when using the IBM device driver. In most cases, if the devices show up in the output, they are accurate. However, if you are unable to define the Storage Agent paths using the device names as they appear (that is, you receive errno 2 - file not found), then you can install the Tivoli Storage Manager device driver for the purpose of temporarily getting the device information. For further details on installing the Tivoli Storage Manager device driver to obtain the device name, see IBM Tivoli Storage Manager Administrator’s Guide for your operating system platform.

6.6 Compatibility concernsYou should consider the following compatibility concerns when preparing for LAN-free data movement:

� Storage Agent V5.2 does not operate with a previous version of the Tivoli Storage Manager Server.

� Tivoli Storage Manager Server V5.2 does not operate with a previous version of the Storage Agent.

� Tivoli Storage Manager Server V5.3 supports only Storage Agent V5.2.3, V5.2.4, and V5.3.

� At the time of writing, Storage Agents V5.2 or later cannot access shared file volumes using SANergy on V5.3 or later of the Tivoli Storage Manager server using LAN-free. Any such LAN-free requests are redirected to the server over the LAN.



Chapter 7. LAN-free backup to tape

This chapter describes the process that is involved in configuring and verifying configuration of LAN-free tape backups. It discusses the following topics:

� Overview of the lab environment� Setting up a policy domain for LAN-free clients� Registering a new client node� Enabling LAN-free data movement� Configuring the Storage Agent� Verifying the LAN-free path� Communicating with and monitoring the Storage Agent� Configuring other Tivoli products for LAN-free

7


7.1 Overview of the lab environmentIn a LAN-free to tape environment, a Storage Agent is used to transfer data over the SAN on behalf of a client. The Storage Agent might reside on the same machine as the client node or on a separate machine. This section includes steps for both types of environments.

Figure 7-1 on page 173 shows the Storage Agent and the client node residing on the same machine, as well as a single dedicated Storage Agent that is used by multiple clients to transfer data over the SAN.

The examples used in this chapter are based on the LAN-free configuration that we performed in our lab, which is shown in Figure 7-1 on page 173. Our lab environment consisted of the following hosts:

� AZOV: AIX V5.2, Tivoli Storage Manager server V5.3.1.0.

� SENEGAL: Windows 2000, running Tivoli Storage Manager Backup-Archive Client V5.3.0 and Storage Agent V5.3.1.0. The client node name is SENEGAL and the Storage Agent name is SENEGAL_STA.

� KANAGA: AIX V5.3, running Tivoli Storage Manager Backup-Archive Client V5.3.0. The client node name is KANAGA.

The SENEGAL host is attached to the SAN, which allows the Tivoli Storage Manager client SENEGAL to perform LAN-free data transfer to and from the SAN-attached tape drives. The second client KANAGA has a LAN connection but no SAN connection. Therefore, it cannot access the SAN-attached tape drives directly. Using the LANFREETCPSERVERADDRESS option, we configured KANAGA to use the Storage Agent, SENEGAL_STA to transfer data over the SAN as well as to and from the SAN-attached tape drives.

Figure 7-1 on page 173 also summarizes most of the important configuration options are described in this chapter.


Figure 7-1 LAN-free environment in our lab

Setting up LAN-free data movement requires steps on the Tivoli Storage Manager server and the Storage Agent and client systems.

IMPORTANT: Before you can proceed in this chapter, you must have defined your tape devices on the Tivoli Storage Manager server for use by the server. This definition includes configuring the library, drives, device class, and a storage pool for all tape devices. This chapter covers configuring those devices for use by the Storage Agent. If your storage devices have not been defined for use by the server, refer to the following:

� Chapter 2, “Tape library sharing planning” on page 11� Chapter 3, “SCSI tape library sharing” on page 43� Chapter 4, “IBM 3494 tape library sharing” on page 93� Chapter 5, “Library sharing with the ACSLS Manager” on page 127� IBM Tivoli Storage Manager Administration Guide for your platform

SAN

LAN

STORAGE AGENTSENEGAL_STA

SERVERAZOV

3582 Tape Library LTODrive 1

LTO Drive 2

Server-to-Server Communication

CLIENTKANAGA

CLIENTSENEGAL

ENABLElanfree yes

LANFREETCPServer senegal

LANFRECommmethod tcpip

LANFREETCPport 1502

TCPServeraddress azov

TCPport 1500

ENABLELanfree yes

LANFREECommmethod sharedmem

LANFREEShmport 1TCPServeraddress azovTCPport 1500

dsm.opt

dsm.sys

COMMmethod TCPIPCOMMmethod SHAREDMEM

TCPport 1502

SHMPort 1

SANDISCOVERY ON

dsmsta.opt

LEGENDClient data transferLibrary control/ Client meta data

File Library onShared Disk

define server senegal_sta

define library path for azov

define drive paths for azov

define drive paths for senegal_sta

Chapter 7. LAN-free backup to tape 173

7.2 Setting up a policy domain for LAN-free clientsYou create a new policy domain with a default management class that points to the SAN-attached storage device to be used for this LAN-free configuration. You set this management class as the default to allow clients that are registered to it to use it automatically.

This section describes the setup on the Tivoli Storage Manager server from the Administration Center and using the command line interface.

7.2.1 Setting up a policy domain from the Administration CenterFrom the Administration Center:

1. From the Work Items list to the left, select Policy Domains and Client Nodes. The Policy Domains screen appears, as shown in Figure 7-2.

Figure 7-2 The Policy Domains screen

2. Select the server name under which you want to create the new policy domain. We are using server AZOV. The server1_Policy Domains screen appears, as shown in Figure 7-3, where server1 is the name of your server. Click Select Action, select Create a Policy Domain, and click Go.

Figure 7-3 The current policy domains show up

3. The General input screen appears, as shown in Figure 7-4 on page 175. Enter a meaningful name for this LAN-free policy domain and the appropriate retention information. Click Next.


Figure 7-4 The Create Policy Domain General screen

4. The Storage Pools input screen appears, as shown in Figure 7-5. Select an appropriate storage pool that is associated with your SAN-attached device(s). If you have not configured storage pools on the Tivoli Storage Manager server for tape device, refer to the library sharing chapters (Chapter 3, “SCSI tape library sharing” on page 43, Chapter 4, “IBM 3494 tape library sharing” on page 93, and Chapter 5, “Library sharing with the ACSLS Manager” on page 127) for details on how to do it. Click Next.

Figure 7-5 Create Policy Domain Storage Pools screen


5. The Assign Client Nodes Now? screen appears, as shown in Figure 7-6. Click No, if you have not yet registered the client node for LAN-free backup, Otherwise, click Yes. Click Next. If you select yes, skip to step 8 on page 177, otherwise continue with the next step.

Figure 7-6 Create Policy Domain Assign Client Node Now? screen

6. The Summary screen appears, as shown in Figure 7-7. Verify the information and click Finish.

Figure 7-7 Create Policy Domain, Summary screen


7. Your new policy domain should now be defined and appears in the list of domains, as shown in Figure 7-8.

Figure 7-8 List of policy domains

8. If you choose to assign a client to the policy domain in Figure 7-6 on page 176, the Assign Client Nodes screen appears. Select the option to view all client nodes and click Next.

Figure 7-9 Create Policy Domain Assign Client Node View Clients screen


9. All the client nodes are displayed, as shown in Figure 7-10. Check the client node(s) to be assigned and click Next.

Figure 7-10 Create Policy Domain, Assign Client Nodes, Select a client node to assign

10.The Summary screen appears, as shown in Figure 7-11. Verify that the information is correct and click Finish.

Figure 7-11 Create Policy Domain Summary after selecting a client to assign


7.2.2 Setting up a policy domain using the command line interfaceThis section contains the commands that we used in our environment to set up the policy domain. After each command, you should check that the command completed successfully. If a command fails, check the activity log to determine the cause.

To set up a policy domain using the command line interface:

DEFINE DOMAIN lan-free-policy DESCRIPTION=”Policy Domain for LAN-free data transfer to tape” BACKRETENTION=30 ARCHRETENTION=365DEFINE POLICYSET lan-free-policy standard desc=”Standard policy set”DEFINE MGMTCLASS lan-free-policy standard standard desc=”Standard management class”DEFINE COPYGROUP lan-free-policy standard standard destination=3582_TAPEDEFINE COPYGROUP lan-free-policy standard standard type=archive destination=3582_TAPEASSIGN DEFMGMTCLASS lan-free-policy standard standardVALIDATE POLICYSET lan-free-policy standardACTIVATE POLICYSET lan-free-policy standard

Example 7-1 shows the settings for our activated LAN-free policy setup.

Example 7-1 Policy Domain created for LAN-free clients

Policy Domain Name : LAN-FREE-POLICY Policy Set Name : ACTIVE Mgmt Class Name : STANDARD Copy Group Name : STANDARD Copy Group Type : Backup Versions Data Exists : 2 Versions Data Deleted : 1 Retain Extra Versions : 30 Retain Only Version : 60 Copy Mode : Modified Copy Serialization : Shared Static Copy Frequency : 0 Copy Destination : 3582_TAPETable of Contents (TOC) Destination : Last Update by (administrator) : ADMIN Last Update Date/Time : 3/29/05 4:57:33 PM PST Managing profile :

7.3 Registering a new client nodeIf the client node that will use LAN-free transport is not registered to the Tivoli Storage Manager server, you need to register it. If the node is already registered, then ensure that it is updated to use the policy domain that is intended for LAN-free use, and you can skip this section. This section covers the steps from the Administration Center and using the command line interface.

7.3.1 Registering the node from the Administration CenterFrom the Administration Center:

1. Select Policy Domains and Client Nodes from the Work Items list on the left. The Policy Domains screen appears, listing all the Tivoli Storage Manager servers and their defined policy domains, as shown in Figure 7-12 on page 180.


Figure 7-12 Tivoli Storage Manager servers and their policy domains

2. Click the server name under which you want to create the new policy domain. We are using AZOV. The server1_Policy Domains screen appears, where server1 is the name of your server, as shown in Figure 7-13.

Figure 7-13 Policy domains for a Tivoli Storage Manager server

3. Select the policy domain to be used for LAN-free movement. This is the domain defined in 7.2, “Setting up a policy domain for LAN-free clients” on page 174. The Policy_name Properties screen appears, where Policy_name is the name of the policy domain that is intended for LAN-free use. In our case, this name would be LAN-FREE-POLICY.

4. Click Client Nodes. The Select Action menu appears.

5. Click Select Action, select Create a Client Node, and click Go. The Create Client Node General screen appears.

6. Enter the new client node name. We recommend using the client host name for the client node name. The remaining options on this screen are not required at this time and can be updated later. Click Next. The Security screen appears.

7. Enter a password and verify it. The remaining options on this screen are optional. Click Next. The Summary screen appears and states that the node has been defined. In our case, we have registered the node SENEGAL in the LAN-FREE-POLICY, as shown in Figure 7-14 on page 181.


Figure 7-14 Newly defined node.

7.3.2 Registering the node using the command line interfaceTo register the client node using the command line interface, use these commands:

REGISTER NODE senegal mypassword CONTACT=”Joe Smith” DOMAIN=LAN-FREE-POLICY FORCEPWRESET=NO

In this command, mypassword represents an actual password that is used.

If the node is already registered, then ensure that it is updated to use the policy domain that is intended for LAN-free use. For example:

UPDATE NODE senegalDOMAIN=LAN-FREE-POLICY

Check the results by querying the new node:

Q NODE SENEGAL

Your output should be similar to Figure 7-2, which shows that the LAN-FREE-POLICY is selected.

Example 7-2 Query node output

Node Name : SENEGAL Platform : WinNT Policy Domain Name : LAN-FREE-POLICYDays Since Last Access : 3Days Since Password Set : 16 Locked? : No


7.4 Enabling LAN-free data movementThis section describes the necessary steps on the server to enable LAN-free data movement. It includes instructions to enable LAN-free data movement from the Administration Center as well as from the command line interface

7.4.1 Setting LAN-free from the Administration CenterUsing the Administration Center, you can set up the server communication options and enable LAN-free data movement.

Setting up server communication options from the Administration Center

To prepare the Tivoli Storage Manager server to communicate with Storage Agents and other servers, first set the necessary Tivoli Storage Manager server settings on the destination Tivoli Storage Manager server. These settings include a server name and password that will be used by Storage Agents and other servers.


1. Select Enterprise Management on the Work Items list on the left. Select the Tivoli Storage Manager server that will act as the destination for the Storage Agent or other servers. From the Select Action menu, choose Server-to-Server Communication Settings, as shown in Figure 7-15.

Figure 7-15 Start the Server-to-Server communication settings

2. The Server-to-Server Settings input screen appears, as shown in Figure 7-16. Enter a name for the Tivoli Storage Manager server (if not already set), password, and TCP/IP information. Click OK to finish.

Figure 7-16 Server-to-Server Settings input screen


Enabling LAN-free data movement from the Administration CenterWhen you enable LAN-free data movement, you:

� Restrict or allow LAN-free data transfer for a client node.� Select or create a Storage Agent for LAN-free use.� Select or create a storage pool for LAN-free use.� Defines paths to SAN-attached devices for LAN-free use.

To enable LAN-free data movement:

1. From the Client Nodes screen on the Tivoli Storage Manager server, select the client that you want to configure for LAN-free (SENEGAL, in our case). Select Enable LAN-free Data Movement from the task menu, as shown in Figure 7-17.

Figure 7-17 Select node and Enable LAN-free Data Movement

2. The Welcome screen, as shown in Figure 7-18, gives an overview of the process. Click Next.

Figure 7-18 LAN-Free client configuration


3. The Verify Data Transfer Settings screen appears, as shown in Figure 7-19. Select whether you want the client to read and write over the SAN or over the SAN and LAN. For this example, we select SAN and LAN for both read and write. Click Next.

Figure 7-19 Verify Data Transfer Settings screen

4. The Create or Select a Storage Agent screen appears, as shown in Figure 7-20. Select Create a Storage Agent. If you had previously defined a Storage Agent for this node to use, then you should select Use an existing Storage Agent and select the appropriate Storage Agent from the Select a Storage Agent list. Click Next.

Figure 7-20 Create or Select Storage Agent

5. The Create a Storage Agent screen appears, as shown in Figure 7-21 on page 185. Enter a name for your Storage Agent (we call it SENEGAL_STA), specify a password, enter the TCP/IP address of the Storage Agent system (which is 9.1.39.166), and the port which will be used for Server communication. Note the default on this screen is to use port 1500, which is the same as for regular Backup-Archive Client operations. We will use a different port number, 1502. These parameters will be used later when configuring the Storage Agent on the actual client machine, as described in 7.5, “Configuring the Storage Agent” on page 193. Click Next.


Figure 7-21 Create Storage Agent screen

6. The Select a Storage Pool screen appears, as shown in Figure 7-22. Select the desired storage pool and operation. For this example, select the storage pool that is defined on the 3582 library, which matches the storage pool that we assigned in the policy domain. Click Next.

Figure 7-22 Select Storage Pool screen

7. The Create Drive Paths for your_library screen appears, as shown in Figure 7-23 on page 186. This displays the tape drives in the library. Select the first drive. Select Modify Drive Path and click Go.


Figure 7-23 Create Drive Paths screen

8. The Modify the Path for your1stdrive screen appears, as shown in Figure 7-24 on page 187. Enter the device name for the tape drive as it appears on the Storage Agent machine. Click OK.

You should know the device names from the Storage Agent’s perspective from the information that was gathered in 6.5.1, “Obtaining the device name(s)” on page 166. In this instance, for the Windows Storage Agent, we listed the devices visible in Example 6-2 on page 168. This output shows the serial numbers. Therefore, you can match up the correct serial number to device name. Note that the autodetect option is not available.

To set up paths for additional tape drives, click Next Drive and enter appropriate device names for the remaining drives. When the paths for all tape drives are modified, click Next.

Note: We strongly recommend that you enable the Tivoli Storage Manager V5.3 SAN Discovery option within the server and Storage Agent options files to allow Tivoli Storage Manager to assist with device recovery. When SAN Discovery is performed on a Windows tape drive, the Windows device name (that is, \.\tape0) is used. For further details about SAN Discovery, see to Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.


Figure 7-24 Modify Drive Path screen

9. The Create Drive Path screen appears, as shown in Figure 7-25. This is the same display as in Figure 7-23 on page 186, but now the device names are shown beside each drive. Click Next.

Figure 7-25 Create Drive Paths screen showing assigned device names

10.The Configure Another Storage Pool? screen appears, as shown in Figure 7-26 on page 188. Select No and click Next.


Figure 7-26 Configure Another Storage Pool? screen

11.The Summary screen appears, as shown in Figure 7-27. Click Next to complete the enable LAN-free data movement wizard.

Figure 7-27 LAN-free setup complete


7.4.2 Setting up LAN-free data movement using the command line interfaceThis section describes how to set up LAN-free data movement using the Tivoli Storage Manager command line interface. (Refer to the sections of the same name in 7.4.1, “Setting LAN-free from the Administration Center” on page 182 for information to use when issuing the commands.)

Setting up server communication options using the command line interface

To enable the Tivoli Storage Manager server to communicate with Storage Agents and other servers, you must set its name, password, and TCP/IP Information. For example,

SET SERVERNAME azov_1SET SERVERPASSWORD myserverpwSET SERVERHLADDRESS 9.1.39.168SET SERVERLLADDRESS 1500

After completing these commands, issue the QUERY STATUS command. Verify that the server information is correct and that the Server Password Set value is Yes as shown in Example 7-3.

Example 7-3 QUERY STATUS output showing server communication definitions

tsm: AZOV_1>query status Storage Management Server for AIX-RS/6000 - Version 5, Release 3, Level 0.0

Server Name: AZOV_1 Server host name or IP address: 9.1.39.89 Server TCP/IP port number: 1500 Server URL: Crossdefine: On Server Password Set: Yes

Enabling LAN-free data movement using the command line interfaceUsing the command line interface, you can:

1. Control whether both backups and restores use the LAN-free path by using the DATAWRITEPATH and DATAREADPATH options. In this example, we use the UPDATE NODE command to have the client node SENEGAL execute both backups and restores over the SAN.

UPDATE NODE SENEGAL DATAWRITEPATH=ANY DATAREADPATH=ANY

2. Use the DEFINE SERVER command to define the Storage Agent SENEGAL_STA:

DEFINE SERVER senegal_sta SERVERPASSWORD=mystapassword HLADDRESS=9.139.166 LLADDRESS=1502

Use the QUERY SERVER command to see the newly created Storage Agent server, as shown in Example 7-4 on page 190.


Example 7-4 Query server senegal_sta

AZOV_1> q server senegal_sta Server Name : SENEGAL_STA Comm. Method : TCPIP High-level Address : 9.1.39.166 Low-level Address : 1502 Days Since Last Access : <1 Server Password Set : YesVirtual Volume Password Set : No Allow Replacement : No

3. Use the DEFINE PATH command to create a path for the Storage Agent SENEGAL_STA to access the tape devices mt2.0.0.2 and mt3.0.0.2. These are the special device names for the tape drive as they appear on the Storage Agent system.

DEFINE PATH senegal_sta DRIVE1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=3582 DEVICE=mt2.0.0.2DEFINE PATH senegal_sta DRIVE2 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=3582 DEVICE=mt3.0.0.2

4. Use the QUERY PATH command to look at the newly created path, as shown in Example 7-5.

Example 7-5 Query path senegal_sta f=d

AZOV_1> q path senegal_sta f=d Source Name : SENEGAL_STA Source Type : SERVER Destination Name : DRIVE1 Destination Type : DRIVE Library : 3582 Node Name : Device : mt2.0.0.2 External Manager : LUN : Initiator : 0 Directory : On-Line : YesLast Update by (administrator) : SERVER_CONSOLE Last Update Date/Time : 4/5/05 11:04:42 AM PDT

Source Name : SENEGAL_STA Source Type : SERVER Destination Name : DRIVE2 Destination Type : DRIVE Library : 3582 Node Name : Device : mt3.0.0.2 External Manager : LUN : Initiator : 0 Directory : On-Line : YesLast Update by (administrator) : ADMIN Last Update Date/Time : 3/30/05 4:32:59 PM PST


7.4.3 Configuring the clientAfter configuring the Tivoli Storage Manager server, you next need to configure the client. The instructions in this section assume that you have installed the Tivoli Storage Manager Backup-Archive Client and that you have configured and tested it for normal backup to the Tivoli Storage Manager server. For more detailed information about setting up the Backup-Archive Client, see the Backup-Archive Clients Installation and User’s Guide for your client platform.

You should have set the following options to enable a backup to the Tivoli Storage Manager server, as shown in Example 7-6. You should perform a test backup at this stage to verify the communication between the client and server. This backup goes over the LAN to the storage device.

Example 7-6 Normal Backup-Archive Client options

COMMmethod TCP/IPTCPPort 1500TCPServeraddress azov.almaden.ibm.com

LAN-free options (used between the client and the Storage Agent)To enable the SAN path to be used, you need to set these additional options in the client options file:

� ENABLELANFREE

The ENABLELANFREE option is always set to yes.

The setting of the other options depends on whether you are using a Storage Agent and Tivoli Storage Manager client on the same system or using a separate (external) Storage Agent for the Tivoli Storage Manager client.

� LANFREECOMMMETHOD

Set the option LANFREECOMMMETHOD to identify what communication method to use between the Backup-Archive Client and the Storage Agent.

� LANFREETCPPORT or LANFREESHMPORT

Identify a port to use using either the LANFREETCPPORT or LANFREESHMPORT option.

� LANFREETCPSERVERADDRESS

The option LANFREETCPSERVERADDRESS is only used with an external Storage Agent.

Storage Agent and client on same systemIf the Storage Agent is on the same system as the Backup-Archive Client (as in the case of SENEGAL in Figure 7-1 on page 173), you should specify LANFREECOMMMETHOD of sharedmem. Using shared memory gives the best performance when the communication is local, as in this case. You then specify the port to use with the LANFREESHMPORT option.

Note: We strongly recommend that you enable the Tivoli Storage Manager V5.3 SAN Discovery option within the server and Storage Agent options files to allow Tivoli Storage Manager to assist with device recovery. When SAN Discovery is performed on a Windows tape drive, the Windows device name (that is, \\.\tape0) is used. For further details on SAN Discovery, see to Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253.


This is a different port than the one for use between the Storage Agent and the Tivoli Storage Manager server. Therefore, SENEGAL’s option file looks similar to that shown in Example 7-7. Setting the LANFREESHMPORT to one (1) matches the default SHMPORT setting in the Storage Agent’s dsmsta.opt file. Therefore, you do not need to change it as discussed in 7.5, “Configuring the Storage Agent” on page 193.

Example 7-7 Client options file with Storage Agent on same system as client node

ENABLELanfree YesLANFREECommmethod sharedmemLANFREESHMPORT 1

Using an external Storage AgentAlternatively, a Backup-Archive Client can use an external Storage Agent which transfers data on behalf of one or more client nodes. In this case, the Backup-Archive Client does not have the Storage Agent installed, but instead points to another or external Storage Agent. The external Storage Agent might itself be a Backup-Archive Client as well, or it might be installed on a dedicated machine whose purpose is to transfer data over the SAN on behalf of one or more clients. This setup allows clients without direct access to SAN-attached devices to perform LAN-free backups through the dedicated Storage Agent. A second benefit is that some of the overhead of transferring the data to the SAN-attached storage devices is removed from the client machines and placed on the machine that hosts the Storage Agent.

Figure 7-1 on page 173 also summarizes the configuration when using a separate Storage Agent from the Backup-Archive Client. )Figure 7-28 shows just this configuration. The machine SENEGAL has the Tivoli Storage Manager client and Storage Agent software installed and configured on it. The machine KANAGA has just the Tivoli Storage Manager client software installed and configured. We set up the configuration so that KANAGA uses the Storage Agent on SENEGAL to transfer its data via the SAN to the SAN-attached storage devices.

Figure 7-28 LAN-free backup using a dedicated Storage Agent.


Tivoli Storage ManagerClient node:SENEGAL


To set up a client to use an external Storage Agent to transfer data over the SAN, set the LANFREETCPSERVERADDRESS in the client option file.

These are the values that we used on KANAGA:

� It needs the normal client options including TCPSERVERADDRESS. This is 9.1.39.89, corresponding to AZOV, the actual Tivoli Storage Manager server.

� We set ENABLELANFREE to yes as before.

� The LANFREETCPSERVERADDRESS, 9.1.39.166 is SENEGAL, which is hosting the Storage Agent for KANAGA.

� Because the Storage Agent is external, we need to set the LANFREECOMMMETHOD to TCP/IP. When TCP/IP is used, you specify LANFREETCPPORT. This setting it 1502, which matches the port that was defined for the Storage Agent. It also matches the TCPPORTsetting for the Storage Agent’s options file, dsmsta.opt, which we will set later.

Example 7-8 shows KANAGA’s option file.

Example 7-8 Client options file when using an external Storage Agent

COMMmethod TCP/IPTCPPort 1500TCPServeraddress 9.1.39.89ENABLELanfree YesLANFREECommmethod TCPIPLANFREETCPSERVERADDRESS 9.1.39.166 LANFREETCPPORT 1502

7.5 Configuring the Storage AgentIf the Storage Agent software has not been installed, you need to install it before you proceed with the configuration steps discussed in this section. If your Storage Agent is on Windows, you have the option of using the Administration Center to configure it. On other platforms, however, you have to use a command line interface. This section discusses both ways to configure the Storage Agent. For the example in this section, we are configuring the Storage Agent on the host SENEGAL.

Note: Information on how to install the Storage Agent and device drivers is described in Chapter 6, “Planning for LAN-free” on page 159. The installation was done this way to obtain the SAN-attached device names using the tsmdlst utility, which is a part of the Storage Agent software. The device names were required to define the device paths on the Tivoli Storage Manager server.


7.5.1 Configuring the Storage Agent from the Management ConsoleTo configure the Storage Agent from the Management Console:

1. On the machine where the Storage Agent is installed, start the Tivoli Storage Manager management console by selecting Start → Programs → Tivoli Storage Manager → Management Console. The management console appears, as shown in Figure 7-29.

2. Expand Tivoli Storage Manager to show the client node name. Expand this entry and then Tivoli Storage Manager StorageAgent1. The Tivoli Storage Manager Device Driver expand button also appears if you have installed it. The Reports and Wizards options appear under Tivoli Storage Manager StorageAgent1.

Figure 7-29 Management console showing Tivoli Storage Manager StorageAgent1 expansion

3. Start the Tivoli Storage Manager StorageAgent1 Wizard by double clicking Storage Agent Initialization, which appears on the right side of the window. Ensure that Wizards is highlighted in the left-hand panel. You can also start the wizard by right-clicking Storage Agent Initialization and selecting Action → Start, as shown in Figure 7-30.

Figure 7-30 Start Storage Agent Initialization wizard


4. The Welcome to the Storage Agent Initialization Wizard screen appears, as shown in Figure 7-31. Click Next to continue.

Figure 7-31 The Welcome to the Storage Agent Initialization Wizard screen

5. The Tivoli Storage Manager Server Account Information input screen appears, as shown in Figure 7-32.

Enter the Storage Agent name, password, and TCP/IP information. This information must match the information that was used when defining the Storage Agent as a server on the Tivoli Storage Manager server. Click Next.

Figure 7-32 The Tivoli Storage Manager Server Account Information screen filled in


6. The Tivoli Storage Manager Server Communication Information input screen appears, as shown in Figure 7-33. Enter the Tivoli Storage Manager server name, password, and TCP/IP information. This information must match the entries for the Tivoli Storage Manager server that were defined in “Setting up server communication options from the Administration Center” on page 182. Click Next.

Figure 7-33 Tivoli Storage Manager Server Communication Information screen completed

7. The Storage Agent Account Information input screen appears, as shown in Figure 7-34. Enter the information about a suitable Windows account that will be used by the Storage Agent. Make sure to select Automatically when Windows boots. Click Next.

Figure 7-34 Storage Agent Account Information


8. The wizard is now complete. On the final screen, Figure 7-35, click Finish.

Figure 7-35 Completing the Storage Agent Initialization Wizard

9. A message appears, as shown in Figure 7-36. This message indicates that the Storage Agent configuration was successful. Click OK.

Figure 7-36 The Storage Agent has been initialized

10.Verify that the Storage Agent service is running in the Windows Services applet, as shown in Figure 7-37.

Figure 7-37 Storage Agent service


11.At this stage, you should stop the Storage Agent and set the TCP/IP port which will be used for Storage Agent communication. This was defined as LANFREETCPPORT 1502 when configuring the client in “LAN-free options (used between the client and the Storage Agent)” on page 191. To set this on the Storage Agent, edit the dsmsta.opt file in the C:\Program Files\Tivoli\Tsm\storageagent directory and set the TCPPORT option to 1502 (the default is 1500).

TCPPORT 1502

12.Tivoli Storage Manager V5.3 has the SAN Discovery feature, discussed in Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253. This feature for the Tivoli Storage Manager server and Storage Agent allows Tivoli Storage Manager to assist in the recovery when the SAN device configuration changes.

To enable SAN Discovery on the Storage Agent, edit the configuration file, dsmsta.opt, in the C:\Program Files\Tivoli\TSM\Storageagent\ on Windows directory. Set the option:

SANDISCOVERY ON

13.Restart the Storage Agent to pick up the changed options using the Services applet.

14.For troubleshooting, you can run the Storage Agent in the foreground from the operating system command prompt. To do this, make sure the Storage Agent service is not running, and enter dsmsta from the Storage Agent directory, as shown in Example 7-9.

Example 7-9 The output from running the Storage Agent in foreground

C:\Program Files\Tivoli\Tsm\storageagent>dsmstaANR0900I Processing options file C:\PROGRA1\Tivoli\Tsm\STORAG1\dsmsta.opt.ANR7800I DSMSERV generated at 04:26:40 on Mar 29 2005.

Tivoli Storage Manager for WindowsVersion 5, Release 3, Level 1.0

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990, 2004.All rights reserved.U.S. Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corporation.

ANR4726I The ICC support module has been loaded.ANR8273I Shared memory driver ready for connection with clients on port 1.ANR8200I TCP/IP driver ready for connection with clients on port 1502.ANR0408I Session 1 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for storageagent.ANR0408I Session 2 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for librarysharing.ANR8920I Initialization and recovery has ended for shared library 3582.ANR0409I Session 2 ended for server AZOV_1 (AIX-RS/6000).ANR0408I Session 3 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for eventlogging.ANR0408I Session 4 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for storageagent.ANR0993I Server initialization complete.ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use.TSM:SENEGAL_STA>


Note that the Storage Agent ports being used is listening for TCP/IP sessions from external Backup-Archive Clients on port 1502 and for shared memory sessions from the local client on port 1.

7.5.2 Configuring the Storage Agent using the command line interfaceIf your Storage Agent is running on UNIX or Linux, you can only use the command line interface to configure the Storage Agent. You can also use the command line interface on Windows, as shown in the example in this section.

First, install the Storage Agent package and check that the required SAN devices are visible. The proceed with the configuration by following these steps:

1. Change the directory to the Storage Agent folder:

– C:\Program Files\Tivoli\TSM\Storageagent\ on Windows– usr/tivoli/tsm/StorageAgent/bin on AIX– /opt/tivoli/tsm/StorageAgent/bin on other UNIX

2. Edit the Storage Agent options file (dsmsta.opt) and set the following options:

DEVCONFIG devconfig.outSANDISCOVERY ONTCPPORT 1502

In these commands, devconfig.out points to an output file that is used by the Storage Agent to store device configuration information.

The SANDISCOVERY ON option allows Tivoli Storage Manager to assist in the recovery of SAN-attached devices. Save and close the dsmsta.opt file.

You have set the TCPPORT to 1502 to match our previous definitions.

3. Start a command prompt in the Storage Agent directory. Issue the following command to set up a communication between the Storage Agent and the server (from SENEGAL to AZOV in this case). The parameter settings must match the definitions on the Tivoli Storage Manager server that were created in “Setting up server communication options using the command line interface” on page 189.

dsmsta setstorageserver myname=senegal_sta mypassword=xxxx myhladdress=9.1.39.89 servername=azov_1 serverpassword=xxxx hladdress=9.1.39.89 lladdress=1500

This command updates the device configuration output file (devconfig.out) so that it looks similar to Example 7-10.

Example 7-10 Storage Agent device configuration file

Set STANAME senegal_staSET STAPASSWORD xxxxxxxSET STAHLADDRESS 9.1.39.166DEFINE SERVER azov_1 server password=xxxxxx HLADDRESS=9.1.39.89 LLADDRESS=1500

The Storage Agent option file (dsmsta.opt) is updated with the following:

SERVERNAME AZOV_1

Note: The SANDISCOVERY option is supported for Tivoli Storage Manager V5.3 and later.


7.6 Verifying the LAN-free pathNow that you have configured the server, client, and Storage Agent systems, you can check the setup. In Tivoli Storage Manager V5.3, verification is simplified by using the new VALIDATE LANFREE server command. The output from this command shows whether a client node, as associated with a specific Storage Agent, is capable of LAN-fee data movement. The command looks at the policy information, storage pool, and path definitions that are associated with the specified client node and Storage Agent to determine if the destination is LAN-free capable. This information can be useful when troubleshooting a suspected LAN-free configuration issue.

The VALIDATE LANFREE command replaces the undocumented SHOW LANFREE command in Tivoli Storage Manager V5.2.

The syntax of the VALIDATE LANFREE command is:

VALidate LAnfree node_name stgagent_name

The parameters for this command are:

� node_name (Required), which is the name of the node to evaluate. � stgagent_name (Required), which is the name of the Storage Agent to evaluate.

Example 7-11 shows the output from the VALIDATE LANFREE command in our setup, run on the Tivoli Storage Manager server, AZOV for the client, and Storage Agent SENEGAL.

Example 7-11 VALIDATE LANFREE command output

tsm: AZOV_1>validate lanfree senegal senegal_sta ANR0387I Evaluating node SENEGAL using storage agent SENEGAL_STA for LAN-free data movement. Node Name : SENEGAL Storage Agent : SENEGAL_STA Operation : BACKUPMgmt Class Name : STANDARDDestination Name : 3582_TAPELAN-Free capable? : Yes Explanation :

Node Name : SENEGAL Storage Agent : SENEGAL_STA Operation : ARCHIVEMgmt Class Name : STANDARDDestination Name : 3582_TAPELAN-Free capable? : Yes Explanation :

ANR1706I Ping for server 'SENEGAL_STA' was able to establish a connection.ANR0388I Node SENEGAL using storage agent SENEGAL_STA has 2 storage pools capable of LAN-free data movement and 0 storage pools not capable of LAN-free data movement.

The output shows that the node SENEGAL using Storage Agent SENEGAL_STA has two storage pools that are capable of LAN-free data movement. If there were other storage pools not capable of LAN-free data movement, they would be shown as LAN-Free cable? : No.

Notice also the message that the server AZOV established a connection with the Storage Agent, SENEGAL_STA, using ping. This information tells us that the PING SERVER command was issued by the Tivoli Storage Manager server and was able to successfully communicate with the Storage Agent.


If the server is not able to ping the Storage Agent successfully, the error shown in Example 7-12 appears in the VALIDATE LANFREE output.

Example 7-12 Server unable to ping the Storage Agent

ANR1705W Ping for server 'SENEGAL_STA' was not able to establish a connection.

To resolve this issue, you should first verify that the Storage Agent service/daemon is running on the client system. If it is running, you could stop and restart it and make sure that it remains running. Issue the PING SERVER command from the Tivoli Storage Manager server to test the connection with the Storage Agent. For example:

PING SERVER SENEGAL_STA

If the server is unable to establish a connection with the Storage Agent, verify that the following TCP/IP port settings all match.

� LLADDRESS

On the Tivoli Storage Manager server, check the LLADDRESS that is used for the Storage Agent server definition. Issue QUERY SERVER storage_agent_name F=D, where storage_agent_name is the actual name of your Storage Agent. The specified port is opened to communicate with the Storage Agent,.

� TCPPORT

On the Storage Agent machine, edit the option file, dsmsta.opt to verify that the TCPPORT value. The specified port is opened to communicate with the server and client.

� LANFREETCPPORT

On the client machine, view or edit the client options file, to verify the LANFREETCPPORT option. The specified port is opened to communicate with the storage age. LANFREETCPPORT is used only when the LANFREECOMMMETHOD is set to TCPIP. If a shared memory or named pipes is being used, then disregard this option.

For our other client, KANAGA, which is using SENEGAL as its external Storage Agent, the VALIDATE LANFREE output looks similar to that shown in Example 7-13.

Example 7-13 Validate LAN-free on client using proxy Storage Agent.

tsm: AZOV_1>validate lanfree kanaga senegal_staANR0387I Evaluating node KANAGA using storage agent SENEGAL_STA for LAN-freedata movement.

Node Storage Operation Mgmt Class Destination LAN-Free ExplanationName Agent Name Name capable?----- -------- --------- ---------- ------------ --------- --------------------KANA- SENEGAL- BACKUP STANDARD 3582_TAPE Yes GA _STAKANA- SENEGAL- ARCHIVE STANDARD 3582_TAPE Yes GA _STAANR1706I Ping for server 'SENEGAL_STA' was able to establish a connection.ANR0388I Node KANAGA using storage agent SENEGAL_STA has 2 storage poolscapable of LAN-free data movement and 0 storage pools not capable of LAN-freedata movement.


After you have verified that a LAN-free path is available, you can perform a client backup to test the LAN-free connection. When the backup is started, you can confirm that data is being transferred over the SAN:

� If using the Backup-Archive interface, the Detailed Status Report should reveal the number of LAN-free Data Bytes that has been transferred, as shown in Figure 7-38. This is different from a normal LAN backup, when this option is grayed out.

Figure 7-38 Example of Backup-Archive Client that shows bytes transferred using LAN-free

� If using the Backup-Archive Client, it will show the LAN-free data bytes, as part of the backup/restore status report, as shown in Example 7-14. This line does not appear on a LAN backup.

Example 7-14 Backup-Archive Client that shows LAN-free bytes

Total number of objects inspected: 2Total number of objects backed up: 2Total number of objects updated: 0Total number of objects rebound: 0Total number of objects deleted: 0Total number of objects expired: 0Total number of objects failed: 0Total number of bytes transferred: 1.95 GBLanFree data bytes: 1.95 GB

� On the Tivoli Storage Manager server confirm that the data is being transferred using LAN-free data movement by looking for messages in the activity log similar to those shown in Example 7-15.

Example 7-15 Activity log messages that confirm LAN-free data movement

ANR0415I Session 991 proxied by SENEGAL_STA started for node SENEGAL. ANR0408I Session 992 started for server SENEGAL_STA (Windows) (Tcp/Ip) for library sharing.


7.7 Communicating with and monitoring the Storage AgentIt is sometimes useful to communicate with or monitor the Storage Agent to get a better understanding of what is going on (for example, when troubleshooting).

7.7.1 Querying from the Tivoli Storage Manager serverYou can issue query commands for the Storage Agent machine from the Tivoli Storage Manager server. For example, you can query the tape mounts that are held by the Storage Agent senegal_sta using the QUERY MOUNT command. Use the Storage Agent name as a prefix to the command, as shown in Example 7-16.

Example 7-16 Using the server to perform queries on the Storage Agent

tsm: AZOV_1>senegal_sta: query mount ANR1699I Resolved SENEGAL_STA to 1 server(s) - issuing command Q MOUNT against server(s).ANR1687I Output for command 'Q MOUNT ' issued against server SENEGAL_STA follows:ANR8329I LTO volume 032AKK is mounted R/W in drive DRIVE1 (\\.\Tape0), status: IDLE.ANR8334I 1 matches found.ANR1688I Output for command 'Q MOUNT ' issued against server SENEGAL_STA completed.ANR1694I Server SENEGAL_STA processed command 'Q MOUNT ' and completed successfully.ANR1697I Command 'Q MOUNT ' processed by 1 server(s): 1 successful, 0 with warnings, and 0 with errors.

7.7.2 Using the command line interfaceYou can also use the command line interface to the Storage Agent itself to issue commands or to run it in console mode for monitoring purposes. To do this, you need to install the Tivoli Storage Manager command line interface package, which is part of the Backup-Archive Client. The command line interface package can be installed on any system with TCP/IP connectivity to the Storage Agent system. You can then run dsmadmc for the Storage Agent by using the flags -tcps option (to specify the tspserveraddress of the Storage Agent) and the -tcpp option (to specify the tcpport of the Storage Agent).

For example, to start a command line interface session to the Storage Agent SENEGAL_STA, use:

dsmadmc -tcps=9.1.39.166 -tcpp=1502

To submit the ID and password without being prompted, use:

dsmadmc -tcps=9.1.39.166 -tcpp=1502 -id=admin -pa=admin

To run in console mode, use:

dsmadmc -tcps=9.1.39.166 -tcpp=1502 -consolemode -id=admin -pa=admin

Alternatively, you can add a server stanza to the appropriate client configuration file using the following parameters:

SErvername senegal_sta TCPServeraddress 9.1.39.166TCPPort 1502

You can then run the command line interface by issuing the following command:

dsmadmc -servername=senegal_sta


7.8 Configuring other Tivoli products for LAN-free This section contains a summary of how to allow the Data Protection clients to make use of a LAN-free configuration. It uses the term Data Protection to refer to the following Tivoli Storage Manager products:

� Tivoli Storage Manager for Mail, including Data Protection for Lotus Domino® and Data Protection for Microsoft Exchange Server.

� Tivoli Storage Manager for Databases, including Data Protection for Oracle™, and Data Protection for Microsoft SQL Server.

� Tivoli Storage Manager for Application Servers, including Data Protection for WebSphere Application Servers.

When configuring the Data Protection clients for LAN-free backup, we recommend that you:

1. Install and configure the Backup-Archive Client and Storage Agent.

Even if you do not plan on using the Backup-Archive Client, it is still a good idea to install and configure it on the system where you will be installing the Data Protection client. By doing this, you have a simple way to validate the LAN-free connection between the client machine, the SAN-attached devices and the Tivoli Storage Manager server by performing a straight file backup and restore, before the additional complication of configuring the TDP client. This will make troubleshooting the initial connection easier.

Installing and configuring the Backup-Archive Client is also recommended because it allows you to protect the rest of the client system data the data that the Data Protection clients can’t backup.

You will install and configure the Backup-Archive Client as described in the Backup-Archive Clients Installation and User’s Guide for your client operating system platform. You will install and configure the Storage Agent as described in this chapter. This includes registering the Backup-Archive Client node to the Tivoli Storage Manager server and configuring the client options file. It is a good idea to register a node for the Data Protection client while your registering one for the Backup-Archive Client.

You install and configure the Data Protection client as per the accompanying installation and user’s guide.

2. Locate the client options file.

The major difference between configuring the Backup-Archive Client and the Data Protection clients for LAN-free are the options files to configure. Even though there are several common options that can be used by both products, each product has its own specific options file. By default the options files for each product is located in the default installation directory.

For example, considering the Backup-Archive Client and Data Protection for Oracle, the options files are:

– Backup-Archive Client

• Windows

C:\Program Files\Tivoli\TSM\baclient\dsm.opt

• AIX

/usr/tivoli/tsm/client/ba/bin/dsm.sys

/usr/tivoli/tsm/client/ba/bin/dsm.opt


– Data Protection for Oracle client’s option file:

• Windows

C:\Program Files\Tivoli\TSM\AgentOBA\dsm.opt

• AIX

/usr/tivoli/tsm/client/oracle/bin/tdpo.opt

/usr/tivoli/tsm/client/oracle/bin/dsm.opt

/usr/tivoli/tsm/client/api/bin/dsm.sys (symbolic linked /usr/tivoli/tsm/client/ba/bin/dsm.sys)

3. Configure the Data Protection client options file for LAN-free.

Once the Backup-Archive Client and Storage Agents are configured and a successful LAN-free backup was performed, you can configure the Data Protection client options file to enable LAN-free data movement. For example, if we installed TDP for Oracle on the machine senegal, we could define an additional node name, senegal_oracle for use by this application. The dsm.opt file in C:\Program Files\Tivoli\TSM\AgentOBA\ would include the options shown in Example 7-17

Example 7-17 Sample option file for TDP for Oracle on Windows

COMMMethod TCPipTCPServeraddress 9.1.39.89NODename senegal_oracleCOMMmethod TCP/IPTCPPort 1500ENABLELanfree YesLANFREECommmethod TCPIPLANFREETCPPORT 1502

In the same environment on AIX, the file dsm.sys is in /usr/tivoli/tsm/client/api/bin/ and have the entries in Example 7-17

Example 7-18 Sample option file for TDP for Oracle on AIX

*Server Stanza for Data Protection for OracleCOMMmethod TCP/IPTCPPort 1500TCPServeraddress 9.1.39.89 ** AZOV TSM server **NODename Kanaga_oracleENABLELanfree YesLANFREECommmethod TCPIPLANFREETCPSERVERADDRESS 9.1.39.166 ** Storage agent on SENEGAL **LANFREETCPPORT 1502

4. Verify LAN-free backup.

Review the steps in 7.6, “Verifying the LAN-free path” on page 200 to ensure that the Data Protection client backup is being transferred over the SAN.

Note: On new installations, sample option files are provided with an .smp extension (for example, tdpo.opt.smp or dsm.sys.smp). You should copy these sample files to the appropriate name.



Chapter 8. LAN-free backup to disk

This chapter discusses the configuration that is necessary to set up Tivoli Storage Manager LAN-free data movement to disk. It covers the following topics:

� Introduction to LAN-free backup to disk� Preconfiguration: Setting up SANergy� Overview of the lab environment� Summary of LAN-free disk configuration� Setting up the SAN-attached disk device on the Tivoli Storage Manager server� Creating a policy domain for LAN-free clients� Registering client node(s)� Setting up server-to-server communication� Installing and configuring the client� Configuring the Storage Agent� Enabling LAN-free data movement� Verifying the LAN-free path

8


8.1 Introduction to LAN-free backup to diskLAN-free backup to disk works similarly to LAN-free backup to tape, in that data is transferred from a Storage Agent to a SAN-attached device. However, the data will be sent to SAN-attached disk. Internally, Tivoli Storage Manager configures the disk as a sequential device so that it emulates a tape library using the FILE device class.

Tivoli SANergy is required to manage shared access to the SAN disk device. A SANergy Metadata Controller (MDC) is required, and each Storage Agent which backs up to the SAN disk needs to be configured as a SANergy host.

Table 8-1 shows the currently tested combinations for these components for LAN-free backup to disk. Other combinations are possible.

Table 8-1 Tested combinations for LAN-free to SANergy managed disk storage pool

8.2 Preconfiguration: Setting up SANergyTo plan and install SANergy in your environment, consult the following documentation:

� A Practical Guide to Tivoli SANergy, SG24-6146 � IBM Tivoli SANergy Administrator’s Guide, Version 3 Release 2, GC32-0740

You can download the IBM Tivoli SANergy Administrator’s Guide from:

http://publib.boulder.ibm.com/tividd/td/link/tdprodlist.html#S

You should ensure that your environment meets all hardware and software system requirements before you install the software.

Obtain the SANergy software (Tivoli SANergy V3.2.4 is included with the Tivoli Storage Manager Storage Agent package) and install it by following the instructions on the screen and in the mentioned documentation. You need to install an MDC, which can be the Tivoli Storage Manager server itself or a separate system. This system must have access to the SAN-attached disks. You then install each Storage Agent that will backup to the

Tivoli Storage Manager server platform

SANergy MDC platform Tivoli Storage Manager client platform

Tivoli Storage Manager server and SANergy MDC on same machine

Windows NT 2000 Windows NT 2000 Windows Yes

Windows NT 2000 Windows NT 2000 Sun Yes

Windows NT 2000 Windows NT 2000 AIX Yes

Sun Sun Windows Yes

Sun Sun Sun Yes

Sun Sun AIX Yes

Windows NT 2000 Sun Windows No

Windows NT 2000 Sun Sun No

Windows NT 2000 Sun AIX No

AIX Sun Windows No


http://publib.boulder.ibm.com/tividd/td/link/tdprodlist.html#S

SAN-attached disks as a SANergy host. The SANergy hosts must also have visibility to the SAN-attached disks.

8.3 Overview of the lab environmentFigure 8-1, shows how we used SANergy in our lab environment. The Windows machine TONGA was set up as the Tivoli Storage Manager server as well as the SANergy MDC. The Windows machine SENEGAL was set up with the Tivoli Storage Manager Backup-Archive Client and the Storage Agent as well as the SANergy Host code.

Figure 8-1 The LAN-free to disk setup in our lab

After installing and configuring SANergy on TONGA, we allocated two SAN-attached disks to TONGA on the attached SAN disk system. These disks were labelled sandisk1 and sandisk2 and appear as local drives on TONGA (E and F, respectively). We created directories on these disks that will be used for sharing and configuring with Tivoli Storage Manager. These directories are E:\mydir1 and F:\mydir2.

We set TONGA, the MDC, to own these two disks within the SANergy configuration.The drives were shared with standard Windows sharing. We created a directory on the root level of each drive to be used by Tivoli Storage Manager.

Note: At the time of writing, there is an issue with sharing file volumes that are located in the root directory of a partition. When defining a shared file device class, you should not use the root directory when specifying a directory location. Refer to the latest copy of the Storage Agent’s readme file for any updates on this matter.

SAN



LAN

File Library

LibraryControlClient

Data

Storage Agent: Senegal_sta

Backup-Archive Client: SENEGAL

SENEGAL9.1.39.166

TONGA9.1.39.168

SANergy MDCSANergy Host

Define path senegal_sta sandisk1....directory=\\9.1.39.168\e$\mydir1,\\9.1.39.168\f$\mydir2

e:\mydir1f:\mydir2

Owned by MDC Tonga

SANDISK1

Chapter 8. LAN-free backup to disk 209

Figure 8-2 shows the SAN-attached disks with their drive letters assigned on TONGA, the MDC. Because TONGA is the MDC, the disks show as local drives.

Figure 8-2 SAN-attached disks to be accessed for LAN-free backup

Figure 8-3 shows that the drives have been shared using Windows.

Figure 8-3 MDC shares the drives


Figure 8-4 shows the managed bus in SANergy on TONGA, the MDC, as well as the disks that are available on that bus.

Figure 8-4 SANergy managed buses

Figure 8-5 shows the devices that are assigned in SANergy on the MDC to be owned by TONGA.

Figure 8-5 SANergy device assignment


Figure 8-6 shows that the SAN volumes have been assigned to TONGA as the MDC owner.

Figure 8-6 Volumes assigned to TONGA

We installed the SANergy host code on the Tivoli Storage Manager client, SENEGAL, making sure it could see the SAN-attached disks that were shared by TONGA. We then used Windows drive mapping to access the disks as network drives. We selected Reconnect at logon when we created the Windows share. The disks were accessed as shares via SANergy on SENEGAL, as shown in Figure 8-7.

Figure 8-7 SANergy shared disks accessed on SENEGAL


8.4 Summary of LAN-free disk configurationThe remaining sections of this chapter discuss the following:

� Using the configured devices to define a Tivoli Storage Manager shared file device class called SANDISK. By specifying the share option when creating the file device class, Tivoli Storage Manager creates automatically a file library named SANDISK and creates a file drive called SANDISK1. The number of drives that are defined is determined by the mount limit in the device class definition. Our example uses a mount limit setting of one. So, only one drive is created. Thus, only one backup/restore operation can take place at a time to this device class. If you specify a higher mount limit, then multiple concurrent options are possible.

� Creating a storage pool that uses this device class and defining a policy domain and management class to use this storage pool by default.

� Registering the client node SENEGAL and defining a server for the Storage Agent that is called SENEGAL_STA.

� Installing the Tivoli Storage Manager Backup-Archive Client and Storage Agent on the host SENEGAL.

� Defining a path to the SAN-attached disk directories for the Storage Agent SENEGAL_STA.

� Validating the configuration and performing a backup.

8.5 Setting up the SAN-attached disk device on the Tivoli Storage Manager server

The SAN-attached disk has been made available by the SANergy MDC (TONGA) to the host SENEGAL, which uses it to backup LAN-free to disk. Now, you can configure Tivoli Storage Manager to allow LAN-free to disk data movement.

This section explains how to configure a device class for the SAN disk device to be used by the server and Storage Agent. It provides the steps that are required from the Administration Center as well as from the command line interface. You execute these steps on the Tivoli Storage Manager server TONGA.

8.5.1 Setting up the SAN disk device from the Administration CenterTo set up the SAN disk device from the Administration Center:

1. From the Work Item menu, select Storage Devices. The Servers screen appears, as shown in Figure 8-8 on page 214. Select the server on which you will work (in this case, TONGA), and from the Select Action list, select View Device Classes. Click Go.


Figure 8-8 Servers screen

2. The current device classes for TONGA displays, as shown in Figure 8-9. Select Create a Device Class and click Go.

Figure 8-9 Device Classes screen

3. The Select Device Type screen appears, as shown in Figure 8-10. Select FILE (uses sequential-access volumes on disk). Click Next.

Figure 8-10 Select Device Type screen


4. On the General Information screen (Figure 8-11), enter a name for the file device class (we chose SANDISK). Enter the directory location(s) where the client node(s) store the client data. (These are the shared directory names of the SAN disks that were created in 8.3, “Overview of the lab environment” on page 209.) You can enter multiple directories and separate them with a comma. Make sure to select the option Allow other servers and Storage Agents to share access to volumes in the specified directories. This option is equivalent to the shared library option for tape libraries, and when checked, the server creates a library file and a drives file automatically for use by the server and Storage Agent. Specify the mount limit, which indicates how many file drives are created. Specify the maximum file size, which represents the size of each file which is created. Click Next.

Figure 8-11 Shared file device class definitions

5. The Summary screen appears (Figure 8-12 on page 216). It contains information that the device class has been created. Click Finish.

Note: At the time of writing, there is an issue with sharing file volumes that are located in the root directory of a disk partition. When defining a shared file device class, you should not use the root directory when specifying a directory location. Refer to the latest copy of the Storage Agent’s readme file for any updates on this matter.


Figure 8-12 Create Device Summary screen

6. The newly created file device class and its properties now appear in the Device Classes screen, as shown in Figure 8-13. Note the created file library, also called SANDISK.

Figure 8-13 Newly created device class SANDISK, with file library called SANDISK.

When defining a shared file device class, the server creates a file library and file drive definitions for those devices automatically. The file library and file drives are named after the file device class.

7. Scroll down to the Libraries for All Servers section, select Refresh Table and click Go. The newly created file library is now listed among the other defined libraries, as shown in Figure 8-14 on page 217.

Note: In Tivoli Storage Manager V5.2, path definitions could be made for the file library and drive but are never actually used by the server. In V5.3, path definitions are not allowed or necessary for file library and drive setups.


Figure 8-14 New library is listed

8. Use the SAN disk device class that you defined to create a storage pool that is used by the client node(s) to store and manage LAN-free to disk data. Select Storage Devices from the Work Items menu. Select the Tivoli Storage Manager server (TONGA in this example). Select View Storage Pools and click Go, as shown in Figure 8-15.


9. On the Storage Pools screen (Figure 8-16), select Create a Storage Pool.

Figure 8-16 Create Storage Pools screen

10.The General Storage Pool Settings screen appears, as shown in Figure 8-17 on page 218. Enter a name for the storage pool and optional description. Select Primary, sequential access, for the type of storage pool to create. Click Next.


Figure 8-17 General Storage Pool Settings screen

11.The Select a Device Class screen appears (Figure 8-18). For the Device class name, select the file device class just created, SANDISK in our case. Specify the maximum number of scratch volumes to use. If this value is set greater than zero, the server creates and uses that number of file volumes automatically. The value entered for the Maximum File Size when defining the file device class, determines the size of each scratch file volume. Ensure that the value entered for maximum scratch volumes, multiplied by the maximum file size, does not exceed the total size of the SAN-attached disk. Click Next.

Figure 8-18 Select a Device Class screen

12.Verify the information included in the Summary screen (Figure 8-19 on page 219) and click Finish.


Figure 8-19 Create Storage Pool Summary screen

13.The newly created storage pool now appears in the list, as shown in Figure 8-20.

Figure 8-20 New storage pool

8.5.2 Setting up the SAN disk device using the command line interfaceTo set up the SAN-attached disk device from the Tivoli Storage Manager command line interface on the server:

1. Create the shared device class, which creates a file library and file drive(s) automatically. Use the DEFINE DEVCLASS command as follows:

DEFINE DEVCLASS sandisk DEVTYPE=FILE DIR=e\mydir1,f:\mydir2 MOUNTLIMIT=1 MAXCAP=500M SHARED=YES

The SHARED=YES setting means that the server creates a file library and file drives automatically for the disk device for use by the server and Storage Agent. The MOUNTLIMIT parameter indicates how many file drives are created. The MAXCAP parameter represents the size of each file that are created. The file library is named the same as the name specified for the file device class. The file drive names consist of the device class names with a number immediately after.


The DIRECTORY parameter corresponds to the SANergy shared directories, as configured in 8.3, “Overview of the lab environment” on page 209. Separate multiple directories with a comma.

After creating the device class, check its details using the QUERY DEVCLASS command and specify the device class name that you created, as in the following command:

Query DEVclass sandisk F=D

Example 8-1 shows the output of the command.

Example 8-1 QUERY DEVCLASS sandisk detailed output

Device Class Name: SANDISK Device Access Strategy: Sequential Storage Pool Count: 1 Device Type: FILE Format: DRIVE Est/Max Capacity (MB): 500 Mount Limit: 1 Mount Wait (min): Mount Retention (min): Label Prefix: Drive Letter: Library: SANDISK Directory: E:\MYDIR1,F:\MYDIR2 Server Name: Retry Period: Retry Interval: Twosided: Shared: Yes High-level Address: Minimum Capacity: WORM: No Scaled Capacity: Last Update by (administrator): ADMIN Last Update Date/Time: 4/1/05 4:01:53 PM PST

2. Look at the devices that were created automatically. To see the library, use the QUERY LIBRARY command, for example:

q library sandisk

Replace sandisk with the name of your device class, because this is the name which is assigned by Tivoli Storage Manager for the library. Example 8-2 shows the output.

Example 8-2 The output from QUERY LIBRARY sandisk

Library Name: SANDISK Library Type: FILE ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: RSM Media Type: Shared: Yes LanFree: ObeyMountRetention:


3. Query the drive(s) that were created automatically. The drives appear as in Example 8-3, SANDISK1 in our case. Remember the number of drives in the file library corresponds to the mount limit that was specified in the device class definition.

Example 8-3 Output from QUERY DRIVE sandisk sandisk1

tsm: TONGA_1>q drive

Library Name Drive Name Device Type On-Line------------ ------------ ----------- -------------------3582LIB DRIVE1 LTO Yes3582LIB DRIVE2 LTO YesSANDISK SANDISK1 FILE Yes

4. Create a storage pool using the SAN disk device class to be used by the client node(s) to store and manage LAN-free to disk data. As part of the DEFINE STGP command, specify the maximum number of scratch volumes to use. If you specify a value greater than zero, the server creates and uses that number of file volumes automatically. The value that you chose for the Maximum File Size, in the device class definition, determines the size of each scratch file volume. The MAXSCRATCH parameter of the storage pool, multiplied by the maximum file size in the device class, must not exceed the capacity of the SAN-attached disk.

DEFINE STGPOOL SANDISKPOOL SANDISK pooltype=primary description=”LANfree to disk use” maxscratch=3

To show the new pool, use the QUERY STGPOOL command.

Q STG SANDISKPOOL F=D

The output is shown in Example 8-4.

Example 8-4 Q STG SANDISK F=D output

Storage Pool Name: SANDISKPOOLDevice Class Name: SANDISKEstimated Capacity: 0 M Pct Util: 0 Pct Migr: 0 High Mig Pct: 90 Low Mig Pct: 70Next Storage Pool:


8.6 Creating a policy domain for LAN-free clientsNext, you create a new policy domain with a default management class that points to the SAN-attached disk to be used for this LAN-free configuration. You set this management class as the default to allow clients that are registered to it to use it automatically.

This section provides instructions for creating a policy domain for LAN-free clients from the Administration Center and using the command line interface.

8.6.1 Creating a policy domain from the Administration CenterTo create a policy domain from the Administration Center:

1. From the Work Items list, select Policy Domains and Client Nodes.

The Policy Domains screen appears, as shown in Figure 8-21. Select the server which will have the new policy domain (TONGA_1 in our case).

Figure 8-21 Policy Domains screen

2. The current list of policy domains displays (Figure 8-22). Select Create a Policy Domain and click Go.

Figure 8-22 List of policy domains

3. The General screen appears, as shown in Figure 8-23 on page 223. Enter a name for the policy domain and specify the Backup and Archive retention as desired. Click Next.


Figure 8-23 Policy Domain General screen

4. On each of the two Select a Storage Pool lists shown in Figure 8-24, select the storage pool or pools that were created to use the shared file device class. We created only one storage pool. Therefore, select SANDISKPOOL. However, if you have different storage pools, you can use them to separate backup and archive data. Click Next.

Figure 8-24 Specify storage pool for the policy domain

5. The Assign Clients Now? screen appears (Figure 8-25 on page 224). Click No, if you have not yet registered the client node for LAN-free backup, then click Next and continue with the next step.

Otherwise, click Yes, then, click Next, and skip to step 7 on page 224.


Figure 8-25 Create Policy Domain Assign Client Nodes Now? screen

6. The Summary screen appears (Figure 8-26). Verify the information and click Finish. Skip to step on page 226.

Figure 8-26 Create Policy Domain Summary screen

7. If you did choose to assign a client to the policy domain in Figure 8-25, then the Assign Client Nodes screen appears, as shown in Figure 8-27 on page 225. Select the option to view all client nodes, and click Next.


Figure 8-27 Create Policy Domain Assign Client nodes screen

8. All the client nodes are displayed, as shown in Figure 8-28. Check the client node(s) to be assigned, and click Next.

Figure 8-28 Select client nodes to assign to the policy domain

9. The Summary screen appears, Figure 8-29 on page 226. Verify that the information is correct and click Finish.


Figure 8-29 The Create Policy Domain Summary screen

The newly created policy domain shows up in the list, as shown in Figure 8-30.

Figure 8-30 The newly created policy domain

8.6.2 Creating a policy domain using the command line interfaceTo define the policy domain and management class structure to allow LAN-free data movement, using the command line interface, enter the following commands:

DEFINE DOMAIN lanfree_disk DESCRIPTION="Policy Domain for Client nodes that use LANfree to disk" BACKRETENTION=30 ARCHRETENTION=365DEFINE POLICYSET lanfree_disk standard desc="Standard policy set"DEFINE MGMTCLASS lanfree_disk standard standard desc="Standard management class"DEFINE COPYGROUP lanfree_disk standard standard destination=SANDISKPOOLDEFINE COPYGROUP lanfree_disk standard standard type=archive destination=SANDISKPOOLASSIGN DEFMGMTCLASS lanfree_disk standard standardVALIDATE POLICYSET lanfree_disk standardACTIVATE POLICYSET lanfree_disk standard

Query the copy group to see the active policy that was created:

Q COPYGROUP


Example 8-5 shows the output from this command.

Example 8-5 Extract from the query copygroup output, showing the new policy domain info

Policy Domain Name: LANFREE_DISK Policy Set Name: ACTIVE Mgmt Class Name: STANDARD Copy Group Name: STANDARDVersions Data Exists: 2Versions Data Deleted: 1Retain Extra Versions: 30Retain Only Version: 60

8.7 Registering client node(s)If the client node that will use LAN-free transport is not already registered to the Tivoli Storage Manager server, register it now. If the node is already registered, then ensure that it is updated to use the policy domain that is intended for LAN-free use, and you can skip this section.

This section explains how to register client nodes from the Administration Center and using the command line interface.

8.7.1 Registering the node from the Administration CenterFrom the Administration Center:

1. From the Policy Domains screen, as shown in Figure 8-30 on page 226, click the newly created policy domain, LANFREE_DISK in our example. The policy domain Properties screen appears. Click Client Nodes and select Create a Client Node, as shown in Figure 8-31. Click Go.

Figure 8-31 Policy domain properties screen, after selecting Create a Client Node

2. The Create Client Node General screen appears, as shown in Figure 8-32 on page 228. Give the client node a name and any other information. Click Next.


Figure 8-32 Create Client Node General screen

3. The Create Client Node Security screen appears, as shown in Figure 8-33. Enter a password and expiration details, and click Next.

Figure 8-33 Create Client Node Security screen

4. The Summary screen (Figure 8-34 on page 229) confirms that the node has been created. Click Finish.


Figure 8-34 Create Client Summary screen

5. The newly created node now appears within the policy domain, as shown in Figure 8-35.

Figure 8-35 The newly created node shows up under the policy domain

8.7.2 Registering a node using the command line interfaceYou can register a client node using the command line interface as follows:

1. Enter the following command:

REGISTER NODE senegal ?***? PASSEXP=0 CONTACT="Joe Smith - TSM Administrator" DOMAIN=LANFREE_DISK FORCEPWRESET=NO URL=http://myclient.mycompany.com:1581

2. If the node is already registered, then ensure that it is updated to use the policy domain that is intended for LAN-free use using the following command:

UPDATE NODE senegalDOMAIN=LANFREE_DISK

3. Check the results by querying the new node:

QUERY NODE SENEGAL


The output should be similar to that shown in Example 8-6.

Example 8-6 QUERY NODE SENAGAL output

Node Name : SENEGAL Platform: (?) Policy Domain Name: LANFREE_DISKDays Since Last Access: <1Days Since Password Set: <1 Locked?: No

8.8 Setting up server-to-server communicationTo prepare the Tivoli Storage Manager server to be communicate with Storage Agents and other servers, you first set the necessary settings on the destination server. These settings includes setting a server name and password that are used by Storage Agents and other servers.You then define a new server to represent the Storage Agent that you use for LAN-free to disk data movement.

This sections includes the steps for setting up server-to-server communication from the Administration Center and using the command line interface.

8.8.1 Setting up server-to-server communication from the Administration Center


1. From the Work Items list, click Enterprise Management. The Enterprise Management screen appears, as shown in Figure 8-36. Click Select next to the server that you would like to set as the Library Manager for the file library (in our case, TONGA). Select Server-to-Server Communication Settings and click Go.

Figure 8-36 Enterprise Management screen

2. The Server-to-Server Settings screen appears, as shown in Figure 8-37 on page 231. If the information is complete, continue to the next step. Otherwise, enter and verify the server password, TCP/IP address, and port number. The Enable cross-definition option is not required for communicating with a Storage Agent but should be used when configuring communications with many other servers in a large environment. Click OK.


Figure 8-37 Server-to-Server settings for the Library Manager server

3. The server list redisplays (Figure 8-36 on page 230). Define a server to represent the Storage Agent. Click the server again (TONGA) and expand the Servers entry, as shown in Figure 8-38.

Figure 8-38 Servers and Server Groups Defined screen

4. From the Select Action list, select Define Server, as shown in Figure 8-39. Click Go.


5. The Welcome screen appears, a shown in Figure 8-40 on page 232. Click Next.


Figure 8-40 Define Server Welcome screen

6. On the General screen (Figure 8-41), enter a name for the Storage Agent. We chose SENEGAL_STA. Specify a password and optional description. We do not select the option to allow the server that is defined to initiate communications with TONGA, because the Storage Agent software has not yet been installed and configured (as described in 8.10, “Configuring the Storage Agent” on page 236). Click Next.

Figure 8-41 Define Server General screen

7. Figure 8-42 on page 233 shows the Communications screen. Enter the TCP/IP address for the Storage Agent machine and the port to be used for communication by this server. We used port 1502, although the default is 1500. The value entered here must match the LANFREETCPPORT setting in the client’s options file and the TCPPORT setting within the Storage Agent’s dsmsta.opt option file, as shown in 8.9, “Installing and configuring the client” on page 235 and 8.10, “Configuring the Storage Agent” on page 236. Click Next.


Figure 8-42 Server-to-server communication screen.

8. The Virtual Volumes screen appears (Figure 8-43). Because virtual volumes are not required when defining a Storage Agent server, do not select to configure this server for virtual volumes. Click Next.

Figure 8-43 Define a Server Virtual Volume screen

9. The Summary screen, as shown in Figure 8-44 on page 234, indicates that the server was defined. Click Finish.


Figure 8-44 Define Server Summary screen

10.The newly created server appears in the Servers screen, as shown in Figure 8-45.

Figure 8-45 Newly created Storage Agent server appears

8.8.2 Setting up server-to-server communication using the command line interface

To set up server-to-server communication using the command line interface:

1. Set the name and TCP/IP settings for the server that will be used for the Library Manager by running the following commands:

SET SERVERNAME tonga_1SET SERVERHLADDRESS 9.1.39.168SET SERVERLLADDRESS 1500SET SERVERPASSWORD tongapw

Use the QUERY STATUS command, as shown in Example 8-7, to show the results.

Example 8-7 QUERY STATUS command showing server definition

Storage Management Server for Windows - Version 5, Release 3, Level 1.0 Server Name: TONGA_1 Server host name or IP address: 9.1.39.168 Server TCP/IP port number: 1500 Crossdefine: Off Server Password Set: Yes


2. Define a server to represent the Storage Agent. We used port 1502, although the default is 1500. The value entered here must match the LANFREETCPPORT setting in the client’s options file and the TCPPORT setting within the Storage Agent’s dsmsta.opt option file, as shown in 8.9, “Installing and configuring the client” on page 235 and 8.10, “Configuring the Storage Agent” on page 236. This port is used for communication between the Storage Agent and the Tivoli Storage Manager server.

DEFINE SERVER senegal_sta SERVERPASSWORD=?***? HLADDRESS=9.1.39.166 LLADDRESS=1502 DESCRIPTION="Storage Agent used for Senegal's LAN-free data movement"

Use the QUERY SERVER command, as shown in Example 8-8, to show the results.

QUERY SERVER SENEGAL_STA

Example 8-8 QUERY SERVER senegal_sta output

Server Name: SENEGAL_STA Comm. Method: TCPIP High-level Address: 9.1.39.166 Low-level Address: 1502 Days Since Last Access: 10 Server Password Set: YesVirtual Volume Password Set: No Allow Replacement: No

8.9 Installing and configuring the clientNext, you configure the client system, SENEGAL, for LAN-free backup. You should have installed the Tivoli Storage Manager Backup-Archive Client and tested it for normal backup to the Tivoli Storage Manager server. For more detailed information about setting up the Backup-Archive Client, see the Backup-Archive Clients Installation and User’s Guide for your client platform. Example 8-9 shows a typical client options file which would enable regular backup to the Tivoli Storage Manager server.

Example 8-9 Sample client options file, dsm.opt to enable backup to TONGA

COMMmethod TCP/IPTCPPort 1500TCPServeraddress 9.1.39.168

8.9.1 LAN-free options (used between the client and the Storage Agent)To enable the SAN (LAN-free) path to be used, you need to set these additional options in the client options file.

� ENABLELANFREE� LANFREECOMMMETHOD� LANFREETCPPORT or LANFREESHMPORT

Always set ENABLELANFREE yes for a LAN-free client. Set LANFREECOMMMETHOD to identify what communication method to use between the Backup-Archive Client and the Storage Agent, and then identify a port to use, using either LANFREETCPPORT or LANFREESHMPORT. The selection of this option depends on whether the client has a local Storage Agent installed, or uses another Tivoli Storage Manager client system (proxy) as the Storage Agent. These configuration options are discussed in 7.4.3, “Configuring the client” on page 191. If you use an external system for the Storage Agent, you would set the client options file as described in “Using an external Storage Agent” on page 192.


Storage Agent and client on same systemIf the Storage Agent is on the same system as the Backup-Archive Client (as in the case of SENEGAL), specify LANFREECOMMMETHOD of sharedmem. Using shared memory gives the best performance when the communication is local, as in this case. Specify the port to use with the LANFREESHMPORT option. This is a different port from the one used between the Storage Agent and the Tivoli Storage Manager server. SENEGAL’s option file looks similar to that shown in Example 8-10.

Example 8-10 Client options file with Storage Agent on same system as client node

ENABLELanfree YesLANFREECommmethod sharedmemLANFREESHMPORT 1

8.10 Configuring the Storage AgentIf the Storage Agent software has not been installed, then do so now and proceed with these configuration steps.

If your Storage Agent is on Windows system, you have the option of using the Administration Center to configure it. On other platforms, you have to use the command line interface, which is discussed in 8.10.2, “Setting up the Storage Agent using the command line interface” on page 241.

Figure 8-46 shows the LAN-free to disk setup in our lab. The Tivoli Storage Manager server is TONGA. The client and Storage Agent are on SENEGAL.

Figure 8-46 LAN-free to disk setup in our lab

Note: Installation of the Storage Agent and device drivers was discussed in Chapter 6, “Planning for LAN-free” on page 159.

SAN



LAN

File Library

LibraryControlClient

Data

Client: SENEGALStorage Agent: SENEGAL_STA

SENEGAL9.1.39.166

TONGA9.1.39.168

e:\mydir1f:\mydir2


8.10.1 Setting up the Storage Agent from the Administration CenterFrom the Administration Center:

1. On the Storage Agent system (SENEGAL), start the Management Console, as shown in Figure 8-47, by selecting Start → Programs → Tivoli Storage Manager → Management Console.

Expand Tivoli Storage Manager to show the client node name. Expand the client node name and then TSM StorageAgent1. (The TSM Device Driver expand button also appears if you have installed it).

Figure 8-47 Management console showing TSM StorageAgent1 expansion

2. The Reports and Wizards selections appear under TSM StorageAgent1. To start the TSM StorageAgent1 Wizard, double-click Storage Agent Initialization, on the right side of the window (make sure Wizards is highlighted in the left-hand panel. Alternatively, right click Storage Agent Initialization and select Start as shown in Figure 8-48.

Figure 8-48 Start the Storage Agent Initialization wizard


3. The Welcome to the Storage Agent Initialization Wizard screen appears, as shown in Figure 8-49.Click Next.

Figure 8-49 The Welcome to the Storage Agent Initialization Wizard screen

4. The TSM Server Account Information input screen appears, Figure 8-50.

Enter the Storage Agent name, password, and TCP/IP information. This information must match the information that was used when defining the Storage Agent as a server on the Tivoli Storage Manager server in 8.8.1, “Setting up server-to-server communication from the Administration Center” on page 230. Click Next.

Figure 8-50 The TSM Server Account Information screen filled in

5. The TSM Server Communication Information input screen appears, Figure 8-51 on page 239. Enter the Tivoli Storage Manager server name, password, and TCP/IP information. This information must match the entries for the Tivoli Storage Manager server shown in Figure 8-37 on page 231. Click Next.


Figure 8-51 TSM Server Communication Information

6. The Storage Agent Account Information input screen appears, Figure 8-52. Enter a suitable Windows account to be used by the Storage Agent. Be sure to select to start Automatically when Windows boots. Click Next.

Figure 8-52 Storage Agent Account Information

7. The wizard is now complete. On the final screen, as shown in Figure 8-53 on page 240, click Finish.


Figure 8-53 Completing the Storage Agent Initialization Wizard

8. The Storage Agent has been initialized message (Figure 8-54) indicates that the Storage Agent configuration was successful. Click OK.

Figure 8-54 The Storage Agent has been initialized

9. Verify that the Storage Agent service is running in the Windows Services applet, as shown in Figure 8-55.

Figure 8-55 Storage Agent service

10.Stop the Storage Agent and set the TCP/IP port which is used for Storage Agent communication with the Tivoli Storage Manager server We defined this as 1502 when creating the Storage Agent server definition. To set this port on the Storage Agent, edit the dsmsta.opt file in the C:\Program Files\Tivoli\Tsm\storageagent directory. Set the TCPPORT option to 1502 (the default is 1500).

TCPPORT 1502


11.Tivoli Storage Manager V5.3 has the SAN Discovery feature, which is discussed in Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253. This feature for the Tivoli Storage Manager server and Storage Agent allows Tivoli Storage Manager to assist in the recovery when the SAN device configuration changes.

To enable SAN Discovery on the Storage Agent, edit the dsmsta.opt configuration file in the C:\Program Files\Tivoli\TSM\Storageagent\ directory on Windows. Set the option:

SANDISCOVERY ON

12.Restart the Storage Agent to pick up the correct port using the Services applet.

13.For troubleshooting, you can run the Storage Agent in the foreground from the operating system command prompt. To do this, make sure the Storage Agent service is not running, and enter dsmsta from the Storage Agent directory, as shown in Example 8-11.

Example 8-11 The output from running the Storage Agent in foreground

C:\Program Files\Tivoli\Tsm\storageagent>dsmstaANR0900I Processing options file C:\PROGRA1\Tivoli\Tsm\STORAG1\dsmsta.opt.ANR7800I DSMSERV generated at 04:26:40 on Mar 29 2005.

Tivoli Storage Manager for WindowsVersion 5, Release 3, Level 1.0

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990, 2004.All rights reserved.U.S. Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corporation.

ANR4726I The ICC support module has been loaded.ANR8273I Shared memory driver ready for connection with clients on port 1.ANR8200I TCP/IP driver ready for connection with clients on port 1502.ANR0408I Session 1 started for server TONGA_1 (Windows) (Tcp/Ip) for storageagent.ANR0993I Server initialization complete.ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use.ANR0408I Session 2 started for server TONGA_1 (Windows) (Tcp/Ip) for eventlogging.TSM:SENEGAL_STA>

Note the ports that are listed: port 1 for communication with the shared memory client and 1502 for communication with the Tivoli Storage Manager server.

14.Enter halt from on the Storage Agent console to terminate it. Restart it as a service. Use the Windows Services applet to check that the Storage Agent is set for automatic start.

8.10.2 Setting up the Storage Agent using the command line interfaceIf your Storage Agent is running on UNIX or Linux, you need to use the command line interface. It also works for Windows, as this example shows. You need to:

1. Install the Storage Agent package.

2. Change to the Storage Agent installation directory:

– C:\Program Files\Tivoli\TSM\Storageagent\ on Windows– usr/tivoli/tsm/StorageAgent/bin on AIX– /opt/tivoli/tsm/StorageAgent/bin on other UNIX platforms


3. Edit the Storage Agent options file (dsmsta.opt) and set the following options:

DEVCONFIG devconfig.outSANDISCOVERY ONTCPPORT 1502

In these commands, devconfig.out points to an output file which is used by the Storage Agent to store device configuration information.

The SANDISCOVERY ON option allows Tivoli Storage Manager to assist in the recovery of SAN-attached devices. After you edit the file, save and close it.

We set the TCPPORT to 1502, which matches the LANFREETCPORT setting within the client’s option file (as discussed in 8.9.1, “LAN-free options (used between the client and the Storage Agent)” on page 235 and the LLADDRESS setting used in the DEFINE SERVER command for the Storage Agent (as discussed in 8.8.2, “Setting up server-to-server communication using the command line interface” on page 234).

4. From the DOS prompt in the Storage Agent directory, issue the following command to set up a communication between the Storage Agent and the server (in this case, from SENEGAL to TONGA):

dsmsta setstorageserver myname=senegal_sta mypassword=xxxx myhladdress=9.1.39.89 servername=azov_1 serverpassword=xxxx hladdress=9.1.39.89 lladdress=1500

These values must match the definitions on the Tivoli Storage Manager server which were created in 8.8.2, “Setting up server-to-server communication using the command line interface” on page 234.

This command updates the device configuration output file (devconfig.out) so that it looks similar to that shown in Example 8-12.

Example 8-12 Storage Agent device configuration file

SET STANAME senegal_staSET STAPASSWORD xxxxxxxSET STAHLADDRESS 9.1.39.166DEFINE SERVER azov_1 server password=xxxxxx HLADDRESS=9.1.39.89 LLADDRESS=1500

The Storage Agent option files (dsmsta.opt) is updated with the following:

SERVERNAME AZOV_1

5. Run the Storage Agent (console) in the foreground by issuing the dsmsta command. Example 8-11 on page 241 shows the output of this command.

6. Enter halt from the Storage Agent console to terminate it. Typically, you run the Storage Agent in background (that is, as a Windows service). Use the Windows Services applet to check that the Storage Agent is set for automatic start and to start the Storage Agent, if necessary.

Note: The SANDISCOVERY option is supported beginning with V5.3.


8.11 Enabling LAN-free data movementBefore enabling LAN-free data movement, verify that you have performed all the previous steps in this chapter, which include:

� Configuring SANergy.

� Configuring the SAN disk device to the Tivoli Storage Manager server.

� Defining a policy domain for clients to use for LAN-free data movement to disk.

� Registering a client to under the LAN-free to disk policy domain.

� Configuring server-to-server communication.

� Installing and configuring the backup-archive client. Ensuring that the LAN-based backup is successful.

� Installing and configuring the Storage Agent software. Ensuring that it is running.

You can now proceed with the final step of configuring the LAN-free data movement to disk. You execute these steps on the Tivoli Storage Manager server. This section includes instructions on how to enable LAN-free data movement from the Administration Center and using the command line interface.

8.11.1 Enabling LAN-free from the Administration CenterFrom the Administration Center:

1. From the Work Items list, select Policy Domains and Client Nodes. The Policy Domains screen appears, as shown in Figure 8-56. Select the server on which you configured LAN-free to disk (in this example, TONGA).

Figure 8-56 Policy Domains screen

2. The Policy Domains that belongs to the server appears (Figure 8-57). Select the policy domain that was created to manage the LAN-free to disk data (in this example, LANFREE_DISK).

Figure 8-57 List of Policy Domains


3. The Properties for the policy domain screen appears below the current contents, as shown in Figure 8-58. Expand Client Nodes.

Figure 8-58 LANFREE_DISK Properties.

4. From the list of client nodes, select the client to be configured (in this example, SENEGAL), as shown in Figure 8-59. Select Enable LAN-free Data Movement. Click Go.

Figure 8-59 Client node used for LAN-free to disk use

5. The Welcome screen (Figure 8-60) provides an overview of the process and also lists prerequisites. Click Next.

Figure 8-60 Enable LAN-free data movement Welcome screen

6. The Verify Data Transfer Settings screen appears, as shown in Figure 8-61 on page 245. With these options, you can enable or restrict LAN-free data movement to backups and restores. Take the default that allows both backup and restores to use LAN and LAN-free data transfer. Click Next.


Figure 8-61 Verify Data Transfer Settings screen

7. The Create or Select a Storage Agent screen appears (Figure 8-62). Because a server that corresponds to the Storage Agent has been configured, select Use an existing Storage Agent. From the Select a Storage Agent list, select the one that was created for LAN-free to disk data transfer (in this example, SENEGAL_STA). Click Next.

Figure 8-62 Select an existing Storage Agent

8. On the Select a Storage Pool screen (Figure 8-63 on page 246), select the storage pool that maps to the SAN-attached disk (in this example, SANDISKPOOL). Click Next.


Figure 8-63 Select a Storage Pool screen

9. The Create the Path to the File Library Directories screen appears, as shown in Figure 8-64 on page 247.

Here, you need to enter the fully qualified (UNC) path for the SAN-attached directories. If you defined multiple directories when defining the shared file device class, then you must define the same directories here and separate each with a comma. Specify the host name or address of the MDC server and use the share names as they appear to the Storage Agent, Figure 8-7 on page 212.

In this example, we entered \\9.1.39.168\e$\mydir1,\\9.1.39.168\f$\mydir2.

Be sure to enter in the entire string, even though the window does not display completely in Figure 8-64 on page 247. The address 9.1.39.168 is the TCP/IP address of TONGA, which is the SANergy MDC and owns the SAN-attached disks that were defined. So, for a Storage Agent to able to access these devices over the SAN, drive mapping must be made on the Storage Agent system (in this case, SENEGAL) to the SAN disk directories that are managed by the SANergy MDC. Click Next.

Note: Before proceeding, check the Storage Agent system on which the SAN disk directories are mapped, as shown in Figure 8-7 on page 212.


Figure 8-64 Specify the directories of the SAN-attached disks

10.The Configure Another Storage Pool screen appears, as shown in Figure 8-65. Select No at this time. However, you can select Yes if you wish to create additional Storage Agents. Click Next.

Figure 8-65 Select whether to configure another Storage Agent.

11.The Summary screen appears (Figure 8-66 on page 248). Verify that the information is correct. Select Completing the setup on the client node.


Figure 8-66 The Enable LAN-free Data Movement Summary screen

12.The information about completing the setup on the client node appears, as shown in Figure 8-66. Verify that you have performed all the items listed. If you followed all the steps outlined in this chapter, items one through three should be complete. The next step is to verify the LAN-free data movement. Click Finish.

Figure 8-67 Completing the setup on the client node overview


8.11.2 Enabling LAN-free with the command line interfaceUsing the command line interface, you enable LAN-free data movement as follows:

1. Use the DATAWRITEPATH and DATAREADPATH parameters to enable or restrict LAN-free data transfer for a node. These parameters are used with the DEFINE NODE or UPDATE NODE commands to enable or restrict LAN-free data movement to backups and restores for a given node. Allow both the backup and restores to use LAN-free data transfer (which is the default) by issuing the following:

UPDATE NODE SENEGAL DATAWRITEPATH=ANY DATAREADPATH=ANY

2. Define the path for the SAN-attached disk devices to the Storage Agent.

Use the DEFINE PATH command as follows:

DEFINE PATH SENEGAL_STA SANDISK1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=SANDISK DEVICE=FILE DIRECTORY=\\9.1.39.168\e$\mydir1,\\9.1.39.168\f$\mydir2

For the DIRECTORY parameter, enter the fully qualified (UNC) path for the SAN-attached directories. If you defined multiple directories when defining the shared file device class, then you must define the same directories here and separate each with a comma. Specify the host name or address of the MDC server and use the share names as they appear to the Storage Agent, Figure 8-7 on page 212.

We entered \\9.1.39.168\e$\mydir1,\\9.1.39.168\f$\mydir2.

The address 9.1.39.168 is the TCP/IP address of TONGA which is the SANergy MDC and owns the SAN-attached disks that were defined. So, for a Storage Agent to able to access these devices over the SAN, drive mapping must be made on the Storage Agent system (in this case, SENEGAL) to the SAN disk directories that are sitting on the SANergy MDC. Define a path from SENEGAL_STA, the Storage Agent to the file drive, to SANDISK1 in the file library, SANDISK.

If the path is defined successfully, you see a message similar to the following:

ANR1720I A path from SENEGAL_STA to SANDISK SANDISK1 has been defined

8.12 Verifying the LAN-free pathNow that you have configured the server, client, and Storage Agent systems, you can check the setup. In Tivoli Storage Manager V5.3, verification is easier with the new VALIDATE LANFREE command. This command shows whether a client node with a specific Storage Agent is capable of LAN-fee data movement. The command looks at the policy information, storage pool, and path definitions that are associated with the specified client node and Storage Agent to determine if the destination is LAN-free capable. This information is useful when troubleshooting a suspected LAN-free configuration problem.

The parameters of this command are:

� node_name (required), which is the name of the node to evaluate. � stgagent_name (required), which is the name of the Storage Agent to evaluate.

Note: Before proceeding, check on the Storage Agent system that the SAN disk directories are mapped, as shown in Figure 8-7 on page 212.

Note: The VALIDATE LANFREE command replaces the undocumented V5.2 SHOW LANFREE command.


Example 8-13 shows the output from the VALIDATE LANFREE command in our setup, which was run on the Tivoli Storage Manager server, TONGA, specifying the client and Storage Agent on SENEGAL.

Example 8-13 VALIDATE LANFREE command output

tsm: TONGA_1>validate lanfree senegal senegal_sta ANR0387I Evaluating node SENEGAL using storage agent SENEGAL_STA for LAN-free data movement. Node Name : SENEGAL Storage Agent : SENEGAL_STA Operation : BACKUPMgmt Class Name : STANDARDDestination Name : SANDISKPOOLLAN-Free capable? : Yes Explanation :

Node Name : SENEGAL Storage Agent : SENEGAL_STA Operation : ARCHIVEMgmt Class Name : STANDARDDestination Name : SANDISKPOOLLAN-Free capable? : Yes Explanation :

ANR1706I Ping for server 'SENEGAL_STA' was able to establish a connection.ANR0388I Node SENEGAL using storage agent SENEGAL_STA has 2 storage pools capable of LAN-free data movement and 0 storage pools not capable of LAN-free data movement.

The output shows that the node SENEGAL using Storage Agent SENEGAL_STA has two storage pools that are capable of LAN-free data movement. If there were other storage pools that are not capable of LAN-free data movement, they would be shown as LAN-Free capable? : No.

Notice also that the message that states that the server was able to establish a connection with the Storage Agent, SENEGAL_STA, using ping. This information tells us that the PING SERVER command was issued by the Tivoli Storage Manager server and was able to successfully communicate with the Storage Agent.

If the server cannot ping the Storage Agent successfully, the following error appears in the VALIDATE LANFREE output:

ANR1705W Ping for server 'SENEGAL_STA' was not able to establish a connection.

To resolve this issue, first verify that the Storage Agent service/daemon is running on the Storage Agent system. If it is running, stop and restart it to be sure that it remains running. Issue the PING SERVER command from the Tivoli Storage Manager server to test the connection with the Storage Agent. For example:

PING SERVER senegal_sta

If the server is still unable to establish a connection with the Storage Agent, verify that the following TCP/IP port settings match:

� LLADDRESS

On the Tivoli Storage Manager server, check the LLADDRESS that is used for the Storage Agent server definition. Issue QUERY SERVER storage_agent_name F=D and specify the name of your Storage Agent. The specified port is opened to communicate with the Storage Agent, in this case.


� TCPPORT

On the Storage Agent machine, edit the option file (dsmsta.opt) to verify the TCPPORT value. The specified port is opened to communicate with the server and client.

� LANFREETCPPORT

On the client machine, edit the client options file to verify the LANFREETCPPORT option. The specified port is opened to communicate with the storage age. LANFREETCPPORT is used only when the LANFREECOMMMETHOD is TCPIP. If a shared memory or named pipes is used, then disregard this option.

After you have verified that a LAN-free path is available, you can backup a client to test the LAN-free connection. When you start the backup, you can see that the data is being transferred correctly over the SAN from the following:

� If using the Backup-Archive Client interface, the Detailed Status Report should reveal the number of LAN-free bytes that have been transferred, as shown in Figure 8-68. This line is grayed out for a traditional LAN-based backup.

Figure 8-68 The Backup-Archive Detailed Status Report that shows LAN-free bytes

� If using the Backup-Archive Client command line interface, it shows the LanFree data bytes, as part of the backup/restore status report, as shown in Example 8-14. This line does not appear on a traditional LAN-based backup.

Example 8-14 Backup-Archive client command line interface that shows LAN-free bytes

Total number of objects inspected: 6Total number of objects backed up: 6Total number of objects updated: 0Total number of objects rebound: 0Total number of objects deleted: 0Total number of objects expired: 0Total number of objects failed: 0Total number of bytes transferred: 500.06 MBLanFree data bytes: 500.00 MB

� On the Tivoli Storage Manager server to confirm that the data is being transferred using LAN-free data movement, look for activity log messages similar to that shown in Example 8-15 on page 252. You can see the sessions for the client node and the Storage Agent. On the server, a volume is mounted to receive the backup data. This volume is actually a file on the SANergy disk that is defined in the device class. Because we are using a device class of FILE, Tivoli Storage Manager handles it similar to a tape drive (that is, mounting the volume in the file drive SANDISK1, in the file library, SANDISK).


Example 8-15 Tivoli Storage Manager server activity log excerpt

ANR0406I Session 23 started for node SENEGAL (WinNT) (Tcp/IpSenegal.almaden.ibm.com(2437)).ANR0408I Session 24 started for server SENEGAL_STA (Windows) (Tcp/Ip) forstorage agent.ANR0415I Session 24 proxied by SENEGAL_STA started for node SENEGAL.ANR0408I Session 25 started for server SENEGAL_STA (Windows) (Tcp/Ip) forlibrary sharing.ANR0409I Session 25 ended for server SENEGAL_STA (Windows).ANR0408I Session 26 started for server SENEGAL_STA (Windows) (Tcp/Ip) forlibrary sharing.ANR8493I FILE volume F:\MYDIR2\00000000.BFS mounted in drive SANDISK1 (FILE) inlibrary SANDISK.ANR8340I FILE volume F:\MYDIR2\00000000.BFS mounted.ANR0409I Session 26 ended for server SENEGAL_STA (Windows).ANR0511I Session 24 opened output volume F:\MYDIR2\00000000.BFS.ANR0408I Session 27 started for server SENEGAL_STA (Windows) (Tcp/Ip) forlibrary sharing.ANR8468I FILE volume F:\MYDIR2\00000000.BFS dismounted from drive SANDISK1(FILE) in library SANDISK.ANR0409I Session 27 ended for server SENEGAL_STA (Windows).ANR0514I Session 24 closed volume F:\MYDIR2\00000000.BFS.ANR0408I Session 28 started for server SENEGAL_STA (Windows) (Tcp/Ip) forlibrary sharing.ANR0409I Session 28 ended for server SENEGAL_STA (Windows).ANR0403I Session 23 ended for node SENEGAL (WinNT).ANR0403I Session 24 ended for node SENEGAL (WinNT).

� You can use the QUERY MOUNT command to show that the volume is mounted.

� You can see the volume that was used for the LAN-free backup using the QUERY VOLUME command, as shown in Example 8-16. The size of the volume is defined by the capacity specified when we created the SANDISK device class, which was 500MB (see Figure 8-11 on page 215).

Example 8-16 Volume in LAN-free storage pool

tsm: TONGA_1>q volume

Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status------------------------ ----------- ---------- --------- ----- --------F:\MYDIR2\00000000.BFS SANDISKPOOL SANDISK 5,120.0 9.8 Filling

� After the backup is complete, you can use the QUERY CONTENTS command on the volume, as shown in Example 8-16.

Example 8-17 Display file volume contents

tsm: TONGA_1>q con f:\mydir2\00000002.bfs

Node Name Type Filespace FSID Client's Name for File Name--------------- ---- ---------- ---- -------------------------------------SENEGAL Bkup \\senegal- 6 \ TSM_IMAGES \c$SENEGAL Bkup \\senegal- 6 \TSM_IMAGES\ JUNK.TXT \c$SENEGAL Bkup \\senegal- 6 \TSM_IMAGES\ IMAGE.ZIP \c$


Chapter 9. Tivoli Storage Manager SAN Discovery

This chapter contains information about the new Tivoli Storage Manager SAN Discovery feature. It shows how to enable the new functions and what is required to respond to changing SAN environments. This chapter discusses the following topics:

� SAN device mapping� New or updated Tivoli Storage Manager commands� Platform support and usage instructions� Example of the automatic device mapping feature

9


9.1 SAN device mappingSAN environments can change dramatically due to device or cabling changes in the environment. In particular, device IDs that are assigned by the SAN might change due to bus resets or other environmental changes to the SAN. For example, consider a Linux Tivoli Storage Manager server that is attached to a tape library with ten drives. If a drive is offline when the server restarts, all the subsequent drives change their device names. This change causes static drive path definitions in Tivoli Storage Manager to be misconfigured and these drives are unusable. The administrator needs to update the devices manually in the Tivoli Storage Manager paths to restore normal operation.

To avoid the need for manual modification, there is an accurate SAN device mapping feature available in Tivoli Storage Manager V5.3. This mapping process involves two steps:

1. Detecting that the device has changed.

This detection is accomplished by recording the device’s serial number, manufacturer, and World Wide Node Name (WWNN), if it exists, in the Tivoli Storage Manager database. Whenever a device is opened, its identity is verified. This feature is available on Windows, AIX, Sun, and Linux servers as well as Storage Agents. This feature has been implemented in the Tivoli Storage Manager V5.2 for Windows.

2. Reconciling the device definitions (paths) dynamically when changes are detected.

This reconciliation requires Tivoli Storage Manager to discover devices in the SAN environment.

Important: Depending on the server platform, this step can require the administrator to manually update the device’s special files in the operating system before Tivoli Storage Manager can detect the new path to the device.

Note: A commonly used workaround for device remapping was to use persistent binding features that are provided by the Fibre Channel HBA. Tivoli Storage Manager SAN device mapping offers a better solution because:

� Specific HBA vendor’s utility programs are required to set up persistent binding. These utilities change often, which can create complexity and confusion between users and support teams. SAN device mapping offers a consistent solution across multiple devices.

� For some applications, the persistent binding is incompatible with the disk failover capabilities for redundant dual-active controller (RDAC) and dynamic multipathing (DMP). To use Tivoli Storage Manager in a LAN-free environment without SAN device mapping, you must use dedicated HBAs to the tape or go without redundancy to their disks, which is not desirable.


9.2 New or updated Tivoli Storage Manager commandsThis section provides information about the new or updated commands in Tivoli Storage Manager V5.3 for implementing SAN device mapping.

9.2.1 SANDISCOVERY server optionTo activate SAN device mapping, set the SANDISCOVERY option to ON in the dsmserv.opt file:

SANDISCOVERY ON

This setting is the default for Windows platforms. For all other platforms, you must set this option in the server options file. To activate SAN Discovery in a running Tivoli Storage Manager instance, use the following setting:

SETOPT SANDISCOVERY ON

9.2.2 QUERY SAN commandThe QUERY SAN command shows the devices that are discovered on the SAN. Example 9-1 shows a sample output from our test environment.

Example 9-1 Output of QUERY SAN command

Device Vendor Product Serial Number DeviceType-------- -------- ---------------- ---------------- ------------------DRIVE IBM ULT3580-TD2 1110177214 /dev/rmt0DRIVE IBM ULT3580-TD2 1110176223 /dev/rmt1LIBRARY IBM ULT3582-TL 0000013108231000 /dev/smc0

To see the details for each device, issue the QUERY SAN F=D command to receive the output as shown in Example 9-2.

Example 9-2 Detailed QUERY SAN output

Device Type: DRIVE Vendor: IBM Product: ULT3580-TD2Serial Number: 1110177214 Device: /dev/rmt0 Data Mover: No Node WWN: 500308C140067006 Port WWN: 500308C140467006 LUN: 0 SCSI Port: 0 SCSI Bus: 0 SCSI Target: 0

Device Type: DRIVE Vendor: IBM Product: ULT3580-TD2Serial Number: 1110176223 Device: /dev/rmt1 Data Mover: No Node WWN: 500308C140067003 Port WWN: 500308C140467003 LUN: 0 SCSI Port: 0

Chapter 9. Tivoli Storage Manager SAN Discovery 255

SCSI Bus: 0 SCSI Target: 0

Device Type: LIBRARY Vendor: IBM Product: ULT3582-TLSerial Number: 0000013108231000 Device: /dev/smc0 Data Mover: No Node WWN: 500308C140067003 Port WWN: 500308C140467003 LUN: 0 SCSI Port: 0 SCSI Bus: 0 SCSI Target: 0

9.2.3 DEFINE LIBRARY commandThe SERIAL parameter is new for the DEFINE LIBRARY command. The relevant syntax for this parameter is as follows:

SERial=AUTODetectDEFine LIBRary—lib_name----+--------------------------+ ------>

SERial=serial_numberSERial=AUTODetect

If a serial number is entered here, it is recorded in the Tivoli Storage Manager server database. It is not validated until the DEFINE PATH command is processed.

When DEFine PATH device=device_name AUTODetect=No is issued (the default value for the AUTODETECT parameter), Tivoli Storage Manager server attempts to open the library and one of the following occurs:

� If the device open fails, the DEFINE PATH command fails.

� If the open is successful but the library does not support reporting the serial number, the Tivoli Storage Manager server does not validate the library serial number entered.

� If the open is successful and the device returns the library serial number, it is compared to the serial number that is in the Tivoli Storage Manager database from the DEFINE LIBRARY command. If they do not match, this error message is issued:

ANR8957E DEFINE PATH: Autodectect is OFF and the serial number reported by the library did not match the serial number in the library definition.

You can re-issue the DEFINE PATH command with AUTODetect set to yes. The serial number in the database is overridden with the correct serial number from the library as follows:

ANR8953I: Library lib_name with serial number xxxx is updated with the newly discovered serial number yyyyyy.

If the device open is successful and the device returns the library serial number, update the database with this value for the serial number, regardless of what was previously in the database.


9.2.4 DEFINE DRIVE serial numberNew parameters for the DEFINE DRIVE command are SERIAL and ELEMENT. The syntax for these parameters is:

SERial=AUTODetect ELEMent=AUTODetectDEFine-Drive---lib_name---drive_name---+--------------------+---------------------------+->

SERial=serial_number ELEMent=addressSERial=AUTODetect ELEMent=AUTODect

If only the serial number is specified with the DEFINE DRIVE command, it is recorded in the server database. It is not validated until the DEFINE PATH command is issued.

When DEFine PATH device=device_name AUTODetect=no is issued, Tivoli Storage Manager attempts to open the drive and one of the following occurs:


� If the open is successful but the drive does not support reporting the serial number, the Tivoli Storage Manager server does not validate drive serial number.

� If the open is successful and the device returns the drive serial number, it is compared to the serial number in the database. If they do not match, this error message is issued:

ANR8958E: DEFINE PATH: Autodectect is OFF and the serial number reported by the drive did not match the serial number in the drive definition.

You can re-issue DEFINE PATH command with AUTODetect set to yes. Now the serial number and element number are overridden with the correct serial number and element number from the drive, as shown in the following.

ANR8955I: Drive drive_name in library lib_name with serial number xxxx is updated with the newly discovered serial number yyyyyyy.

9.2.5 DEFINE DRIVE element numberYou can also specify the element number on the DEFINE DRIVE command.

The syntax for this command is:

SERial=AUTODetect ELEMent=AUTODetectDEFine-Drive---lib_name---drive_name---+--------------------------+---------------------+-?

SERial=serial_number ELEMent=addressSERial=AUTODetect ELEMent=AUTODect

If only the drive element number is entered here, it is recorded in the server database. It is not validated until the DEFINE PATH command is issued. The serial number is detected automatically when the DEFINE PATH command is issued.

When DEFine PATH device=device_name AUTODetect=no is issued, Tivoli Storage Manager attempts to open the drive and one of the following occurs:


� If the open is successful but the drive does not support reporting the serial number, the Tivoli Storage Manager server does not validate the drive serial number and element number.

Note: Element number detection requires that the library supports the SCSI Read Element Status with DVCID (device ID) bit set to one to get the serial number/element number map. Check your vendor documentation to see if DVCID is supported. If DVCID is not supported by the library, you must enter the drive element number with the DEFINE DRIVE command.


� If the open is successful and the device returns the drive serial number, it is used to get the element number from the library’s drive serial number and element number map and is compared to the element number in the database. If they do not match, this error message is issued:

ANR8419E: DEFINE PATH: The drive or element conflicts with an existing drive in library SCSILIB.

You can re-issue DEFINE PATH with AUTODetect set to yes. The serial number and element number in the database are overridden with the correct serial number and element number from the drive, as in the following:

ANR8955I: Drive www in library xxx with serial number yyyyyy is updated with the newly discovered serial number zzzzzz .

9.2.6 SAN Discovery error messagesThe following error messages can occur in Tivoli Storage Manager in conjunction with the SAN Discovery feature:

� ANR1786W HBAAPI not able to get adapter name.

HBA driver problem.

� ANR1787W Not able to open adapter adapterName.

HBA driver problem.

� ANR1788W Not able to get the adapter attributes for adapterName.

HBA driver problem.

� ANR1789W Get HBA target mapping failed.

This is the most commonly occurred error, because the HBA driver has to send commands to all of the devices on the SAN. If any device returns an illegal request bad status, the HBA driver might quit SAN Discovery with this error.

Known issues only Windows systems are:

– The Qlogic HBA driver on Windows with IBM SAN Data Gateway 2108 (this hardware is no longer supported by IBM or ADIC) can see this issue.

– For IBM tape devices, confirm that the latest firmware is installed. Firmware before 4772 for IBM 3580 tape devices cause this problem with QLogic HBAAPI.

Note: If AUTODETECT is set to Yes with the DEFINE PATH command, the serial number and element number obtained in real time is loaded into the database regardless of what was previously in the database from the DEFINE DRIVE or UPDATE DRIVE commands. For that reason, you should use the autodetect parameter only when you define the first path to the drive on the Library Manager. All subsequent paths to the same drive do not require this parameter. Otherwise, you could mistakenly overwrite serial and element number with an unwanted value when pointing to the wrong device.


9.2.7 New Tivoli Storage Manager messagesThe following messages are associated with SAN device discovery and device detection on Tivoli Storage Manager.

ANR8953I: Library library_name with serial number xxxxx is updated with the newly discovered serial number yyyyy.

ANR8955I: Drive drive_name in library library_name with serial number xxxxx is updated with the newly discovered serial number yyyyy.

ANR8957E: DEFINE PATH: Autodectect is OFF and the serial number reported by the library did not match the serial number in the library definition.

ANR8958E: DEFINE PATH: Autodectect is OFF and the serial number reported by the drive did not match the serial number in the drive definition.

ANR8963E: We were not able to find the path to match the serial number defined for library library_name and drive_name.

ANR8964W: We were not able to update the path in the database table library_name and drive drive_name.

ANR8965W: The server is unable to automatically determine the serial number for the device.

ANR8967E: The drive serial conflicts with an existing drive in library library_name.

9.3 Platform support and usage instructionsSAN device mapping is available on all Tivoli Storage Manager server platforms except HP, zLinux, and Windows 64bit.

Before setting SANDISCOVERY ON for a non-Windows platform, confirm that the proper HBA driver is installed. You can find a table that shows the platform and HBA driver levels that required for SAN device mapping at:


9.3.1 Information for Windows systemsSAN device mapping is supported on Windows 2000 and Windows 2003 32-bit with QLogic and Emulex HBAs.

The SAN Discovery feature is enabled by default in the server options file (dsmserv.opt).

If you are using a QLA2200 HBA, be sure to indicate the correct HBA model when getting the QLogic HBA device driver.

If the SAN has any mature, non-supported gateways (such as the SAN Data Gateway 2108), SAN Discovery might not work. You need to either zone out the gateway or replace it with a newer, supported gateway.

With the Windows plug-and-play mechanism, the registry is updated automatically and the device name might be changed without the need to reboot the machine or reload the driver.

Hint: Search on SAN Device Mapping.



SAN device mapping is capable of detecting the changes when it accesses the tape devices during the server start or normal operation. The correct device names are updated in the Tivoli Storage Manager database.

9.3.2 Information for AIX systemsThe following information is relevant to AIX systems:

� SAN device mapping is supported on AIX V5.2 or higher.

� The SANDISCOVERY option defaults to OFF.

� If you enable SANDISCOVERY at a version that precedes AIX V5.2, you get the following message:

ANR1793W TSM SAN Discovery is not supported on this platform or this version of OS.

� You need to install the HBAAPI library from the AIX media. The file name is libHBAAPI.a and must reside in the /usr/lib directory. If it is not installed or is down a level, you get the following errors:

ANR8226E: Error detecting version of HBA-API library

ANR8227E: Fileset devices.common.IBM.fc.hba-api is not at the required level.AIX V5.2 - need 5.2.0.50AIX V5.3 - need 5.3.0.10

� When devices in the SAN are changed, the HBA gets the most up-to-date configuration information as a result of the Registered State Change Notification (RSCN).

� For IBM devices:

Issue the cfgmgr command to get the new configuration and the special file name for IBM tape devices. New devices are added. Special file names are /dev/rmtx and /dev/smcx.

� For Tivoli Storage Manager devices, you can:

– Use smitty → devices → Tivoli Storage Manager devices → remove all defined devices → discover devices supported by Tivoli Storage Manager.

– Reinstall the Tivoli Storage Manager device driver.

9.3.3 Information for Linux systemsThe following information is relevant to Linux systems:

� Supported HBAs are QLogic and Emulex.


� You need to ensure that the HBA driver is at the supported level before setting SANDISCOVERY to ON.


� For IBM devices:

Issue the IBMtapeconfig command to get the new configuration and the special device file names for IBM tape devices. New devices are added. Special file names are /dev/IBMtapex and /dev/IBMchangerx.

� For Tivoli Storage Manager devices, with the new Linux pass-through device driver for Tivoli Storage Manager devices, you have to reload the HBA driver and reload the generic driver to get all the current special device file names. After that, run the autoconf script in the /opt/tivoli/tsm/devices/bin directory so that the Tivoli Storage Manager device driver


can create the lbinfo and mtinfo files in the /dev/tsmscsi directory. These files are used by the SAN device mapping code. Special device file names are /dev/tsmscsi/mtx and /dev/tsmscsi/lbx.

9.3.4 Information for Solaris systemsThe following information is relevant to Solaris systems:

� Supported HBAs are Qlogic and Emulex.


� Ensure that the HBA driver is at the supported level before setting SANDISCOVERY to ON.

� Before turning on SANDISCOVERY, do the following before device names for Tivoli Storage Manager devices can be determined:

a. Modify the /usr/kernel/drv/mt.conf and /usr/kernel/drv/lb.conf files to add the following:

mt.conf: name="mt" parent="pseudo" instance=16383lb.conf name="lb" parent="pseudo" instance=16383

b. Issue the autoconf command.

c. Ensure that the virtual device special files are in the following directory:

/devices/pseudo/mt@16383:tsmmtctl and /devices/pseudo/lb@16383:tsmlbctl

d. Issue the sync sync command.

e. Reboot the system.


� For IBM devices, issue the rem_drv IBMtape and add_drv IBMtape commands. New devices are added. Special file names are /dev/rmt/xst and /dev/rmt/xsmc.

� For Tivoli Storage Manager devices, issue the following commands:

rem_drv lbadd_drv lbrem_drv mtadd_drv mt

As an alternative to unloading and reloading the device drivers, you can reinstall the IBM device driver or the Tivoli Storage Manager device driver as appropriate.

9.4 Example of the automatic device mapping featureAs an example of the automatic device mapping feature, this section shows how to define paths to a Library Client without knowing the device names on the remote machine.

The SAN device mapping feature eases the task of defining drive paths to Tivoli Storage Manager Library Clients and Storage Agents. Prior to Tivoli Storage Manager V5.3, you had to know the exact drive device name on each participating Library Client and Storage Agent. If something in the SAN changed, it required a lot of work to update all drive paths on the Library Manager.

When you have enabled the SANDISCOVERY parameter on the Library Clients and the Storage Agents, defining paths is easy. Just define a generic string as the device name, and


upon first access, the Library Client recognizes the corresponding device name and updates the path accordingly.

In this example, AZOV is the Library Manager, and TONGA is the Library Client, as shown in Figure 9-1.

Figure 9-1 Library Manager and client

In Example 9-3, on the Library Manager AZOV, we defined two paths to the Library Client TONGA. The paths were to the drives DRIVE1 and DRIVE2 in the library 3582.

When defining paths, you cannot omit the device parameter, because it is detected automatically. As an example we used abc, which is not a valid device name.

Example 9-3 Define the paths for the Library Client

tsm: AZOV_1>q path

Source Name Source Type Destination Destination On-Line Name Type----------- ----------- ----------- ----------- -------AZOV_1 SERVER 3582 LIBRARY YesAZOV_1 SERVER DRIVE1 DRIVE YesAZOV_1 SERVER DRIVE2 DRIVE Yes

tsm: AZOV_1>def path tonga_1 drive1 libr=3582 srct=server destt=drive devi=abcANR1720I A path from TONGA_1 to 3582 DRIVE1 has been defined.

tsm: AZOV_1>def path tonga_1 drive2 libr=3582 srct=server destt=drive devi=abc

Note: You do not need the autodetect parameter when defining drives to a Library Client, because the serial number is already present in the Tivoli Storage Manager database. The automatic update to the path to point to the right device is always done when SANDISCOVERY is set to ON and in a supported environment.

TONGA Windows 2000 ITSM Library Client

Data Flow

Tape Library35822xLT02 drives

Library Control

SAN

AZ0V AIX 5.3

Tivoli Storage Manager Library Manager

LAN

server-to-server communication

Data Flow


ANR1720I A path from TONGA_1 to 3582 DRIVE2 has been defined.

tsm: AZOV_1>q path

Source Name Source Type Destination Destination On-Line Name Type----------- ----------- ----------- ----------- -------AZOV_1 SERVER 3582 LIBRARY YesAZOV_1 SERVER DRIVE1 DRIVE YesAZOV_1 SERVER DRIVE2 DRIVE YesTONGA_1 SERVER DRIVE1 DRIVE YesTONGA_1 SERVER DRIVE2 DRIVE Yes

tsm: AZOV_1>q path f=d

Source Name: TONGA_1 Source Type: SERVER Destination Name: DRIVE1 Destination Type: DRIVE Library: 3582 Node Name: Device: abc External Manager: LUN: Initiator: 0 Directory: On-Line: Yes

Last Update by (administrator): ADMIN Last Update Date/Time: 03/24/05 13:15:46

Source Name: TONGA_1 Source Type: SERVER Destination Name: DRIVE2 Destination Type: DRIVE Library: 3582 Node Name: Device: abc External Manager: LUN: Initiator: 0 Directory: On-Line: YesLast Update by (administrator): ADMIN Last Update Date/Time: 03/24/05 13:15:57

tsm: AZOV_1>

When we started an operation on the Library Client (such as a database backup), it detected that the path information that was retrieved from the Library Manager was not correct. It started SAN Discovery and, based on the drive serial number, it found a valid path to the drive. It then updated the new (and this time correct) path information remotely at the Library Manager. Based on the accurate SAN device mapping, it found the drive and performed the requested process, as shown in Example 9-4 on page 264.


Example 9-4 Database backup on the Library Client

tsm: TONGA_1>ba db t=f s=y devc=lto2ANR2280I Full database backup started as process 28.ANS8003I Process number 28 started.

tsm: TONGA_1>q ac03/16/2005 11:40:02 ANR2017I Administrator ADMIN issued command: BACKUP DB t=f s=y devc=lto2c (SESSION: 1681)03/16/2005 11:40:02 ANR0984I Process 28 for DATABASE BACKUP started in the BACKGROUND at 11:40:02. (SESSION: 1681, PROCESS: 28)03/16/2005 11:40:02 ANR2280I Full database backup started as process 28. (SESSION: 1681, PROCESS: 28)03/16/2005 11:40:02 ANR0408I Session 1684 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 1681)03/16/2005 11:40:02 ANR0409I Session 1684 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 1681)03/16/2005 11:40:02 ANR0408I Session 1685 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 1681)03/16/2005 11:40:34 ANR0408I Session 1686 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 1681)03/16/2005 11:40:34 ANR0409I Session 1686 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 1681)03/16/2005 11:40:34 ANR8974I Found new path for TONGA_1 and target name DRIVE2 old path abc new path \\.\Tape1. Path information will be updated remotely. (SESSION: 1681)03/16/2005 11:40:34 ANR0409I Session 1685 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 1681)03/16/2005 11:40:34 ANR8337I LTO volume 034AKK mounted in drive DRIVE2 (\\.\Tape1). (SESSION: 1681)03/16/2005 11:40:34 ANR0511I Session 1681 opened output volume 034AKK. (SESSION: 1681)03/16/2005 11:40:40 ANR0408I Session 1687 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 1681)03/16/2005 11:40:40 ANR0409I Session 1687 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 1681)03/16/2005 11:40:40 ANR0408I Session 1689 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 1689)03/16/2005 11:40:40 ANR0408I Session 1688 started for server AZOV_1 (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 1681)03/16/2005 11:40:40 ANR0409I Session 1688 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 1681)03/16/2005 11:40:40 ANR4550I Full database backup (process 28) complete, 830 pages copied. (SESSION: 1681, PROCESS: 28)03/16/2005 11:40:40 ANR0985I Process 28 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 11:40:40. (SESSION: 1681, PROCESS: 28)03/16/2005 11:40:47 ANR8336I Verifying label of LTO volume 034AKK in drive DRIVE2 (\\.\Tape1). (SESSION: 1681)03/16/2005 11:40:47 ANR8468I LTO volume 034AKK dismounted from drive DRIVE2 (\\.\Tape1) in library 3582. (SESSION: 1681)03/16/2005 11:40:47 ANR0409I Session 1689 ended for server AZOV_1 (AIX-RS/6000). (SESSION: 1689)


When we queried the path information, we saw the updated information, as shown in Example 9-5. Note that the path to DRIVE1 was not updated because it was not used in this operation. However, the path to DRIVE2 reflects the SAN Discovery and the correct device name.

Example 9-5 Path definition on the Library Manager

tsm: AZOV_1>q path f=d

Source Name: TONGA_1 Source Type: SERVER Destination Name: DRIVE1 Destination Type: DRIVE Library: 3582 Node Name: Device: abc External Manager: LUN: Initiator: 0 Directory: On-Line: YesLast Update by (administrator): ADMIN Last Update Date/Time: 03/24/05 13:15:46

Source Name: TONGA_1 Source Type: SERVER Destination Name: DRIVE2 Destination Type: DRIVE Library: 3582 Node Name: Device: \\.\Tape1 External Manager: LUN: Initiator: 0 Directory: On-Line: YesLast Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 03/24/05 15:17:17

tsm: AZOV_1>

Restriction: With SANDISCOVERY set to ON, Tivoli Storage Manager tries to find an alternate path to a device whenever the open of a device fails. In order to find an alternative path, the operating system might be required to update the special device file names, which is, in most cases, not an automatic process. Tivoli Storage Manager is limited to seeing what the operating system reports. However, it frees you from the task of updating paths to point to the right device.



Chapter 10. Server-free data movement

This chapter describes server-free backup and restore and shows how to implement it. It discusses the following topics:

� Overview of server-free data movement� Requirements for server-free data movement� Server-free data movement in our lab environment

Server-free data movement uses the SCSI-3 extended copy command to do full-volume backup and restore. It provides the following advantages:

� Reduces Tivoli Storage Manager client and server processor use.� Eliminates almost all data movement on the LAN.� Improves performance for data movement operations.� Allows the server to handle more concurrent client connections and server operations.

10

Note: The information in this chapter is taken from Tivoli Storage Manager Version 5.1 Technical Guide, SG24-6554. Figures and examples might not match exactly later versions of Tivoli Storage Manager.


10.1 Overview of server-free data movementTivoli Storage Manager Version 5 Release 1 with PTF 5.1.1 introduced server-free data movement. The feature is currently only available with a Windows 2000 client and Windows server platform.

To introduce server-free data movement, let us first look at Tivoli Storage Manager’s image backup feature. Image backup is available for the AIX, HP, Sun, Windows 2000, and Windows 2000 client platforms. Image backup is performed via the Logical Volume Storage Agent (LVSA), which is capable of taking a snapshot of the volume while it is online. Figure 10-1 shows the data flow for image backup.

Figure 10-1 Image backup

This image backup is a block-by-block copy of the data. Optionally, only occupied blocks can be copied. If the snapshot option is used (rather than static), then any blocks which change during the backup process are first kept unaltered in an Original Block File. In this way, the client is able to send a consistent image of a volume as it was at the start of the snapshot process to the Tivoli Storage Manager server.

Server-free data movement is simply a special form of standard Windows 2000 image backup. The Storage Agent used in LAN-free backups is no longer used for this functionality. Figure 10-2 on page 269 shows the data flow for server-free data movement.




Client

LVSA

Tivoli Storage Manager Clientmanageddisk volume

Original BlocksFile (OBF)


Figure 10-2 Server-free backups

The data movement is actually done by a SAN Data Gateway (SDG) or similar device on the SAN. If snapshot is being used, then an Original Block File (OBF) file is created to hold the original blocks if any are changed during the backup. This OBF is sent to the server with the image, which contains any changes made during the backup. On restore, it is the client’s job to merge the restored image with the blocks in the OBF to reproduce the volume as it was at the start of the snapshot backup. Thus, both the Tivoli Storage Manager client and server machines do not have to read and write the data at all. The Tivoli Storage Manager server sends commands to the SDG device to tell it which blocks to move from which SAN-attached disk to which SAN-attached tape device.

Server-free data movement provides a way to back up and restore large volumes of data between client-owned disks and storage devices using a method that considerably reduces overhead on the Tivoli Storage Manager server and the Tivoli Storage Manager client. Remember that only volume images and not individual files can be moved by server-free data movement. It minimizes data transfer on the LAN. The data is transferred block-by-block rather than via file I/O. Both Raw and NTFS volumes can be backed up using server-free data movement but not FAT volumes.

Data that has been backed up using server-free data movement can be restored over a server-free path, over a LAN-free path, or over the LAN itself.

Important: It is worth pointing out that although many references are made to a Data Mover or data mover device in server-free backups, the data is not actually moved per se but is actually copied from the source to the target location. After a backup has completed using server-free data movement, the original data remains on the client disk.


LAN

Tivoli Storage Manager Servermanagedtape library

SAN


Client

LVSA

Data Mover


Chapter 10. Server-free data movement 269

All data movement is out board of the client machine. In this way, data is copied directly from the SAN-attached Tivoli Storage Manager client disk to the SAN-attached tape drive via the SAN Data Gateway data mover. No Storage Agent is involved in the data movement as in LAN-free backups. It is important to realize that this type of backup does not bypass the Tivoli Storage Manager completely. The Tivoli Storage Manager server discovers devices in the SAN, ensures that all the required paths exist, transforms extents to xcopy commands, mounts and positions the tape, records the information about the backup/restore in its database, and so forth. The metadata is written via the traditional LAN path.

Notice that the client data is written directly from SAN-attached disk to SAN-attached tape via the SAN Data Gateway data mover. Metadata goes to the Tivoli Storage Manager server via the LAN path. However, the client machine (application server) no longer has to read the data from disk and write it to the SAN-attached tape as done previously on LAN-free backups. In this way, the data movement is application server-free.

The impact on application servers is minimized with server-free data movement. It reduces both Tivoli Storage Manager client and server processor use. The use of a SCSI-3 EXTENDED COPY command causes data to be transferred directly between devices over the SAN or SCSI bus.

The SCSI-3 command is issued and initiated by the Tivoli Storage Manager server and carried out by the data mover device that exists on the SAN. The Tivoli Storage Manager client builds the extent lists and sends them to the Tivoli Storage Manager server which controls the conversation with the data mover. The data mover device is responsible for moving the data either from a SAN-attached client-owned disk to a SAN-attached tape drive (backup), or from a SAN-attached tape drive to a SAN-attached client-owned disk (restore).The data mover device must support the SCSI-3 EXTENDED COPY command, which conforms to the ANSI T10 SPC-2 standard. For a current list of supported data mover devices, site:

http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

Search on server-free and select the link entitled Server-Free Data Movement Information.

The data mover device can be anywhere in the SAN, but it has to be able to address the LUNs for both the disk and tape devices that it is moving data between. It has to be able to see the LUNs in the same way that the Tivoli Storage Manager server and client see them. The SAN-attached disk must be able to respond to a query for its serial number or WWN so that the Tivoli Storage Manager server can verify that it is sending data to the correct device. Both SCSI and fibre connectivity are supported.

The Tivoli Storage Manager server is able to handle more concurrent client connections because it is not copying data. Similarly, the Tivoli Storage Manager client is able handle more application load because cycles are not needed to send any data buffers to the server.

Online server-free image backup is currently supported with a Windows NT/2000 server and Windows 2000 clients. By default, it uses Tivoli Storage Manager’s Logical Volume Storage Agent, which is installed from the Administration Center, and a SAN Data Gateway for the data movement.

10.1.1 Related optionsYou enable the Tivoli Storage Manager server to perform server-free data movement operations by using the SET SERVERFREE command:

SET SERVERFREE STATUS=ON



You can set the amount of data to be moved during an instance of an extended copy command by specifying the BATCHSIZE parameter when you issue the SET SERVERFREE command. The BATCHSIZE parameter specifies the maximum amount of data, in megabytes, that is copied in a single instance of an extended copy command. The minimum value is 10 MB, the maximum value is 1000 MB, and the default value is 80 MB. For example, if you wanted to set a batchsize of 320 MB, you would issue the following command:

SET SERVERFREE BATCHSIZE=320

You can specify the number of concurrent copy operations that the data mover can support by including the COPYTHREADS parameter when you issue the DEFINE DATAMOVER command. The COPYTHREADS parameter is used to govern how many copy commands can run concurrently using this same data mover. For example, to perform four concurrent server-free data movement operations, specify the following when defining a data mover:

DEFINE DATAMOVER SCSI1 TYPE=SCSI WWN=2002006045160D2A SERIAL=21081300957 DATAFORMAT=NONBLOCK COPYTHREADS=4

The default value is one. See your data mover device specific documentation to obtain the maximum value. The number must be greater than zero. If other programs or servers are using the extended copy capabilities of the data mover device, you might want to specify fewer than the maximum number of concurrent copy commands that are supported by the device for this parameter.

10.1.2 Data format for server-free data movementData that is transferred using server-free data movement must be stored in a different format than the format that has traditionally been used for Tivoli Storage Manager. The new data format is called NONBLOCK and must be specified when you define a data mover for server-free data movement and when you define a storage pool that is used for server-free data movement.

Data that has been backed up or archived using server-free data movement and stored in a storage pool with a data format of NONBLOCK, can be moved to other storage pools. Likewise, you can also move an uncompressed image object backed up or archived by a client from a traditional storage pool to a NONBLOCK storage pool and restore it using server-free.

Server operations such as migration, move data, and storage pool backup can cause this data to be stored in storage pools that do not have a data format of NONBLOCK. If this occurs, it is no longer possible to restore the data using server-free. However, the data can be restored over the LAN.

Attention: The terms NONBLOCK (or NONblock) and Native Without mean the same thing. If you look at a storage pool that has been defined to hold server-free backups, you see NONblock in the Storage Pool Data Format field. However, if you display a SCSI Data Mover device (such as the SAN Data Gateway), then the Storage Pool Data Format there shows Native without.


10.2 Requirements for server-free data movementYou must meet the following requirements when setting up server-free data movement operations:

� Operating system for the Tivoli Storage Manager server and client

Supported Windows operating system for Tivoli Storage Manager server and client.

� Data mover device

The data mover device must support the version of the SCSI-3 EXTENDED COPY command that conforms to the ANSI T10 SPC-2 standard.

� Fibre Channel Host Bus Adapter (FC HBA)

You need to install a Host Bus Adapter DLL that supports the Storage Network Industry Association’s (SNIA) common API for purposes of device discovery. Consult the HBA documentation or the HBA’s manufacturer for the location of the required DLL. For QLogic HBAs refer to:

http://www.qlogic.com/support/home_support.asp

� Tape libraries

SCSI-attached or Fibre Channel-attached tape libraries that are supported by the Tivoli Storage Manager device driver.

� Tape drives

If a tape library contains one or more drives, the data mover must have addressability to all drives that will be used for server-free data movement.

� Disks

The client-owned disks must be accessible from the data mover and the Tivoli Storage Manager server machine’s HBA.

Verify the compatibility of specific combinations of data mover devices, tape devices, and SAN devices with the manufacturers of the hardware. Not all data movers support all drives. Before attempting to set up server-free data movement operations, first verify that Tivoli Storage Manager supports the devices you wish to use.

For more information about supported Data Mover Devices, FC HBAs, Tape Libraries, Tape Drives and Disks, see:


10.2.1 Preparing for server-free data movementAs usual, careful preparation is essential. Allow plenty of time to set up server-free data movement. In our lab, we used a SAN Data Gateway 2108-G07 as data mover. The microcode of the SAN Data Gateway must be 3.43.14 or higher.

Attention: Device addressing in a SAN can be tricky, especially in a Windows environment, where addition or removal of devices without disruption can cause a change to the SCSI address or device name (//./Tape0) of existing devices. If possible, use persistent naming (or binding) with a static device naming convention. For more details, see the IBM Redpaper Managing the device addressing of SAN attached tape for use with Tivoli Storage Manager, REDP0150.



http://www.qlogic.com/support/home_support.asp

First, we installed the current microcode level on the 2108-G07 SDG itself. After that, we enabled the SDG as a data mover. A license key is required to enable data movement. We used the StorWatch SAN Data Gateway Specialist to license the SAN Data Gateway as a data mover.

IBM SAN Data GatewayThe 2108-G07 SDG needs to be at current firmware levels to perform server-free data movement as directed by the Tivoli Storage Manager server.

The following procedure describes how to update the firmware of the SAN Data Gateway Model 2108-G07, enable the data mover, and set up the Gateway for server-free data movement.

1. Download the latest version of the firmware from:

http://www-1.ibm.com/support/docview.wss?rs=528&context=STCVQ5X&q=SAN&uid=ssg1S4000067

2. Install the IBM StorWatch SAN Data Gateway Specialist if you have not already done so. See the IBM Storage Area Network Data Gateway Installation and User’s Guide, SC26-7304, for details on how to do this installation. You need to install both StorWatch server and client code on the machine. The client connects to the server automatically and then the server connects to the SAN Data Gateway of your choice (by IP address).

3. Start the IBM SAN Data Gateway Specialist and connect to the SAN Data Gateway that you want to update using the IP-address of the Gateway. The specialist main window appears, as shown in Figure 10-3.

Figure 10-3 Specialist main window

4. The right side of the window shows the current firmware revision (for example, 3.42.12). Select Controls → Update Firmware to get the file selection window. Choose the new firmware file and click Open. Confirm that you want to download the firmware, as shown in Figure 10-4.

Figure 10-4 Attention! message


http://www-1.ibm.com/support/docview.wss?rs=528&context=STCVQ5X&q=SAN&uid=ssg1S4000067

Downloading the firmware into the SAN Data Gateway is a disruptive process, so the specialist displays a warning message. Click Yes to start the download.

5. After the firmware has been upgraded, you are prompted to restart the SAN Data Gateway, as shown in Figure 10-5. Click Yes to restart.

Figure 10-5 Upload completed message

6. If you are satisfied that I/O is halted, click Yes to the message that is shown in Figure 10-6.

Figure 10-6 Warning! message

7. After the restart, reconnect to the SAN Data Gateway to enable the Data Mover. Select Controls → Feature Enable → Data Mover. The Enter License Key window appears (Figure 10-7). Enter your license key to activate the Data Mover.

Figure 10-7 Enable Data Mover window

8. After you update the firmware and activate the data mover, check whether the setup of the SAN Data Gateway for server-free data movement is correct. Select the Fibre Channel port that is connected to the SAN and click Controls → Fibre Channel, as shown in Figure 10-8 on page 275.


Figure 10-8 Fibre Channel selection

9. The Fibre Channel parameters window appears, as shown in Figure 10-10 on page 276.

Figure 10-9 Fibre Channel parameters window

Select NT as the Host Type to be sure that the Tivoli Storage Manager server can see the Gateway via the SAN. Select Target and Initiator and Public Port Mode to be sure the Gateway can see the disk subsystem as well as the tape drives. For Connection Options use Loop or Point to Point, depending on whether you use a Fibre Channel Hub or a Fibre Channel Switch. Click OK to apply all changes.


10.To check whether the Gateway is correctly connected to the SAN and sees all necessary devices, expand the Fibre Channel section of the Channel you use for your SAN connection, as shown in Figure 10-10.

Figure 10-10 Visible devices for Fibre Channel - 4

If your setup is correct, you see the disk devices, the SAN Data Gateway of the tape library, as well as the medium changer and its tape devices. In this example, you see two disk devices, the SAN Data Gateway, two tape drives, and the medium changer.

Note: The port settings Public and Target and Initiator can only be selected if the Fibre Channel ports of the SAN Data Gateway uses 2200-type HBAs. With 2100-type HBAs, the port settings do not work.


10.3 Server-free data movement in our lab environmentFigure 10-11 shows our lab environment for the original test of server-free data movement (server-free setup 1).

Figure 10-11 Lab server-free setup 1

We have shown the World Wide Names and serial numbers of the devices which were needed during the Path and Device definitions we used. Notice than in this test the tape library was directly attached to the SCSI port on the SAN Data Gateway data mover device itself.

We also tested server-free data movement in our lab with the tape library attached to a second SAN Data Gateway device which was not enabled as a data mover (server-free setup 2), as shown in Figure 10-12 on page 278.

Magstar MP Tape 3570-C02 (2 drives)lb1.3.0.3; mt1 2.0.3; mtl .4.0.3WWN1+2=2001006045161767SN1=0000000 B1982; SN2-00000000B2070

SAN

Fibre

CLYDEITSM 5.1.0.0 ClientQLogic 2200

JAMAICAITSM 5.1.0.0 Server

QLogic 2200

SAN Data GW 2108-G07WWN=200400604516150DSN=21081302315DATAMOVER

FAStT700WWN=200200A0B80CBCE8SN=1T14859797

Fibre

FC Switch2109-S08

Data movement LAN100BaseT

SCSI

Fibre Fibre


Figure 10-12 Lab server-free setup 2

Figure 10-12 shows a Tivoli Storage Manager server (JAMAICA) and Tivoli Storage Manager client (Clyde) both at Tivoli Storage Manager V5.1 and both running Windows 2000. They are connected to a SAN with a FAStT700 disk subsystem and a 2108-G07 SAN Data Gateway which had been enabled as our data mover. The second 2108-G07 SAN Data Gateway was required only because our Magstar library only has SCSI connectivity. We have shown the World Wide Names and serial numbers of all the devices we needed during the preparations for server-free data movement.

Preparing Tivoli Storage ManagerThe following are the relevant names that were used for the required entities as defined on the Tivoli Storage Manager server:

� Server name = JAMAICA� Node name = CLYDE� Library name = MAGLIB� Tape drive 1 = MAGDRV1� Tape drive 2 = MAGDRV2� Device class = MAGCLASS� Storage pool = SRVFREEPOOL� Management class = SRVFREEMC� Data Mover = SRVFREEDM

Magstar MP Tape 3570-C02 (2 drives)lb1.3.0.3; mt1 2.0.3; mtl .4.0.3WWN1+2=2001006045161767SN1=0000000 B1982; SN2-00000000B2070

SAN

Fibre

Fibre

CLYDEITSM 5.1.0.0 ClientQLogic 2200

JAMAICAITSM 5.1.0.0 Server

QLogic 2200

SAN Data GW 2108-G07WWN=200400604516150DSN=21081302315DATAMOVER

FAStT700WWN=200200A0B80CBCE8SN=1T14859797

Fibre

FC Switch2109-S08

Data movement LAN100BaseT

SCSI

Fibre Fibre

Fibre

SAN Data GW 2108-G07WWN=2001006045161767SN=21081302794

Fibre


Configuring Tivoli Storage ManagerTo configure server-free setup 2, perform the following on the Tivoli Storage Manager server:

1. Connect devices to the SAN.

Before you configure Tivoli Storage Manager for server-free data movement, all devices must be connected to the SAN that are needed for this function, including:

– Data mover device– Tape libraries– Tape drives– Disk devices

The devices must exist on the SAN and must be visible for the Tivoli Storage Manager server before they are defined to Tivoli Storage Manager. Also, if you are using zoning, ensure that the following devices can see each other:

– On the Tivoli Storage Manager server: data mover device, tape libraries, tape drives, disk devices

– On the Tivoli Storage Manager client: disk devices

2. Determine the World Wide Name, Serial Number, and LUN

Before you configure Tivoli Storage Manager for server-free data movement, you must first identify and record the World Wide Name, serial number, and LUN of each disk device and tape drive that are used, and the World Wide Name and serial number of the data mover. This information is used when defining devices and device paths. To identify this information, issue the QUERY SAN command. The QUERY SAN command displays the devices that can be detected on the SAN, as well as the information for those devices. Example 10-1 shows the output of this command.

Example 10-1 Output of the QUERY SAN command

Operation Results

Device Vendor Product Serial Device Type Number -------- -------- ------------ ------------ --------------DISK IBM 1742 1T14859797 DISK IBM 1742 1T14859797 GATEWAY PATHLGHT SAN Gateway 21081302794 DRIVE IBM 03570C12 0000000B1982 mt1.2.0.3 LIBRARY IBM 03570C12 0000000B1982 lb1.3.0.3 DRIVE IBM 03570C12 0000000B2070 mt1.4.0.3 GATEWAY PATHLGHT SAN Gateway 21081302315

To get more information, including the World Wide Name, issue the QUERY SAN FORMAT=DETAILED command, which produces the output as shown in Example 10-2.

Example 10-2 Output of ‘query san format=detailed’ command

Operation Results

Device Type: DISK Vendor: IBM Product: 1742Serial Number: 1T14859797 Device: Data Mover: No Node WWN: 200200A0B80CBCE7 Port WWN: 200200A0B80CBCE8 LUN: 0


SCSI Port: 3 SCSI Bus: 0 SCSI Target: 0

Device Type: DISK Vendor: IBM Product: 1742Serial Number: 1T14859797 Device: Data Mover: No Node WWN: 200200A0B80CBCE7 Port WWN: 200200A0B80CBCE8 LUN: 1 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 0

Device Type: GATEWAY Vendor: PATHLGHT Product: SAN GatewaySerial Number: 21081302794 Device: Data Mover: No Node WWN: 1000006045161767 Port WWN: 2004006045161767 LUN: 0 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 1

Device Type: DRIVE Vendor: IBM Product: 03570C12Serial Number: 0000000B1982 Device: mt1.2.0.3 Data Mover: No Node WWN: 1000006045161767 Port WWN: 2004006045161767 LUN: 2 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 1

Device Type: LIBRARY Vendor: IBM Product: 03570C12Serial Number: 0000000B1982 Device: lb1.3.0.3 Data Mover: No Node WWN: 1000006045161767 Port WWN: 2004006045161767 LUN: 3 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 1

Device Type: DRIVE Vendor: IBM Product: 03570C12Serial Number: 0000000B2070


Device: mt1.4.0.3 Data Mover: No Node WWN: 1000006045161767 Port WWN: 2004006045161767 LUN: 4 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 1

Device Type: GATEWAY Vendor: PATHLGHT Product: SAN GatewaySerial Number: 21081302315 Device: Data Mover: Yes Node WWN: 100000604516150D Port WWN: 200400604516150D LUN: 0 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 2

When you record the information, be sure to use Port WWN as the World Wide Name to be used in the path definitions.

For example, the information that we recorded for our first tape drive was:

– World Wide Name: 2004006045161767– Serial number: 0000000B1982– LUN: 2

You can also get the same information from the Tivoli Storage Manager Management Console, as shown in Figure 10-13 and Figure 10-14 on page 282.

Figure 10-13 Device information


Figure 10-14 Device information window

3. Obtain and correlate the disk information

After detecting and recording the information for all of the devices that are detectable on the SAN, you must obtain and correlate the information for the disks that you are backing up.

Log into the client machine that owns the disk and start the Tivoli Storage Manager client command line interface. Run the QUERY DISKINFO command to get the information for disks that are associated with the client, as shown in Example 10-3.

Example 10-3 Disk information of client CLYDE

Disk name LUN Serial number----------------------------------Harddisk0 0 TEF76061Harddisk1 0 1T14859797

Compare the information from the QUERY DISKINFO command output to the output of the QUERY SAN command. In this example, the serial number and LUN from the disk, Harddisk1, match the information for the disk that is displayed in the output from the QUERY SAN command, indicating that this is the disk to be backed up.

The information for the disk that will be backed up is:

– Node name: Clyde– Device name: Harddisk1– World wide name: 200200A0B80CBCE8– Serial number: 1T14859797– LUN: 0

4. Enable the server to perform server-free data movement operations using the SET SERVERFREE command as follows:

set serverfree status=on

Note: The output of the QUERY DISKINFO command will display information about every disk defined on the client, SAN-attached as well as direct attached.


To check if the server supports server-free data movement and the server-free status is enabled, use the QUERY STATUS command. As you can see in the last two rows of the output in Figure 10-15, server-free is enabled and the server-free batch size is 80 MB.

Figure 10-15 QUERY STATUS output

5. Define the library to the server using the DEFINE LIBRARY command:

DEFINE LIBRARY MAGLIB LIBTYPE=SCSI SHARED=NO

6. Define the library path from the Tivoli Storage Manager server to the library using the DEFINE PATH command:

DEFINE PATH JAMAICA MAGLIB SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=LB1.3.0.3

7. Define the tape drive(s) to the Tivoli Storage Manager server using the DEFINE DRIVE command.

DEFINE DRIVE MAGLIB MAGDRV1 ELEMENT=16 WWN=2004006045161767 SERIAL=0000000B1982DEFINE DRIVE MAGLIB MAGDRV2 ELEMENT=17 WWN=2004006045161767 SERIAL=0000000B2070

8. Define the drive paths from the Tivoli Storage Manager server to the tape drive using the DEFINE PATH command:

DEFINE PATH JAMAICA MAGDRV1 SRCT=SERVER DESTTYPE=DRIVE LIBRARY=MAGLIB DEVICE=MT1.2.0.3DEFINE PATH JAMAICA MAGDRV2 SRCT=SERVER DESTTYPE=DRIVE LIBRARY=MAGLIB DEVICE=MT1.4.0.3

9. Define the device class to the Tivoli Storage Manager server using the DEFINE DEVCLASS command:

DEFINE DEVCLASS MAGCLASS DEVTYPE=3570 LIBRARY=MAGLIB

10.Define the storage pool(s) to the Tivoli Storage Manager server using the DEFINE STGPOOL command:

DEFINE STGPOOL SRVFREEPOOL MAGCLASS MAXSCRATCH=5 DATAFORMAT=NONBLOCK

Note: The DATAFORMAT option must be defined as NONBLOCK for server-free.


11.Define the management class using the DEFINE MGMTCLASS command:

DEFINE MGMTCLASS STANDARD STANDARD SRVFREEMC

12.Define the backup copygroup with the server-free storage pool, SRVFREEPOOL, with the DEFINE COPYGROUP command:

DEFINE COPYGROUP STANDARD STANDARD SRVFREEMC TYPE=BACKUP DESTINATION=SRVFREEPOOL

13.Activate a STANDARD policy set in the STANDARD policy domain with the ACTIVATE POLICYSET command:

ACTIVATE POLICYSET STANDARD STANDARD

14.Register the client node CLYDE and the password of the node as a Tivoli Storage Manager node with the REGISTER NODE command:

REGISTER NODE CLYDE CLYDEPWD

15.Define each disk with the DEFINE DISK command:

DEFINE DISK CLYDE HARDDISK1 WWN=200200A0B80CBCE8 SERIAL=1T14859797

16.Define the data mover using the DEFINE DATAMOVER command:

DEFINE DATAMOVER SRVFREEDM TYPE=SCSI WWN=200400604516150D SERIAL=21081302315 DATAFORMAT=NONBLOCK

17.Define the paths from the data mover to the tape drive with the DEFINE PATH command:

DEFINE PATH SRVFREEDM MAGDRV1 SRCTYPE=DATAMOVER DESTTYPE=DRIVE LIBRARY=MAGLIB LUN=2DEFINE PATH SRVFREEDM MAGDRV2 SRCTYPE=DATAMOVER DESTTYPE=DRIVE LIBRARY=MAGLIB LUN=4

18.Define the paths from the data mover to each disk using the DEFINE PATH command:

DEFINE PATH SRVFREEDM HARDDISK1 SRCTYPE=DATAMOVER DESTTYPE=DISK NODE=CLYDE LUN=0

The server setup is now complete.

Setting up Tivoli Storage Manager clientServer-free backup is only available for NTFS-formatted volumes and raw volumes. FAT and FAT32 file systems are not supported. The following volume types are supported:

� Simple � Spanned � Mirrored

Attention: The disk device name is case sensitive.

Note: You might wonder why you have to use a LUN number in the DEFINE PATH command for the data mover when you were able to use the device name (mt1.2.0.3) when doing the DEFINE PATH from the Tivoli Storage Manager server to the same device earlier. The LUN is required because the SAN Data Gateway data mover uses it to directly address the device on the SAN. The SAN Data Gateway does not need to know the device name. The WWN and LUN combination uniquely identify the device. You can obtain the LUN for the device from the Device Information window, as shown in Figure 10-14 on page 282.

Attention: The disk device name is case sensitive.


To enable the Windows client for server-free backup and restore:

1. Enable the client for server-free backups by selecting the Tivoli Storage Manager client preferences editor under the General tab as shown in Figure 10-16.

Figure 10-16 Enabling server-free backups on the client

Alternatively, you can edit the Tivoli Storage Manager client options manually in the dsm.opt file, if you prefer.

Example 10-4 shows what our client dsm.opt file looked like for server-free data movement. You need a line to enable server-free data movement (ENABLESERVERFREE YES) and an INCLUDE.IMAGE statement to identify the target Management Class (in this case, SERVERFREEMC that was defined earlier) and, thus, the target storage pool for any drive you want to backup using server-free data movement.

Example 10-4 Tivoli Storage Manager client options file for Server-Free Data Movement

NODENAME CLYDE PASSWORDACCESS GENERATETCPSERVERADDRESS 9.1.36.156ENABLESERVERFREE YESINCLUDE.IMAGE D: SERVERFREEMC


2. Remember, you must have a SAN Data Mover device enabled and defined to the Tivoli Storage Manager server for server-free data movement to take place. If you attempt a server-free image backup from the client without a data mover configured, you will see the error that is shown in Figure 10-17.

Figure 10-17 Warning if data mover not available on server-free backup

10.3.1 Server-free backup and restoreWhen both the client and server have been configured and enabled for server-free image backups, you can perform server-free backups and restores from the client GUI or using the command line interface.

BackupTo perform a server-free backup from the client GUI, select the SAN-attached drive that you want to back up, select Image Snapshot Backup or Image Backup, and then select Backup. A panel, such as that shown in Figure 10-18, confirms that the image backup is taking place on the server-free path.

Figure 10-18 Server-free image backup in progress

Although the full drive capacity is displayed (in this case, 9.99 GB), you can choose to back up only the occupied blocks and skip the empty ones. To do this, specify a non-zero value for the Image Gap Size option if you are backing up from an NTFS volume. A non-zero value is the default behavior. The default for the Image Gap Size option is 5 MB for server-free backup, meaning that empty regions of 5 MB or larger are skipped.

Note: The Image Gap Size option can be specified as an option to the backup image command, specified in the dsm.opt client options file, or specified in the GUI client preferences. See IBM Tivoli Storage Manager for Windows: Installation and User’s Guide, GC32-0788 for more information about this option.


During backup, the blue progress bar indicates how much data has been transferred. It only reports on the actual data that is transferred, so it does not completely fill the space when the server-free backup has completed. For example, in this case, a 9.99 GB drive was backed up, of which only 971 MB was occupied. Therefore, the bar only went approximately 10% of the way across. When the backup has completed, the status report, as shown in Figure 10-19, shows how much data was actually transferred and the transfer rates that were held. Notice that only one object (one image) was backed up.

Figure 10-19 Server-free backup status report

You can use the command line interface to perform the same image backup. By default, the image backup is a snapshot, but you can request a static backup if you prefer. Figure 10-20 on page 288 shows the typical output that is displayed when performing a server-free image backup via the command line interface. A server background process is started to control the data movement from the client’s SAN-attached disk to the server’s SAN-attached tape device, using the SAN Data Gateway data mover functions. The process reports the size of the entire volume that was backed up and the number of actual bytes that were transferred to the tape device.


Figure 10-20 Server-free image backup using command line interface

The background process that is initiated on the Tivoli Storage Manager server can also be seen in the server’s activity log, using the QUERY ACTLOG command, as shown in Figure 10-21.

Figure 10-21 Activity log extract showing server-free backup

You could also use the QUERY PROCESS command to show any server-free processes in progress on the server.


RestoreYou can restore a backup image server-free from the client GUI or command line interface. On the GUI, select the image to restore and click Restore, as shown in Figure 10-22.

Figure 10-22 Server-free restore selection

You get a warning that the entire volume is about to be overwritten, as shown in Figure 10-23.

Figure 10-23 Warning on image restore

When you click Yes, the Task List panel is displayed (Figure 10-24 on page 290). Notice the indication that the restore is server-free.


Figure 10-24 Server-free image restore

As with the backups, the blue progress bar does not completely fill the space, because it is recording only the data that was transferred (in the occupied blocks) and not the entire volume.

You can also restore the backup image using the command line interface, as shown in Figure 10-25. The default is to restore the image to its original location. As with the image backup, there is an indication that a background process has been started on the Tivoli Storage Manager server to control data movement from the tape device back to the client’s SAN-attached disk.

Figure 10-25 Server-free image restore using command line interface

As with the backup, this background process can be seen in the Tivoli Storage Manager server activity log, as shown in Figure 10-26 on page 291.


Figure 10-26 Activity log extract showing server-free restore

Attention: You might notice that the number of bytes that were processed on the restore is slightly less than the number of bytes processed during the backup. Do not panic! You have not lost any data. The byte count for the backup includes all the bytes that were moved to the tape drive, including the frame headers and the object header. The byte count for the restore only includes the bytes that were actually moved to the disk and does not contain any headers. The larger the image you backup, the greater is this discrepancy.



Chapter 11. Tivoli Storage Manager for Hardware — Data Protection for ESS for mySAP™

This chapter describes the functions of Tivoli Storage Manager with its specific component for mySAP™ environments. Both DB2 and Oracle™ databases are supported. However, the example included in this chapter shows Oracle. This chapter contains the following topics:

� Introduction to Data Protection for mySAP™� Overview of the test environment� Requirements and prerequisites� Installation for this environment� Backup� Restore� Special environments� Determining problems

11

Special Notice: This chapter references the SAPDBA Oracle administration utilities. However, at the time of writing, these utilities have been phased out by SAP. These utilities are now repackaged under a new suite called BR*Tools. In all cases, SAP recommends using the latest release of BR*Tools, which at the time of writing is 6.40.


11.1 Introduction to Data Protection for mySAP™Tivoli Storage Manager for Hardware — Data Protection for ESS for mySAP™ enables you to use ESS FlashCopy for backup/restore of mySAP databases (DB2 UDB and Oracle). All the different modes of FlashCopy are supported within the Data Protection module, including:

� NOCOPY: Data is copied only to the target volumes when changed.

� COPY: Data is copied to target volumes using a background process.

� INCR: The Disk Subsystem keeps track of dirty blocks and copies only changed blocks to the target volumes. The first incremental is a full copy.

The FlashCopy process yields the following benefits over a conventional (direct tape) operation:

� Zero impact backup. The backup window on the operational database is minimal (minutes), and the load for transferring data to backup storage is moved from the production server to a backup server.

� Full operational flexibility. The zero impact characteristic eliminates the need for a backup window and allows backups to occur any time and in shortened intervals (shorter recovery).

� Minute restore: Flashback restore (from backups on disk) shortens the restore time from hours to minutes.

Data Protection for IBM ESS for mySAP (Data Protection for IBM ESS for mySAP) can perform disk-only as well as tape backups to a Tivoli Storage Manager server or a combination of both. In a disk-only backup, copies of the production server’s disks are kept after the FlashCopy operation, and you can perform a very fast FlashBack restore. Recovery can start within minutes, making the database available much faster after data loss. If you have only one set of target volumes, only one disk-only backup will be available for restore, because subsequent backups will overwrite the existing version. Multiple backup generations on disk are supported and need multiple sets of target volumes on the ESS.

If you send the backups to the Tivoli Storage Manager server, then normal Tivoli Storage Manager versioning policy applies, because you can maintain and restore backups from different backup operations.

A number of advanced features are supported with Tivoli Storage Manager for Hardware — Data Protection for IBM ESS for mySAP, including:

� HACMP environments. Special functionality for enhanced volume groups has been added for the target system.

� AIX LVM mirroring for storage high availability (each mirror in a separate ESS) is supported - only one mirror needs to be FlashCopied, FlashCopies can be taken alternating from both ESSs.

� Concurrent I/O (CIO) environments are supported.

� On the backup server, the Subsystem Device Driver (SDD) is used to speed up the backup to the Tivoli Storage Manager server.

� Additional command scripts are provided to support the database administrator for pre- and post-restore operations.

� Data Protection for IBM ESS for mySAP is tightly integrated with database administration utilities (db2admin for DB2 UDB and BRTools utilities for mySAP) for backup and restore operations, which provides for automated processes that are consistent with conventional (tape) backup/restore.


11.2 Overview of the test environmentThe test environment in our lab included three IBM pSeries servers and an IBM ESS. A separate Tivoli Storage Manager server, also running AIX, was set up for other use. In addition , we could have used the backup server as the Tivoli Storage Manager server. Figure 11-1 illustrates the details of the test environment.

Figure 11-1 Test environment in the lab

In machines in our test environment were configured as follows:

� mySAP production server S1: AIX V5.3 with mySAP V4.6C and Oracle V9.2 installed. The sample database used about 30 GB of disk space for the tablespace data.

� Backup server T1: AIX V5.3, which required Tivoli Storage Manager components and the BRTools utilities for mySAP. NFS is required to access profiles residing on the production server and rexec to execute remote commands.

� Tivoli Storage Manager server Y1: Running Tivoli Storage Manager Server V5.2. Note that the Tivoli Storage Manager components on S1 and T1 are at V5.3. The versions do not need to match, as long as they are all supported versions.

� IBM ESS Model 800: Contains all the production filespaces and the target volumes that were used for FlashCopy.

The different components on each server are shown in Figure 11-2 on page 296.

Restriction: It is not possible to use the standby machine of an HACMP cluster as the backup server. An HACMP setup requires the use of three systems (see 11.7.2, “AIX HACMP” on page 373 for details).

ESS

mySAPproductionDB Server

LAN

SAN

FlashCopy

TSMServer

TSM for ERP

BackupServer

TSM for ERPTSM for HW

Target Volumes

pSeries ID Y1AIX 5.2 ML05

NFSREXEC

ITSM 5.2.0.0 disk storage pools

pSeriesID S1AIX 5.3 – JFS2

NFSREXEC

IDES 4.6C Oracle 9.2 (30 GB)SAP executables

pSeries ID T1AIX 5.3 – JFS2

NFSREXEC

BRTools

ESS mod 800ID 2105.23376

FlashCopy V2mcode lvl 2.4.2.31CLI 2.3.0.2

Source Volumes

Chapter 11. Tivoli Storage Manager for Hardware — Data Protection for ESS for mySAP™ 295

Figure 11-2 Machine setup

11.2.1 Overview of the proceduresThe following is a summary of the configuration and the procedures used to backup the mySAP database:

� The production server runs an Oracle database that resides on ESS (source) volumes.

� The production database can be backed up online or offline. The ESS source volumes are copied to target volumes using FlashCopy and then backed up using Data Protection for mySAP from the backup server to the Tivoli Storage Manager server via LAN or LAN-free communications methods.

� Backups are initiated using the brbackup utility for mySAP. This utility calls the backint and splitint interfaces for mySAP. The brbackup utility is always invoked from the backup server. It starts the Data Protection for IBM ESS for mySAP on the production server via the rexec command, checks for FlashCopy conditions, and performs FlashCopy.

� The NFS mounts are mainly used for sharing profiles and backup logs.

� Restores are only invoked on the production server. You must stop mySAP and Oracle.

IBM ESSSource Target

SANGigaBit Network


Public Network

Production System / DB Server

TCP/IP

Backup System

TCP/IP

mySAP DBA Tools

brbackup

Oracle Client

DP for ESSsplitintCORE

IDSLVM

DP for mySAP.com

ITSM APIITSM Client

AIXDisk I/O ESS

CopyServices CLI

AIX JFSAIX LVM

SCSI LayerSCSI / Fibre Channel

NFS

SQLNET

REXEC

mySAP DBA Toolssapdba

brbackup / brarchivebrrestore


IDS LVM

DP for mySAP

ITSM APIITSM Client

NFS

SQLNET

REXEC

AIXDisk I/OESS

CopyServices CLI

AIX JFSAIX LVM

SCSI / Fibre Channel

Oracle Server/Client

Management Network

Storage Area Network

SCSI Layer


11.3 Requirements and prerequisitesThe following sections show the hardware and software requirements.

11.3.1 Hardware requirementsThe hardware requirements are:

� Two pSeries servers connected via SAN to an ESS storage subsystem. The production mySAP database system and the backup system operating system levels must be the same on both systems, because file systems and volumes are imported.

� Supported disk systems at the time of writing: IBM ESS Server 2105, model Exx, Fxx, or 800 with FlashCopy feature 1830-1835.

� ESS microcode level: 1.5.2.144 or higher; 2.2.0.545 or higher when using FlashCopy V2 on ESS source/target volume. LSS setup restrictions: 2.3 or higher to use INCR FlashCopy.

� LAN connection from the production and backup servers to the primary and the backup ESS Copy Services Server.

� LAN connection between the production system and the backup server to execute rexec procedures and NFS mounts.

� If the Tivoli Storage Manager server is not installed on the backup machine, a LAN or SAN (for LAN-free data movement) is required for backup operations.

11.3.2 Software requirementsThe software requirements are (see the readme file for latest instructions):

� AIX V5.1 (32bit or 64bit) with FixPack 3 (AIX 5.1.0.0.03) and PTF U483641 for APAR IY37174 orAIX V5.2 (32bit or 64bit) with FixPack 2 (AIX 5.2.0.0.02) and PTF U486557 for APAR IY52248 orAIX V5.3 (32bit or 64bit)

� Java™ Runtime for AIX, Version 1.1.8, 1.3.0 or 1.3.1

� ESS Copy Services command line interface for AIX (from the ESS microcode, see Hardware requirements)

� Tivoli Storage Manager Backup-Archive Client V5.1 (or higher) for AIX

� Tivoli Storage Manager API level for AIX as required by the version of Data Protection for mySAP

� Tivoli Storage Manager for Hardware — Data Protection for IBM ESS for mySAP (3.3.11 or higher) for Oracle for AIX

� mySAP R/3, Release 4.5B to 4.6D or mySAP e-business solutions (for example, mySAP BW) together with released Oracle V8 or V9

� mySAP utilities and interfaces kernel release 6.20 with patch level 18 or higher (supporting the new splitint architecture)

Note: On the backup machine, only the mySAP utilities with released Oracle client code are required.


� On the production system, the rexecd daemon must be configured and running.

� If using the Korn shell, the file /etc/environment must include the following statement:

ENV=$HOME/.profile

� The PATH environment variable must include the /usr/sbin directory for the user ID that is running the brbackup utility for mySAP (usually Oracle Database Administrator). To add this information, add the following statements to $ORACLE_HOME/.profile (if you are using Korn shell):

PATH=${PATH}:/usr/sbinexport PATH

� When setting up the volumes on the ESS, make sure that:

– The LUNs (volumes) used by the production database are accessible to the production system. These are the source volumes used by the FlashCopy process.

– The LUNs (volumes) intended to be used as target volumes are accessible to the backup system.

– The size of each target LUN matches the size of its source volume.

– Only if FlashCopy V1 is used: all ESS target volumes reside in the same Logical Subsystem (LSS) as their source volume.

– Both the primary and backup ESS Copy Services servers must be able to resolve the host names of the production and backup server systems.

Note: SAP recommends using BR*Tools release 6.40.

Note: Production and backup system product levels must match.

Note: AIX Base System locale must be U.S. English. The locale -a command output must include en_US.ISO8859-1.


11.3.3 Storage classesFigure 11-3 shows the different requirements for storage classes in this type of environment.

Figure 11-3 Disk setup

The db_disk category is for the mySAP data tablespace files. They can reside in one or more Volume Groups (VGs). The redo log files, which also belong in the db_disk category, must reside in a different VG. Use of separate VGs is required, because the scope of the files for different backup types is different. Using the same VG for online redo logs and tablespaces will create problems during backup/restore using the ESS target volumes. This is because during a FlashCopy operation, all the volumes in a VG are flashed. It is recommended to split the VGs of the primary redo logs and their mirrors. Because only the original log files are used for backup, it is space efficient to separate them from their copies.

VGs - volume groupsLPs = logical partitions

LVs = logical volumes

The following are not supported with Data Protection for IBM ESS for mySAP for flashed volumes:

� Databases residing on raw devices.

� Databases on a secondary ESS system in a PPRC environment.

� Soft links to Oracle database files.

� AIX LVM mirrored environments if not set as required (for example, in the same ESS subsystem).

Note: Each jfslog logical volume used in the volume groups with all its logical partitions can only use one ESS volume. Striping is not allowed for jfslog logical volumes.

IBM ESSSource Target

SANGigaBit Network


Public Network


TCP/IP

Backup System

TCP/IP

mySAP DBA Tools

brbackup

Oracle Client


IDSLVM

DP for mySAP.com

ITSM APIITSM Client

AIXDisk I/O ESS

CopyServices CLI

AIX JFSAIX LVM


NFS

SQLNET

REXEC

mySAP DBA Toolssapdba



IDS LVM

DP for mySAP

ITSM APIITSM Client

NFS

SQLNET

REXEC

AIXDisk I/OESS

CopyServices CLI

AIX JFSAIX LVM

SCSI / Fibre Channel


Management Network

Storage Area Network

SCSI Layer


� Inline logs for JFS2 file systems at the time of writing (pending resolution of a problem in the AIX recreatevg command).

� JFSlog LVs spread over more than one ESS volume.

The production and backup systems need to share the following files:

� Oracle configuration files (such as init<SID>.ora and so forth)

� Data Protection for IBM ESS for mySAP profile (init<SID>.sap) as well as the run log of the backup cycles (.aff/.anf)

� The run log summary (back<SID>.log

� Data Protection for mySAP profile (init<SID>.utl) and its configuration file (.bki)

� Data Protection for IBM ESS for mySAP profile (init<SID>.fcs), the target volumes file (init<SID>.fct)

These files reside in the following directories and are shared via NFS export from the production system:

� $ORACLE_HOME/dbs

� /oracle/<SID>/sapbackup

� /oracle/<SID>/sapreorg

� /sapmnt/SID/exe

It is optional to share this directory. Alternatively, you can install it separately on the backup server.

11.4 Installation for this environmentThis section explains the installation instructions for this environment.

11.4.1 mySAP™ and Oracle™Install Oracle and mySAP according to the requirements outlined in Figure 11-3 on page 299. You can find additional help in the manual mySAP for R/3 Installation for UNIX. For a quick demonstration, see the section “Sample R/3 Installation and Customization” in the manual IBM Tivoli Storage Manager for Hardware - Data Protection for IBM ESS for mySAP, Installation and User’s Guide for Oracle, SC33-8205.

For this environment:

� System ID (SID) is RED.

� Users are:

– redadm: Administrative user for mySAP– orared: Administrative user for Oracle

� File systems on production system are:

– /oracle/RED: Instance home– /usr/sap/RED: mySAP home– /sapmnt/RED: mySAP tools– /oracle/RED/sapdata1-6: mySAP tablespaces– /oracle/RED/origlogA: Redo log A– /oracle/RED/origlogB: Redo log B– /oracle/RED/mirrorlogA: Mirror of redo log A– /oracle/RED/mirrorlogB: Mirror of redo log B


� NFS mounts from production to backup system are:

– /oracle/RED/920_64/dbs– /oracle/RED/sapbackup– /oracle/RED/sapreorg– /sapmnt/RED

� File systems on backup system are:

– /oracle/RED: Oracle SQLPLUS client– /usr/sap/RED: mySAP tools executables

Testing access from the backup to the production system databaseTo access the production database from the backup system via the SQLPLUS command:

1. Create an Oracle password file with the orapwd command:

orapwd file=/oracle/<SID>/920_64/dbs/orapwRED password=<password> entries=100

In this command, <password> is the password for the Oracle user SYS (standard is CHANGE_ON_INSTALL).

2. Specify the following parameter in the /oracle/RED/920_64/dbs/initRED.ora file:

remote_login_passwordfile=exclusive

You need to restart the Oracle database to make this change effective on the production system.

3. Give authority SYSOPER to the user SYSTEM in the production database, as shown in Example 11-1.

Example 11-1 Give SYSOPER authority to user SYSTEM

orared@s1:/oracle/RED/920_64/dbs>sqlplus

SQL*Plus: Release 9.2.0.1.0 - Production on Fri Mar 18 19:35:15 2005

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Enter user-name: / as sysdba

Total System Global Area 179224752 bytesFixed Size 741552 bytesVariable Size 100663296 bytesDatabase Buffers 76496896 bytesRedo Buffers 1323008 bytesDatabase mounted.

SQL> grant sysoper to system;Grant succeeded.SQL> alter user system identified by secret;Database altered.

SQL> quitDisconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit ProductionWith the Partitioning optionJServer Release 9.2.0.1.0 - Production

orared@s1:/oracle/RED/920_64/dbs>


4. Verify that you can connect from the backup system to the production database via SQLPLUS as user SYSTEM and SYSDBA role (as shown in Example 11-2).

Example 11-2 Verifying the Oracle connection from the backup system

t1:orared 1> sqlplus

SQL*Plus: Release 9.2.0.1.0 - Production on Tue Mar 22 00:15:37 2005


Enter user-name: SYSTEM@RED as SYSOPEREnter password:

Connected to:Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit ProductionWith the Partitioning optionJServer Release 9.2.0.1.0 - Production

SQL>

11.4.2 Tivoli Storage Manager You must install the following Tivoli Storage Manager products.

Tivoli Storage Manager Backup-Archive Client and APIInstall Tivoli Storage Manager Backup-Archive Client and API components on the production and backup system. For details see IBM Tivoli Storage Manager Backup-Archive Clients Installation and User’s Guide for UNIX and Linux, GC32-0789.

Data Protection for mySAP™Install Data Protection for mySAP on your production and backup system by running the ./install_tdpr3_ora_aix_64bit.bin command from your installation medium.

You are guided through the Data Protection for mySAP setup procedure. To ensure that the setup procedure is carried out properly, read the following description carefully and follow the guidelines on the panels that are displayed during setup. To install Data Protection for mySAP on a UNIX system, do the following:

� Read the Release Notice (RELNOTE) and the readme file that is provided with Data Protection for mySAP.

� Log in as root user on the mySAP database server machine.

� Ensure that you have set the DISPLAY variable correctly because the installer guides you through the installation via a graphical window.

Alternatively use the -console parameter when you run the command.

� Run the installation file for Data Protection for mySAP that is appropriate for your operating system and your Oracle database.

Check the summary at the end of the installation dialog.You will find, among other information, the installation path of Data Protection for mySAP. Installation results are logged in the installation log (log.txt), which is located in the installation path.

During installation, the following modifications are done to your system automatically:

� An entry is created in /etc/inittab to start the background process ProLE � An entry is created in /etc/services, which is needed for internal communication.


After the installation, the following files are available in the installation path of Data Protection for mySAP:

� backint� ProLE� createinfo � backfm � initSID.bki� initSID.utl� libtdp_r3.<ext> � archive.ksh � backup.ksh � crontab.sample � dsm.opt� dsm.sys � gensortfile.sh � inclexcl.list � README

Copy the initSID.bki and initSID.utl files to the /oracle/RED/920_64/dbs directory and rename them accordingly to initRED.bki and initRED.utl. (Note: replace RED with your actual database name).

Example 11-3 shows our initRED.sap file:

Example 11-3 initRED.sap

######################################################################### SAP backup sample profile. ## The parameter syntax is the same as for init.ora parameters. ## Enclose parameter values which consist of more than one symbol in ## double quotes. ## After any symbol, parameter definition can be continued on the next ## line. ## A parameter value list should be enclosed in parentheses, the list ## items should be delimited by commas. ## There can be any number of white spaces (blanks, tabs and new lines) ## between symbols in parameter definition. ## #########################################################################

# backup mode [all | all_data | full | incr | sap_dir | ora_dir# | <tablespace_name> | <file_id> | <file_id1>-<file_id2># | <generic_path> | (<object_list>)]# default: allbackup_mode = all

# restore mode [all | all_data | full | incr | incr_only | incr_full# | <tablespace_name> | <file_id> | <file_id1>-<file_id2># | <generic_path> | (<object_list>)]# redirection with '=' is not supported here - use option '-m' instead# default: allrestore_mode = all

# backup type [offline | offline_force | offline_standby | offline_mirror# | offline_stop | online | online_cons | online_mirror]# default: offlinebackup_type = offline_mirror

# backup device type


# [tape | tape_auto | tape_box | pipe | pipe_auto | pipe_box | disk# | disk_copy | disk_standby | stage | stage_copy | stage_standby# | util_file | util_file_online | rman_util | rman_disk | rman_stage# | rman_prep]# default: tapebackup_dev_type = tape

# backup root directory [<path_name> | (<path_name_list>)]# default: $SAPDATA_HOME/sapbackupbackup_root_dir = $SAPDATA_HOME/sapbackup

# stage root directory [<path_name> | (<path_name_list>)]# default: value of the backup_root_dir parameterstage_root_dir = $SAPDATA_HOME/sapbackup

# compression flag [yes | no | hardware | only]# default: nocompress = no

# compress command# first $-character is replaced by the source file name# second $-character is replaced by the target file name# <target_file_name> = <source_file_name>.Z# for compress command the -c option must be set# recommended setting for brbackup -k only run:# "compress -b 12 -c $ > $"# no defaultcompress_cmd = "compress -c $ > $"

# uncompress command# first $-character is replaced by the source file name# second $-character is replaced by the target file name# <source_file_name> = <target_file_name>.Z# for uncompress command the -c option must be set# no defaultuncompress_cmd = "uncompress -c $ > $"

# directory for compression [<path_name> | (<path_name_list>)]# default: value of the backup_root_dir parametercompress_dir = $SAPDATA_HOME/sapreorg

# brarchive function [save | second_copy | double_save | save_delete# | second_copy_delete | double_save_delete | copy_save# | copy_delete_save | delete_saved | delete_copied]# default: savearchive_function = save

# directory for archive log copies to disk# default: first value of the backup_root_dir parameter# Oracle Parallel Server:# archive_copy_dir = $SAPDATA_HOME/saparchglobalarchive_copy_dir = $SAPDATA_HOME/sapbackup

# directory for archive log copies to stage# should contain <SID> subdirectory# default: first value of the stage_root_dir parameterarchive_stage_dir = $SAPDATA_HOME/sapbackup

# new sapdata home directory for disk_copy | disk_standby# no default


# new_db_home = /oracle/C11

# stage sapdata home directory for stage_copy | stage_standby# default: value of the new_db_home parameter# stage_db_home = /oracle/C11

# original sapdata home directory for split mirror disk backup# no default# orig_db_home = /oracle/C11

# remote host name# no default# remote_host = <host_name>

# remote user name# default: current operating system user# remote_user = <user_name>

# tape copy command [cpio | cpio_gnu | dd | dd_gnu | rman | rman_dd]# default: cpiotape_copy_cmd = cpio

# disk copy command [copy | dd | dd_gnu | rman]# default: copydisk_copy_cmd = copy

# stage copy command [rcp | ftp]# default: rcpstage_copy_cmd = rcp

# flags for cpio output command# default: -ovBcpio_flags = -ovB

# flags for cpio input command# default: -iuvBcpio_in_flags = -iuvB

# flags for cpio command for copy of directories to disk# default: -pdcucpio_disk_flags = -pdcu

# flags for dd output command# default: "obs=16k"# recommended setting:# Unix: "obs=nk bs=nk", example: "obs=64k bs=64k"# NT: "bs=nk", example: "bs=64k"dd_flags = "obs=64k bs=64k"

# flags for dd input command# default: "ibs=16k"# recommended setting:# Unix: "ibs=nk bs=nk", example: "ibs=64k bs=64k"# NT: "bs=nk", example: "bs=64k"dd_in_flags = "ibs=64k bs=64k"

# number of members in RMAN save sets [ 1 | 2 | 3 | 4 | tsp | all ]# default: 1saveset_members = 1


# additional parameters for RMAN# rman_channels and rman_filesperset are only used when rman_util,# rman_disk or rman_stage# rman_channels defines the number of parallel sbt channel allocations# rman_filesperset = 0 means:# one file per save set - for non-incremental backups# all files in one save set - for incremental backups# the others have the same meaning as for native RMAN# rman_channels = 1# rman_filesperset = 0# rman_kbytes = 0# rman_readrate = 0# rman_maxopenfiles = 0# rman_setsize = 0# additional parameters for RMAN version 8.1# the parameters have the same meaning as for native RMAN# rman_diskratio = 0# rman_pool = 0# rman_duplex = 0 | 1 | 2 | 3 | 4# rman_proxy = no | yes | only# special parameters for an external backup library, example:# rman_parms = "BLKSIZE=65536 ENV=(BACKUP_SERVER=HOSTNAME)"# rman_send = "'<command>'"# rman_send = ("channel sbt_1 '<command1>' parms='<parameters1>'",# "channel sbt_2 '<command2>' parms='<parameters2>'")

# remote copy-out command (backup_dev_type = pipe)# $-character is replaced by current device address# no defaultcopy_out_cmd = "dd ibs=8k obs=64k of=$"

# remote copy-in command (backup_dev_type = pipe)# $-character is replaced by current device address# no defaultcopy_in_cmd = "dd ibs=64k obs=8k if=$"

# rewind command# $-character is replaced by current device address# no default# operating system dependent, examples:# HP-UX: "mt -f $ rew"# OSF1: "mt -f $ rewind"# AIX: "tctl -f $ rewind"# SINIX: "mt -f $ rewind"# SUN: "mt -f $ rewind"# NT: "mt -f $ rewind"# Linux: "mt -f $ rewind"rewind = "mt -f $ rewind"

# rewind and set offline command# $-character is replaced by current device address# default: value of the rewind parameter# operating system dependent, examples:# HP-UX: "mt -f $ offl"# OSF1: "mt -f $ offline"# AIX: "tctl -f $ offline"# SINIX: "mt -f $ offline"# SUN: "mt -f $ offline"# NT: "mt -f $ offline"# Linux: "mt -f $ offline"


rewind_offline = "mt -f $ offline"

# tape positioning command# first $-character is replaced by current device address# second $-character is replaced by number of files to be skipped# no default# operating system dependent, examples:# HP-UX: "mt -f $ fsf $"# OSF1: "mt -f $ fsf $"# AIX: "tctl -f $ fsf $"# SINIX: "mt -f $ fsf $"# SUN: "mt -f $ fsf $"# NT: "mt -f $ fsf $"# Linux "mt -f $ fsf $"tape_pos_cmd = "mt -f $ fsf $"

# mount backup volume command in auto loader / juke box# used if backup_dev_type = tape_box | pipe_box# no default# mount_cmd = "<mount_cmd> $ $ $ [$]"

# dismount backup volume command in auto loader / juke box# used if backup_dev_type = tape_box | pipe_box# no default# dismount_cmd = "<dismount_cmd> $ $ [$]"

# split mirror disks command# used if backup_type = offline_split | online_split# no default# split_cmd = "<split_cmd> [$]"split_options= "-p /oracle/RED/920_64/dbs/initRED.fcs -d "

# resynchronize mirror disks command# used if backup_type = offline_split | online_split# no default# resync_cmd = "<resync_cmd> [$]"split_resync=yes

# volume size in KB = K, MB = M or GB = G (backup device dependent)# default: 1200M# recommended values for tape devices without hardware compression:# 60 m 4 mm DAT DDS-1 tape: 1200M# 90 m 4 mm DAT DDS-1 tape: 1800M# 120 m 4 mm DAT DDS-2 tape: 3800M# 125 m 4 mm DAT DDS-3 tape: 11000M# 112 m 8 mm Video tape: 2000M# 112 m 8 mm high density: 4500M# DLT 2000 10/20 GB: 10000M# DLT 2000XT 15/30 GB: 15000M# DLT 4000 20/40 GB: 20000M# DLT 7000 35/70 GB: 35000M# recommended values for tape devices with hardware compression:# 60 m 4 mm DAT DDS-1 tape: 1000M# 90 m 4 mm DAT DDS-1 tape: 1600M# 120 m 4 mm DAT DDS-2 tape: 3600M# 125 m 4 mm DAT DDS-3 tape: 10000M# 112 m 8 mm Video tape: 1800M# 112 m 8 mm high density: 4300M# DLT 2000 10/20 GB: 9000M# DLT 2000XT 15/30 GB: 14000M


# DLT 4000 20/40 GB: 18000M# DLT 7000 35/70 GB: 30000Mtape_size = 1200M

# volume size in KB = K, MB = M or GB = G used by brarchive# default: value of the tape_size parameter# tape_size_arch = 1200M

# level of parallel execution# default: 0 - set to number of backup devicesexec_parallel = 0

# address of backup device without rewind# [<dev_address> | (<dev_address_list>)]# no default# operating system dependent, examples:# HP-UX: /dev/rmt/0mn# OSF1: /dev/nrmt0h# AIX: /dev/rmt0.1# SINIX: /dev/ios0/rstape005n# SUN: /dev/rmt/0mn# NT: /dev/nmt0 | /dev/nst0# Linux /dev/nst0tape_address = /dev/rmt/0mn

# address of backup device without rewind used by brarchive# default: value of the tape_address parameter# operating system dependent# tape_address_arch = /dev/rmt/0mn

# address of backup device with rewind# [<dev_address> | (<dev_address_list>)]# no default# operating system dependent, examples:# HP-UX: /dev/rmt/0m# OSF1: /dev/rmt0h# AIX: /dev/rmt0# SINIX: /dev/ios0/rstape005# SUN: /dev/rmt/0m# NT: /dev/mt0 | /dev/st0# Linux: /dev/st0tape_address_rew = /dev/rmt/0m

# address of backup device with rewind used by brarchive# default: value of the tape_address_rew parameter# operating system dependent# tape_address_rew_arch = /dev/rmt/0m

# address of backup device with control for mount/dismount command# [<dev_address> | (<dev_address_list>)]# default: value of the tape_address_rew parameter# operating system dependent# tape_address_ctl = /dev/...

# address of backup device with control for mount/dismount command# used by brarchive# default: value of the tape_address_rew_arch parameter# operating system dependent# tape_address_ctl_arch = /dev/...


# volumes for brarchive# [<volume_name> | (<volume_name_list>) | SCRATCH]# no defaultvolume_archive = (SIDA01, SIDA02, SIDA03, SIDA04, SIDA05, SIDA06, SIDA07, SIDA08, SIDA09, SIDA10, SIDA11, SIDA12, SIDA13, SIDA14, SIDA15, SIDA16, SIDA17, SIDA18, SIDA19, SIDA20, SIDA21, SIDA22, SIDA23, SIDA24, SIDA25, SIDA26, SIDA27, SIDA28, SIDA29, SIDA30)

# volumes for brbackup# [<volume_name> | (<volume_name_list>) | SCRATCH]# no defaultvolume_backup = (SIDB01, SIDB02, SIDB03, SIDB04, SIDB05, SIDB06, SIDB07, SIDB08, SIDB09, SIDB10, SIDB11, SIDB12, SIDB13, SIDB14, SIDB15, SIDB16, SIDB17, SIDB18, SIDB19, SIDB20, SIDB21, SIDB22, SIDB23, SIDB24, SIDB25, SIDB26, SIDB27, SIDB28, SIDB29, SIDB30)

# expiration period for backup volumes in days# default: 30expir_period = 30

# recommended usages of backup volumes# default: 100tape_use_count = 100

# backup utility parameter file# default: no parameter file# util_par_file = initSID.utl

util_par_file = /oracle/RED/920_64/dbs/initRED.utl

# mount/dismount command parameter file# default: no parameter file# mount_par_file = initSID.mnt

# Oracle instance string to the primary database# [primary_db = <inst_str> | LOCAL]# no default# primary_db = <inst_str>primary_db = RED.WORLD

# description of parallel instances for Oracle Parallel Server# parallel_instances = <instance_desc> | (<instance_desc_list>)# <instance_desc_list> -> <instance_desc>[,<instance_desc>...]# <instance_desc> -> <Oracle_sid>:<Oracle_home>@<inst_str># <Oracle_sid> -> Oracle system id for parallel instance# <Oracle_home> -> Oracle home for parallel instance# <inst_str> -> Oracle instance string to parallel instance# Do not include the local instance in the parameter definition!# default: no parallel instances## example for initC11.sap:# parallel_instances = (C11_002:/oracle/C11@C11_002,# C11_003:/oracle/C11@C11_003)## example for initC11_002.sap:# parallel_instances = (C11:/oracle/C11@C11,


# C11_003:/oracle/C11@C11_003)

# database owner of objects to be checked# <owner> | (<owner_list>)# default: all SAP owners# check_owner = sapr3

# database objects to be excluded from checks# all_part | non_sap | [<owner>.]<table> | [<owner>.]<index># | <tablespace> | (<object_list>)# default: no exclusion, example:# check_exclude = (SDBAH, SAPR3.SDBAD)

# database owner of SDBAH, SDBAD and XDB tables for cleanup# <owner> | (<owner_list>)# default: all SAP owners# cleanup_owner = sapr3

# retention period in days for brarchive log files# default: 30# cleanup_brarchive_log = 30

# retention period in days for brbackup log files# default: 30# cleanup_brbackup_log = 30

# retention period in days for brconnect log files# default: 30# cleanup_brconnect_log = 30

# retention period in days for brrestore log files# default: 30# cleanup_brrestore_log = 30

# retention period in days for sapdba log files# default: 30# cleanup_sapdba_log = 30

# retention period in days for offline redo log files saved on disk# default: 30# cleanup_disk_archive = 30

# retention period in days for database file saved on disk# default: 30# cleanup_disk_backup = 30

# retention period in days for sapdba export dumps and scripts# default: 30# cleanup_exp_dump = 30

# retention period in days for Oracle trace and audit files# default: 30# cleanup_ora_trace = 30

# retention period in days for records in SDBAH and SDBAD tables# default: 100# cleanup_db_log = 100

# retention period in days for records in XDB tables# default: 100


# cleanup_xdb_log = 100

# retention period in days for database check messages# default: 100# cleanup_check_msg = 100

# database owner of objects to adapt next extents# <owner> | (<owner_list>)# default: all SAP owners# next_owner = sapr3

# database objects to adapt next extents# all | all_ind | special | [<owner>.]<table> | [<owner>.]<index># | <tablespace> | (<object_list>)# default: all abjects of selected owners, example:# next_table = (SDBAH, SAPR3.SDBAD)

# database objects to be excluded from adapting next extents# all_part | [<owner>.]<table> | [<owner>.]<index> | <tablespace># | (<object_list>)# default: no exclusion, example:# next_exclude = (SDBAH, SAPR3.SDBAD)

# database objects to get special next extent size# all_sel:<size>[/<limit>] | [<owner>.]<table>:<size>[/<limit>]# | [<owner>.]<index>:<size>[/<limit>] | (<object_size_list>)# default: according to table category, example:# next_special = (SDBAH:100K, SAPR3.SDBAD:1M/200)

# maximum next extent size# default: 2 GB - 5 * <database_block_size># next_max_size = 1G

# maximum number of next extents# default: 0 - unlimited# next_limit_count = 300

# database owner of objects to update statistics# <owner> | (<owner_list>)# default: all SAP owners# stats_owner = sapr3

# database objects to update statistics# all | all_ind | all_part | missing | info_cubes | dbstatc_tab# | dbstatc_mon | dbstatc_mona | [<owner>.]<table> | [<owner>.]<index># | <tablespace> | (<object_list>)# default: all abjects of selected owners, example:# stats_table = (SDBAH, SAPR3.SDBAD)

# database objects to be excluded from updating statistics# all_part | info_cubes | non_sap | [<owner>.]<table># | [<owner>.]<index> | <tablespace> | (<object_list>)# default: no exclusion, example:# stats_exclude = (SDBAH, SAPR3.SDBAD)

# method for updating statistics for tables not in DBSTATC# E | EH | EI | EX | C | CH | CX | E= | C= | =H | =I | =X | +H | +I# default: according to internal rules# stats_method = E


# sample size for updating statistics for tables not in DBSTATC# P<percentage_of_rows> | R<thousands_of_rows># default: according to internal rules# stats_sample_size = P10

# number of buckets for updating statistics with histograms# default: 75# stats_bucket_count = 75

# threshold for collecting statistics after checking# default: 50%# stats_change_threshold = 50

# number of parallel threads for updating statistics# default: 1# stats_parallel_degree = 1

# processing time limit in minutes for updating statistics# default: 0 - no limit# stats_limit_time = 0

# parameters for calling DBMS_STATS supplied package# all:R|B:<degree> | all_part:R|B:<degree> | info_cubes:R|B:<degree># | [<owner>.]<table>:R|B:<degree> | (<object_list>)# default: NULL - use ANALYZE statement# stats_dbms_stats = ([ALL:R:1,][<owner>.]<table>:R|B:<degree>,...)

# definition of info cube tables# [<owner>.]<table> | [<owner>.]<prefix>* | (<object_list>)# default: from RSNSPACE control table# stats_info_cubes = (/BIC/D*, /BI0/D*, ...)

The most important parameters for our example are:

� split_options

Points to the Data Protection for IBM ESS for mySAP (see 11.4.3, “Tivoli Storage Manager for Hardware: Data Protection for IBM ESS for mySAP™” on page 319)

– -d causes a disk-only backup– -n1 and -n2 selects different ESS target sets to be used for the FlashCopy operation

� split_resync

Should be set to yes or has to be done manually before next running the brbackup command

� util_par_file

Points to the Data Protection for mySAP configuration file, initSID.utl

The initSID.utl file (initRED.utl in this example) contains information for Tivoli Storage Manager parameters, as shown in Example 11-4.

Example 11-4 initRED.utl

# --------------------------------------------------------------------------## Data Protection for mySAP(R) interface for ORACLE## Sample profile for Data Protection for mySAP(R) Version 5.3 for UNIX## --------------------------------------------------------------------------


## This file should be renamed to $ORACLE_HOME/dbs/init$ORACLE_SID.utl# where $ORACLE_HOME is the home directory of the Oracle database and# $ORACLE_SID is the system ID of the Oracle database.# Default is '/oracle/C21/initC21.utl'.## See the 'Data Protection for mySAP (R) Installation & User's Guide'# for a full description.## For a comment symbol the character '#' can be used.# Everything following this character will be interpreted as comment.## Data Protection for mySAP (R) V5R3 accesses its profile in "read only"# mode only. All variable parameters like passwords, date of last# password change, current version number will be written into the file# specified with the CONFIG_FILE parameter. The passwords will be encrypted.### --------------------------------------------------------------------------# Prefix of the 'Backup ID' which will be used for communication with SAPDBA# and stored in the description field of the Tivoli Storage Manager archive# function.# Maximum 6 characters.# Default: none.# --------------------------------------------------------------------------### --------------------------------------------------------------------------# Number of total parallel sessions to be established. Note: this number should correspond # with the number of simultaneously available tape drives specified for the Tivoli Storage# Manager server.# Default: none.# --------------------------------------------------------------------------BACKUPIDPREFIX RED___MAX_SESSIONS 3 # 1 Tivoli Storage Manager client session is default### --------------------------------------------------------------------------# Number of parallel sessions to be established for the database backup.# Note: this number must not exceed the number of tape drives simultaneously available to # the node for a database backup on the Tivoli Storage Manager servers to be accessed.# Default: MAX_SESSIONS.# --------------------------------------------------------------------------# MAX_BACK_SESSIONS 1 # 1 Tivoli Storage Manager client session for backup### --------------------------------------------------------------------------# Number of parallel sessions to be established for the redo log backup.# Note: this number must not exceed the number of tape drives simultaneously available to # the node for a database backup on the Tivoli Storage Manager servers to be accessed.# Default: MAX_SESSIONS.# --------------------------------------------------------------------------MAX_ARCH_SESSIONS 1 # 1 Tivoli Storage Manager client session for archive### --------------------------------------------------------------------------# Number of parallel sessions to be established for the restore of files. # Note: this number must not exceed the number of tape drives simultaneously available to


# the node for a processing backup on the Tivoli Storage Manager servers to be accessed.# Default: MAX_SESSIONS.# --------------------------------------------------------------------------MAX_RESTORE_SESSIONS 1 # 1 Tivoli Storage Manager client session for restore### --------------------------------------------------------------------------# Number of backup copies of logs. The valid range of REDOLOG_COPIES is from 1 to 9.# Default: 1.# --------------------------------------------------------------------------# REDOLOG_COPIES 2 # 1 is default### --------------------------------------------------------------------------# Specifies whether a null block compression of the data is to be performed# before they are transmiission Tivoli Storage Manager. The null block compression # consumes only little cpu resources. This compression in Data Protection for# MySAP is independent from the Tivoli Storage Manager compression.# Do not compress twice!# Default: NO# --------------------------------------------------------------------------RL_COMPRESSION NO # NO is default### --------------------------------------------------------------------------# Specifies how many files are to be read simultaneously and multiplexed into one # data stream to a Tivoli Storage Manager server. Multiplexing is useful when the data# rate to a Tivoli Storage Manager server is higher (fast tapes, fast network)# than the I/O rate from a single disk.# The valid range of MULTIPLEXING is from 1 to 8.# Default: 1 (meaning no multiplexing)# --------------------------------------------------------------------------# MULTIPLEXING 3 # 1 is default### --------------------------------------------------------------------------# Specifies the block size for disk I/O (in bytes). The valid range is# from 4 KB to 32 MB.# The default values have been chosen from our performance experiments in# standard hardware environments.# Default: 131072 (128 KB) on UNIX, 32768 (32 KB) on Windows NT.# --------------------------------------------------------------------------BUFFSIZE 131072 # block size in bytes### --------------------------------------------------------------------------# --------------------------------------------------# This optional parameter controls how Data Protection for mySAP (R) uses the # internal buffers for transferring data during a backup.#Valid values: SIMPLE | PREVENT | AUTO# Default: SIMPLE# --------------------------------------------------# BUFFCOPY AUTO# Name of a program to be called before the backup task is started.# Default: none.# --------------------------------------------------------------------------# FRONTEND pgmname parameterlist##


# --------------------------------------------------------------------------# Name of a program to be called by after the backup task is completed.# Default: none.# --------------------------------------------------------------------------# BACKEND pgmname parameterlist### --------------------------------------------------------------------------# Maximum number of data base backup versions to be kept.# Note: Version control by Data Protection for mySAP is only# activated if the SAP R/3 release is 3.0C and higher and the parameter# MAX_VERSION is not 0. The valid range of MAX_VERSIONS is from 0 to 9999. Value# of 0 means no versioning.# Default: 0.# --------------------------------------------------------------------------MAX_VERSIONS 4### --------------------------------------------------------------------------# Indicates whether processing is to be done unattended or whether human # intervention is allowed.# Default: YES for the backup processing run and NO for restore processing.# --------------------------------------------------------------------------BATCH YES # unattended automated operation# BATCH NO # manual operation### --------------------------------------------------------------------------# Control of error situations: Indicates whether and when database backups # and restore operations should be ended when an error occurs during unattended # processing.# Valid values:# YES: exit wehn a single file cannot be backed up or restored.# NO: do not exit when an error occurs.# a number of errors resulting in exiting the processing. # the valid range for this number is from 0 to 100.# Default: NO.# --------------------------------------------------------------------------# EXITONERROR 3 # exit after 3 errors### --------------------------------------------------------------------------# Control of information for reporting purposes, e.g. messages, statistics.# Default: NO (no additional data will be reported).# --------------------------------------------------------------------------# REPORT NO # no additional messages# REPORT YES # all additional messagesREPORT 2 # all additional messages + summary### --------------------------------------------------------------------------# Controls generation of a trace file.# Note: we recommend using the trace function only in cooperation with# Data Protection for mySAP support.# Default: OFF.# --------------------------------------------------------------------------TRACE 70### --------------------------------------------------------------------------


# The full path name of the trace file .# Note: for an actual trace the string '%BID' will be replaced by# the current backupid.# (.../backint_%BID.trace changes to .../backint_SAP___9809182300.trace).# Default: none# --------------------------------------------------------------------------# TRACEFILE /oracle/C21/dbs/backint.traceTRACEFILE /oracle/RED/saparch/backint_%BID.trace### --------------------------------------------------------------------------# Specify the full path name of the configuration file.# Default: none.# --------------------------------------------------------------------------CONFIG_FILE /oracle/RED/920_64/dbs/initRED.bki### --------------------------------------------------------------------------# Number of times to retry backup/restore of a file in case an error occurs.# The valid range of FILE_RETRIES is from 0 to 100..# Default: 3.# --------------------------------------------------------------------------# RETRY 5### --------------------------------------------------------------------------# Specify time after which a retry has to be performed (seconds).# Default: 1.# --------------------------------------------------------------------------# TCPWAIT 1### --------------------------------------------------------------------------# Number of times Data Protection for mySAP retries to save/restore# a file in case an error occurs.# Default: 3.# --------------------------------------------------------------------------# FILE_RETRIES 3### --------------------------------------------------------------------------# Send error/status information # to a Tivoli Storage Manager server. The # servername must # match one of the servers listed in a SERVER statement. # Statements for # verbosity are ERROR, WARNING, or DETAIL.# Default: none.# --------------------------------------------------------------------------# LOG_SERVER servername [verbosity]# LOG_SERVER server_a ERROR### --------------------------------------------------------------------------# Denotes if Data Protection for mySAP shall use a manual sorting file for disk# sorting?# Default: none.# --------------------------------------------------------------------------# SORT_FILE /oracle/C21/dbs/manual_sort_file### **************************************************************************# Statement for multiple Servers and multiple Paths.


# may be used multiple times (one for each server).# **************************************************************************#### SERVER server_b # Servername# SESSIONS 2 # Max sessions# PASSWORDREQUIRED YES # Use a password# ADSMNODE NODE # Tivoli Storage Manager Nodename# BRBACKUPMGTCLASS MDB # Mgmt-Classes# BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes## **************************************************************************# Default: all days# **************************************************************************### --------------------------------------------------------------------------###MAX_BACK_SESSIONS 1SERVER server_a # ServernameADSMNODE REDP # Tivoli Storage Manager NodenameBRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-ClassesBRBACKUPMGTCLASS MDB # Mgmt-ClassesPASSWORDREQUIRED YES # Use a passwordSESSIONS 3 # Max sessions# USE_AT 0 1 2 3 4 5 6 # Days for backupFCS_FILE /oracle/RED/920_64/dbs/initRED.fcsEND

We left most of the parameters at the default values. However, you should tune your environment accordingly. IBM Tivoli Storage Manager for Hardware - Data Protection for IBM ESS for mySAP, Installation and User’s Guide for Oracle, SC33-8205.

The SERVER parameter points to the Tivoli Storage Manager server stanza in the dsm.sys file for the Tivoli Storage Manager client.

The initRED.bki file is a binary file that is used for storing the different runtime parameters. It cannot be edited directly.

Figure 11-4 on page 318 shows the relationships between the different configuration files.


Figure 11-4 Configuration files of Data Protection for mySAP

Next, you have to set the Tivoli Storage Manager password. Because the password gets encrypted in the initRED.bki file, you only need to set it on one machine, as shown in Example 11-5.

Example 11-5 Setting the Tivoli Storage Manager password

t1:orared> backint -p initRED.utl -f password

Data Protection for mySAP(R)

Interface between SAPDBA Utilities and Tivoli Storage Manager - Version 5, Release 3, Modification 0 for AIX LF 64-bit - Build: 257 compiled on Nov 23 2004 (c) Copyright IBM Corporation, 1996, 2004, All Rights Reserved.

BKI2027I: Using TSM-API version 5.3.0.0 (compiled with 5.3.0.0).BKI2000I: Successfully connected to ProLE on port tdpr3ora64.BKI0005I: Start of program at: Tue Mar 22 18:25:36 NFT 2005 .BKI2017I: Blocksize is set to 131072 bytesBKI0049I: Please enter password for node REDP on server SERVER_A:BKI0051I: Password successfully verified for node REDP on server SERVER_A.BKI0020I: End of program at: Tue Mar 22 18:25:41 NFT 2005.BKI0021I: Elapsed time: 05 sec..BKI0024I: Return code is: 0.t1:orared>

At this point, you should be able to do regular Tivoli Storage Manager backups from the production system to the Tivoli Storage Manager server. All backup types can be used except online_mirror and offline_mirror using FlashCopy, which only can be used in conjunction with Tivoli Storage Manager for Hardware which is shown in the next section. In other words, any backups run at this time are not exploiting the FlashCopy ESS function but can only be done from the production server. Using the ESS function (Tivoli Storage Manager for Hardware) allows the time spent offline in the database to be minimized because the backup is taken from the FlashCopy target instead of the actual production disks.


init<SID>.bki

init<SID>.sap

backup_dev_type = util_file...

util_par_file = .../init<SID>.utl

dsm.sysSERVERNAME

...

init<SID>.utl

CONFIG_FILE...

SERVERNAME

dsm.opt

empty file


11.4.3 Tivoli Storage Manager for Hardware: Data Protection for IBM ESS for mySAP™

You must install Data Protection for IBM ESS for mySAP on both the production database server machine (the production system) and on the backup system where the brbackup utility for mySAP with FlashCopy disk backups will run.

If there are multiple database instances, Data Protection for IBM ESS for mySAP must be installed on each production system and once on the common backup system.

Each production system running Data Protection for IBM ESS for mySAP to a common backup system must use a different Oracle SID.

The version/maintenance level of Data Protection for IBM ESS for mySAP (splitint) that is used for the FlashCopy of one database instance (SID) must be the same on the production and backup systems.

After installing Data Protection for IBM ESS for mySAP, you must run setup.sh for each specific database instance (SID) on the production system as well as on the backup system.

This approach permits the production systems to have different version/maintenance levels.

Base installationTo install Data Protection for IBM ESS for mySAP:

1. Log in as user ID root on the system to be installed.

2. The install package is delivered as a single executable file named install_tdpessr3_ora.bin on the installation media.

3. Ensure that the environment variable DISPLAY is set to <host>:display, where <host> identifies the host name of the X Server to be contacted and display is the display number. Alternatively, you can use the -console parameter to use a non X installation.

4. Run the install_tdpessr3_ora.bin executable and follow the instructions.

5. Check the summary on the last dialog panel for successful installation. If an error occurs during the installation process, check for the error message in the output panel carefully and correct the problems. After correcting the error(s), repeat the installation procedure beginning at step 3.

Data Protection for IBM ESS for mySAP is installed in the /usr/tivoli/tsm/tdpessr3/oracle directory. Check the readme file for a brief description of all installed files. The directory contains the executables, which are accessed by the setup.sh script that is run after the base installation.

Post-installationFor the proper functioning of Data Protection for IBM ESS for mySAP, after installation, run the setup.sh script. This script does the following:

1. Renames the Data Protection for IBM ESS for mySAP profile (init<SID>.fcs) and copies it to the /oracle/RED/920_64/dbs directory.

2. Copies the splitint interface for mySAP to a version/maintenance level directory.

3. Creates a softlink to the splitint interface for mySAP in the mySAP executables path.


To run the script:

1. Log in as root and enter the following command:

/usr/tivoli/tsm/tdpessr3/oracle/setup.sh

2. Enter the system ID (SID) for the mySAP system to be backed up (in this example, RED).

3. Enter the path for the mySAP executables, normally found in the /usr/sap/RED/sys/exe/run directory. If appropriate, you can use the suggested default by pressing Enter.

4. Enter the path for the Data Protection for IBM ESS for mySAP profile (initRED.fcs). If appropriate, you can use the suggested default by pressing Enter. This must be an NFS directory.

The Data Protection for IBM ESS for mySAP installation procedure is complete when you have run the installation on the production and backup systems.

Now, you must enter the necessary information in the initRED.fcs configuration file, as shown in Figure 11-6.

Example 11-6 initRED.fcs

################################################################# 5.3.0 # ################################################################# This profile contains setup information for# IBM Tivoli Storage Manager for Hardware - Data Protection for IBM ESS for mySAP(R) # on Oracle(R)## as described in the manual# “IBM Tivoli Storage Manager for Hardware - Data Protection for IBM ESS for mySAP(R) # on Oracle(R) Installation and User's Guide"## This profile is referred to there and here as the# TDP for ESS profile.## For a full description see the above referenced manual.#### File name: init<SID>.fcs# Directory: /oracle/<SID>/dbs# where <SID> stands for the used Oracle System ID.# In R/3 environments, 3 character System IDs are# used. In the sample, A01 is used as the System ID.# Usage :# Whenever TDP for ESS will be used, a profile has to# be passed along with the TDP for ESS command splitint# as the value of the -p parameter, for example:## splitint -f xxxxxx -p /oracle/<SID>/dbs/init<SID>.fcs## where xxxxxx stands for a function of TDP for ESS# (resynch, withdraw, unmount, inquire, password or# query) being performed by splitint.

Note: The setup.sh script ensures that several levels of Data Protection for IBM ESS for mySAP (splitint) can be used simultaneously on the backup and various production systems.


### With the product deliverables, you get the sample file# initSID.fcs. If you have not used the install script,# rename it to $ORACLE_HOME/dbs/init$ORACLE_SID.fcs,# where $ORACLE_HOME is the home directory of the Oracle database.## In the sample the name /oracle/A01/dbs/initA01.fcs is used.### Rules for the profile setup must be followed as shown:# - Directory names and files names are case sensitive# - All directories and file names must be available# via NFS mounts on the production (here: columbus)# or backup system (here: magellan)

# Any comments must start with the character '#' in column 1.## Tabs should not be used.

# Layout of the profile# The profile is divided into topics. The present# release contains the following topics:# global and# shark_data# Each topic has a unique set of specific parameters, of which# some are required and some will default to a value.# Each topic is enclosed by a topic begin statement (>>>) and a# topic end statement (<<<) followed by the topic name separated# by a blank character.

# Parameters of the 'global' topic>>> global

#------------------------------------------------------------------## LOGON_HOST_PROD (changed with TDP for ESS 1.1.10.1)# Defines the parameters needed to reach the production system# on which the R/3 database server is running.## The syntax with 2 parameters is:## LOGON_HOST_PROD tcp_name userid## where tcp_name is the TCP/IP name or the dot address under# which the production system can be reached# using rexec services# (here called columbus_et)## userid is the R/3 userid ora<sid> (here called oraa01)# The password for this userid has to be provided# - once TDP for ESS has been installed - using# the password function of TDP for ESS and will be# encrypted and stored in the file specified in# CONFIG_FILE.#### The syntax with 3 parameters (introduced with 1.1.0.3 is still# working however the 1st parameter is not any longer checked# to be true) is:


## LOGON_HOST_PROD hostname tcp_name userid## where hostname is the host name (result of hostname command)# of the production system (here called columbus).# tcp_name is the TCP/IP name or the dot address of the# production system.# (here called columbus_et)# userid is the R/3 userid ora<sid> (here called oraa01)# The password for this userid has to be provided# - once TDP for ESS has been installed - using# the password function of TDP for ESS and will be# encrypted and stored in the file specified in# CONFIG_FILE.#### Parameter definition is required.#------------------------------------------------------------------#LOGON_HOST_PROD s1 orared

#------------------------------------------------------------------## LOGON_HOST_BACK# Defines the host name of the backup system (as a result of the# hostname command) on which the R/3 DBA tool brbackup will be# started with a FlashCopy request for TDP for ESS# (here called magellan).## Once the task for this request has finished, brbackup will# start the backup on the backup system by calling# Tivoli Data Protection for R/3.## Parameter definition is required.#------------------------------------------------------------------#LOGON_HOST_BACK t1

#------------------------------------------------------------------## BACKUP_MAX# Defines the number of backup cycles kept in the directory of the# IDS_CONTROL_FILE path; if BACKUP_MAX is reached,# the logs and traces belonging to a backup cycle will also be# deleted (see also LOG_TRACE_DIR).# Parameter definition is optional.# Default: 30#------------------------------------------------------------------#BACKUP_MAX 30

#------------------------------------------------------------------## IDS_CONTROL_FILE# Defines the file which contains the summary information# of such a backup cycle entry. TDP for ESS will create an entry# in this file each time it starts a FlashCopy on behalf of a# FlashCopy request by R/3 DBA tool brbackup.## This file must be reachable via an NFS setup from the production# and backup systems.# In the sample, /oracle/A01/sapbackup is already available


# as an NFS directory.## Parameter definition is required.#------------------------------------------------------------------#IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssave

#------------------------------------------------------------------## CONFIG_FILE# Defines the file which contains the information required# when the backup system needs to work with other hosts# like the production system.## The file will be created by calling the password function of# TDP for ESS, once it had been installed, and each time the# password of the ora<sid> user (here in our sample oraa01) has# been changed.## This file must be reachable via an NFS setup from the production# and backup systems.# In the sample, /oracle/A01/dbs is already available# as an NFS directory.## Parameter definition is required.#------------------------------------------------------------------#CONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcp

#------------------------------------------------------------------## WORK_DIR# Specifies the directory where temporary files will be written# by TDP for ESS.# This file must be reachable via an NFS setup from the production# and backup systems.# In the sample, /oracle/A01/dbs is already available# as an NFS directory.## Parameter definition is required.#------------------------------------------------------------------#WORK_DIR /oracle/RED/sapbackup/work

#------------------------------------------------------------------## TRACE# Controls the generation of a trace file.# Note: we recommend using the trace function# - at implementation time and# - in cooperation with the hotline## Parameter definition is optional.# Default: YES#------------------------------------------------------------------#TRACE YES

#------------------------------------------------------------------## LOG_TRACE_DIR# Specifies the directory for log and trace files to be written# by TDP for ESS.# Trace files will be written to this directory if TRACE ON is


# specified in the TRACE parameter.## This file must be reachable via an NFS setup from the production# and backup systems.# In the sample, /oracle/A01/dbs is already available# as an NFS directory.## Parameter definition is optional.# Default: if not specified, logs and traces will be written to the# directory specified as the WORK_DIR parameter.#------------------------------------------------------------------#LOG_TRACE_DIR /oracle/RED/sapbackup/logtraces

#------------------------------------------------------------------## SUPPORT_ADMIN_ASSISTANT# Defines whether TDP for ESS sends its log records to# the TDP for R3 Administrator Assistant.# For proper setup of the Administrator Assistant see the# TDP for R/3 Installation and User's Guide## Possible parameter values: YES | NO## Parameter definition is optional.# DEFAULT value : NO#------------------------------------------------------------------#SUPPORT_ADMIN_ASSISTANT NO

#------------------------------------------------------------------## PROLE_SERVICE_NAME# This parameter specifies the service name with which DP for ESS# communicates with DP for mySAP prole to provide information# to the Administrator Assistant.# The service name is defined by DP for mySAP at installation# time in /etc/services. Check this file.# This parameter is required only if SUPPORT_ADMINISTRATOR_ASSISTANT# is set to YES.## Default: (no name provided)#------------------------------------------------------------------## PROLE_SERVICE_NAME tdpr3ora64 | tdpr3ora<<< global

# Parameters of the 'shark_data' topic>>> shark_data#------------------------------------------------------------------## The 'shark_data' topic contains all the parameters# required to let TDP for ESS use the ESS CopyServices CLI# to request ESS FlashCopy, withdraw, and inquire# operations on the primary server of an ESS Cluster in which the# volumes of interest reside.## To access the ESS, a username and password# are required. You will get the username and the# password from the ESS administrator, who likely has also# set up for you# the ESS (source) volumes to allow you to install R/3 with# an Oracle DB and# the ESS (target) volumes#


## The password for this username has to be provided - once# TDP for ESS has been installed - using the password function# of TDP for ESS and will be encrypted and stored in the file# specified in CONFIG_FILE (see above).#------------------------------------------------------------------#

#------------------------------------------------------------------## JAVA_HOME_DIRECTORY# Defines the directory of the Java runtime executables## Parameter definition is required.#------------------------------------------------------------------#JAVA_HOME_DIRECTORY /usr/jdk_base

#------------------------------------------------------------------## SHARK_COPY_SERVICE_CODE# Defines the directory into which the complete ibm2105 installation# package (ESS Copy Services code) was installed.## For IBM2105 Command Line Interface 1.1 the install path is# /usr/opt/ibm2105cli## Parameter definition is required.#------------------------------------------------------------------#SHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105cli

#------------------------------------------------------------------## SHARK_SERVERNAME_PRIMARY# Defines the DNS or TCP/IP address of the primary ESS Copy# Services server of the ESS cluster you plan to have# TDP for ESS work with.# Should the primary ESS Copy Services Server not be reached,# TDP for ESS will try the connection to the backup Copy Services# Server.## Parameter definition is required.#------------------------------------------------------------------#SHARK_SERVERNAME_PRIMARY 172.31.1.15

#------------------------------------------------------------------## SHARK_SERVERNAME_BACKUP# Defines the DNS or TCP/IP address of the backup ESS Copy# Services server of the ESS cluster you plan to have# TDP for ESS work with.# Should the backup ESS Copy Services Server not be reached as well# TDP for ESS will terminate with an error message.## Parameter definition is required.#------------------------------------------------------------------#SHARK_SERVERNAME_BACKUP 172.31.1.19

#------------------------------------------------------------------## SHARK_USERNAME# Defines the username which was set up in the ESS# to work with the ESS Copy Services Server.## Parameter definition is required.#------------------------------------------------------------------#SHARK_USERNAME ess


#------------------------------------------------------------------## FLASHCOPY_TYPE# Defines whether the ESS performs a NOCOPY or a COPY.# COPY results in a bit-by-bit copy of data from one physical volume# (source) to another physical volume (target).## Possible parameter values: INCR | COPY | NOCOPY## Parameter definition is optional.# DEFAULT: COPY#------------------------------------------------------------------#FLASHCOPY_TYPE COPY

#------------------------------------------------------------------## SHARK_VOLUMES_FILE# Defines the fully qualified file name containing a list of all# target volumes planned for use by serial number.# The specified file must be reachable via the NFS setup.## To distinguish this from other profiles and control files,# define the character string 'fct' as the name suffix.## Parameter definition is required.#------------------------------------------------------------------#SHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fct

#------------------------------------------------------------------#

<<< shark_data

#------------------------------------------------------------------#

The SHARK_VOLUMES_FILE parameter points to the initRED.fct configuration file, which contains the target volume IDs to be used for the FlashCopy procedure (Example 11-7).

Example 11-7 initRED.fct

#=====================================================================##===#=== This file contains setup information about source/target volumes#=== as they will be used in the flashcopy function.#=== The file will be pointed to by the file name specified#=== in the SHARK_VOLUMES_FILE parameter of the#=== 'Data Protection for ESS for mySAP' profile#=== (if standard naming conventions have been used then#=== this would be /oracle/<SID>/dbs/init<SID>.fcs)#===#=== It is required to embed the SHARK_TARGET_VOLUMES parameter#=== between the topic start parameter (>>>shark_volume_set_x)#=== and topic end parameter (<<<shark_volume_set_x) where x should#=== indicate the TargetVolumeSet you would like to use.#=== 'Tivoli Data Protection for ESS for R/3 ' V1R1 supports only#=== shark_volumes_set_1#===#===#===#=== Example:


#=== File name (suggested): init<SID>.fct#=== Directory (suggested): /oracle/<SID>/dbs#===#=== ATT: on the parameter statement SHARK_TARGET_VOLUME#=== 1st value is target_volume_serial_number#=== 2nd value is source_volume_serial_number or -#=== 3rd value is Size=2.0_GB or -#===#=== If you specify source volume serial number and size,#=== you must ensure the target volume size is the same.#=====================================================================#

>>> shark_volumes_set_1#=====================================================================##SHRK_ID_LVM_MIRROR 23376## Use this parameter only in case of an AIX LVM Mirror environment.# It defines the serial number of the ESS machine which# contains a complete set of at least 1 copy of all DB LVs# which shall become object of the backup process.# Only the ESS source volumes of the specified ESS will be used# on the production system by DP for ESS for the flashcopy process.## Possible parameter values : XXXXX# where XXXXX is the 5 digit ESS box serial number.# It must be whithin the topic >>> shark_volumes_set_x .## Parameter definition can o n l y be used if an appropriate# setup had been done as defined in the DP for ESS manual.## DEFAULT : NOT DEFINED##=====================================================================#SHARK_TARGET_VOLUME 1A323376 1A023376 6.10_GBSHARK_TARGET_VOLUME 1A423376 1A123376 6.10_GBSHARK_TARGET_VOLUME 1A523376 1A223376 6.10_GBSHARK_TARGET_VOLUME 33123376 32F23376 6.10_GBSHARK_TARGET_VOLUME 33223376 33023376 6.10_GBSHARK_TARGET_VOLUME 19B23376 19A23376 1.50_GBSHARK_TARGET_VOLUME 35A23376 35923376 1.50_GB<<< shark_volumes_set_1#=====================================================================## Fill in the topic shark_volumes_set_2 only in case of LVM mirror or # if you want to maintain multiple FlashCopy backup versions (multiple # target sets)#=====================================================================##>>> shark_volumes_set_2#SHARK_ID_LVM_MIRROR 13158#SHARK_TARGET_VOLUME 51913158 - -#SHARK_TARGET_VOLUME 52013158 - -# ...#<<< shark_volumes_set_2

This example shows all the source and target volume serial numbers and the sizes, which were filled in after the first backup run. However, when configuring the file initially, we recommend that you enter in lines of the following format:

SHARK_TARGET_VOLUME 1A323376 - -


That is, enter a line for each target volume with the other parameters (source volume and size) replaced by a dash. In this case, providing that there are sufficient target volumes of the correct size (matching the source volumes), Data Protection for IBM ESS for mySAP finds the source volumes and the sizes automatically and updates the information in the .fct file as shown in our example. The file is updated when the first backup operation is initiated. (You could run a test backup where no data is sent, using the brbackup -q command.)

Figure 11-5 shows the relationships between the various configuration files in detail.

Figure 11-5 mySAP backup environment: configuration files

The initRED.fcp file is a binary file which stores the compiled information retrieved from the other configuration files. It cannot be edited manually.

Now, you need to set the passwords for the orared user and the ess user on the ESS Copy Services server, using the splitint interface for mySAP (Example 11-8).

Example 11-8 Setting the orared and ess user passwords

t1:orared> splitint -p initRED.fcs -f password

IBM Tivoli Storage Manager for Hardware Data Protection for IBM ESS for mySAP(R) on Oracle(R)

BR*Tools Interface SPLITINT for the IBM Enterprise Storage Server - Version 5, Release 3, Level 0 for AIX (32 Bit) - Build: 225 generated at 15:09:41 on Mar 21 2005 (c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.

IDS1310W The free space in the file system containing the directory / is only 27.55 MB (9 percent).IDS1411I The intended FlashCopy type has a value of 'INCR'.Profile initRED.fcsLog file splitint_?_20052203183101.logTrace file splitint_?_20052203183101.trace

init<SID>.fcp

Backup SystemProductionSystem / DB Server

init<SID>.sap

split_options = "... init<SID>.fcs ..."split_resync = "..."primary_db = <SID>.WORLDbackup_type = ...backup_dev_type = util_file

...

util_par_file = .../init<SID>.utl

init<SID>.utl

FCS_FILECONFIG_FILE

...

SERVERNAME

>>> shark_volumes_set_1SHARK_TARGET_VOLUME ...SHARK_TARGET_VOLUME ...SHARK_TARGET_VOLUME ...<<< shark_volumes_set_1

CONFIG_FILESHARK_VOLUMES_FILE...

init<SID>.bki

dsm.sysSERVERNAME

...

dsm.opt

empty file

init<SID>.fct

init<SID>.fcs

dsm.sysSERVERNAME

...

dsm.opt

empty file

NFS mounts via GigaBit Network


-- Parameters of splitint profile --

LOGON_HOST_PROD s1 oraredLOGON_HOST_BACK t1BACKUP_MAX 30IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssaveCONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcpWORK_DIR /oracle/RED/sapbackup/workTRACE YESLOG_TRACE_DIR /oracle/RED/sapbackup/logtracesSUPPORT_ADMIN_ASSISTANT NOJAVA_HOME_DIRECTORY /usr/jdk_baseSHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105cliSHARK_SERVERNAME_PRIMARY 172.31.1.15SHARK_SERVERNAME_BACKUP 172.31.1.19SHARK_USERNAME essFLASHCOPY_TYPE INCRSHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fctIDS1015I Start of splitint program at: 03/22/05-18:31:01.Function passwordIDS1051I: Enter the password for the user 'orared' :IDS1052I: Enter the password for the user 'orared' again:IDS1051I: Enter the password for the user 'ess on the ESS' :IDS1052I: Enter the password for the user 'ess on the ESS' again:IDS1023I Exiting with return code 0.t1:orared>

The environment is now set up to allow the actual backup and restore commands to be run.

11.4.4 Backup and restore commandsThe commands that are used for backup and restore are:

� brbackup utility for mySAP

Starts the actual backup run.

– -h shows help– -c is no-prompt batch mode– -t overrides the backup mode, for example, online_mirror– -q simulates actions and checks settings

� splitint interface for mySAP

Can be used to perform manual actions on the ESS subsystem and is also called by the brbackup utility to perform the ESS-specific functions.

– -f inquire or ts_inquire shows status of target volumes– -f unmount unmounts target volumes from backup system in case of an error

� tdpessora

Used for querying the status of FlashCopy based backups and for restoring backups.

The following types of backups can be taken:

� On the backup system (disk-only as well as Tivoli Storage Manager backups are possible)

– Full database offline FlashCopy backup (brbackup -t offline_mirror)– Full database online FlashCopy backup (brbackup -t online_mirror)


� On the production system (all backups are Tivoli Storage Manager backups)

– Full/partial database offline/online backup (for example, brbackup -t offline)– Incremental database backup (brbackup...)– Backup of the offline redo log files (brarchive)

� Non-database related files (Tivoli Storage Manager Backup-Archive Client)

� Base system related files (operating system specific methods such as mksysb)

11.5 BackupThere are different types of backups available. You can choose between online-mirror and offline-mirror backups that are combined with the ESS FlashCopy modes NOCOPY, COPY, and INCR. Furthermore, you can choose whether to do disk-only backups or transfer the data to Tivoli Storage Manager.

Figure 11-6 shows the different steps that are executed during a backup run.

Figure 11-6 FlashCopy backup scheme

The following sections contain examples that explain the different phases.


2

Sourcevolumes

(SVs) IBMESS

Targetvolumes

(TVs)

ESS Copy Services

mySAPDB server Backup Server

7

1

26

Oracleproduction server

Production system Backup system

OracleRemote Client

DP for mySAP(backint) with

-t offline_mirroror

-t online_mirror

Backup Part 2

Backup Part 1

DP for mySAP(backint)

mySAPutilitybrbackup

mySAPutilities

brbackupbrarchivebrrestore

(not involvedin FlashCopy

Backup)DP for ESS

(splitint)DP for ESS

(splitint)

LVM LAN LVM

2 spl i t i nt- Det er mi ne r el at i on of

DB f i l es t o physi calvol umes( ESS sour ce vol umes)

4 spl i t i nt- On pr oduct i on syst em

- Per f or m Fl ashCopy( I NCR, COPY, NOCOPY)and exi t

- On backup syst em- St ar t Fl ashCopy agent

8 spl i t i nt - f r esynconl y i f spl i t _r esync = yes:- unmount f i l e syst ems

on backup syst em( COPY, I NCR, NOCOPY) and

- wi t hdr aw t ar get vol umes( NOCOPY)

1 br backup- r emot e connect i on- get f i l e l i st s

3 spl i t i nt- r equest DB backup mode

and wai t

5 spl i t i nt- r equest DB nor mal mode

6 spl i t i nt- i mpor t / var yon VGs of TVs- mount f i l esyst ems

7 backi nt - f backup- exchange i nf o wi t h spl i t i nt- backup dat abase t o

I TSM ser ver- backup l ogs and pr of i l es t o

Ti vol i St or age Manager ser ver

,31’ 3’

5’

1 3

5

7 7

7

2 4 438

56

8’4’

,3,5,8

,4


11.5.1 FlashCopy Backup OFFLINE_MIRROR NOCOPY to Tivoli Storage Manager

This example executes an offline database backup using FlashCopy and transfers the tablespace data files to Tivoli Storage Manager. It uses the FlashCopy NOCOPY method, so that the FlashCopy takes only minutes to complete. However, it is not eligible for a FlashBack restore. The restore has to be done from Tivoli Storage Manager.

If instead it used the COPY option, the data would be fully copied in the background to the target volumes. This target set would then be eligible as a FlashBack restore source.

Figure 11-7 shows the schema of the action taken.

Figure 11-7 OFFLINE_MIRROR backup method

To get an OFFLINE_MIRROR backup you have to change the SPLIT_OPTIONS parameter in the initRED.sap file or call brbackup with -t offline_mirror to override the options in the configuration file. To get the NOCOPY FlashCopy mode, append -C NOCOPY to the SPLIT_OPTIONS parameter in the initRED.sap file or change the FLASHCOPY_TYPE parameter in the initRED.fcs configuration file (see Figure 11-6 on page 320).

In this example, we changed the file initRED.sap file to indicate NOCOPY, so we can call just brbackup with the batch flag -c. The output of this command is very long. Example 11-9 shows the first part. It displays a summary of the operation to be performed and determines the resources required for the requested task.

Example 11-9 Output of brbackup offline_mirror, Tivoli Storage Manager, NOCOPY

t1:orared 1> brbackup -cBR051I BRBACKUP 6.400 (116+)BR055I Start of database backup: bdpnlfyi.aff 2005-03-18 01.33.24BR280I Time stamp 2005-03-18 01.33.25BR295I Splitting mirror disks...BR278I Command output of '/usr/sap/RED/SYS/exe/run/splitint -u RED -f split -i /oracle/RED/sapbackup/.bdpnlfyi.lst -t offline -c -s -p /oracle/RED/920_64/dbs/initRED.fcs -C NOCOPY':

Tablespace files Tablespace files

ESS Source Volumes

Production System Backup System Backup System or Other System

VG1

VG2

ESS Target Volumes Backup to Tivoli Storage Manager

Complete DB Backup

DB control files DB control files

Online redo logs(origlog A/B)

Online redo logs(origlog A/B)

Online redo logs(mirrlog A/B)

Online redo logs(mirrlog A/B)

1st control file only

All files

All files

Not backed upseparately

ITSM

backint (part 1)splitint

brbackup



BR*Tools Interface SPLITINT for the IBM Enterprise Storage Server - Version 5, Release 3, Level 0 for AIX (32 Bit) - Build: 220 generated at 16:54:57 on Nov 25 2004 (c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.

IDS1411I The intended FlashCopy type has a value of 'NOCOPY'.Profile /oracle/RED/920_64/dbs/initRED.fcsLog file splitint_?_20051803013325.logTrace file splitint_?_20051803013325.trace


LOGON_HOST_PROD s1 oraredLOGON_HOST_BACK t1BACKUP_MAX 30IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssaveCONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcpWORK_DIR /oracle/RED/sapbackup/workTRACE YESLOG_TRACE_DIR /oracle/RED/sapbackup/logtracesSUPPORT_ADMIN_ASSISTANT NOJAVA_HOME_DIRECTORY /usr/jdk_baseSHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105cliSHARK_SERVERNAME_PRIMARY 172.31.1.15SHARK_SERVERNAME_BACKUP 172.31.1.19SHARK_USERNAME essFLASHCOPY_TYPE NOCOPYSHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fctIDS1005I Start of splitint program at: 03/18/05-01:33:25.EEO0020I ====>Performing DP FOR ESS BACKUP command.IDS1121I Getting the source volumes...Function getresourcesBackup list /oracle/RED/sapbackup/.bdpnlfyi.lstIDS1035I The IDS control file exists and a new backup cycle entry has been created.IDS1101I New assigned Backup Sequence Number 00002IDS1025I Time stamp: 03/18/05-01:33:34.

Next, we determine the relationship of the database files to physical volumes (ESS source volumes), as shown in Example 11-10.

Example 11-10 Getting source volumes

IDS1026I Start of splitint on the production system...



IDS1411I The intended FlashCopy type has a value of 'NOCOPY'.Profile /oracle/RED/920_64/dbs/initRED.fcsLog file splitint_?_20051803013325.logTrace file splitint_?_20051803013325.traceIDS1015I Start of splitint program at: 03/18/05-01:33:34.


Function getresourcesSubfunction performsplitBackup list /oracle/RED/sapbackup/work/.bdpnlfyi.lstEEO0022I AIX Version: 5300 Oslevel: 0.EEO0023I ESS CopyServices CLI Version: 2.3.EEO0362I Checking the status of the primary Copy Services Server: 172.31.1.15EEO0363I Primary Copy Services server is ready.EEO0156I Finding the serial numbers...IDS1404I The target set with ID '1' is selected for this run.Matching pair tgt: <1A323376> src: <1A023376> size: <6.10_GB>Matching pair tgt: <1A423376> src: <1A123376> size: <6.10_GB>Matching pair tgt: <1A523376> src: <1A223376> size: <6.10_GB>Matching pair tgt: <33123376> src: <32F23376> size: <6.10_GB>Matching pair tgt: <33223376> src: <33023376> size: <6.10_GB>Matching pair tgt: <19B23376> src: <19A23376> size: <1.50_GB>Matching pair tgt: <35A23376> src: <35923376> size: <1.50_GB>EEO0371I Value of Flashcopy type is: NOCOPY.EEO0359I Incremental Change Recording: Not SetEEO0381I Querying ESS for pending sectors for volume: 1A023376EEO0381I Querying ESS for pending sectors for volume: 1A123376EEO0381I Querying ESS for pending sectors for volume: 1A223376EEO0381I Querying ESS for pending sectors for volume: 32F23376EEO0381I Querying ESS for pending sectors for volume: 33023376EEO0381I Querying ESS for pending sectors for volume: 19A23376EEO0381I Querying ESS for pending sectors for volume: 35923376EEO0374I Querying ESS for status of volume: 1A023376EEO0374I Querying ESS for status of volume: 1A323376EEO0374I Querying ESS for status of volume: 1A123376EEO0374I Querying ESS for status of volume: 1A423376EEO0374I Querying ESS for status of volume: 1A223376EEO0374I Querying ESS for status of volume: 1A523376EEO0374I Querying ESS for status of volume: 32F23376EEO0374I Querying ESS for status of volume: 33123376EEO0374I Querying ESS for status of volume: 33023376EEO0374I Querying ESS for status of volume: 33223376EEO0374I Querying ESS for status of volume: 19A23376EEO0374I Querying ESS for status of volume: 19B23376EEO0374I Querying ESS for status of volume: 35923376EEO0374I Querying ESS for status of volume: 35A23376IDS1023I Exiting with return code 0.#INFO remote shell terminated successfullyIDS1027I Splitint ended successfully on the production system.IDS1025I Time stamp: 03/18/05-01:37:23.

Now, we shutdown the database, as shown in Example 11-11.

Example 11-11 Shutdown database

IDS1320I Setting the tablespaces in backup mode or, in case of type offline, the database will be shutdown.

BR280I Time stamp 2005-03-18 01.37.28#BEGIN SPLIT /tmp/yaaQWqnUy

BR280I Time stamp 2005-03-18 01.37.28BR307I Shutting down database instance RED/PRIMARY ..

BR280I Time stamp 2005-03-18 01.37.54BR308I Shutdown of database instance RED/PRIMARY successful


Next, we perform the actual backup, calling splitint on the production system to perform the FlashCopy, as shown in Example 11-12.

Example 11-12 Perform FlashCopy

IDS1122I Flashcopying the sources to the target volumes...Function flashcopy_onlyBackup list /oracle/RED/sapbackup/.bdpnlfyi.lstIDS1025I Time stamp: 03/18/05-01:37:58.

IDS1026I Start of splitint on the production system...



IDS1411I The intended FlashCopy type has a value of 'NOCOPY'.Profile /oracle/RED/920_64/dbs/initRED.fcsLog file splitint_?_20051803013325.logTrace file splitint_?_20051803013325.traceIDS1015I Start of splitint program at: 03/18/05-01:37:59.Function flashcopy_onlySubfunction performsplitEEO0022I AIX Version: 5300 Oslevel: 0.EEO0023I ESS CopyServices CLI Version: 2.3.EEO0371I Value of Flashcopy type is: NOCOPY.EEO0272I Flushing the buffers to disk...IDS1030I Flashcopy started...EEO0362I Checking the status of the primary Copy Services Server: 172.31.1.15EEO0363I Primary Copy Services server is ready.EEO0030I Number of ESS Volumes to be Flashcopied: 7EEO0354I Performing NOCOPY FlashCopy of source ESS volume 1A023376 to target ESS volume 1A323376EEO0354I Performing NOCOPY FlashCopy of source ESS volume 19A23376 to target ESS volume 19B23376EEO0354I Performing NOCOPY FlashCopy of source ESS volume 1A223376 to target ESS volume 1A523376EEO0354I Performing NOCOPY FlashCopy of source ESS volume 1A123376 to target ESS volume 1A423376EEO0354I Performing NOCOPY FlashCopy of source ESS volume 32F23376 to target ESS volume 33123376EEO0354I Performing NOCOPY FlashCopy of source ESS volume 35923376 to target ESS volume 35A23376EEO0354I Performing NOCOPY FlashCopy of source ESS volume 33023376 to target ESS volume 33223376EEO0366I Flashcopy was performed with NOCOPY option.IDS1031I Flashcopy successful.IDS1024I Exiting with return code 0.#INFO remote shell terminated successfullyIDS1027I Splitint ended successfully on the production system.IDS1025I Time stamp: 03/18/05-01:38:19.

After the FlashCopy is complete, we restart the database, as shown in Example 11-13 on page 335. Production can now resume on the production system.


Example 11-13 Start up database

IDS1321I The tablespaces will end the backup mode or, in case of offline_split, the database will be started.

BR280I Time stamp 2005-03-18 01.38.19#END SPLIT /tmp/zaadIqnUz

BR280I Time stamp 2005-03-18 01.38.19BR304I Starting and opening database instance RED/PRIMARY...

BR280I Time stamp 2005-03-18 01.38.29BR305I Start and open of database instance RED/PRIMARY successful

At this point, the production system no longer needs to be involved in the operation, and the actual backup is now taken on the backup system. The offline backup caused exactly 61 seconds of downtime to the mySAP database system. Next, we make the resources that are required (VGs and file systems) available to the backup system, as shown in Example 11-14.

Example 11-14 Varyon VGs, import VGs and mount file systems

EEO0371I Value of Flashcopy type is: NOCOPY.IDS1123I Enabling the volumes and filesystems...Function setresourcesBackup list /oracle/RED/sapbackup/.bdpnlfyi.lstIDS1076I Trying to set the semaphore for the critical part of importing/exporting...IDS1046I Start of listing of importing volume groups/mounting file systems...EEO0126I Trying to find new devices to match the source device. This process will take some time.......EEO0148I Importing volume groups now...EEO0149I Newly imported volume group: REDtdp1EEO0149I Newly imported volume group: REDtdp2EEO0124I Mounting filesystem: /oracle/RED/mirrlogA.EEO0124I Mounting filesystem: /oracle/RED/mirrlogB.EEO0124I Mounting filesystem: /oracle/RED/origlogA.EEO0124I Mounting filesystem: /oracle/RED/origlogB.EEO0124I Mounting filesystem: /oracle/RED/sapdata1.EEO0124I Mounting filesystem: /oracle/RED/sapdata2.EEO0124I Mounting filesystem: /oracle/RED/sapdata3.EEO0124I Mounting filesystem: /oracle/RED/sapdata4.EEO0124I Mounting filesystem: /oracle/RED/sapdata5.EEO0124I Mounting filesystem: /oracle/RED/sapdata6.IDS1077I Semaphore released.IDS1047I End of listing.IDS1025I Time stamp: 03/18/05-01:40:27.

BR280I Time stamp 2005-03-18 01.40.33BR629I SPLITINT command sent success message: #SUCCESSIDS1024I Exiting with return code 0.

BR280I Time stamp 2005-03-18 01.40.33BR296I Split of mirror disks successful

BR280I Time stamp 2005-03-18 01.40.34


We transfer the data from the backup system to Tivoli Storage Manager, as shown in Example 11-15.

Example 11-15 Backup data to Tivoli Storage Manager

BR057I Backup of database: REDBR058I BRBACKUP action ID: bdpnlfyiBR059I BRBACKUP function ID: affBR110I Backup mode: ALLBR077I Database files for backup:/oracle/RED/origlogA/log_g11m1.dbf/oracle/RED/origlogB/log_g12m1.dbf/oracle/RED/origlogA/log_g13m1.dbf/oracle/RED/origlogB/log_g14m1.dbf/oracle/RED/sapdata1/cntrl/cntrlRED.dbfBR061I 41 files found for backup, total size 24150.049 MBBR143I Backup type: offline_mirrorBR130I Backup device type: util_fileBR109I Files will be saved by backup utilityBR126I Unattended mode active - no operator confirmation required

BR280I Time stamp 2005-03-18 01.40.34BR229I Calling backup utility...BR278I Command output of '/usr/sap/RED/SYS/exe/run/backint -u RED -f backup -i /oracle/RED/sapbackup/.bdpnlfyi.lst -t file -p /oracle/RED/920_64/dbs/initRED.utl -c':



BKI2027I: Using TSM-API version 5.3.0.0 (compiled with 5.3.0.0).BKI2000I: Successfully connected to ProLE on port tdpr3ora64.BKI0005I: Start of program at: Fri Mar 18 01:40:34 NFT 2005.

-- Parameters --Input File : /oracle/RED/sapbackup/.bdpnlfyi.lstProfile : /oracle/RED/920_64/dbs/initRED.utlConflictive : /oracle/RED/920_64/dbs/initRED.bkiManual sorting file : disabledTracefile : /oracle/RED/saparch/backint_RED___A0E6FO2ZQM.traceTraceflags : FILEIO_MAX COMPR_MIN TSM_MINParallel sessions : 1Multiplexed files : 1RL compression : 0Retries for files : 3Exit on error : disabledBATCH : enabledBuffer size : 131072Buffer Copy Mode : SIMPLERedologcopies : disabledVersioning : enabled Current Version : 134 Versions to keep : 4 Delete Versions : <= 130Backup Type : fileTSM log server : disabledTSM server : SERVER_A with 3 sessions configured, using 1 session TSM client node : REDP


TSM server version : 5.2.0.0 TSM server ip : Y1.BOEBLINGEN.DE.IBM.COM TSM server name : ??? TSM server type : AIX-RS/6000 Sign-in id name : REDP Compression : client determined Archive deletion : allowed Days for backup : Sun Mon Tue Wed Thu Fri Sat Backup mgmt class : MDB Archiv mgmt class : MLOG1 MLOG2

BKI2017I: Blocksize is set to 131072 bytesBKI7311I: Profile used by DP ESS mySAP: /oracle/RED/920_64/dbs/initRED.fcs.BKI7536I: Execute command 'splitint -p /oracle/RED/920_64/dbs/initRED.fcs -f set_bki_info -i /tmp/bkiRED.ids':DP ESS mySAP:DP ESS mySAP: IBM Tivoli Storage Manager for HardwareDP ESS mySAP: Data Protection for IBM ESS for mySAP(R) on Oracle(R)DP ESS mySAP:DP ESS mySAP: BR*Tools Interface SPLITINT for the IBM Enterprise Storage ServerDP ESS mySAP: - Version 5, Release 3, Level 0 for AIX (32 Bit) -DP ESS mySAP: Build: 220 generated at 16:54:57 on Nov 25 2004DP ESS mySAP: (c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.DP ESS mySAP:DP ESS mySAP: IDS1411I The intended FlashCopy type has a value of 'NOCOPY'.DP ESS mySAP: Profile /oracle/RED/920_64/dbs/initRED.fcsDP ESS mySAP: Log file splitint_?_20051803014034.logDP ESS mySAP: Trace file splitint_?_20051803014034.traceDP ESS mySAP:DP ESS mySAP: -- Parameters of splitint profile --DP ESS mySAP:DP ESS mySAP: LOGON_HOST_PROD s1 oraredDP ESS mySAP: LOGON_HOST_BACK t1DP ESS mySAP: BACKUP_MAX 30DP ESS mySAP: IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssaveDP ESS mySAP: CONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcpDP ESS mySAP: WORK_DIR /oracle/RED/sapbackup/workDP ESS mySAP: TRACE YESDP ESS mySAP: LOG_TRACE_DIR /oracle/RED/sapbackup/logtracesDP ESS mySAP: SUPPORT_ADMIN_ASSISTANT NODP ESS mySAP: JAVA_HOME_DIRECTORY /usr/jdk_baseDP ESS mySAP: SHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105cliDP ESS mySAP: SHARK_SERVERNAME_PRIMARY 172.31.1.15DP ESS mySAP: SHARK_SERVERNAME_BACKUP 172.31.1.19DP ESS mySAP: SHARK_USERNAME essDP ESS mySAP: FLASHCOPY_TYPE NOCOPYDP ESS mySAP: SHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fctDP ESS mySAP: IDS1015I Start of splitint program at: 03/18/05-01:40:34 .DP ESS mySAP: #SAVED /oracle/RED/sapdata2/btabd_2/btabd.data2

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

DP ESS mySAP: #SAVED /oracle/RED/sapdata1/cntrl/cntrlRED.dbfDP ESS mySAP: BID RED___A0E6FO2ZQMDP ESS mySAP: UTL /oracle/RED/920_64/dbs/initRED.utlDP ESS mySAP: INF /oracle/RED/sapbackup/.bdpnlfyi.lstDP ESS mySAP: EBT fileDP ESS mySAP: EBC BRBACKUPDP ESS mySAP: EBB FULL


DP ESS mySAP: EBR NEWDP ESS mySAP: INL /oracle/RED/sapdata2/btabd_2/btabd.data2

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

DP ESS mySAP: INL /oracle/RED/sapdata1/cntrl/cntrlRED.dbfDP ESS mySAP: IDS1033I Information from DP for mySAP was found with backup ID RED___A0E6FO2ZQM.DP ESS mySAP: IDS1023I Exiting with return code 0.BKI5016I: Time: 03/18/05 01:40:48 New TSM session created: MGMNT-CLASS: MDB, TSM-Server: SERVER_A, type: SIMPLEBKI0027I: Time: 03/18/05 01:40:48 Object: 1 of 41 in process: /oracle/RED/sapdata1/stabi_1/stabi.data1 Size: 2000.008 MB, MGMNT-CLASS: MDB, TSM-Server: SERVER_A .BKI0023I: Time: 03/18/05 01:44:12 Done: 2000.008 MB (8.3 %) of 23.584 GB. Estimated end time: 03/18/05 02:24:26.BKI0053I: Time: 03/18/05 01:44:12 Object: 1 of 41 done: /oracle/RED/sapdata1/stabi_1/stabi.data1 with: 2000.008 MB saved with description RED___A0E6FO2ZQM.BKI0055I: Object /oracle/RED/sapdata1/stabi_1/stabi.data1 with 2000.008 MB saved with description RED___A0E6FO2ZQM_SERVER_A@MDB#340145 00134.

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

BR280I Time stamp 2005-03-18 02.18.27#FILE..... /oracle/RED/sapdata1/cntrl/cntrlRED.dbf#SAVED.... RED___A0E6FO2ZQMBKI2009I: Deleting all versions with version number <= 130 on server SERVER_A.

Nr. Object Server 1 /oracle/RED/sapdata1/stabi_1/stabi.data1 SERVER_A

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

41 /oracle/RED/sapdata1/cntrl/cntrlRED.dbf SERVER_A

Nr. Size Time Sec GB/h Mgmtclass 1 2000.008 MB 00 h 03 min 25 sec 205 34.299 MDB

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

41 4888.000 KB 00 h 00 min 01 sec 1 16.782 MDB

BKI1215I: Average transmission rate was 37.336 GB/h (10.620 MB/sec).BKI1227I: Average compression factor was 1.000.BKI0020I: End of program at: Fri Mar 18 02:18:30 NFT 2005 .BKI0021I: Elapsed time: 37 min 56 sec .BKI0024I: Return code is: 0.

BR280I Time stamp 2005-03-18 02.18.31BR232I 41 of 41 files saved by backup utilityBR230I Backup utility called successfully

BR280I Time stamp 2005-03-18 02.18.34


Then, we send the logs and profiles to Tivoli Storage Manager, as shown in Example 11-16.

Example 11-16 Back up logs and profiles to Tivoli Storage Manager

BR229I Calling backup utility...BR278I Command output of '/usr/sap/RED/SYS/exe/run/backint -u RED -f backup -i /oracle/RED/sapbackup/.bdpnlfyi.lst -t file -p /oracle/RED/920_64/dbs/initRED.utl -c':



BKI2027I: Using TSM-API version 5.3.0.0 (compiled with 5.3.0.0).BKI2000I: Successfully connected to ProLE on port tdpr3ora64.BKI0005I: Start of program at: Fri Mar 18 02:18:35 NFT 2005.

-- Parameters --Input File : /oracle/RED/sapbackup/.bdpnlfyi.lstProfile : /oracle/RED/920_64/dbs/initRED.utlConfigfile : /oracle/RED/920_64/dbs/initRED.bkiManual sorting file : disabledTracefile : /oracle/RED/saparch/backint_RED___A0E6FPFXM5.traceTraceflags : FILEIO_MAX COMPR_MIN TSM_MINParallel sessions : 1Multiplexed files : 1RL compression : 0Retries for files : 3Exit on error : disabledBATCH : enabledBuffer size : 131072Buffer Copy Mode : SIMPLERedologcopies : disabledVersioning : enabled Current Version : 135Backup Type : fileTSM log server : disabledTSM server : SERVER_A with 3 sessions configured, using 1 session TSM client node : REDP TSM server version : 5.2.0.0 TSM server ip : Y1.BOEBLINGEN.DE.IBM.COM TSM server name : ??? TSM server type : AIX-RS/6000 Sign-in id name : REDP Compression : client determined Archive deletion : allowed Days for backup : Sun Mon Tue Wed Thu Fri Sat Backup mgmt class : MDB Archiv mgmt class : MLOG1 MLOG2

BKI2017I: Blocksize is set to 131072 bytesBKI5016I: Time: 03/18/05 02:18:38 New TSM session created: MGMNT-CLASS: MDB, TSM-Server: SERVER_A, type: SIMPLEBKI0027I: Time: 03/18/05 02:18:38 Object: 1 of 8 in process: /oracle/RED/sapbackup/bdpnlfyi.aff Size: 64.285 KB, MGMNT-CLASS: MDB, TSM-Server: SERVER_A .BKI0023I: Time: 03/18/05 02:18:38 Done: 64.285 KB (53.5 %) of 120.058 KB. Estimated end time: 03/18/05 02:18:40.


BKI0053I: Time: 03/18/05 02:18:38 Object: 1 of 8 done: /oracle/RED/sapbackup/bdpnlfyi.aff with: 65.759 KB saved with description RED___A0E6FPFXM5.BKI0055I: Object /oracle/RED/sapbackup/bdpnlfyi.aff with 65.759 KB saved with description RED___A0E6FPFXM5_SERVER_A@MDB#380186 00135.

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

BR280I Time stamp 2005-03-18 02.18.39#INLOG.... /oracle/RED/sapreorg/reorgRED.log#SAVED.... RED___A0E6FPFXM5

Nr. Object Server 1 /oracle/RED/sapbackup/bdpnlfyi.aff SERVER_A 2 /oracle/RED/920_64/dbs/initRED.dba SERVER_A 3 /oracle/RED/920_64/dbs/initRED.utl SERVER_A 4 /oracle/RED/920_64/dbs/initRED.sap SERVER_A 5 /oracle/RED/920_64/dbs/initRED.ora SERVER_A 6 /oracle/RED/sapreorg/structRED.log SERVER_A 7 /oracle/RED/sapbackup/backRED.log SERVER_A 8 /oracle/RED/sapreorg/reorgRED.log SERVER_A

Nr. Size Time Sec GB/h Mgmtclass 1 64.285 KB 00 h 00 min 00 sec 0 0.245 MDB 2 19.589 KB 00 h 00 min 00 sec 0 0.075 MDB 3 12.347 KB 00 h 00 min 01 sec 1 0.042 MDB 4 11.981 KB 00 h 00 min 00 sec 0 0.046 MDB 5 6152 Bytes 00 h 00 min 00 sec 0 0.023 MDB 6 4976 Bytes 00 h 00 min 00 sec 0 0.019 MDB 7 852 Bytes 00 h 00 min 00 sec 0 0.003 MDB 8 160 Bytes 00 h 00 min 00 sec 0 0.001 MDB

BKI1215I: Average transmission rate was 0.208 GB/h (0.059 MB/sec).BKI1227I: Average compression factor was 0.987.BKI0020I: End of program at: Fri Mar 18 02:18:39 NFT 2005 .BKI0021I: Elapsed time: 04 sec .BKI0024I: Return code is: 0.


BR280I Time stamp 2005-03-18 02.18.41

After the backup is complete, we free the resources from the backup system by unmounting file systems, varying off VGs, exporting VGs, and withdrawing the ESS target volumes, as shown in Example 11-17.

Example 11-17 Resync and withdraw

BR297I Resynchronizing mirror disks...BR278I Command output of '/usr/sap/RED/SYS/exe/run/splitint -u RED -f resync -i /oracle/RED/sapbackup/.bdpnlfyi.lst -c -s -p /oracle/RED/920_64/dbs/initRED.fcs -C NOCOPY':


BR*Tools Interface SPLITINT for the IBM Enterprise Storage Server - Version 5, Release 3, Level 0 for AIX (32 Bit) - Build: 220 generated at 16:54:57 on Nov 25 2004


(c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.

IDS1310W The free space in the file system containing the directory / is only 24.85 MB (8 percent).IDS1411I The intended FlashCopy type has a value of 'NOCOPY'.Profile /oracle/RED/920_64/dbs/initRED.fcsLog file splitint_?_20051803021842.logTrace file splitint_?_20051803021842.trace


LOGON_HOST_PROD s1 oraredLOGON_HOST_BACK t1BACKUP_MAX 30IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssaveCONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcpWORK_DIR /oracle/RED/sapbackup/workTRACE YESLOG_TRACE_DIR /oracle/RED/sapbackup/logtracesSUPPORT_ADMIN_ASSISTANT NOJAVA_HOME_DIRECTORY /usr/jdk_baseSHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105cliSHARK_SERVERNAME_PRIMARY 172.31.1.15SHARK_SERVERNAME_BACKUP 172.31.1.19SHARK_USERNAME essFLASHCOPY_TYPE NOCOPYSHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fctIDS1005I Start of splitint program at: 03/18/05-02:18:43 .Function withdrawBackup list /oracle/RED/sapbackup/.bdpnlfyi.lstIDS1025I Time stamp: 03/18/05-02:18:50.EEO0371I Value of Flashcopy type is: NOCOPY.IDS1060I Start of listing of exported volume groups/unmounting file systems ...IDS1076I Trying to set the semaphore for the critical part of importing/exporting ...EEO0273I Unmounting the file system /oracle/RED/sapdata6...EEO0273I Unmounting the file system /oracle/RED/sapdata5...EEO0273I Unmounting the file system /oracle/RED/sapdata4...EEO0273I Unmounting the file system /oracle/RED/sapdata3...EEO0273I Unmounting the file system /oracle/RED/sapdata2...EEO0273I Unmounting the file system /oracle/RED/sapdata1...EEO0273I Unmounting the file system /oracle/RED/mirrlogB...EEO0273I Unmounting the file system /oracle/RED/mirrlogA...EEO0273I Unmounting the file system /oracle/RED/origlogB...EEO0273I Unmounting the file system /oracle/RED/origlogA...EEO0152I Removing volume group REDtdp1 ....EEO0152I Removing volume group REDtdp2 ....EEO0153I Varied off and exported volume group : REDtdp1EEO0153I Varied off and exported volume group : REDtdp2EEO0138I Flashcopy type is set to NOCOPY.Removing disk meta data for all target disks...This backup is NOT valid for a FlashCopy restore.Please restore from TSM Server.EEO0127I Removing device : vpath39EEO0127I Removing device : vpath36EEO0127I Removing device : vpath35EEO0127I Removing device : vpath29EEO0127I Removing device : vpath28EEO0127I Removing device : vpath27EEO0127I Removing device : vpath26EEO0127I Removing device : hdisk95


EEO0127I Removing device : hdisk92EEO0127I Removing device : hdisk91EEO0127I Removing device : hdisk83EEO0127I Removing device : hdisk82EEO0127I Removing device : hdisk81EEO0127I Removing device : hdisk80EEO0127I Removing device : hdisk47EEO0127I Removing device : hdisk43EEO0127I Removing device : hdisk42EEO0127I Removing device : hdisk33EEO0127I Removing device : hdisk32EEO0127I Removing device : hdisk31EEO0127I Removing device : hdisk30EEO0127I Removing device : hdisk135EEO0127I Removing device : hdisk132EEO0127I Removing device : hdisk131EEO0127I Removing device : hdisk126EEO0127I Removing device : hdisk125EEO0127I Removing device : hdisk124EEO0127I Removing device : hdisk123IDS1077I Semaphore released.IDS1047I End of listing.IDS1025I Time stamp: 03/18/05-02:20:10.EEO0022I AIX Version: 5300 Oslevel: 0.EEO0023I ESS CopyServices CLI Version: 2.3.EEO0362I Checking the status of the primary Copy Services Server: 172.31.1.15EEO0363I Primary Copy Services server is ready.IDS1061I Start of withdraw of the target-source pairs ...EEO0020I ====>Performing DP FOR ESS WITHDRAW command.EEO0357I Performing FlashCopy withdraw of source ESS volume 1A023376 from target ESS volume 1A323376EEO0357I Performing FlashCopy withdraw of source ESS volume 19A23376 from target ESS volume 19B23376EEO0357I Performing FlashCopy withdraw of source ESS volume 1A223376 from target ESS volume 1A523376EEO0357I Performing FlashCopy withdraw of source ESS volume 1A123376 from target ESS volume 1A423376EEO0357I Performing FlashCopy withdraw of source ESS volume 32F23376 from target ESS volume 33123376EEO0357I Performing FlashCopy withdraw of source ESS volume 35923376 from target ESS volume 35A23376EEO0357I Performing FlashCopy withdraw of source ESS volume 33023376 from target ESS volume 33223376EEO0366I Flashcopy was performed with WITHDRAW option.IDS1047I End of listing.IDS1025I Time stamp: 03/18/05-02:21:20.


BR280I Time stamp 2005-03-18 02.21.20BR298I Resynchronization of mirror disks successful

BR056I End of database backup: bdpnlfyi.aff 2005-03-18 02.18.39BR280I Time stamp 2005-03-18 02.21.20BR053I BRBACKUP terminated successfully t1:orared>


The whole offline database backup cycle took 48 minutes to complete, backing up a 30 GB mySAP database to Tivoli Storage Manager over a 100 MB Ethernet connection. The production database was offline for only 61 seconds.

To verify the status of the backup run the tdpessora command:

tdpessora -p initRED.sap

The output is shown in Example 11-18.

Example 11-18 Output of tdpessora FlashCopy Backup using NOCOPY

-------------------------------------------------------------------------------- IBM Tivoli Storage Manager for Hardware Data Protection for IBM ESS for mySAP(R) on Oracle(R)

Log history of the database backups SystemID: RED

-------------------------------------------------------------------------------- # Log Start of backup Type BackupID TSM FlashCopy-------------------------------------------------------------------------------- 1 bdpnlfyi.aff 05-03-18 01.33.24 offline_mirror RED___A0E6FO2ZQM ok nocopy

d - show details r - refresh display o - choose from older backups f - show FlashCopy backups only (target set state IN_USE) e - emergency FlashCopy restore x - exit tdpessora

Enter your selection =>

From the output, you can determine the backup type (offline_mirror), the backup ID (mySAP generated), if the data was transferred to the Tivoli Storage Manager serve, r and the FlashCopy type.

11.5.2 FlashCopy Backup ONLINE_MIRROR Disk-only INCRIn this example, we back up the mySAP database online. To do this, we put the database in backup mode, FlashCopy the tablespace volumes using the incremental INCR FlashCopy feature of the ESS, and as soon as the FlashCopy relationship is accomplished, the database is put into production again. This is a disk-only backup and only the changed data blocks are synchronized in the ESS subsystem. This is the fastest backup method available and puts the production database in backup mode for only a few minutes.

To start this type of backup, change the BACKUP_TYPE to ONLINE_MIRROR and SPLIT_OPTIONS parameter to -C INCR in the initRED.sap configuration file. Then run brbackup -c as shown in Example 11-19.

Example 11-19 Output of brbackup ONLINE_MIRROR, Disk Only, INCR

t1:orared 17> brbackup -cBR051I BRBACKUP 6.400 (116+)BR055I Start of database backup: bdpnotka.anf 2005-03-18 18.43.44

BR319I Control file copy was created: /oracle/RED/sapbackup/cntrlRED.dbf 5005312

BR280I Time stamp 2005-03-18 18.43.45BR295I Splitting mirror disks...


BR278I Command output of '/usr/sap/RED/SYS/exe/run/splitint -u RED -f split -i /oracle/RED/sapbackup/.bdpnotka.lst -t online -c -s -p /oracle/RED/920_64/dbs/initRED.fcs -d -C INCR':



IDS1189I The option '-C INCR' will override the value 'INCR' of the parameter FLASHCOPY_TYPE in the profile.IDS1411I The intended FlashCopy type has a value of 'INCR'.Profile /oracle/RED/920_64/dbs/initRED.fcsLog file splitint_?_20051803184345.logTrace file splitint_?_20051803184345.trace


LOGON_HOST_PROD s1 oraredLOGON_HOST_BACK t1BACKUP_MAX 30IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssaveCONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcpWORK_DIR /oracle/RED/sapbackup/workTRACE YESLOG_TRACE_DIR /oracle/RED/sapbackup/logtracesSUPPORT_ADMIN_ASSISTANT NOJAVA_HOME_DIRECTORY /usr/jdk_baseSHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105cliSHARK_SERVERNAME_PRIMARY 172.31.1.15SHARK_SERVERNAME_BACKUP 172.31.1.19SHARK_USERNAME essFLASHCOPY_TYPE INCRSHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fctIDS1005I Start of splitint program at: 03/18/05-18:43:46 .EEO0020I ====>Performing DP FOR ESS BACKUP command.IDS1121I Getting the source volumes ...Function getresourcesBackup list /oracle/RED/sapbackup/.bdpnotka.lstIDS1035I The IDS control file exists and a new backup cycle entry has been created.IDS1101I New assigned Backup Sequence Number 00005IDS1025I Time stamp: 03/18/05-18:43:54.

Determine the relationship of the database tablespace files to the physical volumes (ESS source volumes), as shown in Example 11-20.

Example 11-20 Gather source volumes

IDS1026I Start of splitint on the production system ...




IDS1189I The option '-C INCR' will override the value 'INCR' of the parameter FLASHCOPY_TYPE in the profile.IDS1411I The intended FlashCopy type has a value of 'INCR'.Profile /oracle/RED/920_64/dbs/initRED.fcsLog file splitint_?_20051803184345.logTrace file splitint_?_20051803184345.traceIDS1015I Start of splitint program at: 03/18/05-18:43:54 .Function getresourcesSubfunction performsplitBackup list /oracle/RED/sapbackup/work/.bdpnotka.lstEEO0022I AIX Version: 5300 Oslevel: 0.EEO0023I ESS CopyServices CLI Version: 2.3.EEO0362I Checking the status of the primary Copy Services Server: 172.31.1.15EEO0363I Primary Copy Services server is ready.EEO0156I Finding the serial numbers ...IDS1404I The target set with ID '1' is selected for this run.Matching pair tgt: <1A323376> src: <1A023376> size: <6.10_GB>Matching pair tgt: <1A423376> src: <1A123376> size: <6.10_GB>Matching pair tgt: <1A523376> src: <1A223376> size: <6.10_GB>Matching pair tgt: <33123376> src: <32F23376> size: <6.10_GB>Matching pair tgt: <33223376> src: <33023376> size: <6.10_GB>EEO0371I Value of Flashcopy type is: INCR.EEO0359I Incremental Change Recording: EnabledEEO0381I Querying ESS for pending sectors for volume: 1A023376EEO0071ISource volume: 1A023376 Target volume: 1A323376 Pending Sectors: 0EEO0381I Querying ESS for pending sectors for volume: 1A123376EEO0071ISource volume: 1A123376 Target volume: 1A423376 Pending Sectors: 0EEO0381I Querying ESS for pending sectors for volume: 1A223376EEO0071ISource volume: 1A223376 Target volume: 1A523376 Pending Sectors: 0EEO0381I Querying ESS for pending sectors for volume: 32F23376EEO0071ISource volume: 32F23376 Target volume: 33123376 Pending Sectors: 0EEO0381I Querying ESS for pending sectors for volume: 33023376EEO0071ISource volume: 33023376 Target volume: 33223376 Pending Sectors: 0EEO0374I Querying ESS for status of volume: 1A023376EEO0374I Querying ESS for status of volume: 1A123376EEO0374I Querying ESS for status of volume: 1A223376EEO0374I Querying ESS for status of volume: 32F23376EEO0374I Querying ESS for status of volume: 33023376EEO0374I Querying ESS for status of volume: 1A323376EEO0374I Querying ESS for status of volume: 1A423376EEO0374I Querying ESS for status of volume: 1A523376EEO0374I Querying ESS for status of volume: 33123376EEO0374I Querying ESS for status of volume: 33223376IDS1023I Exiting with return code 0.#INFO remote shell terminated successfullyIDS1027I Splitint ended successfully on the production system.IDS1025I Time stamp: 03/18/05-18:46:41.


Put the tablespaces in backup mode, as shown in Example 11-21.

Example 11-21 Put tablespaces in backup mode

IDS1320I Setting the tablespaces in backup mode or, in case of type offline, the database will be shutdown.

BR280I Time stamp 2005-03-18 18.46.47#BEGIN SPLIT /tmp/yaaD6al7y

BR280I Time stamp 2005-03-18 18.46.47BR315I 'Alter tablespace PSAPBTABD begin backup' successful

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

BR280I Time stamp 2005-03-18 18.46.47BR315I 'Alter tablespace PSAPUSER1I begin backup' successful

BR280I Time stamp 2005-03-18 18.46.48BR315I 'Alter tablespace SYSTEM begin backup' successful

Create the FlashCopy target volumes using incremental FlashCopy. If this is the first time an incremental FlashCopy is done, all source data is copied to the target volumes in the background. However, the target volumes are immediately available to the backup system, as shown in Example 11-22.

Example 11-22 Create the FlashCopy target volumes

IDS1122I Flashcopying the sources to the target volumes ...Function flashcopy_onlyBackup list /oracle/RED/sapbackup/.bdpnotka.lstIDS1025I Time stamp: 03/18/05-18:46:52.IDS1026I Start of splitint on the production system ...



IDS1189I The option '-C INCR' will override the value 'INCR' of the parameter FLASHCOPY_TYPE in the profile.IDS1411I The intended FlashCopy type has a value of 'INCR'.Profile /oracle/RED/920_64/dbs/initRED.fcsLog file splitint_?_20051803184345.logTrace file splitint_?_20051803184345.traceIDS1015I Start of splitint program at: 03/18/05-18:46:52 .Function flashcopy_onlySubfunction performsplitEEO0022I AIX Version: 5300 Oslevel: 0.EEO0023I ESS CopyServices CLI Version: 2.3.EEO0371I Value of Flashcopy type is: INCR.EEO0272I Flushing the buffers to disk...IDS1030I Flashcopy started ...EEO0362I Checking the status of the primary Copy Services Server: 172.31.1.15EEO0363I Primary Copy Services server is ready.EEO0030I Number of ESS Volumes to be Flashcopied: 5


EEO0354I Performing INCR FlashCopy of source ESS volume 1A023376 to target ESS volume 1A323376EEO0354I Performing INCR FlashCopy of source ESS volume 1A223376 to target ESS volume 1A523376EEO0354I Performing INCR FlashCopy of source ESS volume 1A123376 to target ESS volume 1A423376EEO0354I Performing INCR FlashCopy of source ESS volume 32F23376 to target ESS volume 33123376EEO0354I Performing INCR FlashCopy of source ESS volume 33023376 to target ESS volume 33223376EEO0366I Flashcopy was performed with INCR option.IDS1031I Flashcopy successful.IDS1024I Exiting with return code 0.#INFO remote shell terminated successfullyIDS1027I Splitint ended successfully on the production system.IDS1025I Time stamp: 03/18/05-18:47:11.

End backup mode for the tablespaces, as shown in Example 11-23.

Example 11-23 End backup mode

IDS1321I The tablespaces will end the backup mode or, in case of offline_split, the database will be started.

BR280I Time stamp 2005-03-18 18.47.11#END SPLIT /tmp/zaamLal7z

BR280I Time stamp 2005-03-18 18.47.11BR317I 'Alter tablespace PSAPBTABD end backup' successful

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

BR280I Time stamp 2005-03-18 18.47.11BR317I 'Alter tablespace PSAPUSER1I end backup' successful

BR280I Time stamp 2005-03-18 18.47.11BR317I 'Alter tablespace SYSTEM end backup' successful

The tablespaces were in backup mode for just 24 seconds, so very little overhead is generated on the redo logs.

The next step is to import VGs, varyon VGs, and mount file systems on the backup server, as shown in Example 11-24.

Example 11-24 Import VGs, varyon VGs and mount filesystems

EEO0371I Value of Flashcopy type is: INCR.IDS1540I Start of fcagent on the backup system ...IDS1123I Enabling the volumes and filesystems ...Function setresourcesBackup list /oracle/RED/sapbackup/.bdpnotka.lstIDS1076I Trying to set the semaphore for the critical part of importing/exporting ...IDS1046I Start of listing of importing volume groups/mounting file systems ...EEO0126I Trying to find new devices to match the source device. This process will take some time.......EEO0148I Importing volume groups now...EEO0149I Newly imported volume group: REDtdp1EEO0124I Mounting filesystem : /oracle/RED/sapdata1.EEO0124I Mounting filesystem : /oracle/RED/sapdata2.


EEO0124I Mounting filesystem : /oracle/RED/sapdata3.EEO0124I Mounting filesystem : /oracle/RED/sapdata4.EEO0124I Mounting filesystem : /oracle/RED/sapdata5.EEO0124I Mounting filesystem : /oracle/RED/sapdata6.IDS1077I Semaphore released.IDS1047I End of listing.IDS1025I Time stamp: 03/18/05-18:49:05.


BR280I Time stamp 2005-03-18 18.49.12BR296I Split of mirror disks successful

BR280I Time stamp 2005-03-18 18.49.12BR340I Switching to next online redo log file for database instance RED ...BR321I Switch to next online redo log file for database instance RED successful

BR280I Time stamp 2005-03-18 18.49.12

The database backup is now done (FlashCopy is complete). Because we specified a disk-only backup, no data is actually sent to Tivoli Storage Manager. In order to get this backup entered as a valid backup into the BRBackup log (to be later used for restore by BRRestore), a dummy backup with a BackupID is started. All files are reported as saved to BRBackup via the backint interface, and only a small amount of control information is transferred to the Tivoli Storage Manager server. See Example 11-25 for details.

Example 11-25 Backup data - dummy Tivoli Storage Manager session

BR057I Backup of database: REDBR058I BRBACKUP action ID: bdpnotkaBR059I BRBACKUP function ID: anfBR110I Backup mode: ALLBR077I Database file for backup: /oracle/RED/sapbackup/cntrlRED.dbfBR061I 37 files found for backup, total size 24070.047 MBBR143I Backup type: online_mirrorBR130I Backup device type: util_fileBR109I Files will be saved by backup utilityBR126I Unattended mode active - no operator confirmation required

BR280I Time stamp 2005-03-18 18.49.12BR229I Calling backup utility...BR278I Command output of '/usr/sap/RED/SYS/exe/run/backint -u RED -f backup -i /oracle/RED/sapbackup/.bdpnotka.lst -t file -p /oracle/RED/920_64/dbs/initRED.utl -c':



BKI2027I: Using TSM-API version 5.3.0.0 (compiled with 5.3.0.0).BKI2000I: Successfully connected to ProLE on port tdpr3ora64.BKI0005I: Start of program at: Fri Mar 18 18:49:12 NFT 2005 .


-- Parameters --Input File : /oracle/RED/sapbackup/.bdpnotka.lstProfile : /oracle/RED/920_64/dbs/initRED.utlConfigfile : /oracle/RED/920_64/dbs/initRED.bkiManual sorting file : disabledTracefile : /oracle/RED/saparch/backint_RED___A0E6GOTU2Z.traceTraceflags : FILEIO_MAX COMPR_MIN TSM_MINParallel sessions : 1Multiplexed files : 1RL compression : 0Retries for files : 3Exit on error : disabledBATCH : enabledBuffer size : 131072Buffer Copy Mode : SIMPLERedologcopies : disabledVersioning : enabled Current Version : 135 Versions to keep : 4 Delete Versions : <= 131Backup Type : fileTSM log server : disabledTSM server : SERVER_A with 3 sessions configured, using 1 session TSM client node : REDP TSM server version : 5.2.0.0 TSM server ip : Y1.BOEBLINGEN.DE.IBM.COM TSM server name : ??? TSM server type : AIX-RS/6000 Sign-in id name : REDP Compression : client determined Archive deletion : allowed Days for backup : Sun Mon Tue Wed Thu Fri Sat Backup mgmt class : MDB Archiv mgmt class : MLOG1 MLOG2

BKI2017I: Blocksize is set to 131072 bytesBKI7304I: Performing DISK ONLY backup.BKI7311I: Profile used by DP ESS mySAP: /oracle/RED/920_64/dbs/initRED.fcs.BKI7536I: Execute command 'splitint -p /oracle/RED/920_64/dbs/initRED.fcs -f set_bki_info -i /tmp/bkiRED.ids':DP ESS mySAP:DP ESS mySAP: IBM Tivoli Storage Manager for HardwareDP ESS mySAP: Data Protection for IBM ESS for mySAP(R) on Oracle(R)DP ESS mySAP:DP ESS mySAP: BR*Tools Interface SPLITINT for the IBM Enterprise Storage ServerDP ESS mySAP: - Version 5, Release 3, Level 0 for AIX (32 Bit) -DP ESS mySAP: Build: 220 generated at 16:54:57 on Nov 25 2004DP ESS mySAP: (c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.DP ESS mySAP:DP ESS mySAP: IDS1310W The free space in the file system containing the directory / is only 24.85 MB (8 percent).DP ESS mySAP: IDS1411I The intended FlashCopy type has a value of 'INCR'.DP ESS mySAP: Profile /oracle/RED/920_64/dbs/initRED.fcsDP ESS mySAP: Log file splitint_?_20051803184913.logDP ESS mySAP: Trace file splitint_?_20051803184913.traceDP ESS mySAP:DP ESS mySAP: -- Parameters of splitint profile --DP ESS mySAP:DP ESS mySAP: LOGON_HOST_PROD s1 orared


DP ESS mySAP: LOGON_HOST_BACK t1DP ESS mySAP: BACKUP_MAX 30DP ESS mySAP: IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssaveDP ESS mySAP: CONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcpDP ESS mySAP: WORK_DIR /oracle/RED/sapbackup/workDP ESS mySAP: TRACE YESDP ESS mySAP: LOG_TRACE_DIR /oracle/RED/sapbackup/logtracesDP ESS mySAP: SUPPORT_ADMIN_ASSISTANT NODP ESS mySAP: JAVA_HOME_DIRECTORY /usr/jdk_baseDP ESS mySAP: SHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105cliDP ESS mySAP: SHARK_SERVERNAME_PRIMARY 172.31.1.15DP ESS mySAP: SHARK_SERVERNAME_BACKUP 172.31.1.19DP ESS mySAP: SHARK_USERNAME essDP ESS mySAP: FLASHCOPY_TYPE INCRDP ESS mySAP: SHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fctDP ESS mySAP: IDS1015I Start of splitint program at: 03/18/05-18:49:13 .DP ESS mySAP: #SAVED /oracle/RED/sapdata2/btabd_2/btabd.data2

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

DP ESS mySAP: #SAVED /oracle/RED/sapdata4/system_2/system.data2DP ESS mySAP: BID RED___A0E6GOTU2ZDP ESS mySAP: UTL /oracle/RED/920_64/dbs/initRED.utlDP ESS mySAP: INF /oracle/RED/sapbackup/.bdpnotka.lstDP ESS mySAP: EBT fileDP ESS mySAP: EBC BRBACKUPDP ESS mySAP: EBB FULLDP ESS mySAP: EBR NEWDP ESS mySAP: INL /oracle/RED/sapdata2/btabd_2/btabd.data2

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

DP ESS mySAP: INL /oracle/RED/sapbackup/cntrlRED.dbfDP ESS mySAP: IDS1033I Information from DP for mySAP was found with backup ID RED___A0E6GOTU2Z.DP ESS mySAP: IDS1023I Exiting with return code 0.BKI0027I: Time: 03/18/05 18:49:26 Object: 1 of 37 in process: /oracle/RED/sapdata1/stabi_1/stabi.data1 Size: 2000.008 MB, MGMNT-CLASS: disk_only, TSM-Server: splitint .

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

BR280I Time stamp 2005-03-18 18.49.27#FILE..... /oracle/RED/sapdata1/temp_5/temp.data5#SAVED.... RED___A0E6GOTU2ZBKI5016I: Time: 03/18/05 18:49:28 New TSM session created: MGMNT-CLASS: MDB, TSM-Server: SERVER_A, type: SIMPLEBKI0027I: Time: 03/18/05 18:49:28 Object: 37 of 37 in process: /oracle/RED/sapbackup/cntrlRED.dbf Size: 4888.000 KB, MGMNT-CLASS: MDB, TSM-Server: SERVER_A .BKI0023I: Time: 03/18/05 18:49:28 Done: 23.506 GB (100.0 %) of 23.506 GB. Estimated end time: 03/18/05 18:49:28.BKI0053I: Time: 03/18/05 18:49:28 Object: 37 of 37 done: /oracle/RED/sapbackup/cntrlRED.dbf with: 4888.000 KB saved with description RED___A0E6GOTU2Z.BKI0055I: Object /oracle/RED/sapbackup/cntrlRED.dbf with 4888.000 KB saved with description RED___A0E6GOTU2Z_SERVER_A@MDB#130275 00135.


BR280I Time stamp 2005-03-18 18.49.28#FILE..... /oracle/RED/sapbackup/cntrlRED.dbf#SAVED.... RED___A0E6GOTU2ZBKI1215I: Average transmission rate was 5288.828 GB/h (1504.377 MB/sec).BKI1227I: Average compression factor was 1.000.BKI0020I: End of program at: Fri Mar 18 18:49:29 NFT 2005 .BKI0021I: Elapsed time: 17 sec .BKI0024I: Return code is: 0.


BR280I Time stamp 2005-03-18 18.49.31

Next, back up the logs and profiles to the Tivoli Storage Manager server, as shown in Example 11-26.

Example 11-26 Backup logs and profiles

BR229I Calling backup utility...BR278I Command output of '/usr/sap/RED/SYS/exe/run/backint -u RED -f backup -i /oracle/RED/sapbackup/.bdpnotka.lst -t file -p /oracle/RED/920_64/dbs/initRED.utl -c':



BKI2027I: Using TSM-API version 5.3.0.0 (compiled with 5.3.0.0).BKI2000I: Successfully connected to ProLE on port tdpr3ora64.BKI0005I: Start of program at: Fri Mar 18 18:49:31 NFT 2005 .

-- Parameters --Input File : /oracle/RED/sapbackup/.bdpnotka.lstProfile : /oracle/RED/920_64/dbs/initRED.utlConfigfile : /oracle/RED/920_64/dbs/initRED.bkiManual sorting file : disabledTracefile : /oracle/RED/saparch/backint_RED___A0E6GOU8EE.traceTraceflags : FILEIO_MAX COMPR_MIN TSM_MINParallel sessions : 1Multiplexed files : 1RL compression : 0Retries for files : 3Exit on error : disabledBATCH : enabledBuffer size : 131072Buffer Copy Mode : SIMPLERedologcopies : disabledVersioning : enabled Current Version : 135Backup Type : fileTSM log server : disabledTSM server : SERVER_A with 3 sessions configured, using 1 session TSM client node : REDP TSM server version : 5.2.0.0 TSM server ip : Y1.BOEBLINGEN.DE.IBM.COM


TSM server name : ??? TSM server type : AIX-RS/6000 Sign-in id name : REDP Compression : client determined Archive deletion : allowed Days for backup : Sun Mon Tue Wed Thu Fri Sat Backup mgmt class : MDB Archiv mgmt class : MLOG1 MLOG2

BKI2017I: Blocksize is set to 131072 bytesBKI5016I: Time: 03/18/05 18:49:31 New TSM session created: MGMNT-CLASS: MDB, TSM-Server: SERVER_A, type: SIMPLEBKI0027I: Time: 03/18/05 18:49:31 Object: 1 of 8 in process: /oracle/RED/sapbackup/bdpnotka.anf Size: 59.867 KB, MGMNT-CLASS: MDB, TSM-Server: SERVER_A .BKI0023I: Time: 03/18/05 18:49:31 Done: 59.867 KB (51.5 %) of 116.264 KB. Estimated end time: 03/18/05 18:49:31.BKI0053I: Time: 03/18/05 18:49:31 Object: 1 of 8 done: /oracle/RED/sapbackup/bdpnotka.anf with: 61.341 KB saved with description RED___A0E6GOU8EE.BKI0055I: Object /oracle/RED/sapbackup/bdpnotka.anf with 61.341 KB saved with description RED___A0E6GOU8EE_SERVER_A@MDB#310276 00135.

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

BR280I Time stamp 2005-03-18 18.49.32#INLOG.... /oracle/RED/sapbackup/backRED.log#SAVED.... RED___A0E6GOU8EEBKI0027I: Time: 03/18/05 18:49:32 Object: 8 of 8 in process: /oracle/RED/sapreorg/reorgRED.log Size: 160 Bytes, MGMNT-CLASS: MDB, TSM-Server: SERVER_A .BKI0023I: Time: 03/18/05 18:49:32 Done: 116.264 KB (100.0 %) of 116.264 KB. Estimated end time: 03/18/05 18:49:32.BKI0053I: Time: 03/18/05 18:49:32 Object: 8 of 8 done: /oracle/RED/sapreorg/reorgRED.log with: 160 Bytes saved with description RED___A0E6GOU8EE.BKI0055I: Object /oracle/RED/sapreorg/reorgRED.log with 160 Bytes saved with description RED___A0E6GOU8EE_SERVER_A@MDB#310283 00135.

BR280I Time stamp 2005-03-18 18.49.32#INLOG.... /oracle/RED/sapreorg/reorgRED.log#SAVED.... RED___A0E6GOU8EE

Nr. Object Server 1 /oracle/RED/sapbackup/bdpnotka.anf SERVER_A 2 /oracle/RED/920_64/dbs/initRED.dba SERVER_A 3 /oracle/RED/920_64/dbs/initRED.utl SERVER_A 4 /oracle/RED/920_64/dbs/initRED.sap SERVER_A 5 /oracle/RED/920_64/dbs/initRED.ora SERVER_A 6 /oracle/RED/sapreorg/structRED.log SERVER_A 7 /oracle/RED/sapbackup/backRED.log SERVER_A 8 /oracle/RED/sapreorg/reorgRED.log SERVER_A

Nr. Size Time Sec GB/h Mgmtclass 1 59.867 KB 00 h 00 min 00 sec 0 0.228 MDB 2 19.589 KB 00 h 00 min 00 sec 0 0.075 MDB 3 12.347 KB 00 h 00 min 00 sec 0 0.047 MDB 4 11.981 KB 00 h 00 min 00 sec 0 0.046 MDB 5 6152 Bytes 00 h 00 min 00 sec 0 0.023 MDB 6 4976 Bytes 00 h 00 min 00 sec 0 0.019 MDB 7 1491 Bytes 00 h 00 min 00 sec 0 0.006 MDB 8 160 Bytes 00 h 00 min 00 sec 0 0.001 MDB


BKI1215I: Average transmission rate was 0.404 GB/h (0.114 MB/sec).BKI1227I: Average compression factor was 0.987.BKI0020I: End of program at: Fri Mar 18 18:49:32 NFT 2005 .BKI0021I: Elapsed time: 01 sec .BKI0024I: Return code is: 0.


BR280I Time stamp 2005-03-18 18.49.33

Finally, unmount the file systems, varyoff VGs, and export VGs, as shown in Example 11-27. The target relationships with the source volumes are not withdrawn, because the next incremental FlashCopy backs up only the changed blocks. The ESS system tracks the changes automatically.

Example 11-27 Unmount the file systems, varyoff VGs and export VGs

BR297I Resynchronizing mirror disks...BR278I Command output of '/usr/sap/RED/SYS/exe/run/splitint -u RED -f resync -i /oracle/RED/sapbackup/.bdpnotka.lst -c -s -p /oracle/RED/920_64/dbs/initRED.fcs -d -C INCR':



IDS1189I The option '-C INCR' will override the value 'INCR' of the parameter FLASHCOPY_TYPE in the profile.IDS1411I The intended FlashCopy type has a value of 'INCR'.Profile /oracle/RED/920_64/dbs/initRED.fcsLog file splitint_?_20051803184933.logTrace file splitint_?_20051803184933.trace


LOGON_HOST_PROD s1 oraredLOGON_HOST_BACK t1BACKUP_MAX 30IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssaveCONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcpWORK_DIR /oracle/RED/sapbackup/workTRACE YESLOG_TRACE_DIR /oracle/RED/sapbackup/logtracesSUPPORT_ADMIN_ASSISTANT NOJAVA_HOME_DIRECTORY /usr/jdk_baseSHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105cliSHARK_SERVERNAME_PRIMARY 172.31.1.15SHARK_SERVERNAME_BACKUP 172.31.1.19SHARK_USERNAME essFLASHCOPY_TYPE INCRSHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fctIDS1005I Start of splitint program at: 03/18/05-18:49:33 .Function unmountBackup list /oracle/RED/sapbackup/.bdpnotka.lst


EEO0371I Value of Flashcopy type is: INCR.IDS1060I Start of listing of exported volume groups/unmounting file systems ...IDS1076I Trying to set the semaphore for the critical part of importing/exporting ...EEO0273I Unmounting the file system /oracle/RED/sapdata6...EEO0273I Unmounting the file system /oracle/RED/sapdata5...EEO0273I Unmounting the file system /oracle/RED/sapdata4...EEO0273I Unmounting the file system /oracle/RED/sapdata3...EEO0273I Unmounting the file system /oracle/RED/sapdata2...EEO0273I Unmounting the file system /oracle/RED/sapdata1...EEO0152I Removing volume group REDtdp1 ....EEO0153I Varied off and exported volume group : REDtdp1EEO0140I Flashcopy type is set to COPY or INCR.Leaving disk meta data intact for all target disks...This backup is valid for a FlashCopy restore.EEO0127I Removing device : vpath36EEO0127I Removing device : vpath35EEO0127I Removing device : vpath29EEO0127I Removing device : vpath28EEO0127I Removing device : vpath27EEO0127I Removing device : hdisk92EEO0127I Removing device : hdisk91EEO0127I Removing device : hdisk83EEO0127I Removing device : hdisk82EEO0127I Removing device : hdisk81EEO0127I Removing device : hdisk43EEO0127I Removing device : hdisk42EEO0127I Removing device : hdisk33EEO0127I Removing device : hdisk32EEO0127I Removing device : hdisk31EEO0127I Removing device : hdisk132EEO0127I Removing device : hdisk131EEO0127I Removing device : hdisk126EEO0127I Removing device : hdisk125EEO0127I Removing device : hdisk124IDS1077I Semaphore released.IDS1047I End of listing.IDS1025I Time stamp: 03/18/05-18:50:15.


BR280I Time stamp 2005-03-18 18.50.15BR298I Resynchronization of mirror disks successful

BR056I End of database backup: bdpnotka.anf 2005-03-18 18.49.32BR280I Time stamp 2005-03-18 18.50.15BR053I BRBACKUP terminated successfully t1:orared>

The entire process took 6 minutes and 31 seconds. However, the database spent 24 seconds in backup mode. Only the backup logs and the profiles were transferred to Tivoli Storage Manager.


You can check the status of the backup using tdpessora, as shown in Example 11-28.

Example 11-28 Query the status of the ONLINE_MIRROR backup



-------------------------------------------------------------------------------- # Log Start of backup Type BackupID TSM FlashCopy--------------------------------------------------------------------------------1 bdpnotka.anf 05-03-18 18.43.44 online_mirror RED___A0E6GOTU2Z * ok2 bdpnlfyi.aff 05-03-18 01.33.24 offline_mirror RED___A0E6FO2ZQM ok invalid

d - show details r - refresh display o - choose from older backups f - show FlashCopy backups only (target set state IN_USE) e - emergency FlashCopy restore x - exit tdpessora

Enter your selection =>

For the entry 1, the backup that we just made, the asterisk (*) in the Tivoli Storage Manager column indicates that the data was not sent to Tivoli Storage Manager, because it was a disk-only backup. The FlashCopy entry is ok, because we can do a FlashBack of this backup version. For the entry 2, our previous backup, this is valid for a Tivoli Storage Manager restore (status ok), but not for a Flash restore, because we have only one target set, and the latest backup overwrote that data.

To ensure that a background copy has ended before you start another one, you can use the splitint interface for mySAP (Example 11-29).

Example 11-29 Query the status of the target set ESS volumes

t1:orared> splitint -p initRED.fcs -f ts_inquire



IDS1310W The free space in the file system containing the directory / is only 24.86 MB (8 percent).IDS1411I The intended FlashCopy type has a value of 'INCR'.Profile initRED.fcsLog file splitint_?_20051803191513.logTrace file splitint_?_20051803191513.trace


LOGON_HOST_PROD s1 oraredLOGON_HOST_BACK t1BACKUP_MAX 30


IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssaveCONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcpWORK_DIR /oracle/RED/sapbackup/workTRACE YESLOG_TRACE_DIR /oracle/RED/sapbackup/logtracesSUPPORT_ADMIN_ASSISTANT NOJAVA_HOME_DIRECTORY /usr/jdk_baseSHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105cliSHARK_SERVERNAME_PRIMARY 172.31.1.15SHARK_SERVERNAME_BACKUP 172.31.1.19SHARK_USERNAME essFLASHCOPY_TYPE INCRSHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fctIDS1015I Start of splitint program at: 03/18/05-19:15:13 .Function ts_inquire

IDS1014I 1 IN_USE RED___A0E6GOTU2Z 00005 BSI_DISKONLY PSI_UNMOUNT_DONE - INCR 20051803184345 - - - - - -

IDS1023I Exiting with return code 0.t1:orared>

The output shows that the target set is in use by the backup run RED___A0E6GOTU2Z which was disk-only using the INCR FlashCopy method. The target set volumes have been unmounted from the backup server.

11.6 RestoreThis section explains how to restore the mySAP database from a disk-only backup.

11.6.1 FlashBack Restore As an example for restoring the mySAP database, we show you how to do a FlashBack restore. This procedure restores the database from the disk-only backup discussed in 11.5.2, “FlashCopy Backup ONLINE_MIRROR Disk-only INCR” on page 343. We use the data that is residing on the target volumes in the ESS subsystem. Figure 11-8 on page 357 shows an overview of the different steps in the restore process. These steps are outlined in each section in the restore example.

There are different ways to do a restore. As an example, we chose to use the tdpessora command. For different commands and procedures see IBM Tivoli Storage Manager for Hardware - Data Protection for IBM ESS for mySAP, Installation and User’s Guide for Oracle, SC33-8205.


Figure 11-8 FlashBack restore

We begin with the tdpessora command:

tdpessora -p initRED.sap

We select the backup which we want to restore. If you want to do a FlashBack restore, the FlashCopy status must be ok. You cannot restore from an invalid target set, because it has been overwritten by a subsequent backup. Example 11-30 shows the output.

Example 11-30 FlashBack Restore



-------------------------------------------------------------------------------- # Log Start of backup Type BackupID TSM FlashCopy-------------------------------------------------------------------------------- 1 bdpnotka.anf 05-03-18 18.43.44 online_mirror RED___A0E6GOTU2Z * ok 2 bdpnoodd.anf 05-03-18 17.44.25 online_mirror RED___A0E6GMQ0BC * invalid 3 bdpnlfyi.aff 05-03-18 01.33.24 offline_mirror RED___A0E6FO2ZQM ok invalid

d - show details r - refresh display o - choose from older backups # - restore the backup number #, including pre- and post-processing f - show FlashCopy backups only (target set state IN_USE) x - exit tdpessora

Enter your selection => 1IDS1425I You selected to restore the backup log 'bdpnotka.anf'.IDS1423I There is only a FlashCopy backup available for the backup log 'bdpnotka.anf'.

FlashCopyBackupcomplete

Initiate DB Restore

Check backup/informationstatus with tdpessora

DBA

Pre-

Rest

ore

Activ

ities

DBA

Post

-Res

tore

Activ

ities

Restore/Recovery Activities

Restore the DB

Stop the DB

Save controlfiles and redologs

Restore savedcontrol information

Restore offline redo logs

Redo any structural changes

Normal DB activity

BR256I

Deletedatabasefiles

brrestore -m full

[1] [2] [3] [4] [5]

backint-f restore

splitint -f flashbacksplitint

[1]Pre-restore activites: stop the database; check for structural changes performed, such as removing/adding ESS volumes to the volumegroups and file systems for the purpose of adding, extending, or deleting tablespaces; save current DB control and online redo log files (seesample script PreRestore.sh). Use tdpessora to get summarized information of previous backups.

[2]Restore: start brrestore (preferred) or backfm for a FlashBack Restore of a complete database. BR256I, BKI7316I, and IDS1084I are prompts,that require a user reply.

[3]Post-restore activities: Prior to the recovery, re-do any structural changes; restore DB control and online redo log files (see sample scriptPostRestore.sh). If required, restore from ITSM archived redo log files.

[4]DB recovery

[5]DB started for production transactions

It is highly recommended, and sometimes essential, to run another FlashCopy Backup after doing structural changes following a firstFlashCopy Backup. This will avoid discrepancies in, or failure of, the FlashBack Restore or DB recovery.

Note:

FlashCopybackgroundprocess in ESS

FlashBack Restore (Overall Process)

IDS1084I

User selectsFlashCopybackup type forFlashBackRestore

BKI7316I TerminationmessagesIDS1020IIDS1023IBKI0024IBR403I

Normal DBactivity

Start upDB forrecovery

Start DBfor production

FlashCopybackgroundprocess in ESS

(Possible structuralchanges)

1

Recover the DB

2

6

5

78

9

10

12

13 14 15

1611

20 21

19

18

17

4

3


IDS1434I Production volumes and files systems will be checked.IDS1435I Enter 'c[ont]' to continue or any other key to cancel.cIDS1180I The FlashCopy run 00005 is a valid disk backup.EEO0371I Value of Flashcopy type is: INCR.EEO0156I Finding the serial numbers ...REDdatavg:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

lvREDdata1 jfs 156 156 1 open/syncd /oracle/RED/sapdata1

loglv06 jfslog 1 1 1 open/syncd N/A






REDdatavg:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

vpath55 active 181 0 00..00..00..00..00

vpath56 active 181 0 00..00..00..00..00

vpath57 active 181 0 00..00..00..00..00

vpath58 active 181 0 00..00..00..00..00

vpath59 active 181 31 00..00..00..00..31

EEO0293I List of the current file systems on the backed up volume groups ...Name Nodename Mount Pt VFS Size Options Auto Accounting

/dev/lvREDdata1 -- /oracle/RED/sapdata1 jfs 10223616 rw yes no






EEO0294I List of file systems which will be restored...Name Nodename Mount Pt VFS Size Options Auto Accounting/dev/lvREDdata1 -- /oracle/RED/sapdata1 jfs 10223616rw yes no/dev/lvREDdata2 -- /oracle/RED/sapdata2 jfs 12255232rw yes no/dev/lvREDdata3 -- /oracle/RED/sapdata3 jfs 8192000rw yes no/dev/lvREDdata4 -- /oracle/RED/sapdata4 jfs 9175040rw yes no


/dev/lvREDdata5 -- /oracle/RED/sapdata5 jfs 7143424rw yes no/dev/lvREDdata6 -- /oracle/RED/sapdata6 jfs 10223616rw yes no/oracle/RED/sapdata/oracle/RED/sapdata/oracle/RED/sapdata/oracle/RED/sapdata/oracle/RED/sapdata/oracle/RED/sapdataIDS1435I Enter 'c[ont]' to continue or any other key to cancel.c

After determining which file systems need to be restored, the script PreRestore.sh which is provided by Data Protection for IBM ESS for mySAP is run. It checks prerequisites; it also checks if anything has changed on the production machine because the FlashCopy backup was performed. It checks if the backup is valid. It copies the redo logs and control files (if they are still available) away from the original locations, because they will get flashed over with the target volumes (Example 11-31).

Example 11-31 PreRestore.sh

Do you want to run 'IDS1431IDo you want to run 'PreRestore.sh -b logname -E tdpessora'? ('y'es/'e'dit/'q'uit) [y] =>PreRestore.sh -b bdpnotka.anf -E tdpessora'? ('y'es/'e'dit/'q'uit) [y] => yIDS1306I Issuing command 'PreRestore.sh -b bdpnotka.anf -E tdpessoraecho hdwIntRC: $?' ...PreRestore: ------------------------------------------------------------------------------PreRestore: PreRestore: IBM Tivoli Storage Manager for Hardware PreRestore: Data Protection for IBM ESS for mySAP(R) on Oracle(R)PreRestore: PreRestore: Restore Preprocessing script PreRestore: PreRestore: - Version 5, Release 3, Level 0 for AIX - PreRestore: (c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.PreRestore: PreRestore: ------------------------------------------------------------------------------PreRestore: checking user ...PreRestore: Oracle user orared foundPreRestore: $ORACLE_SID = <RED>PreRestore: $ORACLE_HOME = </oracle/RED/920_64>PreRestore: $SAPDATA_HOME = </oracle/RED>PreRestore: AIX version: 5300 oslevel: 00PreRestore: Time stamp: 03/18/05 19:30:38PreRestore: ------------------------------------------------------------------------------PreRestore: PreRestore: PART 1: command line options PreRestore: PreRestore: ------------------------------------------------------------------------------PreRestore: checking commandline options ...PreRestore: Option -d <backup_root_dir> is not specifiedPreRestore: Assuming default dir: </oracle/RED/sapbackup>PreRestore: backup_root_dir = </oracle/RED/sapbackup>PreRestore: Option -r <sapreorg_dir> is not specifiedPreRestore: Assuming default dir: </oracle/RED/sapreorg>PreRestore: sapreorg_dir = </oracle/RED/sapreorg>PreRestore: brbackup log = </oracle/RED/sapbackup/bdpnotka.anf>PreRestore: Time stamp: 03/18/05 19:30:38PreRestore: ------------------------------------------------------------------------------PreRestore: PreRestore: PART 2: check SAP / Oracle / DP for ESS environment


PreRestore: PreRestore: ------------------------------------------------------------------------------PreRestore: checking for running SAP instance RED ... OKPreRestore: checking for running Oracle instance RED ... OKPreRestore: reading brbackup log /oracle/RED/sapbackup/bdpnotka.anf ... OKPreRestore: brbackup backup type = <online_mirror>PreRestore: SAP profile used = </oracle/RED/920_64/dbs/initRED.sap>PreRestore: DP for mySAP util file used = </oracle/RED/920_64/dbs/initRED.utl>PreRestore: DP for ESS control file = </oracle/RED/sapbackup/idssave/idssave>PreRestore: DP for ESS backup sequence number = <00005>PreRestore: Current Oracle log sequence number = <10>PreRestore: checking for FlashBack Rerun ... OKPreRestore: No FlashBack with backup sequence number <00005> wasPreRestore: performed previously.PreRestore: Oracle log file : /oracle/RED/origlogA/log_g11m1.dbf foundPreRestore: Oracle log file : /oracle/RED/mirrlogA/log_g11m2.dbf foundPreRestore: Oracle log file : /oracle/RED/origlogB/log_g12m1.dbf foundPreRestore: Oracle log file : /oracle/RED/mirrlogB/log_g12m2.dbf foundPreRestore: Oracle log file : /oracle/RED/origlogA/log_g13m1.dbf foundPreRestore: Oracle log file : /oracle/RED/mirrlogA/log_g13m2.dbf foundPreRestore: Oracle log file : /oracle/RED/origlogB/log_g14m1.dbf foundPreRestore: Oracle log file : /oracle/RED/mirrlogB/log_g14m2.dbf foundPreRestore: Oracle control file : /oracle/RED/sapdata1/cntrl/cntrlRED.dbf foundPreRestore: Oracle control file : /oracle/RED/sapdata2/cntrl/cntrlRED.dbf foundPreRestore: Oracle control file : /oracle/RED/sapdata3/cntrl/cntrlRED.dbf foundPreRestore: space needed for backup of log and control files: 217.905 MBPreRestore: checking freespace in /oracle/RED/sapreorg ... OKPreRestore: freespace in directory </oracle/RED/sapreorg> : 1425.64 MBPreRestore: freespace after copying all files : 1207.74 MBPreRestore: creating directory /oracle/RED/sapreorg/restore_050318193039 ... OKPreRestore: Time stamp: 03/18/05 19:30:39PreRestore: ------------------------------------------------------------------------------PreRestore: PreRestore: PART 3: copy Oracle online log files PreRestore: PreRestore: ------------------------------------------------------------------------------PreRestore: copying /oracle/RED/origlogA/log_g11m1.dbf ... OKPreRestore: copying /oracle/RED/mirrlogA/log_g11m2.dbf ... OKPreRestore: copying /oracle/RED/origlogB/log_g12m1.dbf ... OKPreRestore: copying /oracle/RED/mirrlogB/log_g12m2.dbf ... OKPreRestore: copying /oracle/RED/origlogA/log_g13m1.dbf ... OKPreRestore: copying /oracle/RED/mirrlogA/log_g13m2.dbf ... OKPreRestore: copying /oracle/RED/origlogB/log_g14m1.dbf ... OKPreRestore: copying /oracle/RED/mirrlogB/log_g14m2.dbf ... OKPreRestore: Time stamp: 03/18/05 19:30:46PreRestore: ------------------------------------------------------------------------------PreRestore: PreRestore: PART 4: copy Oracle control files PreRestore: PreRestore: ------------------------------------------------------------------------------PreRestore: copying /oracle/RED/sapdata1/cntrl/cntrlRED.dbf ... OKPreRestore: copying /oracle/RED/sapdata2/cntrl/cntrlRED.dbf ... OKPreRestore: copying /oracle/RED/sapdata3/cntrl/cntrlRED.dbf ... OKPreRestore: Time stamp: 03/18/05 19:30:47PreRestore: ------------------------------------------------------------------------------PreRestore: PreRestore: Restore Preprocessing finished successfullyPreRestore: PreRestore: ------------------------------------------------------------------------------PreRestore:PreRestore: Program PreRestore.sh completed successfully.PreRestore: hdwIntRC: 0


For a FlashBack restore no data is actually transferred over the backint interface under BRRestore control. Therefore, a dummy restore is performed next, analogous to the disk only backup (Figure 11-25 on page 348) to satisfy the backint interface conventions for BRRestore (Example 11-32).

Example 11-32 Restore from Tivoli Storage Manager

Do you want to run 'IDS1432IDo you want to run 'brrestore -m full -b logname -r initSID.utl -p initSID.sap'? ('y'es/'e'dit/'q'uit) [y] =>brrestore -m full -b bdpnotka.anf -r /oracle/RED/920_64/dbs/initRED.utl -p /oracle/RED/920_64/dbs/initRED.sap'? ('y'es/'e'dit/'q'uit) [y] => yIDS1306I Issuing command 'brrestore -m full -b bdpnotka.anf -r /oracle/RED/920_64/dbs/initRED.utl -p /oracle/RED/920_64/dbs/initRED.sapecho hdwIntRC: $?echo hdwIntRC: $?' ...brrestore: BR401I BRRESTORE 6.400 (116)brrestore: BR169I Value 'online_mirror' of parameter/option 'backup_type/-t' ignored for 'brrestore' - 'offline' assumedbrrestore: BR405I Start of file restore: rdpnoxov.rsb 2005-03-18 19.30.53brrestore: BR437W File /oracle/RED/origlogA/log_g11m1.dbf to be restored was not savedbrrestore: BR437W File /oracle/RED/mirrlogA/log_g11m2.dbf to be restored was not savedbrrestore: BR437W File /oracle/RED/origlogB/log_g12m1.dbf to be restored was not savedbrrestore: BR437W File /oracle/RED/mirrlogB/log_g12m2.dbf to be restored was not savedbrrestore: BR437W File /oracle/RED/origlogA/log_g13m1.dbf to be restored was not savedbrrestore: BR437W File /oracle/RED/mirrlogA/log_g13m2.dbf to be restored was not savedbrrestore: BR437W File /oracle/RED/origlogB/log_g14m1.dbf to be restored was not savedbrrestore: BR437W File /oracle/RED/mirrlogB/log_g14m2.dbf to be restored was not savedbrrestore: BR280I Time stamp 2005-03-18 19.30.53brrestore: BR256I Enter 'c[ont]' to continue, 's[top]' to cancel the program:cbrrestore: BR280I Time stamp 2005-03-18 19.30.57brrestore: BR257I Your reply: 'c'brrestore: BR259I Program execution will be continued...brrestore:brrestore: BR428W File /oracle/RED/sapdata2/btabd_2/btabd.data2 will be overwritten

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

brrestore: BR428W File /oracle/RED/sapdata3/cntrl/cntrlRED.dbf will be overwrittenbrrestore: BR280I Time stamp 2005-03-18 19.30.57brrestore: BR256I Enter 'c[ont]' to continue, 's[top]' to cancel the program:cbrrestore: BR280I Time stamp 2005-03-18 19.31.15brrestore: BR257I Your reply: 'c'brrestore: BR259I Program execution will be continued...brrestore:brrestore: BR280I Time stamp 2005-03-18 19.31.15brrestore: BR407I Restore of database: REDbrrestore: BR408I BRRESTORE action ID: rdpnoxovbrrestore: BR409I BRRESTORE function ID: rsbbrrestore: BR449I Restore mode: FULLbrrestore: BR411I Database files for restore:brrestore: /oracle/RED/sapdata1/cntrl/cntrlRED.dbfbrrestore: /oracle/RED/sapdata2/cntrl/cntrlRED.dbfbrrestore: /oracle/RED/sapdata3/cntrl/cntrlRED.dbfbrrestore: BR419I Files will be restored from backup: bdpnotka.anf 2005-03-18 18.43.44brrestore: BR416I 37 files found to restore, total size 24070.047 MBbrrestore: BR421I Restore device type: util_file


brrestore: BR280I Time stamp 2005-03-18 19.31.15brrestore: BR256I Enter 'c[ont]' to continue, 's[top]' to cancel the program:cbrrestore: BR280I Time stamp 2005-03-18 19.31.20brrestore: BR257I Your reply: 'c'brrestore: BR259I Program execution will be continued...brrestore:brrestore: BR280I Time stamp 2005-03-18 19.31.22brrestore: BR229I Calling backup utility...brrestore: BR278I Command output of '/usr/sap/RED/SYS/exe/run/backint -u RED -f restore -i /oracle/RED/sapbackup/.rdpnoxov.lst -t file -p /oracle/RED/920_64/dbs/initRED.utl':brrestore:brrestore: Data Protection for mySAP(R) brrestore:brrestore: Interface between SAPDBA Utilities and Tivoli Storage Managerbrrestore: - Version 5, Release 3, Modification 0 for AIX LF 64-bit -brrestore: Build: 257 compiled on Nov 23 2004brrestore: (c) Copyright IBM Corporation, 1996, 2004, All Rights Reserved.brrestore:brrestore: BKI2027I: Using TSM-API version 5.3.0.0 (compiled with 5.3.0.0).brrestore: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.brrestore: BKI0005I: Start of program at: Fri Mar 18 19:31:22 NFT 2005 .brrestore:brrestore:brrestore: -- Parameters --brrestore: Input File : /oracle/RED/sapbackup/.rdpnoxov.lstbrrestore: Profile : /oracle/RED/920_64/dbs/initRED.utlbrrestore: Configfile : /oracle/RED/920_64/dbs/initRED.bkibrrestore: Manual sorting file : disabledbrrestore: Tracefile : /oracle/RED/saparch/backint_RED___A0E6GQC1W8.tracebrrestore: Traceflags : FILEIO_MAX COMPR_MIN TSM_MINbrrestore: Parallel sessions : 1brrestore: Multiplexed files : disabledbrrestore: RL compression : disabledbrrestore: Retries for files : 3brrestore: Exit on error : disabledbrrestore: BATCH : enabledbrrestore: Buffer size : 131072brrestore: Redologcopies : disabledbrrestore: Versioning : enabledbrrestore: Current Version : 135brrestore: Backup Type : unknownbrrestore: SNMPTRAP : disabledbrrestore: TSM log server : disabledbrrestore: TSM server : SERVER_A with 3 sessions configuredbrrestore: TSM client node : REDPbrrestore: TSM server version : 5.2.0.0brrestore: TSM server ip : Y1.BOEBLINGEN.DE.IBM.COMbrrestore: TSM server name : ???brrestore: TSM server type : AIX-RS/6000brrestore: Sign-in id name : REDPbrrestore: Compression : client determinedbrrestore: Archive deletion : allowedbrrestore: Days for backup : Sun Mon Tue Wed Thu Fri Satbrrestore: Backup mgmt class : MDBbrrestore: Archiv mgmt class : MLOG1 MLOG2brrestore: TSM server : idscntl with 1 session configuredbrrestore: TSM client node :brrestore: TSM server version :brrestore: TSM server ip :


brrestore: TSM server name :brrestore: TSM server type :brrestore: Sign-in id name :brrestore: Compression : unknownbrrestore: Archive deletion : unknownbrrestore: Days for backup : Sun Mon Tue Wed Thu Fri Satbrrestore: Backup mgmt class :brrestore: Archiv mgmt class :brrestore:brrestore:brrestore: BKI2017I: Blocksize is set to 131072 bytesbrrestore: BKI7536I: Execute command 'splitint -p /oracle/RED/920_64/dbs/initRED.fcs -f get_disk_backups':brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: IBM Tivoli Storage Manager for Hardwarebrrestore: DP ESS mySAP.com: Data Protection for IBM ESS for mySAP(R) on Oracle(R)brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: BR*Tools Interface SPLITINT for the IBM Enterprise Storage Serverbrrestore: DP ESS mySAP.com: - Version 5, Release 3, Level 0 for AIX (32 Bit) -brrestore: DP ESS mySAP.com: Build: 220 generated at 16:54:57 on Nov 25 2004brrestore: DP ESS mySAP.com: (c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: IDS1411I The intended FlashCopy type has a value of 'INCR'.brrestore: DP ESS mySAP.com: Profile /oracle/RED/920_64/dbs/initRED.fcsbrrestore: DP ESS mySAP.com: Log file splitint_?_20051803193126.logbrrestore: DP ESS mySAP.com: Trace file splitint_?_20051803193126.tracebrrestore: DP ESS mySAP.com: IDS1015I Start of splitint program at: 03/18/05-19:31:26 .brrestore: DP ESS mySAP.com: #FOUND RED___A0E6GOTU2Z /oracle/RED/sapdata2/btabd_2/btabd.data2 yes

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

brrestore: DP ESS mySAP.com: #FOUND RED___A0E6GOTU2Z /oracle/RED/sapdata4/system_2/system.data2 yesbrrestore: DP ESS mySAP.com: IDS1023I Exiting with return code 0.

Restore the log and profiles from Tivoli Storage Manager, as shown in Example 11-33.

Example 11-33 Restore log and profiles from Tivoli Storage Manager

brrestore: BKI7536I: Execute command 'splitint -p /oracle/RED/920_64/dbs/initRED.fcs -f flashback_check -i /tmp/baaM.Ieib -b RED___A0E6GOTU2Z':brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: IBM Tivoli Storage Manager for Hardwarebrrestore: DP ESS mySAP.com: Data Protection for IBM ESS for mySAP(R) on Oracle(R)brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: BR*Tools Interface SPLITINT for the IBM Enterprise Storage Serverbrrestore: DP ESS mySAP.com: - Version 5, Release 3, Level 0 for AIX (32 Bit) -brrestore: DP ESS mySAP.com: Build: 220 generated at 16:54:57 on Nov 25 2004brrestore: DP ESS mySAP.com: (c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.brrestore: DP ESS mySAP.com:


brrestore: DP ESS mySAP.com: IDS1411I The intended FlashCopy type has a value of 'INCR'.brrestore: DP ESS mySAP.com: Profile /oracle/RED/920_64/dbs/initRED.fcsbrrestore: DP ESS mySAP.com: Log file splitint_?_20051803193129.logbrrestore: DP ESS mySAP.com: Trace file splitint_?_20051803193129.tracebrrestore: DP ESS mySAP.com: IDS1015I Start of splitint program at: 03/18/05-19:31:30 .brrestore: DP ESS mySAP.com: #FOUND RED___A0E6GOTU2Z /oracle/RED/sapdata2/btabd_2/btabd.data2 yes

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

brrestore: DP ESS mySAP.com: #FOUND RED___A0E6GOTU2Z /oracle/RED/sapdata4/system_2/system.data2 yesbrrestore: DP ESS mySAP.com: IDS1023I Exiting with return code 0.

Now, the actual FlashBack restore ESS function is executed, as shown in Example 11-34.

Example 11-34 FlashBack Restore ESS function

brrestore: BKI7320I: Start FLASHCOPY restore.brrestore: BKI7536I: Execute command 'splitint -p /oracle/RED/920_64/dbs/initRED.fcs -f flashback -i /tmp/caaQHIeic -b RED___A0E6GOTU2Z':brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: IBM Tivoli Storage Manager for Hardwarebrrestore: DP ESS mySAP.com: Data Protection for IBM ESS for mySAP(R) on Oracle(R)brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: BR*Tools Interface SPLITINT for the IBM Enterprise Storage Serverbrrestore: DP ESS mySAP.com: - Version 5, Release 3, Level 0 for AIX (32 Bit) -brrestore: DP ESS mySAP.com: Build: 220 generated at 16:54:57 on Nov 25 2004brrestore: DP ESS mySAP.com: (c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: IDS1411I The intended FlashCopy type has a value of 'INCR'.brrestore: DP ESS mySAP.com: Profile /oracle/RED/920_64/dbs/initRED.fcsbrrestore: DP ESS mySAP.com: Log file splitint_?_20051803193132.logbrrestore: DP ESS mySAP.com: Trace file splitint_?_20051803193132.tracebrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: -- Parameters of splitint profile --brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: LOGON_HOST_PROD s1 oraredbrrestore: DP ESS mySAP.com: LOGON_HOST_BACK t1brrestore: DP ESS mySAP.com: BACKUP_MAX 30brrestore: DP ESS mySAP.com: IDS_CONTROL_FILE /oracle/RED/sapbackup/idssave/idssavebrrestore: DP ESS mySAP.com: CONFIG_FILE /oracle/RED/920_64/dbs/initRED.fcpbrrestore: DP ESS mySAP.com: WORK_DIR /oracle/RED/sapbackup/workbrrestore: DP ESS mySAP.com: TRACE YESbrrestore: DP ESS mySAP.com: LOG_TRACE_DIR /oracle/RED/sapbackup/logtracesbrrestore: DP ESS mySAP.com: SUPPORT_ADMIN_ASSISTANT NObrrestore: DP ESS mySAP.com: JAVA_HOME_DIRECTORY /usr/jdk_basebrrestore: DP ESS mySAP.com: SHARK_COPY_SERVICE_CODE /usr/opt/ibm/ibm2105clibrrestore: DP ESS mySAP.com: SHARK_SERVERNAME_PRIMARY 172.31.1.15brrestore: DP ESS mySAP.com: SHARK_SERVERNAME_BACKUP 172.31.1.19brrestore: DP ESS mySAP.com: SHARK_USERNAME essbrrestore: DP ESS mySAP.com: FLASHCOPY_TYPE INCRbrrestore: DP ESS mySAP.com: SHARK_VOLUMES_FILE /oracle/RED/920_64/dbs/initRED.fctbrrestore: DP ESS mySAP.com: IDS1015I Start of splitint program at: 03/18/05-19:31:32 .


brrestore: DP ESS mySAP.com: Function flashbackbrrestore: DP ESS mySAP.com: Backup list /tmp/caaQHIeicbrrestore: DP ESS mySAP.com: EEO0020I ====>Performing DP FOR ESS RESTORE command.brrestore: DP ESS mySAP.com: IDS1180I The FlashCopy run 00005 is a valid disk backup.brrestore: DP ESS mySAP.com: IDS1025I Time stamp: 03/18/05-19:31:34.brrestore: DP ESS mySAP.com: EEO0022I AIX Version: 5300 Oslevel: 0.brrestore: DP ESS mySAP.com: EEO0023I ESS CopyServices CLI Version: 2.3.brrestore: DP ESS mySAP.com: EEO0362I Checking the status of the primary Copy Services Server: 172.31.1.15brrestore: DP ESS mySAP.com: EEO0363I Primary Copy Services server is ready.brrestore: DP ESS mySAP.com: EEO0371I Value of Flashcopy type is: INCR.brrestore: DP ESS mySAP.com: EEO0359I Incremental Change Recording: Enabledbrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: -- Data content of the backup cycle with BSEQ_N/BID = 00005 --brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: IDS1014I 1 BACKUP_SEQUENCE_NO 00005brrestore: DP ESS mySAP.com: 2 BACKUP_STATUS BSI_DISKONLYbrrestore: DP ESS mySAP.com: 3 PROCESSING_STATUS PSI_UNMOUNT_DONEbrrestore: DP ESS mySAP.com: 4 BACKUP_ID RED___A0E6GOTU2Zbrrestore: DP ESS mySAP.com: 5 VOL_TARGET_SET 1brrestore: DP ESS mySAP.com: 6 DT_FLASHCOPY_START 20051803184345brrestore: DP ESS mySAP.com: 7 DT_FLASHCOPY_END 03/18/05-18:47:11brrestore: DP ESS mySAP.com: 8 DT_MOUNT_END 20051803184905brrestore: DP ESS mySAP.com: 9 EXCHANGE_FILE exchange.00005brrestore: DP ESS mySAP.com: 10 UTIL_FILE /oracle/RED/920_64/dbs/initRED.utlbrrestore: DP ESS mySAP.com: 11 INPUT_FILE /oracle/RED/sapbackup/.bdpnotka.lstbrrestore: DP ESS mySAP.com: 12 BACKINT_OPT_T filebrrestore: DP ESS mySAP.com: 13 BI_CALLER BRBACKUPbrrestore: DP ESS mySAP.com: 14 BI_BACKUP FULLbrrestore: DP ESS mySAP.com: 15 BI_REQUEST NEWbrrestore: DP ESS mySAP.com: 16 DATABASE_FILE -brrestore: DP ESS mySAP.com: 17 DT_WITHDRAW_START -brrestore: DP ESS mySAP.com: 18 DT_WITHDRAW_END -brrestore: DP ESS mySAP.com: 19 VERSION 530220brrestore: DP ESS mySAP.com: 20 FLASHCOPY_TYPE INCRbrrestore: DP ESS mySAP.com: 21 RSI -brrestore: DP ESS mySAP.com: 22 BACKUP_DESTINATION DISKONLYbrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: EEO0156I Finding the serial numbers ...brrestore: DP ESS mySAP.com: REDdatavg:brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINTbrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: lvREDdata1 jfs 156 156 1 open/syncd /oracle/RED/sapdata1brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: loglv06 jfslog 1 1 1 open/syncd N/Abrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: lvREDdata2 jfs 187 187 2 open/syncd /oracle/RED/sapdata2brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: lvREDdata3 jfs 125 125 1 open/syncd /oracle/RED/sapdata3brrestore: DP ESS mySAP.com:


brrestore: DP ESS mySAP.com: lvREDdata4 jfs 140 140 1 open/syncd /oracle/RED/sapdata4brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: lvREDdata5 jfs 109 109 1 open/syncd /oracle/RED/sapdata5brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: lvREDdata6 jfs 156 156 4 open/syncd /oracle/RED/sapdata6brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: REDdatavg:brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTIONbrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: vpath55 active 181 0 00..00..00..00..00brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: vpath56 active 181 0 00..00..00..00..00brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: vpath57 active 181 0 00..00..00..00..00brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: vpath58 active 181 0 00..00..00..00..00brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: vpath59 active 181 31 00..00..00..00..31brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: EEO0293I List of the current file systems on the backed up volume groups ...brrestore: DP ESS mySAP.com: Name Nodename Mount Pt VFS Size Options Auto Accountingbrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: /dev/lvREDdata1 -- /oracle/RED/sapdata1 jfs 10223616 rw yes nobrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: /dev/lvREDdata2 -- /oracle/RED/sapdata2 jfs 12255232 rw yes nobrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: /dev/lvREDdata3 -- /oracle/RED/sapdata3 jfs 8192000 rw yes nobrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: /dev/lvREDdata4 -- /oracle/RED/sapdata4 jfs 9175040 rw yes nobrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: /dev/lvREDdata5 -- /oracle/RED/sapdata5 jfs 7143424 rw yes nobrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: /dev/lvREDdata6 -- /oracle/RED/sapdata6 jfs 10223616 rw yes nobrrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com:brrestore: DP ESS mySAP.com: EEO0294I List of file systems which will be restored...brrestore: DP ESS mySAP.com: Name Nodename Mount Pt VFS Size Options Auto Accountingbrrestore: DP ESS mySAP.com: /dev/lvREDdata1 -- /oracle/RED/sapdata1 jfs 10223616rw yes no


brrestore: DP ESS mySAP.com: /dev/lvREDdata2 -- /oracle/RED/sapdata2 jfs 12255232rw yes nobrrestore: DP ESS mySAP.com: /dev/lvREDdata3 -- /oracle/RED/sapdata3 jfs 8192000rw yes nobrrestore: DP ESS mySAP.com: /dev/lvREDdata4 -- /oracle/RED/sapdata4 jfs 9175040rw yes nobrrestore: DP ESS mySAP.com: /dev/lvREDdata5 -- /oracle/RED/sapdata5 jfs 7143424rw yes nobrrestore: DP ESS mySAP.com: /dev/lvREDdata6 -- /oracle/RED/sapdata6 jfs 10223616rw yes nobrrestore: DP ESS mySAP.com: IDS1084I This is your last chance to stop the FlashBack Restore. Enter 'c[ont]' to continue, 's[top]' to cancel.cbrrestore: DP ESS mySAP.com: IDS1134I Disabling the volumes and filesystems ...brrestore: DP ESS mySAP.com: IDS1076I Trying to set the semaphore for the critical part of importing/exporting ...brrestore: DP ESS mySAP.com: #UNMOUNTING_FSbrrestore: DP ESS mySAP.com: EEO0273I Unmounting the file system /oracle/RED/sapdata6...brrestore: DP ESS mySAP.com: EEO0402I rmfs -r /oracle/RED/sapdata6brrestore: DP ESS mySAP.com: EEO0273I Unmounting the file system /oracle/RED/sapdata5...brrestore: DP ESS mySAP.com: EEO0402I rmfs -r /oracle/RED/sapdata5brrestore: DP ESS mySAP.com: EEO0273I Unmounting the file system /oracle/RED/sapdata4...brrestore: DP ESS mySAP.com: EEO0402I rmfs -r /oracle/RED/sapdata4brrestore: DP ESS mySAP.com: EEO0273I Unmounting the file system /oracle/RED/sapdata3...brrestore: DP ESS mySAP.com: EEO0402I rmfs -r /oracle/RED/sapdata3brrestore: DP ESS mySAP.com: EEO0273I Unmounting the file system /oracle/RED/sapdata2...brrestore: DP ESS mySAP.com: EEO0402I rmfs -r /oracle/RED/sapdata2brrestore: DP ESS mySAP.com: EEO0273I Unmounting the file system /oracle/RED/sapdata1...brrestore: DP ESS mySAP.com: EEO0402I rmfs -r /oracle/RED/sapdata1brrestore: DP ESS mySAP.com: EEO0402I rmlv -f loglv06brrestore: DP ESS mySAP.com: EEO0152I Removing volume group REDdatavg ....brrestore: DP ESS mySAP.com: EEO0153I Varied off and exported volume group : REDdatavgbrrestore: DP ESS mySAP.com: IDS1135I Flashcopying the target to the source volumes ...brrestore: DP ESS mySAP.com: IDS1030I Flashcopy started ...brrestore: DP ESS mySAP.com: EEO0362I Checking the status of the primary Copy Services Server: 172.31.1.15brrestore: DP ESS mySAP.com: EEO0363I Primary Copy Services server is ready.brrestore: DP ESS mySAP.com: EEO0030I Number of ESS Volumes to be Flashcopied: 5brrestore: DP ESS mySAP.com: EEO0354I Performing INCR FlashCopy of source ESS volume 1A323376 to target ESS volume 1A023376brrestore: DP ESS mySAP.com: EEO0354I Performing INCR FlashCopy of source ESS volume 1A523376 to target ESS volume 1A223376brrestore: DP ESS mySAP.com: EEO0354I Performing INCR FlashCopy of source ESS volume 1A423376 to target ESS volume 1A123376brrestore: DP ESS mySAP.com: EEO0354I Performing INCR FlashCopy of source ESS volume 33123376 to target ESS volume 32F23376brrestore: DP ESS mySAP.com: EEO0354I Performing INCR FlashCopy of source ESS volume 33223376 to target ESS volume 33023376brrestore: DP ESS mySAP.com: EEO0366I Flashcopy was performed with INCR option.brrestore: DP ESS mySAP.com: IDS1031I Flashcopy successful.brrestore: DP ESS mySAP.com: IDS1545I Start of fcagent on the production system ...brrestore: DP ESS mySAP.com: IDS1123I Enabling the volumes and filesystems ...brrestore: DP ESS mySAP.com: IDS1046I Start of listing of importing volume groups/mounting file systems ...brrestore: DP ESS mySAP.com: EEO0402I importvg -V 65 -y REDdatavg -n vpath55brrestore: DP ESS mySAP.com: EEO0274I Bringing up the volume groups...brrestore: DP ESS mySAP.com: EEO0124I Mounting filesystem : /oracle/RED/sapdata1.brrestore: DP ESS mySAP.com: EEO0124I Mounting filesystem : /oracle/RED/sapdata2.brrestore: DP ESS mySAP.com: EEO0124I Mounting filesystem : /oracle/RED/sapdata3.brrestore: DP ESS mySAP.com: EEO0124I Mounting filesystem : /oracle/RED/sapdata4.


brrestore: DP ESS mySAP.com: EEO0124I Mounting filesystem : /oracle/RED/sapdata5.brrestore: DP ESS mySAP.com: EEO0124I Mounting filesystem : /oracle/RED/sapdata6.brrestore: DP ESS mySAP.com: IDS1077I Semaphore released.brrestore: DP ESS mySAP.com: IDS1047I End of listing.brrestore: DP ESS mySAP.com: #FS_MOUNTEDbrrestore: DP ESS mySAP.com: IDS1025I Time stamp: 03/18/05-19:34:03.brrestore: DP ESS mySAP.com: #RESTORED /oracle/RED/sapdata2/btabd_2/btabd.data2

>>>>>>> output deleted >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

brrestore:brrestore: BR406I End of file restore: rdpnoxov.rsb 2005-03-18 19.34.09brrestore: BR280I Time stamp 2005-03-18 19.34.09brrestore: BR403I BRRESTORE terminated successfully brrestore: hdwIntRC: 0brrestore: hdwIntRC: 0

Execute the PostRestore.sh script is to copy back the previously saved redo log and control files to the original file systems (Example 11-35).

Example 11-35 PostRestore.sh

Do you want to run 'IDS1433IDo you want to run 'PostRestore.sh -b logname -E tdpessora'? ('y'es/'e'dit/'q'uit) [y] =>PostRestore.sh -b bdpnotka.anf -E tdpessora'? ('y'es/'e'dit/'q'uit) [y] => yIDS1306I Issuing command 'PostRestore.sh -b bdpnotka.anf -E tdpessoraecho hdwIntRC: $?' ...PostRestore: ------------------------------------------------------------------------------PostRestore: PostRestore: IBM Tivoli Storage Manager for Hardware PostRestore: Data Protection for IBM ESS for mySAP(R) on Oracle(R)PostRestore: PostRestore: Restore Postprocessing script PostRestore: PostRestore: - Version 5, Release 3, Level 0 for AIX - PostRestore: (c) Copyright IBM Corporation, 2000, 2004, All Rights Reserved.PostRestore: PostRestore: ------------------------------------------------------------------------------PostRestore: checking user ...PostRestore: Oracle user orared foundPostRestore: $ORACLE_SID = <RED>PostRestore: $ORACLE_HOME = </oracle/RED/920_64>PostRestore: $SAPDATA_HOME = </oracle/RED>PostRestore: Time stamp: 03/18/05 19:34:15PostRestore: ------------------------------------------------------------------------------PostRestore: PostRestore: PART 1: command line options PostRestore: PostRestore: ------------------------------------------------------------------------------PostRestore: checking commandline options ...PostRestore: Option -d <backup_root_dir> is not specifiedPostRestore: Assuming default dir: </oracle/RED/sapbackup>PostRestore: backup_root_dir = </oracle/RED/sapbackup>PostRestore: Option -r <sapreorg_dir> is not specifiedPostRestore: Assuming default dir: </oracle/RED/sapreorg>PostRestore: sapreorg_dir = </oracle/RED/sapreorg>PostRestore: brbackup log = </oracle/RED/sapbackup/bdpnotka.anf>PostRestore: Option -m <restoretype> is not be specified!PostRestore: Assuming default restore type: ALL


PostRestore: Restore type = <ALL>PostRestore: All log files and control files saved by PreRestore.sh will be restored.PostRestore: Time stamp: 03/18/05 19:34:15PostRestore: ------------------------------------------------------------------------------PostRestore: PostRestore: PART 2: check SAP / Oracle / DP for ESS environment PostRestore: PostRestore: ------------------------------------------------------------------------------PostRestore: checking for running SAP instance RED ... OKPostRestore: checking for running Oracle instance RED ... OKPostRestore: reading brbackup log /oracle/RED/sapbackup/bdpnotka.anf ... OKPostRestore: brbackup backup type = <online_mirror>PostRestore: SAP profile used = </oracle/RED/920_64/dbs/initRED.sap>PostRestore: DP for mySAP util file used = </oracle/RED/920_64/dbs/initRED.utl>PostRestore: DP for ESS control file = </oracle/RED/sapbackup/idssave/idssave>PostRestore: DP for ESS backup sequence number = <00005>PostRestore: Current Oracle log sequence number = <10>PostRestore: checking for FlashBack ... OKPostRestore: A FlashBack with backup sequence number <00005> wasPostRestore: performed previously.PostRestore:PostRestore: check directory /oracle/RED/sapreorg/restore_050318193039 ... OKPostRestore:PostRestore: DP ESS mySAP has detectedPostRestore: - the current FlashBack Restore withPostRestore: backup sequence number <00005> used target set 1PostRestore:PostRestore: The PostRestore.sh script will now copy the log and control files from the currentPostRestore: restore run to the original location.PostRestore:PostRestore: The following log files will be copied back to the original destinationPostRestore: Oracle log file : /oracle/RED/origlogA/log_g11m1.dbfPostRestore: Oracle log file : /oracle/RED/mirrlogA/log_g11m2.dbfPostRestore: Oracle log file : /oracle/RED/origlogB/log_g12m1.dbfPostRestore: Oracle log file : /oracle/RED/mirrlogB/log_g12m2.dbfPostRestore: Oracle log file : /oracle/RED/origlogA/log_g13m1.dbfPostRestore: Oracle log file : /oracle/RED/mirrlogA/log_g13m2.dbfPostRestore: Oracle log file : /oracle/RED/origlogB/log_g14m1.dbfPostRestore: Oracle log file : /oracle/RED/mirrlogB/log_g14m2.dbfPostRestore: The following control files will be copied back to the original destinationPostRestore: Oracle control file : /oracle/RED/sapdata1/cntrl/cntrlRED.dbfPostRestore: Oracle control file : /oracle/RED/sapdata2/cntrl/cntrlRED.dbfPostRestore: Oracle control file : /oracle/RED/sapdata3/cntrl/cntrlRED.dbfPostRestore: Time stamp: 03/18/05 19:34:16PostRestore: ------------------------------------------------------------------------------PostRestore: PostRestore: PART 3: copy Oracle online log files PostRestore: PostRestore: ------------------------------------------------------------------------------PostRestore: copying /oracle/RED/origlogA/log_g11m1.dbf ... OKPostRestore: copying /oracle/RED/mirrlogA/log_g11m2.dbf ... OKPostRestore: copying /oracle/RED/origlogB/log_g12m1.dbf ... OKPostRestore: copying /oracle/RED/mirrlogB/log_g12m2.dbf ... OKPostRestore: copying /oracle/RED/origlogA/log_g13m1.dbf ... OKPostRestore: copying /oracle/RED/mirrlogA/log_g13m2.dbf ... OKPostRestore: copying /oracle/RED/origlogB/log_g14m1.dbf ... OKPostRestore: copying /oracle/RED/mirrlogB/log_g14m2.dbf ... OKPostRestore: Time stamp: 03/18/05 19:34:20


PostRestore: ------------------------------------------------------------------------------PostRestore: PostRestore: PART 4: copy Oracle control files PostRestore: PostRestore: ------------------------------------------------------------------------------PostRestore: copying /oracle/RED/sapdata1/cntrl/cntrlRED.dbf ... OKPostRestore: copying /oracle/RED/sapdata2/cntrl/cntrlRED.dbf ... OKPostRestore: copying /oracle/RED/sapdata3/cntrl/cntrlRED.dbf ... OKPostRestore: Time stamp: 03/18/05 19:34:21PostRestore: ------------------------------------------------------------------------------PostRestore: PostRestore: Restore Postprocessing finished successfully PostRestore: PostRestore: ------------------------------------------------------------------------------PostRestore: PostRestore: In order to perform a forward recovery you will need all Oracle redo logPostRestore: files beginning with log sequence number 10 up to the point inPostRestore: time you want to recover your database. PostRestore: PostRestore: Make sure you have restored all redo log files from TSM prior starting thePostRestore: recovery. PostRestore: PostRestore: ------------------------------------------------------------------------------PostRestore: PostRestore: You can now start the forward recovery using the SQLPlus command PostRestore: PostRestore: SQL> recover database [until time <timestamp>] PostRestore: PostRestore: ------------------------------------------------------------------------------PostRestore:PostRestore: Program PostRestore.sh completed successfully.PostRestore: hdwIntRC: 0IDS1430I Restore from tdpessora ended with return code '0'.



-------------------------------------------------------------------------------- # Log Start of backup Type BackupID TSM FlashCopy-------------------------------------------------------------------------------- 1 bdpnotka.anf 05-03-18 18.43.44 online_mirror RED___A0E6GOTU2Z * ok 2 bdpnoodd.anf 05-03-18 17.44.25 online_mirror RED___A0E6GMQ0BC * invalid 3 bdpnlfyi.aff 05-03-18 01.33.24 offline_mirror RED___A0E6FO2ZQM ok invalid

d - show details r - refresh display o - choose from older backups # - restore the backup number #, including pre- and post-processing f - show FlashCopy backups only (target set state IN_USE) x - exit tdpessora

Enter your selection => xIDS1023I Exiting with return code 0.

orared@s1:/oracle/RED/920_64/dbs>


After that, the database is ready to begin roll forward recovery to the point in time you desire. Because we want to go back to the last transaction, we issue recover database without parameters. After forward recovery has ended, you are ready to start the database and mySAP and begin production again (Example 11-36).

Example 11-36 Roll forward database and start mySAP

orared@s1:/oracle/RED/920_64/dbs>sqlplus

SQL*Plus: Release 9.2.0.1.0 - Production on Fri Mar 18 19:35:15 2005


Enter user-name: / as sysdbaConnected to an idle instance.

SQL> startup mountORACLE instance started.

Total System Global Area 179224752 bytesFixed Size 741552 bytesVariable Size 100663296 bytesDatabase Buffers 76496896 bytesRedo Buffers 1323008 bytesDatabase mounted.ORA-01113: file 1 needs media recoveryORA-01110: data file 1: '/oracle/RED/sapdata4/system_1/system.data1'

SQL> recover databaseMedia recovery complete.SQL> alter database open

SQL> alter database open;Database altered.

SQL> quitDisconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit ProductionWith the Partitioning optionJServer Release 9.2.0.1.0 - Production

orared@s1:/oracle/RED/920_64/dbs>su - redadmredadm's Password:

redadm> startsap

Checking SAP R/3 RED Database------------------------------ Database is running

Starting SAP R/3 Instance------------------------------ Startup-Log is written to /home/redadm/startsap_s1_02.log Instance on host s1 started

redadm>

The complete restore cycle took 5 minutes and 38 seconds to the point of forward recovery. Because we did not change much between the backup and the restore, our redo logs were very small. The FlashBack restore, however, does not depend on how much data is flashed back, because the flashed back source volumes are available immediately after the flash


operation. Only the size of the redo logs slows down the process. So, a FlashBack restore is the fastest method to recovering mySAP databases.

11.7 Special environmentsThis section mentions some special environments which are specifically supported by Data Protection for IBM ESS for mySAP.

11.7.1 AIX LVM mirroringLVM mirroring across two separate storage subsystems provides for storage high availability that is transparent to the application. In case of a failure in one ESS, operation continues seamlessly on the other. Many customers with a high availability requirement use LVM mirroring in combination with a system take-over capability as provided by HACMP or Tivoli System Automation.

This configuration can also be used for disaster recovery by separating the systems and disk subsystems into two locations. Currently, distances of up to 35 miles (60 kilometers) are supported.

Data Protection for IBM ESS for mySAP provides special support for LVM mirrored ESSs to make economic use of storage: only one mirror needs to be FlashCopied for backup. This setup requires that each mirror set is completely contained in one ESS (that is, mirror set 1 and mirror set 2 must each be in separate ESSs). Figure 11-9 shows the required setup.

Figure 11-9 LVM mirroring in mySAP ESS environment

To activate the LVM mirroring support, the SHARK_ID_LVM parameter must be defined (init<SID>.fct), which specifies the ESS subsystems.

IBM ESS 2

SourceVolumes

CopySet 2

TargetVolumes

CopySet 2

2

2

2

2

2

2

2

2

2

2

2

2

AIX LVM Mirroring

IBM ESS 1

SourceVolumes

CopySet 1

TargetVolumes

CopySet 1

1

1

1

1

1

1

1

1

1

1

1

1

FC

1

1

1

1

1

1

1

1

1

1

1

1

FC

2

2

2

2

2

2

2

2

2

2

2

2


TCP/IP

mySAP utilitiessapdba



IDS LVM

DP for mySAP

ITSM APIITSM Client

NFS

SQLNET

REXEC

AIXDisk I/OESS

CopyServicesCLI

AIX JFSAIX LVM



Backup System

TCP/IP

mySAP utilities

brbackup

Oracle Client


IDSLVM

DP formySAP.com

ITSM APIITSM Client

AIXDisk I/O ESS

CopyServicesCLI

AIX JFSAIX LVM


NFS

SQLNET

REXEC


If only one target set is defined (for either ESS), FlashCopies are always performed to this target set.

To provide for fast restore even if one ESS fails, two target sets can be defined, one in each ESS. Data Protection for IBM ESS for mySAP then performs FlashCopies alternating between the ESSs (that is, TS1, TS2, TS1, TS2, and so forth). Thus a disk backup is always available for FlashBack restore.

A specific target set can be selected by specifying it via the -n parameter of the split_options variable in the init<SID>.sap config file.

Data Protection for IBM ESS for mySAP also performs the following checks for AIX LVM mirrored environments:

� A proper AIX LVM mirror setup for all LVs� Mirror Write Consistency is set to YES� Quorum is set to OFF� All PPs synchronized prior and after the FlashCopy� Schedule Policy is used

11.7.2 AIX HACMP High availability environments with HACMP are supported, but only in a three machine environment, as shown in Figure 11-10.

Figure 11-10 HACMP mySAP environment

The backup server system cannot be the same as the HACMP takeover system. If the primary machine fails, it must be able to failover to a separate cluster node, which cannot be the backup server.


TCP/IP




IDS LVM

DP for mySAP

ITSM APIITSM Client

NFS

SQLNET

REXEC

AIXDisk I/OESS

CopyServicesCLI

AIX JFSAIX LVM



AIX LVM Mirroring

Takeover System

TCP/IP




IDS LVM

DP for mySAP

ITSM APIITSM Client

NFS

SQLNET

REXEC

AIXDisk I/OESS

CopyServicesCLI

AIX JFSAIX LVM



IBM ESS 1

SourceVolumes

CopySet 1

TargetVolumes

CopySet 1

1

1

1

1

1

1

1

1

1

1

1

1

FC

1

1

1

1

1

1

1

1

1

1

1

1

IBM ESS 2

SourceVolumes

CopySet 2

TargetVolumes

CopySet 2

2

2

2

2

2

2

2

2

2

2

2

2

FC

2

2

2

2

2

2

2

2

2

2

2

2

Backup System

TCP/IP

mySAP utilities

brbackup

Oracle Client


IDSLVM

DP for mySAP

ITSM APIITSM Client

AIXDisk I/O ESS

CopyServicesCLI

AIX JFSAIX LVM


NFS

SQLNET

REXEC


LVM mirroring is also supported in an HACMP environment.

11.7.3 Multiple backup generations on diskTo address the requirement for minimum outage for database restoration, the time between backups must be decreased (having fewer log files to apply reduces forward recovery duration). In order to maintain the capability for FlashBack restore, multiple backup generations must be kept on disk. Data Protection for IBM ESS for mySAP supports this by managing multiple target sets.

Figure 11-11 illustrates such an environment.

Figure 11-11 Use of two target sets as backup generations


Configuring multiple target sets as backup generations on disk increases the availability of a best-fit backup on disk for FlashBack restore. For example, consider the backup schedule shown in Table 11-1.

Table 11-1 Sample backup schedule

In determining which target set to use for a backup run, Data Protection for IBM ESS for mySAP supports automatic selection, but it also allows the administrator to select a specific set if necessary.

For backup operation, Data Protection for IBM ESS for mySAP prevents you from accidentally running too many backups simultaneously, which would increase the risk that a disk-based backup will not be available if a FlashBack restore is needed. The software checks for any ESS background copies still running on behalf of a previous backup request and prevents a new FlashCopy from being started if a conflict is detected.

In the case of a restore, Data Protection for IBM ESS for mySAP initially verifies that there are no existing ESS source/target relationships that would prevent the FlashBack restore and alerts the administrator to first withdraw these relationships.

Multiple target sets can also be employed in an AIX LVM mirroring configuration (see 11.7.1, “AIX LVM mirroring” on page 372). Data Protection for IBM ESS for mySAP can be configured to perform backups to one of the target sets of a specific mirror copy or alternate the selection between the two mirrors, for example. The advantage of alternating between the mirror sets is that the mirrors can each have an incremental FlashCopy active at the same time.

Daily backup no Time Target set FlashCopy type Backup type

1 12:00 a.m. 1 INCR Disk-only

2 4:00 a.m. 2 COPY Disk and tape (Tivoli Storage Manager)

3 8:00 a.m. 1 INCR Disk-only

4 12:00 p.m. 1 INCR Disk-only

5 4:00 p.m. 2 COPY Disk-only

6 8:00 p.m. 1 INCR Disk-only


11.8 Determining problemsThis section explains some diagnostic commands that you can use to get information about your environment, along with some troubleshooting procedures and issues to watch for when encountering problems.

11.8.1 Diagnostic commandsThe following are helpful diagnostics commands:

� Function 'query' with brbackup –q

Allows Data Protection for IBM ESS for mySAP to perform a test run on the production system without interfering with the production work (database is not put into backup mode).

� Function 'inquire' with splitint -f inquire

Shows information for the latest backup cycles.

� Function 'ts_inquire' with splitint -f ts_inquire

Shows information about the target sets (copy set)

� TRACE YES

Recommended to always set TRACE to YES. In error situations, it provides very helpful information for error analysis and problem determination in spite of its small size.

11.8.2 Summary of various logs and tracesData Protection for IBM ESS for mySAP produces various log and trace files, including:

� Utilities for mySAP:

– BR*Tools– brbackup– brarchive– brrestore

You can find these utilities in the following directories:

– The /oracle/<SID>/sapbackup directory for brbackup logs and brbackup summary logs, and for BR*Tools/brrestore logs

– The /oracle/<SID>/saparch directory for brarchive logs and brarchive summary logs

� Interfaces for Data Protection for IBM ESS for mySAP:

– Logs and traces go into the directory specified in the profile parameter LOG_TRACE_DIR. The file names are:

• splitint_b_<splitint function>_<date time stamp>.log - log for production system• splitint_b_<splitint function>_<date time stamp>.trace - trace for production system• splitint_p_<splitint function>_<date time stamp>.log - log for backup system,• splitint_p_<splitint function>_<date time stamp>.trace - trace for backup system

� ESS info (see the ESS Specialist browser/status menu).

� Data Protection for IBM ESS for mySAP places run time info into the mySAP BRTools logs (see above); in addition traces can be taken.

� AIX operating system error info (run the command: errpt –a).


11.8.3 TroubleshootingHere is a general checklist for when problems occur. Then, some specific actions in particular problem scenarios are given.

A general checklist Here are situations of which you should be aware:

� Are ESS and Oracle installed and set up correctly?

� Do all database files reside on ESS source disks and are the ESS target disks available?

� Are disks visible to appropriate systems:

– Source disks to production host?– Target disks to backup host?

� Are Tivoli Storage Manager Backup-Archive clients and Data Protection for IBM ESS for mySAP set up with required PASSWORDACCESS values in the options files?

� Are production and backup systems registered as Tivoli Storage Manager client nodes?

� Has the Tivoli Storage Manager Backup-Archive Client password file been generated by the Tivoli Storage Manager components (when using PASSWORDACCESS GENERATE in the options files)?

� Are the passwords used by Data Protection for IBM ESS for mySAP defined/established in the CONFIG_FILE?

� Is the ESS Copy Services server running?

� Are ESS target volumes in another FlashCopy or PPRC relationship?

� Are the DNS services in the ESS systems set up properly for the production and backup systems? That is, are their TCP/IP host names known to the ESS Copy Services server?

Specific problem scenariosThe following are some specific problem scenarios that require action:

� If brbackup fails, there is no connection to production database. Check mySAP OSS.

� If splitint fails, check ESS source/target volumes size fails with rc=20.

Possible causes are:

– A size mismatch between source and target volume

– Update ESS Copy Services command line interface to a level higher than 2.1.0.0 and Data Protection for IBM ESS for mySAP higher than V1.2

• Action: Update Data Protection for IBM ESS for mySAP to version 1.2 or higher• Adapt the ESS volumes file by replacing source and size by hyphen

� If no ESS source volume is found, make sure that all database files are located on ESS volumes.

� If no ESS target volume is found, make sure that all ESS source volumes have their corresponding target volumes in the same LSS.

� If splitint / FlashCopy fails because of:

– Duplicate PVIDs, the possible cause might be source volume to target volume1, later to target volume2

– Single Target Set for multiple source systems, the possible cause might be target volume could still be in an ESS source/target relationship or be used (mounted) elsewhere


– Copy Services server no heartbeat, the possible cause might be that the TCP/IP network is down, Copy Services server is down, or the wrong DNS / TCP/IP address was used

– The /etc/hosts file in ESS not set up properly, the possible cause might be that you must configure the DNS names of the production and backup system in the ESS

– Copy Services server down, the possible cause might be that both the primary and backup server are down or the administrator has not switched

– Using command line interface FlashCopy request returns rc=8, then use the following for cause analysis:

• ESS Copy Services server Log• find ESS volume in Copy Services server Log• ESS volume assignment

� Manual cleanup

A manual cleanup might be required if you encounter duplicate PVIDs on the backup system. To clean the ODM as well as the PVID on the physical volume, run these commands:

lsvpcfg (only if SDD)/usr/opt/ibm2105cli/rsList2105s.shlscfg –vl hdiskxxlspvchdev -a pv=clear ...rmdev -dl vpathX (only if SDD)rmdev -df hdiskX


Chapter 12. Backing up SAN File System with Tivoli Storage Manager

This chapter describes the possibilities to backup the IBM TotalStorage SAN File System with Tivoli Storage Manager. It focuses on file-based backup/restore scenarios. For a discussion of LUN-based backups, see the IBM Redbook IBM TotalStorage: Introducing the SAN File System, SG24-7057.


� SAN File System overview� Backing up SAN File System with Tivoli Storage Manager� Backup and restore scenarios with Tivoli Storage Manager� Special environments

12


12.1 SAN File System overviewThe IBM TotalStorage SAN File System (SAN File System) is designed on industry standards so that it can:

� Allow data sharing and collaboration across servers over the SAN with high performance and full file locking support, using a single global namespace for the data.

� Provide more effective storage use by reducing the amount of duplicate data and by sharing free and temporary space across servers.

� Improve productivity and simplify the process for IT storage and server management staff by centralizing management through policy-based storage management automation, thus significantly lowering the cost of storage management.

� Facilitate application server and storage consolidation across the enterprise to scale the infrastructure for storage and data on demand.

� Simplify and lower the cost of data backups through built-in, file-based FlashCopy image function.

� Eliminate data migration during application server consolidation, and also reduce application downtime and failover costs.

SAN File System is a multiplatform, robust, scalable, and highly available file system and is a storage management solution that works with Storage Area Networks (SANs). It uses SAN technology, which allows an enterprise to connect a large number of computers and share a large number of storage devices via a high-performance network.

With SAN File System, heterogeneous clients can access shared data directly from large, high-performance, high-function storage systems, such as IBM TotalStorage Enterprise Storage Server (ESS), IBM TotalStorage SAN Volume Controller (SVC), and IBM TotalStorage DS4000 (formerly IBM TotalStorage FAStT), as well as non-IBM storage devices. The SAN File System is built on a Fibre Channel network and is designed to provide superior I/O performance for data sharing among heterogeneous computers.

SAN File System differs from conventional distributed file systems in that it uses a data-access model that separates file metadata (information about the files, such as owner, permissions, and the physical file location) from actual file data (contents of the files). The metadata is provided to clients by Metadata servers — the clients communicate with the Metadata servers only to get the information they need to locate and access the files. When they have this information, the SAN File System clients access data directly from storage devices via the clients’ own direct connection to the SAN. Direct data access eliminates server bottlenecks and provides the performance necessary for data-intensive applications.

SAN File System presents a single, global namespace to clients where they can create and share data, using uniform file names from any client or application. Furthermore, data consistency and integrity is maintained through SAN File System’s management of distributed locks and the use of leases.

SAN File System also provides automatic file placement through the use of policies and rules. Based on rules specified in a centrally-defined and managed policy, SAN File System automatically stores data on devices in storage pools that are specifically created to provide the capabilities and performance appropriate for how the data is accessed and used.


12.1.1 SAN File System architectureFigure 12-1 illustrates the SAN File System architecture and components. Computers that want to share data and have their storage centrally managed are all connected to the SAN. In SAN File System terms, these are known as clients, because they access SAN File System services. However, in the enterprise context, they would most likely be, for example, database servers, application servers, or file servers.

Figure 12-1 SAN File System architecture

Figure 12-1 shows five such clients, each running a SAN File System currently supported client operating system. The SAN File System client software enables them to access the global namespace through a virtual file system (VFS) on UNIX or Linux systems and an installable file system (IFS) on Windows systems. This layer (VFS/IFS) is built by the operating system vendors for use specifically on special-purpose or newer file systems.

There are also special computers called metadata server (MDS) engines that run the metadata server software, as shown on the left side of the figure. The MDSs manage file system metadata (including file creation time, file security information, file location information, and so on), but the user data accessed over the SAN by the clients does not pass through the MDS.

This architecture eliminates the performance bottleneck from which many existing shared file system approaches suffer, giving near-local file system performance. MDSs are clustered for scalability and availability of metadata operations and are often referred to as the MDS cluster. In a SAN File System server cluster, there is one master MDS and one or more subordinate MDSs. Each MDS runs on a separate physical engine in the cluster. Additional MDSs can be added as required if the workload grows, providing solution scalability.

Storage volumes that store the SAN File System clients’ user data (User Pools) are separated from storage volumes that store metadata (System Pool), as shown in Figure 12-1.

The Administrative server allows SAN File System to be remotely monitored and controlled through a Web-based user interface called the SAN File System console. The Administrative

MasterConsole

Centralized Administration

Load balancing Fail-over processingScalability

Existing IP Network for Participant/File Directory Cluster Communications

Metadata servercluster

.

.

.Metadataserver

engines

LDAPServer

NIS/Active

DirectoryServer

User PoolsSystemPool

SAN Fabric

Win2003Solaris AIX Win2000Linux

VFS VFS VFS IFSIFS

Chapter 12. Backing up SAN File System with Tivoli Storage Manager 381

server also processes requests issued from an administrative command line interface, which can also be accessed remotely.

12.2 Backing up SAN File System with Tivoli Storage ManagerThis section discusses how to use a backup/recovery application, such as Tivoli Storage Manager, with the SAN File System clients to perform a file-based backup of files in the SAN File System global namespace.

12.2.1 Benefits of Tivoli Storage Manager with SAN File SystemBecause SAN File System is a global namespace (the files are visible to all clients), the files can be backed up from any SAN File System client. Therefore, you can back up those files, either directly from the filesets or from a SAN File FlashCopy image on a completely separate SAN File System client from the client that normally runs any applications on these files, thus giving application server-free backup. This backup method eliminates the application servers themselves from the data path of the backup and frees them from expending any processor cycles on the backup process. If you back up the files from a FlashCopy image, this effectively almost eliminates the backup window (that is, a period of outage of the application to clients), because you create an online consistent copy of the data that is then backed up. The application then proceeds uninterrupted while the backup is executed against the FlashCopy image.

This principle is illustrated in Figure 12-2.

Figure 12-2 Backing up SAN File System with Tivoli Storage Manager

The following procedure provides application server-free backup:

1. Create FlashCopy images of the filesets that you want to protect. This step requires minimal disruption to the SAN File System clients that are performing a production workload (Web servers, application servers, database servers, and so on).

Pools

"Production" SAN FSClients Tivoli

Storage Manager Server

LAN

TapeLibraryUser System

SAN FS ClientsTivoli Storage Manager or LAN-Freeclients

SAN


2. Now you can back up these FlashCopy images using a file-based backup application such as Tivoli Storage Manager, where the Tivoli Storage Manager client is installed on a separate SAN File System client. It still sees all the files, but the backups run independently of the production SAN File System clients. To keep all file attributes, if you have both Windows and UNIX (including Linux)-created data in your SAN File System environment, it should be separated by fileset. Then you should run two separate Tivoli Storage Manager clients in this instance: a Windows Tivoli Storage Manager/SAN File System client to back up Windows files, and an AIX Tivoli Storage Manager/SAN File System client to back up UNIX (including Linux) files. You can also run multiple instances of these if required to improve backup performance. The Tivoli Storage Manager server can be on any supported Tivoli Storage Manager server platform, and only needs to be SAN and LAN attached. It does not need to be a SAN File System client.

3. If you have implemented a non-uniform SAN File System configuration, such that not all filesets are visible to all clients, you need additional backup clients to ensure that all filesets can be backed up by a client that has visibility to it.

4. You can use the LAN-free backup client to also back up these files directly over the SAN to a SAN-attached library as shown, rather than using the LAN for backup data traffic. Therefore, we have LAN-free and (application) server-free backup capability.

12.3 Backup and restore scenarios with Tivoli Storage ManagerThis section presents the following scenarios for restore:

� Backing up user data in Windows filesets using Tivoli Storage Manager client for Windows

– Selected file to original location

– File restore to different location from a FlashCopy image backup

� Backing up user data in UNIX filesets using Tivoli Storage Manager client for AIX

– Backing up and restoring files using data in an actual fileset

– Backing up and restoring SAN File System FlashCopy images using the -snapshotroot Tivoli Storage Manager option

In our lab, we installed the Tivoli Storage Manager server on a Windows 2000 machine and two clients on the following platforms:

� AIX 5L™ Version 5.2, Maintenance Level 03, 32-bit version

� Windows 2000 Service Pack 4

Both Tivoli Storage Manager server and client code versions used in our lab were at V5.2.2.0. Note that in order to back up SAN File System data from AIX and Windows SAN File System clients, you need Tivoli Storage Manager client V5.1 and higher. To back up SAN File System

Note: Tivoli Storage Manager, in backing up the files in SAN File System, automatically also backs up the associated file metadata. Tivoli Storage Manager also supports restoring files to the same or a different location, and even to a different Tivoli Storage Manager client. This means you could restore files backed up from SAN File System not only to a different SAN File System environment but also (as in a disaster recovery situation) to a local file system on another UNIX or Windows Tivoli Storage Manager client that is not a SAN File System client (that is, you could still restore these files from a Tivoli Storage Manager backup even if you do not have a SAN File System environment to which to restore them). After all, they are just files to Tivoli Storage Manager — the metadata will be handled appropriately for the restore platform, depending on whether the restore destination is a directory in the SAN File System global namespace or a local file system.


data from Linux and Solaris clients, you need Tivoli Storage Manager client V5.2.3_1 or higher.

All these clients are also SAN File System clients. The following sections introduce sample backup and restore scenarios for both Windows and UNIX SAN File System filesets.

12.3.1 Backing up user data in Windows filesets using Tivoli Storage Manager client for Windows

First, we back up the files with the Tivoli Storage Manager client:

1. To start the Backup-Archive Client interface, select Start → Programs → Tivoli Storage Manager → Backup-Archive GUI, and select the Backup function. Select the files to back up, as shown in Figure 12-3. Notice that the SAN File System drive and filesets appear as a Local drive in the Backup-Archive Client.

Figure 12-3 User files selection

2. Start the backup by clicking Backup. The files are backed up to the Tivoli Storage Manager server. Note that we selected for our backup not only the actual content of the INSTALL directory but also its SAN File System FlashCopy image, which resides in the .flashcopy/Image-8 folder. If you make a FlashCopy image each day (using a different directory) and back it up, Tivoli Storage Manager incremental backup will back up all the files each time. For information about how to back up SAN File System FlashCopy images incrementally using the Tivoli Storage Manager -snapshotroot option, see 12.3.3,


“Backing up FlashCopy images with Tivoli Storage Manager the -snapshotroot option” on page 390.

Restoring user data using Tivoli Storage Manager client for WindowsHaving backed up both actual data and its FlashCopy image, we can execute the restore scenarios.

Scenario 1: Restoring selected file to original destinationThis scenario restores files from the Tivoli Storage Manager backup of the actual fileset. We deleted the INSTALL directory, which we now restore using Tivoli Storage Manager. We are showing the restore of one folder for demonstration purposes, but Tivoli Storage Manager can restore multiple files or folders as well as an entire file system.

The steps in this scenario are:

1. Start the Tivoli Storage Manager Backup-Archive Client and select Restore. In Figure 12-4, we chose to restore the folder.

Figure 12-4 Restore selective file selection

2. We chose to restore to the original location, as shown in Figure 12-5 on page 386. Click Restore to start the restore.


Figure 12-5 Select destination of restore file(s)

The deleted file is restored.

Scenario 2: Restoring FlashCopy image to a different destinationThis scenario restores the files that were backed up from the FlashCopy image to the real fileset location. The steps in this scenario are:

1. Start the Tivoli Storage Manager Backup-Archive Client. Select Restore.

2. Select the files to restore, as shown in Figure 12-6. We are restoring the Image-8 folder from the FlashCopy image.

Figure 12-6 Restore files selection for FlashCopy image backup

3. Select the destination to restore the files to. We restore the folder to the win2kfiles fileset in S:\winhome\win2kfiles\testfolder, as shown in Figure 12-7 on page 387. Click Restore


to start the restore. Note that we could not (and it would not make sense to) restore the files to the .flashcopy directory as FlashCopy images, so their directories are read-only.

Figure 12-7 Restore files destination path selection

The restore of the FlashCopy files is now complete — the original folder is restored.

12.3.2 Backing up user data in UNIX filesets with Tivoli Storage Manager client for AIX

This section introduces the following backup and restore scenarios:

� Backing up and restoring files using data in an actual fileset

� Backing up and restoring SAN File System FlashCopy images using the -snapshotroot Tivoli Storage Manager option

Backing up and restoring files using data in an actual filesetThis scenario backs up sample files in the aixfiles and lixfiles filesets, as shown in Example 12-1. Our example uses the command line interface.

Example 12-1 Files to back up using Tivoli Storage Manager AIX client

Rome:/sfs/sanfs/lixfiles/linuxhome/install >ls -ltotal 2048-rw-rw-rw- 1 root system 696679 Jun 01 11:07 TIVguid.i386.rpmRome:/sfs/sanfs/lixfiles/linuxhome/install >ls -l ../../../aixfiles/aixhome/inst.imagestotal 48897-rw-r--r-- 1 root system 0 May 26 17:47 .toc-rw-r--r-- 1 root system 25034752 May 26 17:46 510005.v2.tardrwxr-x--- 2 root system 48 May 26 17:47 lost+found/

Tip: Regular periodic FlashCopy images are highly recommended. They are the most efficient method for backing up and restoring files quickly in scenarios where the metadata is still available.


1. Back up the files with the Tivoli Storage Manager client. Example 12-2 shows the output.

Example 12-2 Backing up files using Tivoli Storage Manager AIX command line client

Rome:/sfs/sanfs >dsmc selective "/sfs/sanfs/aixfiles/aixhome/inst.images/*" "/sfs/sanfs/lixfiles/linuxhome/install/*"IBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 2.0(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Node Name: AIXROMESession established with server NPSRV2: Windows Server Version 5, Release 2, Level 2.0 Server date/time: 06/02/04 09:51:00 Last access: 06/02/04 09:48:37

Selective Backup function invoked.

Directory--> 72 /sfs/sanfs/aixfiles/aixhome/inst.images [Sent]Directory--> 312 /sfs/sanfs [Sent]Directory--> 96 /sfs/sanfs/aixfiles [Sent]Directory--> 144 /sfs/sanfs/aixfiles/aixhome [Sent]Normal File--> 27,673,600 /sfs/sanfs/aixfiles/aixhome/inst.images/IP22727.tivoli.tsm.client.ba.32bit [Sent]Selective Backup processing of '/sfs/sanfs/aixfiles/aixhome/inst.images/*' finished without failure.

Directory--> 72 /sfs/sanfs/lixfiles/linuxhome/install [Sent]Directory--> 312 /sfs/sanfs [Sent]Directory--> 72 /sfs/sanfs/lixfiles [Sent]Directory--> 192 /sfs/sanfs/lixfiles/linuxhome [Sent]Normal File--> 696,679 /sfs/sanfs/lixfiles/linuxhome/install/TIVguid.i386.rpm [Sent]Selective Backup processing of '/sfs/sanfs/lixfiles/linuxhome/install/*' finished without failure.

Total number of objects inspected: 10Total number of objects backed up: 10Total number of objects updated: 0Total number of objects rebound: 0Total number of objects deleted: 0Total number of objects expired: 0Total number of objects failed: 0Total number of bytes transferred: 27.05 MBData transfer time: 2.32 secNetwork data transfer rate: 11,909.43 KB/secAggregate data transfer rate: 9,186.13 KB/secObjects compressed by: 0%Elapsed processing time: 00:00:03

2. In Example 12-3, we simulate data loss in the fileset that was backed up earlier. We delete the /sfs/sanfs/aixfiles/aixhome/inst.images/inst.images and /sfs/sanfs/lixfiles/linuxhome/install directories.

Example 12-3 Simulating the loss of data by deleting directories that we backed up in step 1

Rome:/sfs/sanfs >rm -rf /sfs/sanfs/lixfiles/linuxhome/installRome:/sfs/sanfs >rm -rf /sfs/sanfs/aixfiles/aixhome/inst.images

3. We restore our files using the Tivoli Storage Manager AIX line client from the backup created earlier, as shown in Example 12-4 on page 389.


Example 12-4 Restoring files from Tivoli Storage Manager AIX client backup

dsmc restore "/sfs/sanfs/aixfiles/aixhome/inst.images/*";dsmc restore "/sfs/sanfs/lixfiles/linuxhome/install/*"IBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 2.0(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Restore function invoked.


ANS1247I Waiting for files from the server...Restoring 72 /sfs/sanfs/aixfiles/aixhome/inst.images [Done]Restoring 27,673,600 /sfs/sanfs/aixfiles/aixhome/inst.images/IP22727.tivoli.tsm.client.ba.32bit [Done]

Restore processing finished.

Total number of objects restored: 2Total number of objects failed: 0Total number of bytes transferred: 26.39 MBData transfer time: 20.45 secNetwork data transfer rate: 1,321.14 KB/secAggregate data transfer rate: 1,174.53 KB/secElapsed processing time: 00:00:23IBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 2.0(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Restore function invoked.


ANS1247I Waiting for files from the server...Restoring 72 /sfs/sanfs/lixfiles/linuxhome/install [Done]Restoring 696,679 /sfs/sanfs/lixfiles/linuxhome/install/TIVguid.i386.rpm [Done]< 680.40 KB> [ - ]Restore processing finished.

Total number of objects restored: 2Total number of objects failed: 0Total number of bytes transferred: 680.40 KBData transfer time: 0.36 secNetwork data transfer rate: 1,877.42 KB/secAggregate data transfer rate: 135.87 KB/secElapsed processing time: 00:00:05


4. We check whether the files have been restored to their original locations in Example 12-5.

Example 12-5 Check if files have been successfully restored

Rome:/sfs/sanfs >ls -l /sfs/sanfs/lixfiles/linuxhome/installtotal 2048-rw-rw-rw- 1 root system 696679 Jun 01 13:26 TIVguid.i386.rpmRome:/sfs/sanfs >ls -l /sfs/sanfs/aixfiles/aixhome/inst.imagestotal 55296-rw-r----- 1 root system 27673600 Jun 01 14:38 IP22727.tivoli.tsm.client.ba.32bit

12.3.3 Backing up FlashCopy images with Tivoli Storage Manager the -snapshotroot option

Before we introduce an actual backup and restore scenario that uses -snapshotroot (the Tivoli Storage Manager option for backing up data), we will briefly explain the purpose of this Tivoli Storage Manager option.

The -snapshotroot option can be used with Tivoli Storage Manager incremental and selective backups as well as archives. It helps to associate snapshot data that is created by any third-party application with a native FlashCopy capability, such as SAN File System FlashCopy, with the actual file space data that is stored on the Tivoli Storage Manager. The -snapshotroot option does not provide any functionality to take a FlashCopy (snapshot) image. It only helps to manage data that has been already created by a FlashCopy-capable software application.

Our example explains how -snapshotroot works.

Assume that we have a fileset called aixfiles, attached to directory /sfs/sanfs/aixfiles/aixhome. When we create a SAN File System FlashCopy image for this particular fileset, a subdirectory is created in the /sfs/sanfs/aixfiles/aixhome/.flashcopy directory. That subdirectory holds the snapshot of the actual files and directories stored in /sfs/sanfs/aixfiles/aixhome and its subdirectories. Example 12-6 shows two FlashCopy images that we created for the purpose of this scenario.

Example 12-6 SAN File System FlashCopy images in /sfs/sanfs/aixfiles/aixhome.flashcopy directory

Rome:/sfs/sanfs/aixfiles/aixhome/.flashcopy >pwd/sfs/sanfs/aixfiles/aixhome/.flashcopyRome:/sfs/sanfs/aixfiles/aixhome/.flashcopy >ls -ltotal 2d--------- 5 root system 120 Jun 01 22:32 Image06-01-2004/d--------- 5 root system 120 Jun 01 22:33 Image06-02-2004/

Now, in order to back up the SAN File System FlashCopy image using the Tivoli Storage Manager client, you would normally run the following command:

dsmc incr "/sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-01-2004/*" -subdir=yes

In this case, Tivoli Storage Manager client starts to process the data in the /sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-01-2004/ directory and its subdirectories.

Important: This section only introduces our example, highlighting any necessary considerations and steps that you need to take. We give more detailed instructions in “Setting up the environment for snapshotroot-based Tivoli Storage Manager backup” on page 392.


With the snapshotroot option, we cane to base the backup on the SAN File System FlashCopy image, while still preserving (from the Tivoli Storage Manager server perspective) the actual absolute directory structure and file names from which that particular SAN File System FlashCopy image originates. However, the main reason you might consider using a snapshotroot based backup approach is that it allows you to back up SAN File System FlashCopy images using Tivoli Storage Manager incremental methods. This requires you to add virtual mount point definitions into the Tivoli Storage Manager client’s dsm.sys configuration file for:

� All the filesets you plan to back up� Each and every SAN File System FlashCopy image that you create for any of your filesets

In Example 12-7, you can see how we have defined virtual mount points in our dsm.sys configuration file.

Example 12-7 Virtual mount point definitions example

virtualmountpoint /sfs/sanfs/aixfiles/aixhomevirtualmountpoint /sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-01-2004virtualmountpoint /sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-02-2004

Without these virtual mount point definitions, the Tivoli Storage Manager server would store all SAN File System related backups into a single file space (in our example, AIXRome /sfs), as shown in Example 12-8.

Example 12-8 Q FILESPACE command: no virtual mount point definitions

tsm: NPSRV2>q filesp

Node Name: AIXROME Filespace Name: /sfs FSID: 5 Platform: AIX Filespace Type: SANFSIs Filespace Unicode?: No Capacity (MB): 294,480.0 Pct Util: 3.7

If we, however, define a virtual mount point for our aixfiles fileset and also for all of our SAN File System FlashCopy images, and run a Tivoli Storage Manager backup, then the file space layout on the Tivoli Storage Manager server (output of the q filesp command) will now look as shown in Example 12-9.

Example 12-9 Q FILESPACE command: With virtual mount point definitions


Node Name: AIXROME Filespace Name: /sfs FSID: 5 Platform: AIX Filespace Type: SANFSIs Filespace Unicode?: No Capacity (MB): 294,480.0 Pct Util: 3.7

Node Name: AIXROME Filespace Name: /sfs/sanfs/aixfiles/aixhome FSID: 6 Platform: AIX


Filespace Type: SANFSIs Filespace Unicode?: No Capacity (MB): 304,688.0 Pct Util: 3.6

Node Name: AIXROME Filespace Name: /sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-01-2004 FSID: 7 Platform: AIX Filespace Type: SANFSIs Filespace Unicode?: No Capacity (MB): 304,688.0 Pct Util: 3.6

Node Name: AIXROME Filespace Name: /sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-02-2004 FSID: 8 Platform: AIX Filespace Type: SANFSIs Filespace Unicode?: No Capacity (MB): 304,688.0 Pct Util: 3.6

So far, we have explained the purpose of the -snapshotroot option and have outlined the role of Tivoli Storage Manager client’s virtual mount points. Now, we describe how to back up SAN File System data using the -snapshotroot option.

Using the -snapshotroot option to back up SAN File System filesetsAs mentioned earlier, you could back up a SAN File System FlashCopy image using a dsmc command with a syntax similar to the following, specifying the FlashCopy image directory:

dsmc incr "/sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-01-2004/*" -subdir=yes

However with the -snapshotroot backup approach, you do not specify FlashCopy image directory but instead the actual fileset data directory. The FlashCopy directory is then specified as the option for the -snapshotroot option, as shown here:

dsmc incr /sfs/sanfs/aixfiles/aixhome/ -snapshotroot=/sfs/sanfs/aixfiles/aixhome/.flashcopy /Image06-02-2004

Because we have now explained the concept behind backing up SAN File System data based on their FlashCopy images using the -snapshotroot Tivoli Storage Manager client option, we can now show a step-by-step scenario for this type of backup in our lab environment.

Setting up the environment for snapshotroot-based Tivoli Storage Manager backup

The -snapshotroot option for SAN File System is supported, at the time of writing, on Tivoli Storage Manager V5.2.3.1 and higher clients for AIX, Windows, Solaris, and Linux. To set up the environment for this option:

1. Make sure that you have a virtual mount point defined for your fileset in the Tivoli Storage Manager dsm.sys file. If you do not, create the following definition:

virtualmountpoint /sfs/sanfs/aixfiles/aixhome


2. Create the SAN File System FlashCopy image. You can use either the SAN File System graphical console or the command line interface. In our example, we use the command line interface:

sfscli>mkimage -fileset aixfiles -dir Image06-01-2004 aixfiles_fcopy1

3. Add a new virtual mount point definition in dsm.sys file for the newly created SAN File System FlashCopy image in step 2:

virtualmountpoint /sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-01-2004

4. Make sure that the .flashcopy directory is excluded from normal Tivoli Storage Manager backups by adding the appropriate exclude.dir option into the dsm.sys file:

exclude.dir t:\...\.flashcopy

5. This step is for AIX only. If you are configuring this example on another client than AIX, skip this step. Add the testflag option to the dsm.sys file to prevent undesired object updates due to AIX LVM inode number differences between the actual and FlashCopy data:

testflag ignoreinodeupdate

Example 12-10 shows the completed dsm.sys file for our environment.

Example 12-10 Example of the dsm.sys file in our environment

Rome:/usr/tivoli/tsm/client/ba/bin >cat dsm.sysSErvername config1 COMMmethod TCPip TCPPort 1500 TCPServeraddress 9.42.164.126 Nodename AIXRome Passwordaccess generate

***** added for SAN File System *****testflag ignoreinodeupdatevirtualmountpoint /sfs/sanfs/aixfiles/aixhomevirtualmountpoint /sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-01-2004virtualmountpoint /sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-02-2004

Note: If you are using a Windows client, the dsm.sys file is not present. Instead, you have to use Windows sharing to create a local share for the fileset directory, as follows:

net share WINfileset t:\winhome\win2kfiles\

You also need to create another local share for the directory location of the FlashCopy image to be backed up, as follows:

net share WINimage1 t:\winhome\win2kfiles\.flashcopy\Image1

Exclude the .flashcopy directory from Tivoli Storage Manager so the data is not backed up twice. Include the following in the dsm.opt file:

exclude.dir /.../.flashcopy

Then in the dsmc command, specify the share names, as follows:

dsmc inc \\WINWASHINGTON\Winfileset -snapshotroot=\\WINWASHINGTON\Image1


6. Perform the Tivoli Storage Manager incremental, selective, or archive backup operation. In our case, we performed an incremental backup of the fileset, with the -snapshotroot option based on Image06-02-2004, as follows:

dsmc incr /sfs/sanfs/aixfiles/aixhome/\ \-snapshotroot=/sfs/sanfs/aixfiles/aixhome/.flashcopy/Image06-02-2004

7. Now that we have backed up the SAN File System data incrementally using the FlashCopy image, we can delete that FlashCopy image on MDS using the command line interface:

rmimage -fileset aixfiles aixfiles_fcopy1

The next section introduces the backup scenario that is based on the -snapshotroot option, which demonstrates how the Tivoli Storage Manager incremental backup using -snapshotroot really works.

Scenario: Backing up using the -snapshotroot option Assume that we have a fileset named aixfiles and no SAN File System Flash Copy images have been created yet. The SAN File System fileset’s directory initially contains a file named file1.exe. To back up using the -snapshotroot option:

1. Create SAN File System Flash Copy image for fileset aixfiles, as shown in Example 12-11.

Example 12-11 Create SAN File System Flash Copy image

sfscli> mkimage -fileset aixfiles -dir aixfiles-image-1 aixfiles-image-1CMMNP5168I FlashCopy image aixfiles-image-1 on fileset aixfiles was created successfully

2. Add the virtual mount point definition to our DSM.SYS configuration file and run an incremental backup of the fileset’s data using the snapshotroot option, as shown in Example 12-12.

Example 12-12 Run Tivoli Storage Manager backup of the data

Rome:/sfs/sanfs/aixfiles/aixhome >dsmc incr /sfs/sanfs/aixfiles/aixhome/ -snapshotroot=/sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-1

IBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 2.0(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.


Incremental backup of volume '/sfs/sanfs/aixfiles/aixhome/'Directory--> 48 /sfs/sanfs/aixfiles/aixhome/lost+found [Sent]Normal File--> 5,495,760 /sfs/sanfs/aixfiles/aixhome/file1.exe [Sent]Successful incremental backup of '/sfs/sanfs/aixfiles/aixhome/*'

Total number of objects inspected: 2Total number of objects backed up: 2Total number of objects updated: 0Total number of objects rebound: 0Total number of objects deleted: 0Total number of objects expired: 0Total number of objects failed: 0Total number of bytes transferred: 5.24 MBData transfer time: 0.44 sec


Network data transfer rate: 11,973.98 KB/secAggregate data transfer rate: 1,775.06 KB/secObjects compressed by: 0%Elapsed processing time: 00:00:03Rome:/sfs/sanfs/aixfiles/aixhome >

The /sfs/sanfs/aixfiles/aixhome/file1.exe file was backed up by Tivoli Storage Manager using the SAN File System image in /sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-1/file1.exe.

3. Add a new file into the /sfs/sanfs/aixfiles/aixhome directory named file2.exe.

4. Create a new SAN File System FlashCopy image in the /sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-2 directory, as shown in Example 12-13.

Example 12-13 Creating a new FlashCopy image

sfscli> mkimage -fileset aixfiles -dir aixfiles-image-2 aixfiles-image-2CMMNP5168I FlashCopy image aixfiles-image-2 on fileset aixfiles was created successfully.

5. Add a new virtual mount point for the new SAN File System FlashCopy image aixfiles-image-2 (Example 12-14).

Example 12-14 Adding a new virtual mount point definition into DSM.SYS and run new backup

Rome:/sfs/sanfs/aixfiles/aixhome >cat /usr/tivoli/tsm/client/ba/bin/dsm.sysSErvername config1 COMMmethod TCPip TCPPort 1500 TCPServeraddress 9.42.164.126 Nodename AIXRome Passwordaccess generate

***** added for SAN File System *****testflag ignoreinodeupdatevirtualmountpoint /sfs/sanfs/aixfiles/aixhomevirtualmountpoint /sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-1virtualmountpoint /sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-2

6. Run backup again, using the -snapshotroot option pointing to the latest Flashcopy image, aixfiles-image-2 (Example 12-15).

Example 12-15 Run backup again, this time using the aixfiles-image-2 image

Rome:/sfs/sanfs/aixfiles/aixhome >dsmc incr /sfs/sanfs/aixfiles/aixhome/\ \-snapshotroot=/sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-2 IBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 2.0(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.


Incremental backup of volume '/sfs/sanfs/aixfiles/aixhome/'Normal File--> 5,495,760 /sfs/sanfs/aixfiles/aixhome/file2.exe [Sent]Successful incremental backup of '/sfs/sanfs/aixfiles/aixhome/*'

Total number of objects inspected: 3Total number of objects backed up: 1


Total number of objects updated: 0Total number of objects rebound: 0Total number of objects deleted: 0Total number of objects expired: 0Total number of objects failed: 0Total number of bytes transferred: 5.24 MBData transfer time: 0.40 secNetwork data transfer rate: 13,141.99 KB/secAggregate data transfer rate: 1,771.75 KB/secObjects compressed by: 0%Elapsed processing time: 00:00:03

As you can see, the /sfs/sanfs/aixfiles/aixhome directory was backed up incrementally, this time using the aixfiles-image-2 image. Therefore, we just backed up the newly added file - file2.exe.

7. Create the file3.exe file in the /sfs/sanfs/aixfiles/aixhome directory.

8. Make a SAN File System FlashCopy image named aixfiles-image-3, as shown in Example 12-16.

Example 12-16 Making another SAN File System FlashCopy image

sfscli> mkimage -fileset aixfiles -dir aixfiles-image-3 aixfiles-image-3CMMNP5168I FlashCopy image aixfiles-image-3 on fileset aixfiles was created successfully.

9. Add another file named file4.exe.

10.Run a backup, pointing the snapshotroot to the aixfiles-image-3 SAN File System FlashCopy image (do not forget to add a new virtual mount point for the aixfiles-image-3 image to the DSM.SYS configuration file). In this case, only the file3.exe is backed up and file4.exe should be ignored. Why? Because we added the file4.exe to the actual file system directory and did not generate a new SAN File System FlashCopy image afterwards. The SAN File System FlashCopy image aixfiles-image-3 does not contain the image of the file file4.exe, because the file was created after the image was taken. Therefore, file4.exe is not backed up. This is how the snapshotroot option works. In each case, the fileset is backed up incrementally, using the specified FlashCopy image as a base.

Example 12-17 Final backup

Rome:/sfs/sanfs/aixfiles/aixhome >hotroot=/sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-3 <IBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 2.0(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.


Incremental backup of volume '/sfs/sanfs/aixfiles/aixhome/'Normal File--> 5,495,760 /sfs/sanfs/aixfiles/aixhome/file3.exe [Sent]Successful incremental backup of '/sfs/sanfs/aixfiles/aixhome/*'

Total number of objects inspected: 4Total number of objects backed up: 1Total number of objects updated: 0Total number of objects rebound: 0Total number of objects deleted: 0


Total number of objects expired: 0Total number of objects failed: 0Total number of bytes transferred: 5.24 MBData transfer time: 0.40 secNetwork data transfer rate: 13,115.34 KB/secAggregate data transfer rate: 1,768.19 KB/secObjects compressed by: 0%Elapsed processing time: 00:00:03

As you can see, our assumption that only the file3.exe file is backed up was right. The Tivoli Storage Manager backup client searches the actual data directory /sfs/sanfs/aixfiles/aixhome for existing objects to be backed up, but for the backup itself, it uses the SAN File System FlashCopy directory specified by the snapshotroot option, in our case, /sfs/sanfs/aixfiles/aixhome/aixfiles-image-3.

This scenario also explains the role of the virtual mount point entries in the DSM.SYS configuration file. As you can see in Example 12-14 on page 395, there is one virtual mount point created for the /sfs/sanfs/aixfiles/aixhome directory. We need this option to say to the Tivoli Storage Manager server that it has to create and use a new separate file space for the /sfs/sanfs/aixfiles/aixhome directory. See the output of the q filesp command from the Tivoli Storage Manager command line interface shown in Example 12-18.

Example 12-18 Query filesp command output from command line interface


Node Name: AIXROME Filespace Name: /sfs/sanfs/aixfiles/aixhome FSID: 10 Platform: AIX Filespace Type: SANFSIs Filespace Unicode?: No Capacity (MB): 352,800.0 Pct Util: 8.1

Simply put, if you did not specify a virtual mount point for the /sfs/sanfs/aixfiles/aixhome directory (which is also the attach point of the SAN File System fileset aixfiles), and then ran a backup, the Tivoli Storage Manager file space name would be /sfs only (as shown in Example 12-8 on page 391) and you would not be able to run incremental backups using the snapshotroot option.

So, why do we need virtual mount point entries in dsm.sys for all of our SAN File System FlashCopy images? The reason is that you can only specify a mount point to the snapshotroot option, not a directory. If the virtualmountpoint entry for the aixfiles-image-3 image was not made, and you tried to run a backup with the snapshotroot option pointing to the /sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-3 directory, Tivoli Storage Manager client would generate an error message, as shown in Example 12-19 below.

Example 12-19 Need for dsm.sys virtual mount point entries for SAN File System FlashCopy images

Rome:/sfs/sanfs/aixfiles/aixhome >dsmc incr /sfs/sanfs/aixfiles/aixhome/ -snapshotroot=/sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-3

ANS7533E The specified drive '/sfs/sanfs/aixfiles/aixhome/.flashcopy/aixfiles-image-3' does not exist or is not a local drive.


ConclusionsUsing the snapshotroot option with your Tivoli Storage Manager backup client gives you the ability to use SAN File System FlashCopy images to back up data while still using the incremental backup method. In order to use the snapshotroot option, you need to add a virtualmountpoint entry for the actual fileset and also for each and every SAN File System FlashCopy image generated for that particular fileset. You can avoid the manual modification to your DSM.SYS file (in order to add a specific virtualmountpoint entry) by choosing the standard naming convention for your SAN File System FlashCopy images (Image-1, Image-2, Image-3, and so on). Because the SAN File System supports a maximum number of FlashCopy images of 32, you can predefine all your virtual mount points to your DSM.SYS configuration file and then automate the backup process using scripts.

12.4 Special environmentsThe next two examples show special considerations for SAN File System backup in large environments. An environment can be large in terms of the total size of data (for example, very large files) or the number of files to be transferred. In the first case, the bottleneck is most likely the data movement process. So, we can improve performance by increasing the number of Tivoli Storage Manager clients. In the second case (many files), the Tivoli Storage Manager server database is typically the bottleneck.

12.4.1 Large quantity of dataAn example scenario is a SAN File System media environment where there can be several hundred terabytes stored in the user pools. The average file size is large. Where there are specific backup windows or required backup throughput to be met, consider dedicating several SAN File System clients as backup nodes (as many as you need to achieve the throughput) and installing the Tivoli Storage Manager Storage Agent for LAN-free data transfer on them. Figure 12-2 on page 382 illustrates this scenario.

Beginning with Tivoli Storage Manager V5.3, you can back up the file data to the same node name using the Proxy Node feature. On the client, define node names as usual (for example, SANFS1, SANFS2, SANFS3) — one for each physical Tivoli Storage Manager client.

On the Tivoli Storage Manager server, using the Tivoli Storage Manager REGISTER NODE command, define a single virtual node name (for example, SFS) and also register the real node names of each of the Tivoli Storage Manager-clients for SAN File System (that is, SANFS1, SANFS2, SANFS3, and so forth).

Then associate each of the real client node names with the proxy (virtual) node name using the GRANT PROXY command, for example:

GRANT PROXY SFS SANFS1GRANT PROXY SFS SANFS2

Now, any of the SAN File System Tivoli Storage Manager clients can perform backup and restore equivalently, using the -asnodename parameter as follows:

dsmc -asnodename=SFS incr /filsystem1

By issuing this command for each fileset from a different Tivoli Storage Manager client, you can distribute the data movement load onto different machines and get the throughput as desired. For planning we recommend setting up schedules so that individual filesets or parts of filesets are backed up by particular Tivoli Storage Manager clients.


Now, all the data is stored in Tivoli Storage Manager under a single node name. All clients see the same view of the backed up data (QUERY BACKUP command) and on the server, QUERY FILESPACE, QUERY OCCUPANCY, and similar commands show the data as all owned by the virtual node. Using the single node name makes it easier to back up different filespaces from different Tivoli Storage Manager clients and to change the configuration if necessary. When it comes to restore, you can restore the data from any of the Tivoli Storage Manager clients (that is, you do not need to know which of the clients originally backed up the files).

12.4.2 Large amounts of filesIf your SAN FIle System environment contains a large number of files (for example, several million), the Tivoli Storage Manager database might be the bottleneck for backup performance and scalability. With a large number of files, the metadata processing overhead becomes increasingly significant compared to the actual data transfer time. In this case, you can improve throughput by having multiple, dedicated Tivoli Storage Manager servers installed preferably on the backup SAN File System clients themselves. Then, each of these machines can backup file systems independently to a dedicated Tivoli Storage Manager database. You can choose whether to have a dedicated tape library attached to each server, or you can use Library Sharing and use a single tape library for all of the servers (Figure 12-8).

Figure 12-8 Large amounts of files

In this scenario, because separate Tivoli Storage Manager servers are used, you do need to know which backup server is responsible for which fileset to find the data to restore.

Restriction: The throughput can only be as good as the bandwidth that is available from the user data LUNs. Watch for disk related bottlenecks.

SAN FS ClientsTivoli Storage Manager ServersTivoli Storage Manager ClientsLibrary Sharing

Pools

"Production" SAN FSClients

LAN

TapeLibraryUser System

SAN



Chapter 13. General troubleshooting

This chapter provides some general guidelines on how to troubleshoot a Tivoli Storage Manager SAN-based environment. It helps you identify the topic or component of an error by following an easy-to-understand flow chart. Additional sources for help are also included. This chapter discusses the following topics:

� Introduction to troubleshooting� Library and SAN troubleshooting� Operating system and drivers� Troubleshooting library sharing configurations

13


13.1 Introduction to troubleshootingFor resolving tape drive or library related problems in your Tivoli Storage Manager installation, follow the steps outlined in the flow chart shown in Figure 13-1 on page 403.

Today’s SAN environments can be very complex and configurations can vary significantly. Therefore, it is not possible to cover every possible error situation you might encounter. This chapter gives some general guidelines and orientation to figure out which component is the source of the error.

The troubleshooting process divides at the very beginning into two different tracks:

� Tivoli Storage Manager V5.3 environments using the SAN Discovery feature

� Tivoli Storage Manager environments prior to V5.3, or V5.3 where SAN Discovery is not used

So, follow the track that is suitable for your environment and try to resolve the issue or identify the faulty component. Annotations for each step are given in the text.

Additional resources for self-help support can be found on the Tivoli Storage Manager support Web site at:




Figure 13-1 General troubleshooting flow chart

Tape / Library Problems

SANDISCOVERY supported and enabled?

q path f=dq san

Q san shows device?

Is correct device driver installed?

Test device with mttest / lbtest /

tapeutil

OK?

Problem solved

YES

YES

YES

YES

NO

NO

Library and SAN

OS and Drivers

Powercycle device

OK?

Contact Vendor

NO

NO

NO

Path points to the right Device? update path

Test Device with mttest / lbtest /

tapeutil

OK?

NO

YES

NO

Is path online? update path

YES

NO

YES

1.1

1.2

1.3

1.41.5 1.6

1.7

1.8

1.9

1.10

1.11

1.3

1.6

Chapter 13. General troubleshooting 403

13.1.1 Step 1.1: QUERY SAN commandIssue the QUERY SAN command at the Tivoli Storage Manager server and examine the output (Example 13-1).

Example 13-1 QUERY SAN

tsm: AZOV_1>q san

Device Vendor Product Serial Number DeviceType-------- -------- ---------------- ---------------- ------------------DRIVE IBM ULT3580-TD2 1110176223 /dev/rmt0LIBRARY IBM ULT3582-TL 0000013108231000 /dev/smc0DRIVE IBM ULT3580-TD2 1110177214 /dev/rmt1LIBRARY IBM ULT3582-TL 0000013108231000 /dev/smc1

tsm: AZOV_1>

The intention is to determine if the drive or changer device can (still) be seen by the Tivoli Storage Manager server. The QUERY SAN command initiates a SAN Discovery and shows any devices that can be seen in the SAN. If the output includes the device you are looking for, then the whole chain of SAN, zoning, and so forth is correct and you do not have to worry about it.

If the device is missing or no devices at all appear, go to “Library and SAN troubleshooting” on page 409.

For more information about paths, see Chapter 6, Configuring Storage Devices, Defining Devices and Paths in IBM Tivoli Storage Manager Administrator’s Guide for your Tivoli Storage Manager server platform.

13.1.2 Step 1.2: Is the correct device driver installedIf there is no device driver installed or if you are not sure, go to 13.3, “Operating system and drivers” on page 412.

13.1.3 Step 1.3: Test the device Use the appropriate utility, depending on whether the Tivoli Storage Manager device driver or IBM tape device driver is used for the device in question. In general, IBM tape drives and libraries use the IBM tape device driver, and non-IBM devices use the Tivoli Storage Manager device driver.

Tivoli Storage Manager device driverWhen you install the Tivoli Storage Manager device driver fileset, there are two commands you can use for troubleshooting devices that are under the Tivoli Storage Manager tape driver (mt and lb devices):

� mttest, for testing tape drives� lbtest, for testing changer devices

These commands are in the following directories:

� /usr/tivoli/tsm/devices/bin on AIX� /opt/tivoli/tsm/devices/bin on other UNIX systems� C:\program files\tivoli\tsm\device (for example) on Windows systems


IBM tape driverFor IBM tape drives and libraries there is a utility called:

� tapeutil (AIX, Solaris)� ntutil (Windows)� IBMtapeutil (Linux), which is the equivalent to mttest/lbtest

The usage is similar to either the Tivoli Storage Manager device driver utility or the IBM tape drive utility. You invoke the utility, define the device name on which to operate, open the device, and issue a command (for example, a query to the device). If everything works, the device is ready for use.

Example 13-2 queries the element information about AIX /dev/rmt0 with tapeutil.

Example 13-2 tapeutil

azov.almaden.ibm.com:/usr/tivoli/tsm/devices/bin# tapeutil

General Commands: 1. Open a Device 5. Inquiry 9. Log Sense Page 2. Close a Device 6. Test Unit Ready 10. Mode Sense Page 3. Device Info 7. Reserve Device 11. Release Device 4. Tape Drive Service Aids 8. Request Sense Q. Quit Program

Medium Changer Commands: 12. Element Information 16. Move Medium 13. Position To Element 17. Load/Unload Medium 14. Element Inventory 18. Initialize Element Status 15. Exchange Medium 19. Prevent/Allow Medium Removal

Tape Commands: 20. Query/Set Parameters 30. Read and Write Tests 21. Prevent/Allow Medium Removal 31. Unload Tape 22. Rewind 32. Erase 23. Erase Gap 33. Write Filemarks 24. Forward Space Filemarks 34. Backward Space Filemarks 25. Forward Space Records 35. Backward Space Records 26. Space to End of Data 36. Query/Set Tape Position 27. Log Sense 37. Read or Write Files 28. Display Message 38. Query/Create/Change Partition 29. Synchronize Buffers 39. Report Density Support

Enter Selection: 1

Enter the device special file name (Example: /dev/rmt0): /dev/rmt0

Select mode (1=Read/Write, 2=Read Only, 3=Write Only, 4=Append): 1

Opening device...

Hit <enter> to continue...

Enter Selection for /dev/rmt0: 12

Getting element information...

Number of Robots .............. 1 First Robot Address ........... 1 Number of Slots ............... 22 First Slot Address ............ 4096


Number of Import/Exports ...... 1 First Import/Export Address ... 16 Number of Drives .............. 2 First Drive Address ........... 256

Hit <enter> to continue...

Enter Selection: q

azov.almaden.ibm.com:/usr/tivoli/tsm/devices/bin#

For more information about devices and drivers in Tivoli Storage Manager, see Chapter 5 in the IBM Tivoli Storage Manager Administrator’s Guide for your Tivoli Storage Manager server platform.

For more information about IBM tape driver issues, see IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers, User and Installation Guide, GC35-0154 at:

ftp://ftp.software.ibm.com/storage/devdrvr/Doc/

13.1.4 Step 1.4: Powercycle the deviceIf there are short outages in the SAN fabric or problems with a faulty cable or GBIC, the device might appear in the operating system but not report to tapeutil or mttest. In this case, the drive has probably hung, but the Fibre Channel interface might still work. To resolve this issue, powercycle (power off and power on) the drive. Either use the management interface of the library to do the powercycle, or if this is not possible, remove the power plug and reinsert. Wait a few minutes for the drive to complete its self-test cycle, and try to test it again.

Figure 13-2 shows how to powercycle a drive in an IBM 3584 tape library.

Figure 13-2 Powercycle a drive in a 3584 library



For more information about tape libraries see your vendors documentation. For information about IBM tape libraries see:

http://www-1.ibm.com/servers/storage/support/

13.1.5 Step 1.5: Confirm that the path is onlineAfter an error condition has occurred, Tivoli Storage Manager might set a path to a tape drive or library to offline. It then stays offline until it is set manually to online again. To determine if a path is offline, use the Tivoli Storage Manager QUERY PATH command (Example 13-3). The example shows that the path from SENEGAL_STA to DRIVE1 is offline.

Example 13-3 Determine if path is offline

tsm: AZOV_1>q path

Source Name Source Type Destination Destination On-Line Name Type----------- ----------- ----------- ----------- -------AZOV_1 SERVER 3582 LIBRARY YesAZOV_1 SERVER DRIVE1 DRIVE YesAZOV_1 SERVER DRIVE2 DRIVE YesSENEGAL_STA SERVER DRIVE1 DRIVE NoSENEGAL_STA SERVER DRIVE2 DRIVE YesTONGA_1 SERVER DRIVE1 DRIVE YesTONGA_1 SERVER DRIVE2 DRIVE Yes

tsm: AZOV_1>

For more information about paths, see Chapter 6 in the IBM Tivoli Storage Manager Administrator’s Guide for your Tivoli Storage Manager server platform.

13.1.6 Step 1.6: Update the pathTo set a path online, use the UPDATE PATH command, as shown in Example 13-4.

Example 13-4 Update path

tsm: AZOV_1>upd path senegal_sta drive1 srct=server destt=drive libr=3582 online =yesANR1722I A path from SENEGAL_STA to 3582 DRIVE1 has been updated.

tsm: AZOV_1>

If for any reason the device name has changed, update the path to point to the right drive (Example 13-5).

Example 13-5 Update path device name

tsm: AZOV_1>update path senegal_sta drive1 srct=server destt=drive libr=3582 dev i=mt3.1.1.0ANR1722I A path from SENEGAL_STA to 3582 DRIVE1 has been updated.

tsm: AZOV_1>



http://www-1.ibm.com/servers/storage/support/

13.1.7 Step 1.7: q path f=d To determine the device name that Tivoli Storage Manager uses for a tape drive, use the QUERY PATH command with the f=d parameter, as shown in Example 13-6.

Example 13-6 q path to get device name

tsm: AZOV_1>q path senegal_sta drive1 f=d

Source Name: SENEGAL_STA Source Type: SERVER Destination Name: DRIVE1 Destination Type: DRIVE Library: 3582 Node Name: Device: mt2.0.0.2 External Manager: LUN: Initiator: 0 Directory: On-Line: YesLast Update by (administrator): ADMIN Last Update Date/Time: 03/31/05 15:12:28

tsm: AZOV_1>

If there is no path that matches the drive, you need to define one.


13.1.8 Step 1. 8: Confirm that the path points to the correct deviceDevice names can change due to SAN reconfigurations. Depending on the platform used, you should use HBA persistent binding to bind the device name to a certain drive, or beginning with Tivoli Storage Manager V5.3, the SAN Discovery feature dynamically keeps track of device changes (see Chapter 9, “Tivoli Storage Manager SAN Discovery” on page 253).


13.1.9 Step 1. 9: Contact the vendorIf all else fails, contact the vendor of your tape library, drive, server, SAN switch, or Tivoli Storage Manager software. You can find information about how to contact IBM at:

http://www.ibm.com/planetwide

Note that you need the IBM customer number and any hardware serial numbers to open a problem record.



13.2 Library and SAN troubleshootingUse the flow-chart in Figure 13-3 to resolve library or SAN-related problems.

Figure 13-3 Library and SAN flow-chart

Is device visible in SAN Nameserver?

Check cablesCheck Switch PortPowercycle Device

OK?

Contact Vendor

Is Zoning correct? Fix Zoning

Is Server visible in SAN Nameserver?

Check cablesCheck Switch Port

OK?

Upgrade / Install Drivers and Firmware

OK?

Check HBA Drivers and Firmware

OK?

NO

YES

YES

YES

NO

NO

NO

NO

NO

NO

2.12.2

2.3

2.6

2.72.12.2


Additional information for the different steps are given in the sections that follow. When you have finished these steps, go to 13.3, “Operating system and drivers” on page 412 and continue the process.

13.2.1 Step 2.1: Is the device visible in SAN NameserverThe starting point in troubleshooting SAN problems is to check whether the device has logged in to the SAN fabric. To determine if the device has properly registered with the fabric nameserver, open the SAN switch management application, and list the nameserver entries. In our example, we use an IBM SAN switch 2005-B32. For Brocade switches, point your Web browser to the management IP address of the switch, and open the nameserver by clicking the icon in the lower left corner. Figure 13-4 shows the nameserver entries.

Figure 13-4 SAN switch nameserver

If a device appears in the list, it means it has properly registered with the SAN switch, and the cabling and physical should be OK.

For additional information about SAN switches see the IBM Redbook Implementing an Open IBM SAN, SG24-6116 or your vendor’s documentation.

13.2.2 Step 2.2: Check cables for drive etcIf a device does not appear in the nameserver list, check the following:

� Is the drive powered on?

� Is there a cable connection?

� Have you used the appropriate cable (Short Wave® or Long Wave, multi-mode, mono-mode, and so forth)?

� Is the switch port enabled?

� Is the switch port auto-sensing or fixed concerning speed (1 or 2 Gbps) or type (Gx)?

� Is the GBIC / SFP defective?


For more information about configuring or troubleshooting SAN components, see the IBM Redbook Implementing an Open IBM SAN, SG24-6116, or vendor-specific information.

13.2.3 Step 2.3: Is the zoning correctMany SAN-related problems are caused by incorrectly configured zoning. There are many different constraints regarding different environments, which can depend on:

� Is there only one server using a tape drive, or are multiple servers accessing a drive (for example, for library sharing or LAN-free)?

� Is the control path multipathed?

� Is the data path multipathed?

� Are there disk and tape devices in the SAN?

� Are there different servers platform in the SAN?

For specific information about zoning see:

� Designing and Optimizing an IBM Storage Area Network, SG24-6419

� IBM TotalStorage: SAN Product, Design, and Optimization Guide, SG24-6384

� Implementing IBM Tape in UNIX Systems, SG24-6502

� Implementing IBM Tape in Linux and Windows, SG24-6268

13.2.4 Step 2.1: Is the server visible in SAN NameserverYou can follow the instructions in 13.2.1, “Step 2.1: Is the device visible in SAN Nameserver” on page 410 for this step.

13.2.5 Step 2.2: Check cables for server etcYou can follow the instructions in 13.2.2, “Step 2.2: Check cables for drive etc” on page 410 for this step.

13.2.6 Step 2.6: Check HBA drivers and firmwareDue to incompatibilities in HBA drivers and firmware with SAN switch models or firmware, it is often the case that the HBA drivers and firmware have to be updated. It is always recommended to use the highest supported level. To determine supported HBAs and driver and firmware levels for IBM products, see the IBM HBA tool at:

http://knowledge.storage.ibm.com/HBA/HBASearchTool

13.2.7 Step 2.7: Contact the vendorIf all else fails, contact the vendor of your tape library, drive, server, SAN switch, or Tivoli Storage Manager software. You can find information about how to contact IBM at:




http://knowledge.storage.ibm.com/HBA/HBASearchTool


13.3 Operating system and driversFollow the flow-chart in Figure 13-5 to resolve operating system related problems with storage devices.

Figure 13-5 Operating system and drivers flow-chart

Check IBM Tape Device Driver

Is this an IBM device?

Is the right level installed?

Install / Update IBM Tape Device

Driver

Discover New Devices

Check TSM Device Driver

Is the right level installed?

Install / Update Tivoli Storage

Manager Device Driver

Devices visible to OS?

Contact Vendor

NO YES

NO

YES

NO

NO

YES

Reboot Server

NOOK?

3.1

3.23.3

3.4

3.5

3.6


Additional information is discussed in the sections that follow. When you have gathered the relevant information, if the problem still persists, return to the 13.1, “Introduction to troubleshooting” on page 402 and continue with the steps there.

13.3.1 Step 3.1: Is this an IBM deviceFor tape and changer device drivers, first determine whether your device is from IBM or from another vendor. Tivoli Storage Manager supports third-party products only through the Tivoli Storage Manager tape device driver. IBM devices are supported only with the IBM tape device driver. For information about your tape drive or library for AIX, HP, Sun, and Windows, see:


For Linux, see:


13.3.2 Step 3.2: Check the Tivoli Storage Manager device driverThe Tivoli Storage Manager tape device driver comes with the Tivoli Storage Manager server software. It is possible that device-related problems are fixed in a higher maintenance or patch level of Tivoli Storage Manager. See Tivoli Storage Manager support for details:


13.3.3 Step 3.3: Check the IBM tape device driverYou can download the IBM tape device driver from:

ftp://ftp.software.ibm.com/storage/devdrvr

It is always recommended to have the latest supported level installed.

For more information about IBM tape driver issues, see the IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers, User and Installation Guide, GC35-0154, at:


13.3.4 Step 3.4: Discover new devicesAfter changes in the SAN or the library, it might be necessary to scan the SAN in order for the operating system to recognize the new or changed devices. For information about how to scan for new devices, see 9.1, “SAN device mapping” on page 254 for details.

13.3.5 Step 3.5: Is the device visible to the operating systemIt is important that the operating system of the Tivoli Storage Manager server or Storage Agent can see the necessary tape devices.

AIXOn AIX, use the following commands:

� lsdev -Cc tape for IBM devices (Example 13-7 on page 414)� lsdev -Cc adsmtape for Tivoli Storage Manager devices (Example 13-8 on page 414)




ftp://ftp.software.ibm.com/storage/devdrvr



Example 13-7 List devices on AIX

azov.almaden.ibm.com:/# lsdev -Cc tapermt0 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)rmt1 Available 1D-08-02 IBM 3580 Ultrium Tape Drive (FCP)smc0 Available 1Z-08-02-PRI IBM 3582 Library Medium Changer (FCP)smc1 Available 1D-08-02-ALT IBM 3582 Library Medium Changer (FCP)azov.almaden.ibm.com:/#

Example 13-8 List Tivoli Storage Manager devices on AIX

(root@poco) /usr/tivoli/tsm/devices/bin>lsdev -Ccadsmtapemt0 Available 1V-08-01 Tape Drivemt1 Available 1V-08-01 Tape Drivemt2 Defined 1V-08-01 Tape Drivemt3 Defined 1V-08-01 Tape Drive(root@poco) /usr/tivoli/tsm/devices/bin>

To determine the serial numbers, use the lscfg command (Example 13-9).

Example 13-9 List serial numbers in AIX

azov.almaden.ibm.com:/# lscfg -vpl rmt0 rmt0 U0.1-P2-I4/Q1-W500308C140467003-L0 IBM 3580 Ultrium Tape Drive (FCP)

Manufacturer................IBM Machine Type and Model......ULT3580-TD2 Serial Number...............1110176223 Device Specific.(FW)........4772

azov.almaden.ibm.com:/#

To determine the World Wide Names, IDs, and so forth, use the lsattr command (Example 13-10).

Example 13-10 List device attributes in AIX

azov.almaden.ibm.com:/# lsattr -El rmt0alt_pathing no Enable Alternate Pathing Support Trueautoload no Use Autoloading Feature at End-of-Tape Trueblock_size 0 Block Size (0=Variable Length) Truecompress yes Use Hardware Compression on Tape Truedebug_trace no Debug Trace Logging Enabled Truedevtype ULT3580- Device Type Falselocation Location Truelogging no Activate volume information logging Truelun_id 0x0 Logical Unit Number Truemax_log_size 500 Maximum size of log file (in # of entries) Truenew_name New Logical Name Truenode_name 0x500308c140067003 World Wide Node Name Falseprimary_device rmt0 Primary Logical Device Falseretain_reserve no Retain Reservation Falserew_immediate no Use Immediate Bit in Rewind Commands Truescsi_id 0x506cc SCSI Target ID Truespace_mode SCSI Backward Space/Forward Space Record Mode Truetrace_logging no Trace Logging Enabled Truetrailer_labels no Trailer Label Processing Trueww_name 0x500308c140467003 World Wide Port Name Falseazov.almaden.ibm.com:/#


LinuxOn Linux, use the following commands:

� cat /proc/scsi/IBM* for IBM devices (Example 13-11)� autoconf or cat /proc/scsi/scsi for Tivoli Storage Manager devices (Example 13-12)

Example 13-11 List IBM tape devices on Linux

tsmwi:/proc/scsi # cat IBM*IBMtape version: 1.5.3IBMtape major number: 253Attached Changer Devices:Number Model SN HBA FO Path0 03584L32 0000078185860401 QLogic Fibre Channel 2300 Primary1 03584L32 0000078185860401 QLogic Fibre Channel 2300 AlternateIBMtape version: 1.5.3IBMtape major number: 253Attached Tape Devices:Number Model SN HBA FO Path0 ULT3580-TD2 1110207447 QLogic Fibre Channel 2300 NA1 ULT3580-TD2 1110219543 QLogic Fibre Channel 2300 NAtsmwi:/proc/scsi #

Example 13-12 List Tivoli Storage Manager devices on Linux

cadi:/opt/tivoli/tsm/devices/bin # ./autoconfThe total numbers of devices on the system are 4.

Tivoli Tape Drives:===================Index Minor Host CHN ID LUN Type Vendor_ID S/N Product_ID Rev.000 000 002 000 000 000 001 STK 331002037903 9840 1.34001 001 002 000 001 000 001 STK 331000048026 9840 1.34002 002 002 000 002 000 001 00048026 331000048026 9840 1.34003 003 002 000 003 000 001 00048026 331000048026 9840 1.34

cadi:/opt/tivoli/tsm/devices/bin #

cadi:/proc/scsi # cat scsiAttached devices:Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: STK Model: 9840 Rev: 1.34 Type: Sequential-Access ANSI SCSI revision: 03Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: STK Model: 9840 Rev: 1.34 Type: Sequential-Access ANSI SCSI revision: 03Host: scsi2 Channel: 00 Id: 02 Lun: 00 Vendor: IBM Model: 03592J1A Rev: 04E6 Type: Sequential-Access ANSI SCSI revision: 03Host: scsi2 Channel: 00 Id: 03 Lun: 00 Vendor: IBM Model: 03592J1A Rev: 04E6 Type: Sequential-Access ANSI SCSI revision: 03cadi:/proc/scsi #


WindowsOn Windows, see Windows Device Manager under Tape Devices or Medium Changers (Figure 13-6), or use tsmdlst in the console subdirectory of the Tivoli Storage Manager installation (Example 13-13).

Figure 13-6 List tape devices on Windows

The output of tsmdlst gives you more information about devices, whether from IBM or any third-party vendor. You can determine the serial numbers and World Wide Names, as well as IDs, LUNs, and so forth.

Example 13-13 List tape devices in WIndows with tsmdlst

C:\Program Files\Tivoli\tsm\console>tsmdlst

Computer Name: TONGATSM Device Driver: Not Running (TSM information may not be accurate)

TSM Name ID LUN Bus Port SSN WWN TSM Type Device Identifier-----------------------------------------------------------------------------------------------------------mt0.0.0.2 0 0 0 2 1110177214 500308C140467006 LTO IBM ULT3580-TD2 4772lb0.1.0.2 0 1 0 2 0000013108231000500308C140467006 LIBRARY IBM ULT3582-TL 237Bmt1.0.0.2 1 0 0 2 1110176223 500308C140467003 LTO IBM ULT3580-TD2 4772lb1.1.0.2 1 1 0 2 0000013108231000500308C140467003 LIBRARY IBM ULT3582-TL 237BC:\Program Files\Tivoli\tsm\console>


SolarisOn Solaris, use the following commands:

� tapelist for IBM tape devices (Example 13-14)� tsmdlst for all devices, IBM and third-party vendor (Example 13-15)

Example 13-14 List IBM devices on Solaris

bash-2.03# tapelistIBM Tape Device Information : Instance : 6248 Special File : /dev/rmt/8st Device : 03592J1A Serial Number : 000001300117 TGT/LUN : 54/0 Ucode : 04E6 World Wide NN : 50050763020000C5 World Wide PN : 50050763024000C5 Dev Phy Path : /devices/pci@1f,4000/fibre-channel@2/IBMtape@36,0 Path Type : N/A

--- more ---


--- more ---

bash-2.03#

Example 13-15 List all devices on Solaris

bash-2.03# ./tsmdlist

IBM TIVOLI STORAGE MANAGER by IBMDevice List Utility Program for Sun SolarisLicensed Materials - Property of IBM5698-ISE (C) Copyright IBM Corporation 2004. All rights reserved.U.S. Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corporation.

Inst Special File Vendor Product Serial Target LUN World Wide Name Firmware---- ------------- ------- ------- ------------ ------ --- --------------- --------3204 /dev/rmt/2mt STK 9840 331000048026 9 0 500104f00043eaa7 1.346 /dev/rmt/0mt HP C1537A N/A 5 0 N/A L7063203 /dev/rmt/1mt STK 9840 331002037903 8 0 500104f00045cb26 1.34


bash-2.03#


For more information about IBM tape devices, see:

� Implementing IBM Tape in UNIX Systems, SG24-6502� Implementing IBM Tape in Linux and Windows, SG24-6268

13.3.6 Step 3.6: Contact the vendorIf all else fails, contact the vendor of your tape library, drive, server, SAN switch, or Tivoli Storage Manager software. You can find information about how to contact IBM at:



13.4 Troubleshooting library sharing configurationsHere are some tips for troubleshooting a library sharing environment.

13.4.1 Re-synchronizing server-to-server communicationWhen setting up a Library Client, sometimes the shared library definition statement fails, as shown in Example 13-16. Usually this indicates a problem with the server-to-server communication.

Example 13-16 Define shared library failed

tsm: SCAMP_1>define library 3494 libtype=shared primarylibmanager=poco_1ANR2032E DEFINE LIBRARY: Command failed - internal server error detected.ANR9999D ThreadId<36> issued message 2032 from:ANS8001I Return code 4

To solve this problem, you need to synchronize the server-to-server communication. Use the UPDATE SERVER command on both the Library Client (as shown in Example 13-17) and the Library Manager (as shown in Example 13-18).

Example 13-17 Library Client: Synchronize the server-to-server communication

tsm: SCAMP_1>upd server POCO_1 FORCESync=yes

Do you wish to proceed? (Yes (Y)/No (N)) yANR1662I Server POCO_1 updated

Example 13-18 Library Manager: Synchronize the server-to-server communication

tsm: POCO_1>upd server SCAMP_1 FORCESync=yes

Do you wish to proceed? (Yes (Y)/No (N)) yANR1662I Server SCAMP_1 updated



13.4.2 Define library path fails for IBM 3494 Tape LibraryWhen defining a library path for an IBM 3494, you might get an I/O error, as shown in Example 13-19. Check the ibmatl.conf file. The Library Name in this file must be exactly the same as the value in the option DEVICE on the DEFINE PATH statement. In our example, we use the library name 3494c in the ibmatl.conf (as shown in Example 13-20), but we incorrectly tried to define the path with the device=3494b. To fix this problem, rerun the DEFINE PATH command with the correct DEVICE parameter.

Example 13-19 I/O error during the define path command

tsm: SCAMP_1>DEFINE PATH scamp_1 3494b SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=3494bANR8418E DEFINE PATH: An I/O error occurred while accessing library 3494B.ANS8001I Return code 15.

Example 13-20 Ibmatl.conf file

## (C) COPYRIGHT International Business Machines Corp. 1993, 1998# All Rights Reserved# Licensed Materials - Property of IBM## US Government Users Restricted Rights - Use, duplication or# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.### This is the file which defines the 3494 libraries and how they are attached.# The format of this file is:## Library name address identifier <address2>#3494c 9.11.213.8 scamp

13.4.3 ACSLS volume already lockedAfter halting the Tivoli Storage Manager server application, removing all volume locks from ACSLS, and restarting the Tivoli Storage Manager server application, the following error message might be received when Tivoli Storage Manager attempts to access volumes in the ACSLS library:

ANR8860W Volume XXXX is already locked by...

The lack of a user ID in the above error message indicates a problem with ACSLS not retaining the user ID information. StorageTek has released fixes PTF760827 for ACSLS 6.0.1 and PUT0203 for ACSLS 6.1 to resolve this problem. Contact StorageTek to obtain these fixes.

After the fix has been applied, follow these steps to reinitialize the volume locks:

1. Halt Tivoli Storage Manager server.

2. Clear all volume locks for Tivoli Storage Manager volumes using the ACSLS command clear lock.

3. Start the Tivoli Storage Manager server, ensuring that the ACSQUICKINIT option is set to no in the dsmserv.opt file.

If multiple applications, including multiple Tivoli Storage Manager servers, are using the same library, then special care is needed when clearing the ACSLS locks to avoid volume ownership confusion. Contact StorageTek for more information related to the specific steps.


Library initialization might take some time if there are many volumes to lock. The library should be ready for operation when you receive the following message in the Tivoli Storage Manager activity log:

ANR8850I ACSLS library <libraryname> is ready for operations.

13.4.4 ACSLS SSI Daemon requires correct name resolutionThe Tivoli Storage Manager server uses the SSI background process to communicate with the ACSLS server. On start, the SSI obtains the local host name and then uses the configured name resolution service to obtain the IP address for this host name. Then it creates a socket for this IP address. SSI will not function if this host name is resolved to a non-local or non-existent IP address. Most likely, TCP/IP 68 (EADDRNOTAVAIL) is reported in such a case. To verify that the local host name can be resolved to a correct IP address, issue the nslookup <hostname> command from the UNIX prompt.

13.4.5 Cannot connect to a Windows Tivoli Storage Manager server instanceIf we set up more than one Tivoli Storage Manager server instance on a Windows system using the install wizard (as shown in Figure 13-7), in some Tivoli Storage Manager versions, it creates a TCP/IP port conflict.

Figure 13-7 Windows: Add new Tivoli Storage Manager Server

Table 13-1 shows the TCP/IP port assignment after the second Tivoli Storage Manager server installation.

Table 13-1 TCP/IP port assignment after using the Windows wizard

In this case, we have to change the TCPADMINPORT option to a different TCP/IP port. Restart the Tivoli Storage Manager server to activate the new port assignment.

Purpose TSM instance 1 TSM instance 2

HTTPPort 1580 1581

TCPPort 1500 1501

TCPADMINPort 1500 1500


Appendix A. Understanding TCP/IP ports for LAN-free in Tivoli Storage Manager

There are several different TCP/IP port settings that might be used when configuring a LAN-free environment. If these settings are not defined properly, it can cause operations such as server-to-server or the running of the Storage Agent to fail. It can also become quite confusing when trying to incorporate all the different TCP/IP port settings.

This appendix shows these different TCP/IP port related options and explains how they are used. It documents all these options in one spot, so that you do not have to read the various Tivoli Storage Manager manuals to understand how to use the options.

A


Introduction to TCP/IP portsYou might find it necessary to change some TCP/IP ports from their default settings in order to have proper functionality or to avoid port conflicts with other applications. Whatever the case, it is important to understand the interactions that the port settings have with each other. Knowing which port numbers have to match up simplifies the setup.

The key to understanding Tivoli Storage Manager TCP/IP ports is in understanding the way they interact. Figure A-1 shows how the TCP/IP ports match up. Note that not all of the ports are set at their default values. The purpose of using the specified port numbers is to show how the ports correlate. The sections that follow break down the different TCP/IP port definitions and their use.

Figure A-1 Matching TCPPORT settings

STORAGE AGENT(STA)

TIVOLI STORAGE MANAGER SERVER

CLIENT

TCPCLIENTPort 1501

TCPport 1500

LANFREETCPport 1502

TCPADMINPort 1505

DEFINE SERVER…. LLADDRESS=1500

devconfig.out

dsm.opt

TCPport 1502

dsmsta.opt

dsmserv.opt

TCPADMINPort 1505

TCPport 1500

SET SERVERLLADDRESS 1500 CROSSDEFINE YES

DEFINE SERVER STA…LLADDRESS=1502

SERVER-TO-SERVER COMMUNICATION OPTIONS

TIVOLI STORAGE MANAGER

ADMINISTRATOR

ADMINONCLIENTPORT NO

Register Node…LLADRESS=1501 (default)


TCP/IP port definitionsThere are server ports, client ports, and Storage Agent ports.

Server portsServer ports include the following:

� TCPPORT

Specifies the TCP/IP port number on which the server TCP/IP communication driver waits for requests for client sessions. The type of sessions include client sessions and other sessions types such as, administrative sessions, server-to-server sessions, SNMP subagent sessions, Storage Agent sessions, Library Client sessions, managed server sessions, and event server sessions.

Setting different ports for TCPPORT and TCPADMINPORT allows you to set one set of firewall rules for client sessions and another set of firewall rules for the other types of sessions

The default port is 1500.

� TCPADMINPORT

Specifies the TCP/IP port number on which the server’s (or Storage Agent’s) TCP/IP communication driver waits for requests for the other types of client sessions, such as administrative sessions, server-to-server sessions, SNMP subagent sessions, Storage Agent sessions, Library Client sessions, managed server sessions and event server sessions.

Setting different ports for TCPPORT and TCPADMINPORT allows you to set one set of firewall rules for client sessions and another set of firewall rules for the other types of sessions. The server option ADMINONCLIENTPORT must be set to NO in the server options file (dsmserv.opt) to use a separate port for TCPADMINPORT.

The default is the same port used by the TCPPORT option.

� SERVERLLADDRESS

The SERVERLLADDRESS parameter is part of the SET SERVERLLADDRESS command. This command is necessary when setting up server-to-server communication. It is used to set a low-level address of a server. Tivoli Storage Manager uses this address when you issue the DEFINE SERVER command with the CROSSDEFINE=YES option.This TCP/IP port address should match the TCPPORT setting within the server options file, in most cases.

� LLADDRESS

The LLADDRESS option is a part of the DEFINE SERVER command. The DEFINE SERVER command is used when defining another server, to be used in server-to-server communications. This TCP/IP port address should generally match the TCPPORT server option of the target server.

� REGISTER NODE’s LLADDRESS

This option is used when you issue the REGISTER NODE or UPDATE NODE commands. This TCP/IP port address is used whenever the server contacts the client. This option must

Note: For further details on any of the server options or commands, refer to the IBM Tivoli Storage Manager Administrator’s Reference for your Tivoli Storage Manager server platform.

Appendix A. Understanding TCP/IP ports for LAN-free in Tivoli Storage Manager 423

match the TCPCLIENTPORT option in the client’s option file and is the same port the client has for server prompted sessions.

The default is 1501.

Client portsClient ports include the following:

� TCPCLIENTPORT

The TCPCLIENTPORT option specifies a different TCP/IP port number, for the server to contact the client on, than the TCP/IP port that was used to make the first server contact. It is used when the schedmode option is set to server prompted. This port number should match the LLADDRESS used when registering a node.

This option is only valid on Windows clients.


� TCPPORT

The TCPPORT option is the TCP/IP port address that client communicates with the Tivoli Storage Manager server on. It should match the TCPPORT option in the server options file.


� LANFREETCPPORT

The LANFREETCPPORT option is the TCP/IP port address used by the Storage Agent and client to communicate between. This option is valid when you specify a LANFREECOMMMETHOD of TCPIP. This option must match the TCPPORT option that is set within the Storage Agent’s option file.


Storage Agent portsThe following Storage Agent ports are identical to those that are used on the Tivoli Storage Manager server (see “Server ports” on page 423):

� LLADDRESS� TCPADMINPORT� TCPPORT


Related publications

The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook.

IBM RedbooksFor information about ordering these publications, see “How to get IBM Redbooks” on page 426. Note that some of the documents referenced here might be available in softcopy only.

� Implementing an Open IBM SAN, SG24-6116

� Introduction to Storage Area Network, SG24-5470

� Designing and Optimizing an IBM Storage Area Network, SG24-6419

� IBM TotalStorage: SAN Product, Design, and Optimization Guide, SG24-6384

� Implementing IBM Tape in UNIX Systems, SG24-6502

� Implementing IBM Tape in Linux and Windows, SG24-6268


� A Practical Guide to Tivoli SANergy, SG24-6146

� IBM Tivoli Storage Manager in a Clustered Environment, SG24-6679

Other publicationsThese publications are also relevant as further information sources:

� IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers, User and Installation Guide, GC35-0154

� IBM Tivoli Storage Manager for Linux Administrator’s Guide, GC23-4690

� IBM Tivoli Storage Manager for AIX Administrator’s Guide, GC32-0768

� IBM Tivoli Storage Manager for AIX Installation Guide, GC32-1597



� IBM Tivoli SANergy Administrator’s Guide, Version 3 Release 2, GC32-0740



� IBM Tivoli Storage Manager - Data Protection for IBM ESS for mySAP Installation and User’s Guide, SC33-8205


How to get IBM RedbooksYou can search for, view, or download Redbooks, Redpapers, Hints and Tips, draft publications and Additional materials, as well as order hardcopy Redbooks or CD-ROMs, at:

ibm.com/redbooks

Help from IBMIBM Support and downloads

ibm.com/support

IBM Global Services

ibm.com/services




http://www.ibm.com/support/

http://www.ibm.com/support/

http://www.ibm.com/services/

http://www.ibm.com/services/

Index

Numerics3494

AIX setup 96automated tape library service 104configuration file 97configure LMCP instance 98defatl 98define in Tivoli Storage Manager 104device class 124–125device driver 96, 103, 114error diagnostics 114ibmatl 109ibmatl.conf 103, 110, 116IBMtape 112install drive 98Library Manager 94, 96library sharing 95Linux device driver 109Linux setup 109Linux Tivoli Storage Manager definition 111lmcpd 96, 110medium changer 109, 114private volume 124remote console 94scratch tape 124scratch volume 124Solaris configuration file 119Solaris setup 114Solaris Tivoli Storage Manager definition 117special files 113, 117start Windows service 104tape categories 95Windows drive installation 104Windows setup 103with Tivoli Storage Manager 95

3590 173592 17, 95

AAcsAccessId 151ACSDRVID 153ACSID 153AcsLockDrive 151ACSLS 9, 128, 139

ACSDRVID 153ACSID 153ACSSA prompt 153AIX setup 131library client 129library control 131, 134, 142Linux setup 139locked volumes 419query drive 154query volumes 155

© Copyright IBM Corp. 2005. All rights reserved.

server 129, 131Solaris configuration file 146Solaris setup 142Tivoli Storage Manager device class 154Tivoli Storage Manager library sharing 129Tivoli Storage Manager server options 151Windows setup 134

ACSLS commandsclear lock 419query acs all 153query drive 154query scratch 155

AcsQuickInit 151ACSSA 153AcsTimeoutX 151activity log 32, 35, 89, 125, 156, 251Administration Center 73AIX

3494 library sharing 96ACSLS library sharing 131alternate tape path support 52concurrent I/O 294configuration manager 101, 260configure SCSI tape device 47create device 98delete devices 134device driver 133discover TSM devices 133errpt 376HACMP 294–295, 372–373inittab 131install STK library control 131jfslog 299Korn shell 298list devices 50, 100, 134, 413LVM 294LVM mirroring 372mkdev 98mksysb 330recreate VG 300recreatevg 300rescan for devices 50show device attributes 51SMIT 48, 96, 133tapeutil 405

ALMS 12alternate path 53alternate path support 52, 64, 72API 3application server consolidation 380Atape 47, 96, 98, 139

alternate path 52atldd 96availability 2average file size 164

427

Bbarcode 37, 91BATCHSIZE 271block size 9BRTools 294

Ccheck in tapes 14, 81checking in tapes 32checkout tapes 30client options 164, 191client options file 164, 235commands

ASSIGN DEFMGMTCLASS 179, 226AUDIT LIBRARY 37BACKUP DB 29, 89, 125, 156BACKUP DEWCONFIG 29BACKUP VOLHISTORY 29CHECKIN LIBVOLUME 32, 37, 84, 95, 124, 154CHECKOUT LIBVOLUME 30DEFINE COPYGROUP 179DEFINE DEVCLASS 22, 124–125, 154, 156DEFINE DOMAIN 179, 226DEFINE DRIVE 31, 124, 153DEFINE LIBRARY 21, 31, 95, 111, 117, 124–125, 153, 155DEFINE MGMTCLASS 179, 226DEFINE PATH 31, 104, 111, 117, 124–125, 154–155, 160, 190DEFINE POLICYSET 179, 226DEFINE SERVER 189, 235, 242DEFINE STGPOOL 221DELETE VOLHISTORY 23–24DISABLE SESSION 29ENABLE SESSION 29LABEL LIBVOLUME 84, 154PING SERVER 28, 200QUERY ACTLOG 30QUERY DEVCLASS 220QUERY DRIVE 39QUERY LIBRARY 25, 220QUERY LIBVOLUMES 22, 25, 31, 33, 126, 155, 157QUERY MOUNT 38–39, 203QUERY NODE 229QUERY PATH 190QUERY SAN 8, 62, 75–76, 87QUERY SERVER 189QUERY SEVER 235QUERY STATUS 189, 234QUERY STGPOOL 221QUERY VOLHISTORY 23, 25REGISTER NODE 181, 229REPLY 84SCSI RESERVE 21SET SERVERHLADDRESS 234SET SERVERLLADDRESS 234SET SERVERNAME 234SHOW LANFREE 8tsmdlst 167–168

UPDATE LIBRARY 21UPDATE LIBVOLUME 24UPDATE NODE 181, 189, 229, 249VALIDATE LANFREE 8, 200–201

concurrent I/O 294configuration file 240congested network 161consolidation 380control path failover 15, 45, 50COPYTHREADS 271

Ddata mover 5, 269data path failover 16, 45Data Protection for IBM ESS 6Data Protection for IBM ESS for mySAP. See DP for IBM ESS for mySAPDATAREADPATH 189DATAWRITEPATH 189DB2 6, 293

db2admin 294db2admin 294define tape drive 31define tape library 31device class 78, 88, 124–125, 154, 156, 213, 283

FILE 251maximum file size 215mount limit 22, 221shared 219

device configuration 199device driver 15, 45, 47, 63, 114, 139Device Manager 416device names 166disk-only backup 294DLL 103DMP 254DNS 377DP for IBM ESS for mySAP 294

backup 330backup server 295backup types 329brarchive 330brbackup 328–329, 331, 376commands 329configuration file 326, 328db_disk category 299diagnostic commands 376disk-only backup 343FlashBack restore 356HACMP support 373initRED.fct 326initSID.fcs 319–320initSID.sap 300, 343install 319logging 376LVM mirroring 372multiple backup generations 374offline_mirror NOCOPY backup 331online INCR backup 343post restore script 368


post-install script 319PostRestore.sh 368pre restore script 359PreRestore.sh 359problem determination 376production server 295profile 300, 319–320restore 356set passwords 328SPLIT_OPTIONS 331splitint 319, 329, 334, 355, 376storage classes 299tape backup 294tdpessora 329, 343, 355–356tracing 376verify backup status 343, 355

DP for mySAPbrbackup 312configuration files 317install 302

DS4000 380dsm.opt 235dsmadmc 74dsmserv.opt 255, 423dsmsta 198, 241–242dsmsta.opt 198–199, 240, 242DVCID 257dynamic load balancing 52

Eelement address 76ENABLELANFREE 191, 193, 235ENABLESERVERFREE 285error diagnostic daemon 67ESS 6, 294, 380

Copy Services 297–298, 377FlashBack 364FlashCopy 296flashed volumes 299LSS 297–298LUNs 298LVM mirroring 372microcode level 297multiple target sets 374PPRC 299, 377SDD 294source volumes 298, 332target volume 328target volumes 294–295, 298

extended copy command 267extended copy functions 5

FFAStT 380file

metadata 380file drive 215, 219file library 5, 215, 219FlashBack 331, 364

FlashCopy 6, 294, 296, 334, 346, 382benefits 294COPY 294, 330INCR 294, 297, 330, 343multiple target sets 374NOCOPY 294, 330–331online_mirror 318source volumes 298, 332target set 373target volume 328target volumes 295, 298

flashed volumes 299

GGBIC 406global namespace 380, 382

HHACMP 9, 21, 294–295, 372–373HBA 16, 254, 259HBAAPI 260HBAs 45HSM 3

IIBM device driver 46–47, 63, 68, 166, 404, 413IBM Enterprise Storage Server. See ESS.IBM Tivoli Storage Manager for Space Management 3IBM TotalStorage Enterprise Automated Tape Library. See 3494.ibmatl 109ibmatl.conf 97, 110, 116, 419IBMtape 112IBMtape.conf 119IBMtapeconfig 112, 260IBMtaped 114IBMtapeutil 113, 405image backup 268include statement 164, 166init.ora 300initSID.sap 300inittab 131installable file system 381instant copy 6inventory 37

KKorn shell 298

LLAN-based backup 4, 162LAN-free 3

backup 398client install 235client options 191, 235create Storage Agent 184destination 160

Index 429

disk backup 5enable 182enable client 183, 235enable client data movement 189, 249flow of control 160performance 162planning 159policy domain 222port definition 191, 232, 421ports 424separate Storage Agent 192shared memory communications 191, 236Storage Agent port 184storage pool 185tape backup 4, 172TDP clients 204

LAN-free backup 4configuration 165policy domain 174Storage Agent 165supported Storage Agent platforms 165verify 200, 249

LAN-free validation 8LANFREECOMMMETHOD 191, 193, 201, 235, 424LANFREESHMPORT 191, 235LANFREETCPPORT 191, 198, 201, 232, 235, 251, 424LANFREETCPSERVERADDRESS 9, 172, 191lbtest 404LibAttach 134Library 85Library Client 7, 418library control 139library control path failover 15library controller 14library device driver 15Library Manager 7

configure 74library medium changer 44library partitioning 12library sharing 7, 13, 166, 418

3494 95, 122ACSLS 130command differences 37components 14configure Library Client 85disaster recovery 20failover 9Library Client 13–14, 36Library Manager 13–14, 20, 24, 160manager and client interactions 40requirements 19SCSI 44, 73

library special file 15license key 274Linux

/etc/modules.conf 64/proc/scsi/IBMchanger 653494 configuration file 1103494 device driver 1093494 error diagnostics 114

3494 library sharing 109ACSLS library sharing 139alternate path support 64autoconf 260check for tape devices 112configure SCSI tape device 63configure tape drives 140define 3494 library 111ibmatl 109ibmatl.conf 110IBMtape 112IBMtapeconfig 66, 260IBMtapeutil 66, 405install library control 139install tape device driver 139list modules 140load modules 140lsmod 140modprobe 140mt.conf 141reconfigure tape devices 66, 112SAN Discovery 260show tape devices 63, 415tape configuration file 141tape device attributes 66tape error diagnostic 67tape special files 113, 142YAST 110

LLADDRESS 250, 423lmcpd 96, 110, 115logical libraries 12Logical Volume Storage Agent 268LSS 298LTO 44LVM 294LVSA 268

Mmacro 32management class 164, 166, 174, 226, 284Management Console 61MDC 208, 246, 249MDS 381medium changer 103, 114metadata 380Metadata server 381mount retention 91mttest 404, 406multiple opens 58multithreading 162mySAP 6, 293

backint 296backup 294, 330backup logs 351backup mode 343, 346begin backup mode 346brbackup 296, 298, 319, 331, 343BRTools 294–295disk-only backup 330, 343end backup mode 347


FlashBack restore 356flashed volumes 299forward recovery 371, 374HACMP environments 294installation 300LVM mirroring 372multiple backup generations 374offline mirror backup 331online mirror INCR backup 343prepare for online backup 346recover database 371redo log files 299restore 296, 356restore logs 363shutdown database 333SID 300splitint 296, 328, 334start database 334tablespace files 299

NNAS 3Native Without 271NDMP 3network 161NFS 295–297NONBLOCK 271, 283Now we backup the files with 388ntutil 405

OOBF 269open system connectivity 2Oracle 6, 293

configuration files 300init.ora 300

Original Block File 268

Ppersistent binding 254, 272, 408policy domain 174, 222, 226, 243policy set 226PPRC 299, 377primary path 53private tape 13, 83, 95, 124ProLE 302Proxy Node 398

Qquery SAN 255

RRDAC 254reclamation 40recording format 89Redbooks Web site 426

Contact us xix

remote console 94Removable Storage Manager 167rexec 295, 297RS-232 96RSCN 260–261RSM

Windows 167

SSAN 2

availability 2cable 406, 410determine device names 166device discovery 8, 167, 186, 191, 241, 253, 404, 408device mapping 8, 254device mapping commands 255discovery 8, 156, 167, 186, 191, 199, 241, 253, 404, 408fabric 16GBIC 406, 410HBA 16library sharing 13multiple path 16nameserver 410performance 2persistent binding 254, 272, 408query devices 8, 255scalability 2SCSI library 44show devices 87show Tivoli Storage Manager devices 62tape library connection 19Tivoli Storage Manager functions 4troubleshooting 401zoning 46, 50, 411

SAN Data Gateway 5, 259, 269SAN File System

administration 381architecture 381backup with Tivoli Storage Manager 382command line interface 382FlashCopy 382global namespace 380LAN-free backup 398MDS 381Metadata server 381

SANDISCOVERY 8, 255SANergy 3, 5

client 208MDC 208, 246, 249

scalability 2scratch tape 13–14, 24, 40, 83, 95, 124, 218, 221SCSI 257

reservation 21reset 21Solaris tape device driver 71

SCSI tape library 44SCSI-3 5, 267, 270SCSI-3 EXTENDED COPY 272SDD 294

Index 431

SDG 5server consolidation 380server subsystem interface. See SSI.server-free

activity log output 288data format 283enable client 285enable on Tivoli Storage Manager 270Tivoli Storage Manager requirements 272

server-free backup 5, 267server-free backup and restore 286server-free Data Movement 268server-free data movement 269server-free restore 289SERVERHLADDRESS 234SERVERLLADDRESS 423server-to-server communication 7, 14, 19, 28, 73, 85, 123–124, 150, 155, 182, 230, 234, 418shared memory 191, 236shared tape library 7SID 300SMIT 48, 96snapshot 268SNIA 272Solaris

3494 configuration file 1163494 device driver 1143494 library sharing 114ACSLS library sharing 142alternate path support 72autoconf 147, 261configure SCSI tape devices 68configure tape devices 147display drive information 72display tape information 149ibmatl.conf 116IBMtape.conf 69, 119install IBMtape 118install library control 142library control path failover 72list tape devices 121, 417lmcpd 115mtinfo 149native tape device driver 71, 120reload configuration 71reload driver 121SAN Discovery 261special files 117start lmcpd 117tape configuration file 69, 119, 146tape device driver 145tapelist 72, 122tapeutil 405Tivoli Storage Manager 3494 definition 121view library device 72view tape device 71

space management 3special file 45split mirror 6SQL 30

SSI 130–131, 142, 420event logger daemon 133start 133, 144

Storage Agent 3–4, 7, 160, 240, 268configure 193, 236create 184define 232determine device names 166device configuration 199device configuration file 242device driver 166directory 199dsmsta 198, 241–242dsmsta.opt 240, 242, 251external 192failover 9halt 241–242install location 165installation 166LAN-free port 184LANFREETCPSERVERADDRESS 172list devices 168manual start 198, 241monitor 203options file 198–199, 240, 242, 251run in foreground 242SAN Discovery 198–199, 242server communication 199service 197, 240, 242start device driver 167start service 241stop 241–242storage pool 185supported platforms 165tape backup 172TCP/IP port 201TCPPORT 198–199, 232, 240, 242, 251tsmdlst 167–168, 193TSMSCSI 167verify 200

Storage Area Network. See SAN.storage consolidation 380storage pool 175, 185, 217, 221, 283

scratch volumes 218, 221StorageTek 128StorageTek Library Attach 134StorWatch 273SVC 380

Ttape

categories 95checkin 14device driver 15display contents 252label 154labelling 124private volume 124scratch volume 124

tape block size 9


tape driveallocation 22alternate path support 72data path failover 16define path 185, 262device driver 63, 133, 135, 139, 166device name 166display path 190dual port 17element number 76, 257, 405IBM device driver 46, 404install 98install on Solaris 145Linux special file 142mount limit 22mount retention 91native Solaris driver 120recording format 89reset 21SCSI reservation 21SCSI reset 21serial number 125, 257, 263Solaris configuration file 146Solaris special files 117test 404

tape drive special file 15tape drive status 39tape labels 81tape library

alternate path 52alternate path support 64, 72control path failover 15, 45, 50, 72data path failover 45delete volume 22device driver 45, 63device name 166disable access 22error recovery 52medium changer 14, 44, 114mount wait time 84primary path 53reset 21SCSI 44serial number 256special file 15, 45, 113supported by Tivoli Storage Manager

19test 404use 18

tape library access 14tape library initialization 21tape library partitioning 12tape library sharing 7, 13tape mount request 14tape mounts 38tapelist 122tapeutil 405–406target reset 21target volumes 294–295TCPADMINPORT 420, 423

TCPCLIENTPORT 424TCPPORT 198–199, 201, 232, 240, 251, 423–424TCPSERVERADDRESS 193TDP for IBM ESS for mySAP

backup server 296brbackup 343hardware and software requirements 297production server 296restore 296supported disk systems 297

Tivoli SANergy 5Tivoli Storage Manager 3, 382, 423

3493 library sharing 953494 configuration 1223494 library sharing 122AcsAccessid 151AcsLockDrive 151ACSLS initialization 151ACSLS interface 142ACSLS library sharing 129–130ACSLS options 151ACSLS support 9ACSLS timeout value 151AcsQuickInit 151AcsTimeoutX 151activity log 30, 32, 35, 89, 125, 156, 251, 288Administration Center 73ADMINONCLIENTPORT 423ample client options file 205API 302assign default management class 179audit library 37backup database 29, 89, 125, 156backup device configuration 29backup mySAP logs 351backup SAN File System 382backup volume history 29barcode 37BATCHSIZE 271category numbers 95check activity log 30check in tapes 81check server communication 28, 250check volume label 37checkin tapes 14, 32, 95, 124, 154checkout tapes 30client 3client options 164, 191client options file 164, 204, 235, 251, 285command line interface 74commands

QUERY LIBVOLUMES 157configure client 191configure Library Client 85configure Library Manager 74configure SCSI library sharing 73configure Storage Agent 193, 236COPYTHREADS 271create library 86create new instance 28

Index 433

create Storage Agent 184data mover 5, 269database backup 20DATAWRITEPATH option 189dedicated Library Manager 24dedicated tape library 18default management class 226define 3494 library 98, 104, 111, 117, 121define ACSLS library 153define copygroup 179define datamover 284define device class 78, 88, 124–125, 154, 156, 283define drive 153, 257, 283define LAN-free disk path 249define library 31, 95, 124–125define management class 179, 226define path 31, 124, 190, 249, 256, 262, 283, 419define policy domain 179, 226define policy set 179, 226define server 235define Storage Agent 232define storage pool 221, 283define tape drive 31, 124, 257define tape library 155, 283define tape path 124–125, 154–155, 185, 190delete library volume 22delete volume history 23, 34detect element number 257determine device names 166device class 78, 88, 124–125, 154, 156, 213, 219, 283device driver 136, 166, 404, 413device name change 254device names 166device serial number 256–257device type 95disable library access 22disable sessions 29display tape contents 252display tape paths 190drive allocation 22drive element address 76dsm.opt 235, 285dsmadmc 74dsmserv.opt 255, 423element number detection 257enable LAN-free data movement 182–183, 189, 249enable server-free backup 270enable server-free data movement 282enable sessions 29ENABLELANFREE 191, 193, 235ENABLESERVERFREE 285ESS integration 294Extended Edition 19, 130failover 9FILE device class 251file drive 215, 219file library 5, 215, 219FlashCopy backup 6FlashCopy integration 294

for SANs 167HACMP failover 9HSM 3image backup 268INCLUDE statements 164, 166install Storage Agent 166label tape 124, 154LAN-based backup 4, 162LAN-free backup 4LAN-free client install 235LAN-free client options 191LAN-free destination 160LAN-free disk backup 5, 208LAN-free planning 159LAN-free ports 201, 232LAN-free tape backup 4, 172LAN-free tasks 160LANFREECOMMMETHOD 191, 193, 201, 235, 424LANFREESHMPORT 191, 235LANFREETCPPORT 191, 193, 198, 201, 232, 235, 251, 424LANFREETCPSERVERADDRESS 9, 172, 191lbtest 404Library Client 7, 13–14, 36, 165library initialization 21Library Manager 7, 13–14, 20, 24, 94, 103, 109, 123, 130, 160, 165library reset 21library serial number 256library sharing 7, 13, 130, 160, 166library sharing commands 37library sharing common tasks 20library sharing failover 9library sharing interactions 40library sharing requirements 19Linux tape configuration file 141list devices 168LLADDRESS 201, 250, 423macro 32management class 164, 166, 174, 226, 284Management Console 61match serial number 257MAXSCRATCH 218messages 259migration 20mixed device types 95monitor Storage Agent 203mount retention 91mount volume 40, 160mount wait time 84mountlimit 22, 213, 221move Library Manager 27mttest 404multithreading 162mySAP backup 294NONBLOCK 271password 318path to library 31policy domain 174, 222, 226, 243policy information 160


policy set 226ports 421private tape 13, 83, 95, 124progressive incremental backup 162Proxy Node 398proxy node access 398query activity log 288query device class 220query drive 39query library 220query library volumes 25, 31, 33query node 229query SAN 255query SAN devices 75, 87query server 235query status 234query storage pool 221query tape contents 252query tape mounts 38–39, 203, 252query tape volumes 126query tapes 155query volume history 25reclamation 20, 40recording format 89register node 181, 227, 229, 284, 398release volume 40reply to mount request 84restore mySAP logs 363resynchronize server communication 418SAN device mapping 8, 254SAN Discovery 8, 51, 76, 88, 125, 156, 167, 186, 191, 198, 241, 253, 255, 404, 408SAN Discovery messages 259SAN functions 4SAN mapping commands 255SANDISCOVERY 8, 255scratch tape 13–14, 24, 40, 83, 95, 124, 218, 221SCSI library sharing configuration 73SCSI tape library 44separate Storage Agent 192server 3, 160, 295, 297, 317server address 201, 423server communication options 189server connectivity 200server maintenance planning 20server name 234server options file 255server resources 161server-free backup 5, 267server-free restore 289server-to-server communication 7, 14, 19, 28, 73, 85, 123–124, 150, 155, 182, 230, 234, 418set server address 234set server name 234shared device class 219shared memory 191, 236shared tape library 7show client backups 399show device information 61–62show library information 25

show SAN devices 62show servers 234show tape mounts 38show tape volumes 157snapshot option 268snapshotroot 390Solaris tape configuration file 146split mirror backup 6SQL 30, 35SQL commands 23SSI 130–131, 142, 420SSI start 144start device driver 167start SSI daemon 133Storage Agent 3–4, 7, 160, 165, 398Storage Agent command line 203Storage Agent communication 199Storage Agent configuration 193Storage Agent failover 9Storage Agent monitoring 203Storage Agent options 198–199Storage Agent options file 240, 242Storage Agent port 184Storage Agent SAN Discovery 198storage pool 175, 185, 217, 221, 283supported tape libraries 19tape categories 95, 124tape device details 149tape device driver 139tape drive allocation 22tape drive recording format 89tape labels 81tape library sharing 7tape mount request 14tape mount retention 91tape paths 190tape serial number 257TCP/IP ports 421TCPADMINPORT 420, 423TCPCLIENTPORT 424TCPPORT 201, 251, 423–424TCPSERVERADDRESS 193TDP LAN-free 204test drives and libraries 404tested LAN-free disk configurations 208troubleshooting SAN setups 401tsmdlist 149tsmdlst 416TSMSCSI 166–167update device configuration 263update device definitions 254update node 249verify LAN-free path 200, 249virtual mount point 391virtual node 398volume history 23, 25, 83volume inventory 37WORM scratch volumes 95

Tivoli Storage Manager commandsACTIVATE POLICYSET 284

Index 435

ASSIGN DEFMGMTCLASS 179, 226AUDIT LIBRARY 37BACKUP DB 29, 89, 125, 156BACKUP DEVVCONFIG 29BACKUP VOLHISTORY 29CHECKIN LIBVOLUME 32, 37, 84, 95, 124, 154CHECKOUT LIBVOLUME 30DEFINE COPYGROUP 179, 284DEFINE DATAMOVER 271, 284DEFINE DEVCLASS 22, 124–125, 154, 156, 283define device class 219DEFINE DISK 284DEFINE DOMAIN 179, 226DEFINE DRIVE 31, 124, 153, 257, 283DEFINE LIBRARY 21, 31, 95, 111, 117, 124–125, 153, 155, 256, 283DEFINE MGMTCLASS 179, 226, 284DEFINE PATH 31, 104, 111, 117, 124–125, 154–155, 160, 190, 249, 256, 262, 283–284, 419DEFINE POLICYSET 179, 226DEFINE SERVER 189, 235, 242, 423DEFINE STGPOOL 221, 283DELETE VOLHISTORY 23–24DISABLE SESSION 29ENABLE SESSION 29GRANT PROXY 398LABEL LIBVOLUME 84, 124, 154PING SERVER 28, 200, 250QUERY ACTLOG 30, 288QUERY BACKUP 399QUERY CONTENTS 252QUERY DEVCLASS 220QUERY DISKINFO 282QUERY DRIVE 39QUERY FILESPACE 399QUERY LIBRARY 25, 220QUERY LIBVOLUMES 22, 25, 31, 33, 126, 155QUERY MOUNT 38–39, 203, 252QUERY NODE 229QUERY OCCUPANCY 399QUERY PATH 190, 407QUERY PROCESS 288QUERY SAN 8, 62, 75–76, 87, 255, 279, 404QUERY SERVER 189, 235, 250QUERY STATUS 189, 234, 283QUERY STGPOOL 221QUERY VOLHISTORY 23, 25QUERY VOLUME 252REGISTER NODE 181, 229, 284, 398REPLY 84SCSI RESERVE 21SET SERVERFREE 270, 282SET SERVERHLADDRESS 234SET SERVERLLADDRESS 234SET SERVERNAME 234SETOPT 255SHOW LANFREE 8, 249tsmdlst 167–168UPDATE LIBRARY 21UPDATE LIBVOLUME 24

UPDATE NODE 181, 189, 229, 249UPDATE PATH 407UPDATE SERVER 418VALIDATE LANFREE 8, 200–201, 249–250

Tivoli Storage Manager for SAN 167Tivoli Storage Manager server options file 423Tivoli System Automation 372TotalStorage Productivity Center for Data 164TPC for Data 164troubleshooting 401, 418TSM commands

QUERY SAN 255tsmdlist 149tsmdlst 193, 416TSMSCSI 166–167twin-tail configuration 12

UUNC 246, 249

Vvirtual file system 381virtual mount point 391virtual node 398volume history 23, 83VTS 96

WWindows

3494 configuration file 1033494 library sharing 103ACSLS library sharing 134automated tape library service 104configure SCSI tape device 54device driver 103, 135Device Manager 61display tape devices 416drive special name 62enable Tivoli Storage Manager device driver 167IBM tape device driver 58install 3494 device driver 104install library control 134install Tivoli Storage Manager device driver 136library special name 62Management Console 138ntutil 405SAN device mapping 259

World Wide Name 279WORM 95WWN 279WWNN 254

YYAST 110

Zzoning 46, 50, 411


(0.5” spine)0.475”<

->0.873”

250 <->

459 pages

Get More Out of Your SAN w

ith IBM Tivoli Storage M

anager


ith IBM



ith IBM



ith IBM Tivoli Storage M

anager


ith IBM



ith IBM


®

SG24-6687-00 ISBN 0738491004

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks


Provides detailed planning, installation, and configuration scenarios

Describes new features for Tivoli Storage Manager V5.3

Includes flowcharts for troubleshooting

Storage Area Networks (SANs) have changed the way that data is moved, stored, and managed, allowing you to access your data faster and more efficiently. IBM Tivoli Storage Manager allows you to exploit your SAN infrastructure to potentially provide increased performance, greater flexibility in configurations, and more efficient use of your hardware resources.

This IBM Redbook describes the features of Tivoli Storage Manager, which can be deployed in a SAN. These features include LAN-free backup to tape and disk, tape library sharing, and server-free backup. It also discusses how to use Tivoli Storage Manager with other applications and hardware, such as STK libraries, mySAP, and IBM TotalStorage SAN File System. The emphasis of this information is on showing what can be done, why to do it, and how to do it.

This book is written for people who are working for IBM, our clients, vendors, and consulting organizations and who want to understand how Tivoli Storage Manager fits into and enhances a SAN environment, as well as for those wanting detailed assistance in implementing Tivoli Storage Manager using SAN-attached storage.

Back cover


