Page 1: Front Cover
Front cover IBM Tivoli Storage Manager Implementation Guide Use the included worksheets, scripts, and macros to make your job easier See features for new and advanced users Use this hands-on guide for planning and setup Charlotte Brooks Peter McFarlane Norbert Pott...
Page 3 International Technical Support Organization IBM Tivoli Storage Manager Implementation Guide June 2006 SG24-5416-03...
Page 4 Note: Before using this information and the product it supports, read the information in “Notices” on page xxiii. Fourth Edition (June 2006) This edition applies to IBM Tivoli Storage Manager Version 5.3.2. © Copyright International Business Machines Corporation 1999, 2000, 2003, 2006. All rights reserved.
Page 6 2.8.4 Database size ......... . 41 IBM Tivoli Storage Manager Implementation Guide...
Page 7 2.8.5 Archive sizing ......... . 42 2.8.6 Database volume identification .
Page 8 5.1 Database ..........188 5.1.1 Database design considerations ......188 IBM Tivoli Storage Manager Implementation Guide...
Page 9 5.1.2 Defining database volumes....... 190 5.2 Recovery log ..........192 5.2.1 Recovery log design considerations .
Page 10 8.2.3 Working with client nodes ....... . 292 viii IBM Tivoli Storage Manager Implementation Guide...
Page 11 8.3 Client option sets......... . . 298 8.3.1 Considerations .
Page 12 13.7.7 Reclaiming off-site tapes ....... . 441 IBM Tivoli Storage Manager Implementation Guide...
Page 13 13.7.8 Database backup management ......442 13.8 Error conditions ......... . . 445 13.8.1 Tivoli Storage Manager errors.
Page 14 17.3 Configuration steps: Overview ....... 570 IBM Tivoli Storage Manager Implementation Guide...
Page 15 17.4 Setting up server-free data movement ......570 17.4.1 SAN configuration ........570 17.4.2 SAN zoning .
Page 16 22.2.3 Upgrading the server........699 IBM Tivoli Storage Manager Implementation Guide...
Page 17 IBM Redbooks ........
Page 18 IBM Redbooks collections ........
Page 19: Figures
Figures Our IBM Tivoli Storage Manager environment..... 5 Tivoli Storage Manager backup/restore scenarios....17 LAN-free data movement .
Page 20 Database and recovery log mirroring ......203 Storage pool hierarchy for our recommended setup ....216 xviii IBM Tivoli Storage Manager Implementation Guide...
Page 21 13-6 Health monitor details ........411 13-7 IBM Tivoli Operational Reporting result ......413 13-8 How Tivoli Storage Manager tapes are processed .
Page 22 22-4 Device driver upgrade requires reboot of the machine ... . 704 22-5 Updating the server instance: applying the patch level ... . 706 IBM Tivoli Storage Manager Implementation Guide...
Page 23 22-6 AIX lab environment........708 Figures...
Page 24 IBM Tivoli Storage Manager Implementation Guide...
Page 25: Notices
Consult your local IBM representative for information about 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.
Page 26: Trademarks
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. Other company, product, or service names may be trademarks or service marks of others. xxiv IBM Tivoli Storage Manager Implementation Guide...
Page 27: Preface
SAN environments, NDMP, and much more. This practical guide is intended for these audiences: system administrators, new to IBM Tivoli Storage Manager, who are asked to commence a basic IBM Tivoli Storage Manager implementation for the very first time; as well as administrators who want to learn more about the basic and advanced components and their implementation.
Page 28 10 years on AIX and Tivoli Storage Manager. His areas of expertise include high availability, disaster recovery, and storage management. He is a certified Tivoli Storage Manager instructor. He is an author of the IBM Redbook IBM Versatile Storage Server™, SG24-2221.
Page 29 King, Randy Larson, Len Ling, Zong Ling, Steven John Mann, Urs Moser, Charles Nichols, Kathy Pang, Brian Pendergrass, Rosa Plaza, Deanna Shaw, Jim Smith, John Viksne, Chris Zaremba IBM Tivoli Storage Manager Development and Marketing, IBM US Monika Doshi, Nicholas Wilhelm-Olsen, Chris Lueth Network Appliance, Inc.
Page 30: Become A Published Author
Become a published author Join 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.
Page 31: Part 1. Introduction
(such as hardware platform, size of processor, network connectively, and tape library) should all have been done before trying to make IBM Tivoli Storage Manager work in an environment that may not be suitable. © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 32 IBM Tivoli Storage Manager Implementation Guide...
Page 33: Chapter 1. Implementation Checklists
Implementation checklists Chapter 1. In this chapter we offer an overview of the IBM Tivoli Storage Manager environment described in our book, as well as implementation checklists for planning, installing, and operating that environment. Our environment provides an integrated solution that incorporates client and server options, basic performance recommendations, and operational processes.
Page 34: The Big Picture
Separate storage pools for client directory information and client data Client data written to a disk storage pool, then migrated to tape storage pool Duplicate copies of onsite data created for off-site storage Mirrored Tivoli Storage Manager database and recovery log IBM Tivoli Storage Manager Implementation Guide...
Page 35: Our Support Material
OFFDIRS Copy Pools Send copy to vault Figure 1-1 Our IBM Tivoli Storage Manager environment The two primary disk storage pools hold client directory information (DISKDIRS) and client data (DISKDATA). The remaining storage pool (TAPEDATA) is on tape and holds only client data. A copy of the client data is stored in one off-site storage pool (OFFDATA), and a copy of the client directory data is stored in another storage pool (OFFDIRS).
Page 36 Client system options file for AIX mac.admins Administrative macro to define administrators mac.optionsets Administrative macro to define client option sets mac.schedules Administrative macro to define administrative and client schedules mac.scripts Administrative macro to define server scripts IBM Tivoli Storage Manager Implementation Guide...
Page 37: Planning Checklist
File name Contents mac.stgcreate Administrative macro to create storage pools mac.stgdelete Administrative macro to delete default storage pools mac.policy Administrative macro to define policy domains, policy sets, management classes, and copy groups planning.123 Planning spreadsheets (Lotus® 123 format) plan_sampledata.123 Planning spreadsheets (Lotus 123 format) with some sample data planning.xls Planning spreadsheets (Microsoft Excel format)
Page 38: Server Implementation Checklist
1.1.1, “Our support material” on page 5. Table 1-3 Server implementation checklist Tasks Refer to: Macro Download latest server code fixes. 3.2, “Latest software updates” on page 68 IBM Tivoli Storage Manager Implementation Guide...
Page 39 Tasks Refer to: Macro Install base server code and latest fixes. 3.3, “AIX server installation” on page 70, 3.4, “Linux server installations” on page 72 or 3.5, “Windows 2000/2003 server installation” on page 78 for your specific platform Update server options file. 3.7.1, “Server options file”...
Page 40 STANDARD policy domain” on page 279 Define administrator IDs. 8.1, “Management” on admins page 284 Define administrative schedules. 12.2, “Administrative schedules schedules” on page 374 Define client schedules. 12.3, “Client schedules” schedules on page 386 IBM Tivoli Storage Manager Implementation Guide...
Page 41: Client Implementation Checklist
Tasks Refer to: Macro Create client option sets. 8.3, “Client option sets” on optionsets page 298 1.2.2 Client implementation checklist The client implementation checklist consists of two parts that identify those tasks you must complete to set up this Tivoli Storage Manager client environment. The tasks contained in the checklists are shown in Table 1-4 and Table 1-5.
Page 42: Operations Checklist
13.7.3, “On-site and off-site tape management” on page 430 Send Tivoli Storage Manager database copy to off-site. 13.7.8, “Database backup management” on page 442 Check database and log utilization. 13.6, “Daily sanity checks” on page 414 IBM Tivoli Storage Manager Implementation Guide...
Page 43: Summary
Tasks Refer to Monitor number of scratch tapes available. “Number of scratch tapes” on page 419 Check client restartable restores. “Query restartable restore sessions” on page 424 1.3 Summary In conclusion, we have discussed and given you access to many checklists, and now it is time to move into the actual planning details, architectural considerations, environments, and our recommendations.
Page 44 IBM Tivoli Storage Manager Implementation Guide...
Page 45: Chapter 2. Implementation Planning
A successful implementation of IBM Tivoli Storage Manager benefits enormously from planning prior to attempting to set up the environment. We have just discussed the checklists you can use, and now we head into the planning stage. © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 46: Planning
Realistic goals and objectives Understanding Planning In this chapter, as well as in the IBM Redbook IBM Tivoli Storage Management Concepts, SG24-4877, we present a number of planning worksheets that lead you through gathering the client requirements and the data retention requirements in an orderly way.
Page 47: Tivoli Storage Manager Backup/Restore Scenarios
At this point, it is very important that you consider your backup and restore requirements so that you can match the Tivoli Storage Manager features to your needs. Since statistics show that the majority of user restore requests are for single files or other small amounts of data, the Tivoli Storage Manager file-level backup is the foundation of any recovery strategy.
Page 48 If you have a large number of nodes or use a spreadsheet version, you may find the table more workable by transposing it to a landscape orientation. Table 2-1 IBM Tivoli Storage Manager Client requirements worksheet Client Type1 Client Type 2...
Page 49: Client Name
Client Type1 Client Type 2 Workstation Database server Number of archives kept Archive frequency Monthly Monthly Archive window times Monthly Month end Archive number of hours 24 hours 24 hours Number of image backups Image backup frequency Monthly Number of backup sets Backup set frequency Monthly Bi-monthly...
Page 50: Total Storage Available
If your data change percentage is known, then enter that number in the worksheet. Otherwise, use Table 2-2 to estimate a rate, keeping in mind that your numbers may vary. A high estimate is better than one that is too low. IBM Tivoli Storage Manager Implementation Guide...
Page 51: Number Of Files Backed Up
2.2.7 Number of files backed up Calculate the total number of files to be backed up for each client. This number is used to estimate disk and tape storage requirements on the Tivoli Storage Manager server. If the number of files is unknown, two values are possible. Enter either an estimate of the number of files in this field, or enter 10% of the Total Storage Used field, in GB.
Page 52 Table 2-4 Typical data compression ratios Compression ratio Data reduction Database data 3:1–4:1 0.66–0.75 Print and file server data Executables, compressed data, encrypted data IBM Tivoli Storage Manager Implementation Guide...
Page 53: Backup Window Times
2.2.10 Backup window times Enter the times of the day between which Tivoli Storage Manager must start and complete its backup cycle. This window depends on when end-user client usage drops off, by availability requirements and by network capacity usage time frames.
Page 54: Gb Copied Per Archive
This number may be a specific time frame, such as between 23:00 and 04:00, or a more general time frame, such as after month-end processing finishes. 2.2.19 Archive number of hours Identify the number of hours available to complete the archive function. IBM Tivoli Storage Manager Implementation Guide...
Page 55: Number Of Image Backups
2.2.20 Number of image backups Identify the number of eligible system images that you want to back up. For a workstation that does not change very frequently, a good number could be six to twelve per machine. 2.2.21 Image backup frequency Identify how often you want to perform image backups.
Page 56: Data Retention Requirements
Choose a descriptive name for each categorized group of data. In our example, the Workstn group is used for files from a workstation, while the Server group is used for all data from a large file server. IBM Tivoli Storage Manager Implementation Guide...
Page 57: Number Of Backup Versions
2.3.2 Number of backup versions Determine the number of changed copies that you want to keep of a file that exists on the client when the backup task runs. How many different versions of that file do you want to be able to restore? For example, if backup runs every night and a file changes every day, and you want to be able to restore any version up to one week ago, then you would choose 7 as the number of backups to keep.
Page 58: Archive Retention Period
Table 2-6 highlights some factors affecting whether to use collocation. Table 2-6 Factors affecting collocation Onsite Off-site collocation collocation Short restore window Less than 10 Clients, each 10 GB storage IBM Tivoli Storage Manager Implementation Guide...
Page 59: Off-Site Collocation
Onsite Off-site collocation collocation More than 50 clients, each 10 GB storage More than 50 clients, each 100 GB or more Yes/No Limited disk or tape resources Workstations Database, print, and file servers Tivoli Storage Manager implementations that are small (small number of clients managing a small amount of data) do not see much benefit from collocation, due to the small number of tapes required for any restore.
Page 60: Backup Set Retention
Table 2-7 Tivoli Storage Manager server platform considerations Windows UNIX iSeries™ zSeries® system Installed user base AIX +++ Linux- ++; HP-UX, Sun™ Solaris™ + IBM Tivoli Storage Manager Implementation Guide...
Page 61: Installed User Base
Windows UNIX iSeries™ zSeries® system Cost UNIX ++/+++ ++/+++ Linux + Capacity ++/+++ ++/+++ Platform installation Simple Simple Medium Complex Operation Simple Medium Medium Complex Supported devices Many Many Limited Limited 2.4.2 Installed user base The number of Tivoli Storage Manager servers installed for a particular platform is a consideration.
Page 62: Capacity
Windows is lacking in this regard. Operation of Tivoli Storage Manager itself varies only in the way some operating system-specific Tivoli Storage Manager commands are issued on each platform. IBM Tivoli Storage Manager Implementation Guide...
Page 63: Supported Devices
It is important to look at the skills available among your staff for a particular operating system platform. If there are more people familiar with a particular platform, then it will be easier to maintain Tivoli Storage Manager in this environment.
Page 64: Multiple Tivoli Storage Manager Servers
For very large or critical clients such as a large, enterprise-wide business intelligence complex, a dedicated Tivoli Storage Manager server (either on the same system or a different one) might be the best solution. IBM Tivoli Storage Manager Implementation Guide...
Page 65: Disadvantages Of Multiple Servers
In installations where network connectivity is slow or expensive, placing a Tivoli Storage Manager server close to the clients usually makes sense. For example, for a business that has multiple file servers in each of a number of cities interconnected by a slow network, it may be appropriate to install a Tivoli Storage Manager server in each city.
Page 66 SLAs for this environment. Note that this type of calculation does not only apply to backups—it can and should be done for disaster recovery restores and single system restores. IBM Tivoli Storage Manager Implementation Guide...
Page 67 LAN/WAN transports The performance of your network backup solution will be no better than the performance of your network. You must consider expected and real performance of your network when you are designing a Tivoli Storage Manager solution. As an example, calculate theoretical network throughput using Fast Ethernet and a 40% efficiency: Assume 40–80% of total theoretical throughput for a TCP/IP adapter or protocol.
Page 68: Communication Protocol
Most network protocols such as TCP/IP and NETBIOS are supported by Tivoli Storage Manager. TCP/IP is the most common communication method and the easiest to set up. Certain functions, such as server prompted mode and the Web clients, require TCP/IP. IBM Tivoli Storage Manager Implementation Guide...
Page 69: Network Name Resolution
2.7.3 Network name resolution The Tivoli Storage Manager server machine requires a name that clients use to reference the Tivoli Storage Manager server. If TCP/IP is used, create a Domain Name Server (DNS) entry for Tivoli Storage Manager itself, as well as a DNS entry for the machine’s host names.
Page 70: Database Performance
Database performance is a critical factor in design and operation of a Tivoli Storage Manager solution. In this area, there are certain typical performance recommendations for any database, and some that are peculiar to the Tivoli Storage Manager database. IBM Tivoli Storage Manager Implementation Guide...
Page 71: Database Size
As with any database, the faster the disk used for the database the better. Spreading the database over as many physical disks as possible allows for better performance because multiple disk heads can be seeking, reading, and writing simultaneously. Counter to conventional thinking, however, several design ideas are peculiar to Tivoli Storage Manager.
Page 72: Archive Sizing
3. 1,104,000 * 600 = 662.4 MB 4. 1,104,000 * 200 = 220.8 MB 5. 662.4 MB + 220.8 MB = 883.2 MB 6. 883.2 MB * 1.35 = 1192.32 MB database size for archive data IBM Tivoli Storage Manager Implementation Guide...
Page 73: Database Volume Identification
2.8.6 Database volume identification The total required database size including both backup and archive requirements will be 190 + 1192.32 = 1382.4 MB. We recommend using the Tivoli Storage Manager mirroring function for the database instead of a hardware or operating system mirroring, because Tivoli Storage Manager has additional functions to handle error conditions that may affect the mirrored copy.
Page 74: Primary Disk Storage Pool
(for example, database files) to optimize the overall I/O. Consider using the cache=yes parameter on disk storage pools—this means files remain on disk IBM Tivoli Storage Manager Implementation Guide...
Page 75 until space is needed for further backups. This can significantly improve restore performance for recently backed up files. As the cost of per megabyte of disk decreases, more and more disk is being used in Tivoli Storage Manager designs. Some use no tape at all, so that all backed up data is saved to disk.
Page 76: Disk Storage Pool Size
The advantage of this is that generating a backup set requires the Tivoli Storage Manager server only—the client is not involved in any way since the backup set is created using data that has already been sent to the server in normal backup operations. IBM Tivoli Storage Manager Implementation Guide...
Page 77: Image Disk Sizing
To additionally increase the storage pool to hold archive data as well, follow these steps: 1. Using Table 2-1 on page 18 and the GB copied per archive field, group all machines that require simultaneous archive operations during one common time frame (for example, every month).
Page 78: Device Configuration Table And Volume History File
Tivoli Storage Manager database. These files will be invaluable in the event that you need to recover your Tivoli Storage Manager server. IBM Tivoli Storage Manager Implementation Guide...
Page 79: Total Disk
The disk required to run the server platform operating system efficiently also has not been considered. IBM Tivoli Storage Manager code requirements for disk vary depending on the server platform and release level. We use an estimate of 200 MB at the time of writing.
Page 80: Tape Drives And Sizing
Table 2-14 Tape device comparisons Tape drive Native speed Native capacity Assumed speed Assumed (MBps) (GB) (GB/HR) capacity (GB) IBM LTO Gen 2 IBM LTO Gen 3 IBM 3590-E1A IBM 3590-H1A IBM 3592 STK T9840C STK T9940C IBM Tivoli Storage Manager Implementation Guide...
Page 81 The information in Table 2-15 will be used when sizing tape libraries and then when defining them to Tivoli Storage Manager. Table 2-15 Tape drive configuration worksheet Option Library model IBM System Storage™ TS3310 Tape Library Number of drives Drive model...
Page 82: Tape Devices
Manager server for production use should have a library with two or more tape drives. Here are some business reasons for selecting a multiple-drive solution: To avoid a single point of failure To avoid interruptions to automated backup processing (reclamation, backup stgpool, migration contention) IBM Tivoli Storage Manager Implementation Guide...
Page 83: Tape Volumes
To avoid limiting your scalability (few environments are static or shrink with regards to the amount of managed data) To avoid building additional complexity into the design and implementation, which will drive the cost of implementation higher Because the price point for libraries and tape drives have fallen significantly in the recent past Two-drive systems allow for quicker reclamation and pool copies and reduced drive outages, but restores coming from tape may be delayed due to other...
Page 84 4. 5 * 1.5 gives 14 total cartridges required for on-site tapes. 5. If we use collocation for the database servers, since there 4 database servers and 20 file servers, we have enough tape volumes. IBM Tivoli Storage Manager Implementation Guide...
Page 85 Archive tapes For archive tapes: 1. Using Table 2-1 on page 18, multiply the GB copied per archive by (1 - the data compression rate), giving transferred archive data. 2. For each client, multiply the transferred archive data by the number of archives kept in a year times the yearly retention ratio (that is, desired monthly retention/12 months), and sum up, giving total archive data.
Page 86: Off-Site Volumes
To estimate the number of scratch volumes required: 1. Total the number of tape volumes required for on-site tapes, off-site tapes, and database backup tapes. 2. Calculate 15% of this number to allocate for scratch tape volumes. IBM Tivoli Storage Manager Implementation Guide...
Page 87 We have a total of 49 on-site, off-site, and scratch tapes. Fifteen percent of this is nine tapes. Backup set volumes It is worth calculating backup set tape space requirements separately from regular file-based processing due to the nature of backup sets. Note that although the backup set is a server-initiated procedure, our calculations are based on previous file-backup operations.
Page 88: Z/Os Tape Management
68 tape volumes required, growing to 75 in the first year, assuming a 10% growth rate. You then need to consider this number against the library configurations available for your chosen technology. The IBM System Storage TS3310 with expansion unit has space for 128 cartridges, so this leaves some capacity for future growth.
Page 89: Administrator Ids
2.11 Administrator IDs Identify who will be the Tivoli Storage Manager administrators in your organization. A Tivoli Storage Manager administrator controls Tivoli Storage Manager resources. There can be numerous administrators with varying levels of authority over the Tivoli Storage Manager server itself. Also, an administrator can use the Web backup-archive client to perform backup, restore, archive, and retrieve operations on the behalf of other users using a Web browser.
Page 90: License Considerations
This section describes the tasks involved when licensing a Tivoli Storage Manager system, including registering, saving, and auditing. The base IBM Tivoli Storage Manager feature includes the following support: An unlimited number of administrative clients Enterprise Administration, which includes command routing, enterprise...
Page 91 The nodelock file is destroyed or corrupted. Tivoli Storage Manager stores license information in the nodelock file, which is located in the directory from which the server is started. Monitoring licenses When license terms change (for example, a new license is specified for the server), the server conducts an audit to determine whether the current server configuration conforms to the license terms.
Page 92: Other Considerations
Design your client installs to be as generic and as similar as possible. If an automated software install process is available, consult with the process owners regarding the best practices to use in setting up Tivoli Storage Manager clients. IBM Tivoli Storage Manager Implementation Guide...
Page 93: Summary
2.13 Summary Now that we have discussed planning and checklists in the initial chapters, as well as the need to read and understand the IBM Redbook IBM Tivoli Storage Management Concepts, SG24-4877, we can get started on the actual installation phase.
Page 94 IBM Tivoli Storage Manager Implementation Guide...
Page 95: Part 2. Installation
Part In this part of the book we discuss the installation of the server and client code that will be used to implement IBM Tivoli Storage Manager. We provide implementation checklists and describe the various planning considerations you will need to take into account to get the best results.
Page 96 IBM Tivoli Storage Manager Implementation Guide...
Page 97: Chapter 3. Server Installation
Server installation Chapter 3. In this chapter we explain the steps relating to the basic installation of an IBM Tivoli Storage Manager server. We cover the topics of code installation and options file customization. We assume that, before you enter into this installation, you have completed the planning worksheets, and have read and understood the IBM Tivoli Storage Management Concepts, SG24-4877.
Page 98: Software Installation
3.2 Latest software updates Tivoli Storage Manager server and client code fixes and enhancements are released on a regular basis. The fixes are available from IBM via the Internet or CD-ROM. Downloading from the Internet is preferable if your connection supports it.
Page 99 This allows easier distribution and code installation, especially for clients. Attention: If you are using IBM tape devices such as 3580, 3592, and associated libraries, you do not need to install the Tivoli Storage Manager device driver, since these device drivers use the IBM tape driver. The IBM tape device drivers are available at the FTP site: ftp://ftp.software.ibm.com/storage/dev/drvr...
Page 100: Aix Server Installation
– tivoli.tsm.server.com Server samples and diagnostic utilities – tivoli.tsm.server.aix5.rte64 Server runtime - AIX 5.x, 64-bit – tivoli.tsm.msg.en_US.server Message Library and help – tivoli.tsm.msg.en_US.devices SMIT menu catalogs – tivoli.tsm.license.aix5.rte64 License enablement module - 64-bit kernel IBM Tivoli Storage Manager Implementation Guide...
Page 101 – tivoli.tsm.license.cert License certificates – tivoli.tsm.server.webcon Administration Center 4. Perform a preview install to make sure there is sufficient disk space and that PREVIEW only Preview all prerequisite filesets have been selected. With new LICENSE agreements options set to Yes, press Enter. Note: To install the server on AIX V5.2 or later, you must accept the license agreement.
Page 102: Linux Server Installations
Red Hat Linux distribution. For more information about Tivoli Storage Manager Server for Linux, please see the Information Center: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?toc=/com.ibm.i tstorage.doc/toc.xml 3.4.1 Installation packages The installation packages are in rpm format, and include: TIVsm-license-5.3.2-0.i386.rpm TIVsm-server-5.3.2-0.i386.rpm TIVsm-tsmscsi-5.3.2-0.i386.rpm IBM Tivoli Storage Manager Implementation Guide...
Page 103: Installation Commands
3.4.2 Installation commands Go to the directory where the TIVsm-server package was uncompressed and unpacked (or the mount point for CD-ROM). Execute the server installation script, install_server, as shown in Example 3-4. Select the language for installation (2 for English in our example). The license agreement displays.
Page 104 TIVsm-cmdlinehelp.fr_FR-5.3.0-0 10 TIVsm-cmdlinehelp.fr_FR.utf8-5.3.0-0 11 TIVsm-cmdlinehelp.it_IT-5.3.0-0 12 TIVsm-cmdlinehelp.it_IT.utf8-5.3.0-0 13 TIVsm-cmdlinehelp.ja_JP-5.3.0-0 14 TIVsm-cmdlinehelp.ja_JP.utf8-5.3.0-0 15 TIVsm-cmdlinehelp.ko_KR-5.3.0-0 16 TIVsm-cmdlinehelp.ko_KR.utf8-5.3.0-0 17 TIVsm-cmdlinehelp.pt_BR-5.3.0-0 18 TIVsm-cmdlinehelp.pt_BR.utf8-5.3.0-0 19 TIVsm-cmdlinehelp.zh_CN-5.3.0-0 20 TIVsm-cmdlinehelp.zh_CN.gb18030-5.3.0-0 21 TIVsm-cmdlinehelp.zh_CN.utf8-5.3.0-0 22 TIVsm-cmdlinehelp.zh_TW-5.3.0-0 23 TIVsm-cmdlinehelp.zh_TW.euctw-5.3.0-0 24 TIVsm-cmdlinehelp.zh_TW.utf8-5.3.0-0 BASIC INSTALL QUIT IBM Tivoli Storage Manager Implementation Guide...
Page 105 The basic install includes the following packages: TIVsm-server-5.3.2-0 TIVsm-license-5.3.2-0 Should I continue with the basic install? (Y/N) Installing TIVsm-server-5.3.2-0. Preparing... ########################################### [100%] 1:TIVsm-server ########################################### [100%] Upgrading TSM server database... *********************************************************** IMPORTANT: Read the contents of file /README for extensions and corrections to printed product documentation.
Page 106: Post-Installation Steps
(C) Copyright IBM Corporation 1990, 2004. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7800I DSMSERV generated at 03:39:28 on Sep 27 2005. ANR7801I Subsystem process ID is 15131.
Page 107 ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 8 megabytes. ANR0201I Database assigned capacity is 36 megabytes. ANR0306I Recovery log volume mount in progress. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress.
Page 108: Uninstallation Of The Server
CD. Before the installation begins, you are prompted for a location to store the temporary installation files. The default is C:\TSM_Images\TSMSRV5320_WIN. Once the package is extracted, click the Install Products option. An installation menu, as shown in Figure 3-1 on page 79, is displayed. IBM Tivoli Storage Manager Implementation Guide...
Page 109: Windows Tivoli Storage Manager Server Installation Menu
Figure 3-1 Windows Tivoli Storage Manager server installation menu 2. Choose the TSM Server installation package first. The InstallShield Wizard will guide you through the installation of the package. Click Next on the wizard welcome window. 3. The license agreement confirmation is displayed next. Read the license agreement carefully.
Page 110: Tivoli Storage Manager License Package Installation
1. After the server has been installed, choose TSM Server Licenses from the installation menu (Figure 3-1 on page 79). 2. The InstallShield Wizard for IBM Tivoli Storage Manager License initiates. Click Next on the wizard welcome window. 3. Enter customer information and choose access rights to the Tivoli Storage Manager server application.
Page 111: Tivoli Storage Manager Device Driver Package Installation
3.5.3 Tivoli Storage Manager Device Driver package installation To install: 1. Choose TSM Device Driver from the installation menu (Figure 3-1 on page 79). Tip: You should disable the Windows Removable Storage Manager (RSM™) component so that it will not conflict with Tivoli Storage Manager. To disable RSM, select RSM from the Windows services applet and disabled change its startup type to...
Page 112: Windows 2000/2003 Configuration Wizards
(large server configuration). This task is better handled through the use of administrative macros or scripts. Our recommendation is to use the wizards with care. IBM Tivoli Storage Manager Implementation Guide...
Page 113: Integrated Solution Console And Administration Center
Information: The configuration wizards are not discussed in this book. Documentation is provided on the use of these wizards in the section “Performing the Initial Configuration” of IBM Tivoli Storage Manager for Windows Quick Start, GC32-0784. 3.6 Integrated Solution Console and Administration Center Tivoli Storage Manager V5.3 and later servers are administered through a new...
Page 114 You install the Administration Center as an IBM (ISC) component. The Integrated Solutions Console allows you to install components provided by multiple IBM applications, and access them from a single interface. The Tivoli Storage Manager server itself can require a large amount of memory, network bandwidth, and processor resources.
Page 115: Isc And Administration Center Installation
1. Go to the directory to which you have unpacked the ISC and Administration Center code. Start the installation with setupISC.exe. The InstallShield Wizard for IBM Integrated Solutions Console, as shown in Figure 3-5 on page 86, appears. Click Next.
Page 116: Installshield Wizard For Ibm Integrated Solutions Console
We decided to keep the default ID, iscadmin. Once you have completed the input fields click Next. 5. Now you are prompted for the directory location to install the IBM Integrated Solutions Console. If you want to install to another directory, provide your input here—you can browse through your system for an alternate installation...
Page 117: Isc Installation: Review And Confirm Settings
Click Next. You will be asked to review and confirm your settings as shown in Figure 3-6. Figure 3-6 ISC installation: Review and confirm settings Chapter 3. Server installation...
Page 118: Isc Installation Progress
Figure 3-7 ISC installation progress 8. After the ISC installation is complete, a success screen is displayed. Click Next, then click Finish. You can now install the Administration Center, which is provided as a separate package. IBM Tivoli Storage Manager Implementation Guide...
Page 119: Installshield Wizard For Administration Center
9. Change to the directory to which you have extracted the Administration Center code and start setupAC.exe. The InstallShield Wizard for Tivoli Storage Administration Center is displayed, as shown in Figure 3-8. Click Next. Figure 3-8 InstallShield wizard for Administration Center 10.Review the license information.
Page 120: Administration Center Installation: Confirm
IP address instead of a dynamically assigned IP address. A static IP address is necessary because the Administration Center server must be listed on your domain name servers, which map the host name to the physical address of the system. IBM Tivoli Storage Manager Implementation Guide...
Page 121: Customization
Figure 3-10 TSM Administration Center installation: success 3.7 Customization The Tivoli Storage Manager server has a number of options and settings that control its operation. You specify the options in the server options, as well as some individual settings. 3.7.1 Server options file Tivoli Storage Manager has a server options file with a set of default options to start the server.
Page 122 Note: At server initialization, the server reads the server options file. If you update a server option by editing the file, you must stop and restart the server to activate the updated server options. IBM Tivoli Storage Manager Implementation Guide...
Page 123: Settings
For more information about the different server options, see IBM Tivoli Storage Manager Quick Start Manual and Administrator’s Reference Manual for your platform. 3.7.2 Settings Tivoli Storage Manager provides default server run-time settings. These settings are stored in the Tivoli Storage Manager database and persist across server restarts.
Page 124 “Command-line interface” on page 320, for information about how to invoke this. Example 3-11 Set accounting on tsm: TSM>set accounting on ANR2091I Accounting parameter set to ON. tsm: TSM>set actlogretention 10 ANR2090I Activity log retention period set to 10 days. IBM Tivoli Storage Manager Implementation Guide...
Page 125: Summary
3.8 Summary Now you have your Tivoli Storage Manager server installed. It is time to move on to installing the clients and testing your initial backup configuration. The following chapter talks specifically about configuring clients. Chapter 3. Server installation...
Page 126 IBM Tivoli Storage Manager Implementation Guide...
Page 128: Backup-Archive Client Code
The client who is receiving the remote operations needs to install the backup-archive client code, including the Web client component. Figure 4-1 on page 99 shows the difference between a traditional restore using the native backup-archive client and using the Web client. IBM Tivoli Storage Manager Implementation Guide...
Page 129: Difference Between A Local And Web-Based Restore
Web browser installed including Web client Local client restore Remote restore via via IBM Tivoli Web browser to IBM Storage Manager Tivoli Storage client Manager client Figure 4-1 Difference between a local and Web-based restore Chapter 4. Backup-archive client installation...
Page 130: Web Backup-Archive Client Main Window
Web browser. The executable name is DSMCAD. On UNIX and Linux clients, it should be run as a daemon. For Windows 2000, XP, or 2003, it is installed and TSM Client Acceptor run as a service called IBM Tivoli Storage Manager Implementation Guide...
Page 131: Api Client
For more information about installation and configuration of the backup-archive client, refer to the latest version of the IBM Tivoli Storage Manager Backup-Archive Clients Installation and User’s Guide for your specific platform.
Page 132: Backup-Archive Client Code
RSS, or regularly visit the Tivoli Storage Manager support Web site: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html 4.2.2 AIX backup-archive client This section shows how to install the Tivoli Storage Manager backup-archive client code on a pSeries running AIX V5.3 with 64-bit kernel. IBM Tivoli Storage Manager Implementation Guide...
Page 133 Note: With IBM Tivoli Storage Manager V5.3, there is no longer a separate 64-bit AIX client package. The same V5.3 client can be used on either 32-bit or 64-bit machines. Also note that the root user must install the client’s filesets.
Page 134 ACCEPT new license agreements? Preview new LICENSE agreements? We installed the following filesets: – tivoli.tsm.client.ba.jfs2 – tivoli.tsm.client.api.jfs2 – tivoli.tsm.books.en_US.client.htm The tivoli.tsm.client.ba.jfs2 fileset contains the following packages: – tivoli.tsm.client.ba.jfs2.base – tivoli.tsm.client.ba.jfs2.common – tivoli.tsm.client.ba.jfs2.image – tivoli.tsm.client.ba.jfs2.nas – tivoli.tsm.client.ba.jfs2.web IBM Tivoli Storage Manager Implementation Guide...
Page 135 5. Perform a preview install to ensure that there is sufficient disk space and that all prerequisite filesets have been selected. Example 4-4 shows the PREVIEW only Preview new LICENSE agreements options set to Yes. Example 4-4 Smitty screen - preview only installation Install and Update from ALL Available Software Type or select values in entry fields.
Page 136: Linux Backup-Archive Client
Space Managed client (HSM) is possible only from a JFS2 file system. 4.2.3 Linux backup-archive client We installed the client code on SuSE and Redhat Linux distributions. The installation packages are in rpm format. IBM Tivoli Storage Manager Implementation Guide...
Page 137 Store the compressed installation package on the machine where you want to install the backup-archive client and do the following: 1. Decompress the zip file and unpack the tar file, as in Example 4-7. The command output was actually longer, as there were a number of localization files that we deleted for clarity.
Page 138: Windows Backup-Archive Client
TIVsm-API-5.3.2-0 wisla:/tmp/tsm_client/linux86 # For more information about UNIX and Linux installation and prerequisites, see IBM Tivoli Storage Manager for Unix and Linux Backup-Archive Clients Installation and User’s Guide, GC32-0789. 4.2.4 Windows backup-archive client We installed the backup-archive client code on Diomede, running Windows 2003 Server.
Page 139: Backup-Archive Client Installation Packages
Installshield method The method is: 1. Insert the installation CD and when the autorun displays the main installation window, click Install Products to begin. Figure 4-4 shows the available backup-archive client installation packages. Figure 4-4 Backup-archive client installation packages Click the appropriate product for your operating system platform. Our machine runs the 32-bit version of Windows 2003 on an x86-based processor, so we choose to install TSM Backup-archive Client - x32.
Page 140: Client Code Destination
Next and you are given an option to specify the destination folder where the client code is to be installed. In Figure 4-5 we chose to install the code in the default installation path, which is the recommended destination. Figure 4-5 Client code destination IBM Tivoli Storage Manager Implementation Guide...
Page 141: Client Setup Type
3. Choose the type of installation. In Figure 4-6 we chose a typical installation. You may choose Custom installation to select additional components and features, such as Open Files support, Image backup support, and more. However, when these features are not required, our recommendation is to choose Typical installation to make sure that all Tivoli Storage Manager basic client components and prerequisites are installed.
Page 142: Completion Of Client Installation
Tivoli Storage Manager client, and the installation is performed while the client programs are running. Therefore, we recommend that you shut IBM Tivoli Storage Manager Implementation Guide...
Page 143: Customization
Tivoli Storage Manager client programs and services before performing the installation. Example 4-10 Backup-archive sample client silent installation msiexec /i "C:\WindowsClient5.3.2\tsmcli\x32\client\Disk1\IBM Tivoli Storage c:\> Manager Client.msi" RebootYesNo="No" REBOOT="Suppress" ALLUSERS=1 INSTALLDIR="c:\program files\tivoli\ tsm" ADDLOCAL="BackupArchiveGUI,BackupArchiveWeb,ApiRuntime,Readmes" TRANSFORMS=1033.mst /qn /l*v "c:\log.txt" c:\>...
Page 144 Tivoli Storage Manager includes options that control processing for user sessions. For example, you can use options to tell Tivoli Storage Manager which communication method to use, what format to use for dates, whether to use client compression, and more. IBM Tivoli Storage Manager Implementation Guide...
Page 145 We provide recommended option files for the various client platforms, as the layout of the supplied options file is not immediately intuitive. The backup-archive client has at least one configuration file, which is divided into the following parts: Communication options Operational options Site-dependent options Include-exclude options...
Page 146 1501. TCPWINDOWSIZE Specifies the size, in kilobytes, of the TCP/IP sliding window for the client node. This setting is highly operating-system specific. You must only use the allowed values for your TCP/IP implementation. IBM Tivoli Storage Manager Implementation Guide...
Page 147 TCPBUFFSIZE Specifies the size, in kilobytes, of the Tivoli Storage Manager internal TCP/IP communication buffer. This setting is highly operating-system specific. You must only use the allowed values for your TCP/IP implementation. NODENAME Indicates the client node name to over-ride the default value of the host name.
Page 148 Site-dependent options If your locale is not the United States, then we recommend that you adjust the date, number, and time format options and also the language option in your client IBM Tivoli Storage Manager Implementation Guide...
Page 149 options file to support your requirements. Respective client options are DATEFORMAT, NUMBERFORMAT, and TIMEFORMAT. Include-exclude options The include-exclude options are written into the client user options file dsm.opt on non-UNIX platforms. On UNIX/Linux, include-exclude options are either written into the client system options file (dsm.sys)or in a separate file, called the include-exclude file.
Page 150: Web Backup-Archive Client
HTTPPORT 1581 REVOKEREMOTEACCESS NONE WEBPORTS CADPort and AgentPort, defaults are 0 4.3.3 Using the client configuration wizard The next sections describe how to use the backup-archive client configuration wizard on UNIX/Linux and Windows platforms. IBM Tivoli Storage Manager Implementation Guide...
Page 151: Unix/Linux Configuration Wizard
When the GUI client starts, it checks to see whether a client user options file exists. If the client user options file does not exist (which is typically the case when the client is first installed), the setup wizard automatically starts to guide you through the configuration process.
Page 152: Java Gui Client Configuration Wizard
Figure 4-8. We choose Create a new options file and click Next. Figure 4-8 Java GUI client configuration wizard IBM Tivoli Storage Manager Implementation Guide...
Page 153: Server Name Definition
2. In the next screen (Figure 4-9) enter the Tivoli Storage Manager server name. On UNIX clients, you may create multiple server definitions in your central option file (dsm.sys), each with different settings. Each set of definitions uses stanza a different stanza in the dsm.opt file and is identified by a name corresponding to the Tivoli Storage Manager server name.
Page 154: Client/Server Communication Method Screen
We chose TCP/IP, as in Figure 4-10, since this is the most common method across all client types. Figure 4-10 Client/Server communication method screen IBM Tivoli Storage Manager Implementation Guide...
Page 155 4. When using the TCP/IP communication method, we need to provide the address of the server and the TCP/IP port the server instance listens on, as in Figure 4-11. You may use either the TCP/IP address or the host name. In our case, the server is installed on the same machine as the client, ATLANTIC, and since we do not want to depend on name resolution services, we provide the dotted IP address.
Page 156: Client Node Name Configuration Screen
Often this is the same as the host name, but it may not be. In Figure 4-12 we used the host name ATLANTIC as the node name. Figure 4-12 Client node name configuration screen IBM Tivoli Storage Manager Implementation Guide...
Page 157 6. In the final screen, Figure 4-13, you are prompted to apply the settings configured in the previous screens. To review or change any options, click Back. When satisfied, complete the configuration wizard by clicking Finish. Figure 4-13 Completing client configuration 7.
Page 158 Note that this list contains the journal database files. *.jdb.jbbdb *.jdbInc.jbbdb [JournaledFileSystemSettings] JournaledFileSystems=/home /xyz The journal will write initialization information to the file specified by the errorlog option. When you are satisfied the journal is working correctly, you should run IBM Tivoli Storage Manager Implementation Guide...
Page 159: Use Of Windows Configuration Wizards
the script file /usr/tivoli/tsm/client/ba/bin/jbbinittab. This puts the following entry in /etc/inittab so that the journal daemon starts when the machine boots: tsmjbb:2:wait:/usr/tivoli/tsm/client/ba/bin/rc.tsmjbb > /dev/console 2>&1 4.5 Use of Windows configuration wizards The Windows backup-archive client configuration wizard allows you to configure the client options file, Web client, client scheduler, journal engine, online image support, and open file support.
Page 160: Client Configuration Wizard Startup Window
On startup, the client checks whether a client options file exists as specified in the DSM_CONFIG environment variable. If not, it immediately starts a setup wizard to configure the client options file (see Figure 4-15). Click Next. Figure 4-15 Client Configuration Wizard startup window IBM Tivoli Storage Manager Implementation Guide...
Page 161 2. In the next screen (Figure 4-16) you have the option to create, update, or import an options file. We select Create a new options file. Figure 4-16 Windows create options file Chapter 4. Backup-archive client installation...
Page 162 3. Enter a node name to be used by the client. You need to contact your Tivoli Storage Manager administrator to obtain the node name they have used to register your client to the server. In Figure 4-17 we used the host name, DIOMEDE. Figure 4-17 Windows client nodename IBM Tivoli Storage Manager Implementation Guide...
Page 163: Client-Server Communication Method
4. Select the communication method. We chose TCP/IP, as in Figure 4-18. Figure 4-18 Client-server communication method Chapter 4. Backup-archive client installation...
Page 164: Tcp/Ip Parameters
5. Enter the Tivoli Storage Manager server IP address or resolvable host name and the TCP/IP port number. Figure 4-19 shows our values using the default TCP/IP port of 1500. Figure 4-19 TCP/IP parameters IBM Tivoli Storage Manager Implementation Guide...
Page 165 6. Figure 4-20 shows a recommended include/exclude file list. These files are in most cases not needed for system recovery, so the client configuration wizard gives you the option to directly exclude here, while allowing other files to be backed up or archived. Figure 4-20 Recommended Include/Exclude List 7.
Page 166 Either choose all local file systems and system objects by checking the Backup all local file systems option or explicitly select a subset of those. Usually, you want to incrementally back up IBM Tivoli Storage Manager Implementation Guide...
Page 167 all file systems, so we recommend the Backup all local file systems option unless you really do want to exclude certain file systems from backup. Doing this ensures that if you add a new partition or disk, it will be automatically included in incremental backup operations.
Page 168: Completion Of Client Configuration Wizard
Storage Manager administrator for the password that was specified for your client node when it was registered at the Tivoli Storage Manager server. You can now run basic backup operations. Figure 4-24 Windows Tivoli Storage Manager client login IBM Tivoli Storage Manager Implementation Guide...
Page 169: Web Client Configuration
4.5.2 Web client configuration To run the configuration tasks and launch the configuration wizard from the backup-archive client main screen. Select Utilities → Setup Wizard from the client GUI, shown in Figure 4-59 on page 172. 1. We are setting up the Web client, so select Help me configure the TSM Web Client, as shown in Figure 4-25.
Page 170: Installing A New Web Client Screen Panel
2. We want to install a new Web client, so select this option as in Figure 4-26. Figure 4-26 Installing a new Web client screen panel IBM Tivoli Storage Manager Implementation Guide...
Page 171 3. As shown in Figure 4-27, we select the name of the Web Service “Client Acceptor process, which you will see running and also will be seen later in the Windows services list. We accept the default name. Figure 4-27 Selection of the Web services Chapter 4.
Page 172 4. Enter the path and file name of the options file, as in Figure 4-28. We have chosen the default location, which is the client installation directory, in subdirectory baclient. Figure 4-28 Choose the path and file name of the options file IBM Tivoli Storage Manager Implementation Guide...
Page 173 5. In Figure 4-29, specify the port that the Web Client Acceptor will listen on. This will be the port you reference when connecting with your browser. We choose the default, 1581. Figure 4-29 Enter a Web Client Acceptor port number Chapter 4.
Page 174: Enter The Client's Node Name And Password
Figure 4-30. We recommend checking the Contact the TSM server to validate password box so that the client will authenticate with the Tivoli Storage Manager server to validate the password that you specified. Figure 4-30 Enter the client’s node name and password IBM Tivoli Storage Manager Implementation Guide...
Page 175 7. In the Service login options panel, select the Windows account that will start and run the Web client service. Also you can select whether to start the service automatically or manually, as shown in Figure 4-31. Figure 4-31 Selection panel for the account and startup options Chapter 4.
Page 176 Windows services applet. Note that this service only runs when requested by the Web client; therefore, you do not specify startup options here. We accepted the default name. Figure 4-32 Select the name of the client agent IBM Tivoli Storage Manager Implementation Guide...
Page 177: Choose Whether To Allow Remote Access To The Web Client
9. Determine whether you want to revoke access to this Web client for administrators with access privilege, which is shown in Figure 4-33. Note that this will not restrict the administrators who are granted client owner privilege. We leave it with default option, which is no restriction to other administrators. Figure 4-33 Choose whether to allow remote access to the Web client Chapter 4.
Page 178: Choose Whether To Start The Service After The Wizard Completes
10.In the window shown in Figure 4-34 choose whether to start the Web client services after this wizard completes. Figure 4-34 Choose whether to start the service after the wizard completes IBM Tivoli Storage Manager Implementation Guide...
Page 179: Client Scheduler Configuration
11.Figure 4-35 is the completion screen for the wizard. Click Finish to commit the changes or Back to review your selections. Figure 4-35 Completion panel for the Web client configuration 12.Figure 4-36 shows that we are all done. Figure 4-36 That is all for this wizard 4.5.3 Client scheduler configuration This section shows how to use the Windows wizard to configure the client scheduler, which will communicate with the Tivoli Storage Manager server to...
Page 180: Installing A New Client Tsm Scheduler Wizard Selection
2. As this is our first scheduler service, we only have the option to install a new scheduler service, as shown in Figure 4-37. Figure 4-37 Installing a new client TSM Scheduler Wizard selection IBM Tivoli Storage Manager Implementation Guide...
Page 181 3. Enter a name for the scheduler service, as in Figure 4-38. You can choose to install it on the local machine or on a remote machine. Optionally, you may specify for the Web Client Acceptor Daemon (CAD) to operate the scheduler service.
Page 182 4. In Figure 4-39, enter the option file. For our first scheduler instance, this is the standard client options file. If running multiple scheduler clients, then each needs its own client options file. Figure 4-39 Select the option file to use IBM Tivoli Storage Manager Implementation Guide...
Page 183 5. Enter the client node name and password (Figure 4-40). As before in step 6 on page 144, you can choose to immediately authenticate to the Tivoli Storage Manager server. Figure 4-40 Supply the client node name and password Chapter 4. Backup-archive client installation...
Page 184 6. Choose which Windows account to run the service in, and the startup options, as in Figure 4-41. Figure 4-41 Choose the Windows account and starting options for the client IBM Tivoli Storage Manager Implementation Guide...
Page 185: Defining Schedule And Error Log Names
7. Enter a directory and name for the schedule and error log files. We accepted the default locations, as shown in Figure 4-42. We also selected to log events to the Windows Event Log. The schedule log contains the results of scheduled operations, and can be either verbose or summary information, depending on the options set in the dsm.opt file.
Page 186 8. In Figure 4-43, choose whether to start the scheduler service after this wizard completes. Figure 4-43 Startup choice once the wizard has completed IBM Tivoli Storage Manager Implementation Guide...
Page 187: Journal Engine Configuration
9. Figure 4-44 is the completion screen for the wizard. Click Finish to commit the changes or Back to review your selections. Figure 4-44 Configuration completion panel 10.Figure 4-45 shows the successful completion message. Figure 4-45 Scheduler installed 4.5.4 Journal engine configuration The journal engine component observes and keeps track of changes in files in local file systems.
Page 188: Installing A New Journal Engine
TSM Journal Engine from the screen shown in Figure 4-25 on page 139. 2. In Figure 4-46, choose Install a new Journal Engine. This panel also has options to update and remove the journal engine if it already exists. Figure 4-46 Installing a new journal engine IBM Tivoli Storage Manager Implementation Guide...
Page 189 3. In the screen shown in Figure 4-47 select which file systems you want to journal. You can select individual file systems or check to Journal all local file systems. Figure 4-47 Choose the file systems that are to be journaled Chapter 4.
Page 190 Figure 4-48 Specify the location for the journal database IBM Tivoli Storage Manager Implementation Guide...
Page 191 5. In the next screen (Figure 4-49 on page 161) you specify which particular changes in the file systems are to be monitored by the journal engine. By default, creating new objects, changing the content of the existing ones, and changing access control attributes and other NTFS security changes are monitored.
Page 192: Journal Database Maximum Size Panel
6. You can limit the maximum size of the journal database. We recommend not doing this, as shown in Figure 4-50. Figure 4-50 Journal database maximum size panel IBM Tivoli Storage Manager Implementation Guide...
Page 193 7. Define the service login options. As with the other services, we recommend running as the system account, as shown in Figure 4-51. Figure 4-51 Login properties for the journal service Chapter 4. Backup-archive client installation...
Page 194 8. In the screen shown in Figure 4-52 we select to start the service immediately. Figure 4-52 Start up service after the wizard completes IBM Tivoli Storage Manager Implementation Guide...
Page 195: Online Image Support Configuration
9. Figure 4-53 is the completion screen for the wizard. Click Finish to commit the changes or Back to review your selections. Figure 4-53 Journal service completion wizard 10.The journal engine is successfully installed, as shown in Figure 4-54. Figure 4-54 Journal engine successfully installed panel 4.5.5 Online image support configuration In this section we describe how to configure online image support: 1.
Page 196 Figure 4-55 Install panel for the online image support 3. There are no options to select. The agent simply performs the installation. Click Next on the completion window. You are prompted to reboot the system (Figure 4-56 on page 167). IBM Tivoli Storage Manager Implementation Guide...
Page 197: Open File Support Configuration
Figure 4-56 Successful configuration of online image support 4.5.6 Open File Support configuration As with the previous configuration, Open File Support is very short and simple. Open File backup is now supported on all supported Windows platforms, such as Windows 2000, XP, and the recently added Windows 2003. 1.
Page 198: Client Interfaces
Tivoli Storage Manager server. In this section we describe how to start, use, and stop the command line interface (CLI) and the GUI. Example 4-12 on page 169 lists all available backup-archive client interfaces by platform. IBM Tivoli Storage Manager Implementation Guide...
Page 199 Java GUI Web client API client line client Apple Macintosh Hewlett-Packard HP/UX PA-RISC Hewlett-Packard HP/UX Itanium® IBM AIX 5L Linux for x86 Linux for pSeries Linux for iSeries Linux for zSeries Microsoft Windows 2000 Professional Microsoft Windows Microsoft Windows 2000 Server,...
Page 200: Command Line
Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 2.0 Client date/time: 02/20/06 10:54:16 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Node Name: ATLANTIC Please enter your user id <ATLANTIC>: Please enter password for user id “ATLANTIC”: Session established with server ATLANTIC: AIX-RS/6000 Server Version 5, Release 3, Level 2.2...
Page 201 Type help and then select a number from the list. Example 4-14 Backup-archive client help options help tsm> To search the IBM Tivoli Storage Manager technical support Web site to find technical solutions and answers to frequently asked questions, refer to http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.ht The following help topics are available.
Page 202: Gui
To start the GUI, enter dsm at the operating system prompt. The GUI is almost the same on Windows and UNIX/Linux. Figure 4-59 shows the main screen of the client GUI on Windows. Figure 4-59 Windows GUI client interface IBM Tivoli Storage Manager Implementation Guide...
Page 203: Client Scheduler
Figure 4-60 shows the main screen of the Java™-based client GUI on UNIX and Linux. Figure 4-60 Java-based backup-archive client GUI interface Depending on the features of your UNIX machine, for example, if it has the Common Desktop Environment (CDE) installed, you can add an option in the workplace screen so that it is easier to start Tivoli Storage Manager.
Page 204: Starting The Client Scheduler
You can manually start up the Tivoli Storage Manager scheduler if it was accidentally stopped, if you want to re-start it to pick up a changed client option, or if you want to force it to run immediately, for example, while testing a new function. IBM Tivoli Storage Manager Implementation Guide...
Page 205 > IBM Tivoli Storage Manager Command Line backup-archive Client Interface-Version 5, Release 2, Level 0.0 h4 (c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved. Querying server for next scheduled event. Node Name: AIXCLIENT Session established with server TSMSERVER: Windows Server Version 5, Release 2, Level 0.0...
Page 206: Client Scheduler Service Is Running On A Machine
Instead, dsmcutil can be run in a script to configure the scheduler and other services on multiple client machines at once. IBM Tivoli Storage Manager Implementation Guide...
Page 207 /autostart:yes TSM Windows NT Client Service Configuration Utility Command Line Interface - Version 5, Release 3, Level 2.0 (C) Copyright IBM Corporation, 1990, 2005, All Rights Reserved. Last Updated Sep 17 2005 TSM Api Verison 5.3.2 Command: Install TSM Client Service...
Page 208 The dsmcutil utility can also be used to install the other services (Web client, journal engine, and so on) as well as query and update service settings. For more information about the use and syntax of dsmcutil, see IBM Tivoli Storage Manager Backup-Archive Clients installation and User’s Guide, GC32-0788.
Page 209 execute regular schedules, especially if you have an enterprise policy to have Tivoli Storage Manager machines backed up at some point in the day. If you rely on manual startup, this can be easily forgotten if the owner of the client system has to reboot it for some reason, resulting in a missed backup schedule.
Page 210: Stopping The Scheduler
The administrator may need to cancel all multi-threaded sessions for the client. If the scheduler is executing a restore process, the Tivoli Storage Manager administrator needs to cancel the restartable restore by issuing the cancel restore command. IBM Tivoli Storage Manager Implementation Guide...
Page 211: Web Client Usage
/name:"TSM Central Scheduler" TSM Windows NT Client Service Configuration Utility Command Line Interface - Version 5, Release 3, Level 2.0 (C) Copyright IBM Corporation, 1990, 2005, All Rights Reserved. Last Updated Sep 17 2005 TSM Api Verison 5.3.2 Command: Stop TSM Client Service Machine: DIOMEDE(Local Machine) Stopping the 'TSM Central Scheduler' service ..
Page 212: Access Authorization
A user ID with client access privilege can only restore data back to its original system. A user ID with client owner privilege can restore data to another system if required. IBM Tivoli Storage Manager Implementation Guide...
Page 213: Starting The Web Client
4.8.4 Starting the Web client The Web client consists of two processes on the client workstation: the client acceptor and remote client agent. Client acceptor The Client Acceptor Daemon (CAD) is an HTTP daemon that serves the Web client Java applet to the Web browser. The name of the executable is dsmcad. On UNIX/Linux clients, it should be run as a daemon.
Page 214: Stopping The Remote Agent Services
Manager, and the main window displays. Figure 4-64 shows a login dialog box for a Web client session. Figure 4-64 Web client login dialog box 4.8.5 Stopping the remote agent services In general, there is no need to stop the remote agent services manually. IBM Tivoli Storage Manager Implementation Guide...
Page 215 /name:"TSM Remote Client Agent" /autostart:no TSM Windows NT Client Service Configuration Utility Command Line Interface - Version 5, Release 3, Level 2.0 (C) Copyright IBM Corporation, 1990, 2005, All Rights Reserved. Last Updated Sep 17 2005 TSM Api Verison 5.3.2...
Page 216: Summary
4.9 Summary You now have your server and clients installed and basic backup and restore functions tested and working. Next we proceed with further configuration and customization of the environment to suit your specific requirements. IBM Tivoli Storage Manager Implementation Guide...
Page 217: Chapter 5. Database And Recovery Log
Database and recovery log Chapter 5. By now you should have completed the installation of your IBM Tivoli Storage Manager server and clients, and done some basic functional testing. You are ready to move on to further customization. In this chapter we cover the steps to set up and change your database and recovery log settings to a recommended configuration.
Page 218: Database
The examples in this section are from Windows and AIX systems. Use the correct directory separator for your platform when entering file and path names. For other platforms, see the IBM Tivoli Storage Manager Administrator's Reference for that server.
Page 219 If you have a number of physical disks (or logical LUNs) allocated for use with Tivoli Storage Manager, try to position the database volumes on different file systems, to leverage performance provided by the hardware. If using mirroring for database and recovery log volumes, and you do not have enough disks to locate all primary and mirror volumes separately: –...
Page 220: Defining Database Volumes
Administrator’s Reference for your server platform. Whichever method you choose to define the volume, you must extend the database once the volume is defined. The extend db command allows the database to use the newly defined volume. IBM Tivoli Storage Manager Implementation Guide...
Page 221 Example 5-1 shows how to define a new database volume on a Windows server. The volume is called C:\TSMDATA\DBP\DBV_01.DSM and is 1 GB in size. Example 5-1 Defining a database volume define dbvolume c:\tsmdata\dbp\dbv_01.dsm formatsize=1024 tsm: LOCHNESS_SERVER1> wait=yes ANR0984I Process 36 for DEFINE DBVOLUME started in the FOREGROUND at 14:46:43. ANR2240I Database volume C:\TSMDATA\DBP\DBV_01.DSM defined.
Page 222: Recovery Log
See 5.3, “Setting the log mode” on page 196, for more information. As with its database, Tivoli Storage Manager considers the recovery log as one volumes logical object, made up of a number of physical files, or IBM Tivoli Storage Manager Implementation Guide...
Page 223: Recovery Log Design Considerations
5.2.1 Recovery log design considerations Recovery log volume numbers, sizes, and locations affect performance of the recovery log. The following points should be considered: All recovery log volumes must be on random access media (that is, disk drives). If there is more than one recovery log volume, more than one process can access the recovery log simultaneously.
Page 224: Defining Recovery Log Volumes
Then use the define logvolume command to define the recovery log volume to Tivoli Storage Manager (without specifying the FORMATSIZE option). For further information about the DSMFMT utility, see the Administrator’s Reference for your server platform. IBM Tivoli Storage Manager Implementation Guide...
Page 225 Example 5-3 shows how to allocate a new recovery log volume on a Windows server. The volume is called D:\TSMDATA\RLP\LOG_01.DSM and is 512 MB in size. Example 5-3 Defining a recovery log volume define logvol D:\tsmdata\rlp\log_01.dsm formatsize=512 tsm: LOCHNESS_SERVER1> wait=yes ANR0984I Process 72 for DEFINE LOGVOLUME started in the FOREGROUND at 16:04:30.
Page 226: Setting The Log Mode
NORMAL and ROLLFORWARD. NORMAL In normal mode, Tivoli Storage Manager saves only those transactions needed to restore the database to the point of the last database backup. Tivoli Storage Manager deletes any unnecessary transactions from the IBM Tivoli Storage Manager Implementation Guide...
Page 227 recovery log. Changes made to the database since the last backup cannot be recovered if the database is lost. Database backups can only be used to perform point-in-time recovery (that is, to the time of the last database backup). In NORMAL log mode, you need less space for the recovery log, since Tivoli Storage Manager deletes transactions once they have been committed to the database.
Page 228: Defining The Database Backup Trigger
Example 5-7 shows how to set the limit of 75% and run up to six incremental database backups before a full database backup. Example 5-7 Setting the database backup trigger def dbbackuptrigger devclass=lto2-dc logfullpct=75 tsm: LOCHNESS_SERVER1> numincremental=6 incrdevclass=lto2-dc ANR2282I Database backup trigger defined and enabled. query process tsm: LOCHNESS_SERVER1> IBM Tivoli Storage Manager Implementation Guide...
Page 229: Setting The Expansion Trigger
Process Process Description Status Number -------- -------------------- ---------------------------------------- Database Backup Full backup: 0 pages of 1500 backed up. Current output volume: LTO888 query dbbackuptrigger tsm: LOCHNESS_SERVER1> Full Incremental Log Full Incrementals Minimum Minimum Device Device Percentage Between Backup Class Class Fulls Interval Percentage...
Page 230: Database Space Trigger
In this case, the database will keep growing to the system limit. If you need to change the trigger definition later, use the update spacetrigger command. IBM Tivoli Storage Manager Implementation Guide...
Page 231: Recovery Log Space Trigger
Whenever the system detects that the database needs extra space, it triggers the expansion, and writes messages to the activity log, as shown in the query actlog command in Example 5-9. Example 5-9 Activity log messages from database expansion query actlog tsm: LOCHNESS_SERVER1>...
Page 232: Mirroring
If a partial write is detected, a mirror volume can be used to construct valid images of the missing pages. For this reason we recommend that you use the Tivoli Storage Manager provided IBM Tivoli Storage Manager Implementation Guide...
Page 233: Database And Recovery Log Mirroring
mirroring function at a minimum, rather than just operating system software or disk hardware mirroring. Although you can mirror either the database or the recovery log, we recommend that you mirror both. Mirroring both database and log provides better availability and recoverability.
Page 234 If four separate disks for your database and recovery log volumes are not possible, we recommend a minimum of two separate disks. In this way, you can place primary database and mirror log volumes on one disk, and primary log and IBM Tivoli Storage Manager Implementation Guide...
Page 235: Database Mirroring
mirror database volumes on the other. Table 5-2 shows how the volume placement would work. We assume for the UNIX examples, that /tsm and /tsm1 are file systems created on separate disks. Table 5-2 Database and recovery log volume placement on two disks Type of volume UNIX directories Windows location...
Page 236: Recovery Log Mirroring
ANR0986I Process 83 for DEFINE LOGCOPY running in the FOREGROUND processed 1 items for a total of 537,919,488 bytes with a completion state of SUCCESS at 16:36:27. query process tsm: LOCHNESS_SERVER1> Process Process Description Status Number -------- ------------------- --------------------------------------------- IBM Tivoli Storage Manager Implementation Guide...
Page 237: Removing Default Volumes
Recovery Log Copy Volume C:\TSMDATA\RLM\LGM_01.DSM - 256 Synchronization megabytes of 512 tsm: LOCHNESS_SERVER1>query logvol Volume Name Copy Volume Name Copy Volume Name Copy (Copy 1) Status (Copy 2) Status (Copy 3) Status ---------------- ------ ---------------- ------ --------------- ------ C:\TSMDATA\SERV- Sync'd Undef- Undef- ER1\LOG1.DSM...
Page 238 ATLANTIC> Volume Name Copy Volume Name Copy Volume Name Copy (Copy 1) Status (Copy 2) Status (Copy 3) Status ---------------- ------ ---------------- ------ --------------- ------ /usr/tivoli/tsm- Sync'd Undef- Undef- /server/bin/db- ined ined .dsm IBM Tivoli Storage Manager Implementation Guide...
Page 239: Removing The Default Recovery Log Volume
/tsm/db/primary- Sync'd /tsm/db/mirror/- Sync'd Undef- /dbp_01.dsm dbm_01.dsm ined delete dbvol /usr/tivoli/tsm/server/bin/db.dsm tsm: ATLANTIC> ANR2244I Delete process initiated for database volume /usr/tivoli/tsm/ server/bin/db.dsm (process id 11). ANS8003I Process number 11 started. q dbvol tsm: ATLANTIC> Volume Name Copy Volume Name Copy Volume Name Copy (Copy 1)
Page 240: Database Backup
Manager database backups. If the database becomes damaged or lost, you can restore it by running the Tivoli Storage Manager server in database restore mode: DSMSERV RESTORE DB. You will require the latest database backup media. IBM Tivoli Storage Manager Implementation Guide...
Page 241 If you are following the steps in this chapter, the DBBACKUPTRIGGER will already start database backups as needed. However, we also recommend that full you run a database backup on a regular basis (at the least, daily). If you make a number of database configuration changes, such as we did earlier in this chapter, you should run a backup immediately afterwards.
Page 242: Additional Commands
The problem can be compounded by the fact that each database backup requires its own tape—it is not possible to “stack” multiple backups onto a single tape. IBM Tivoli Storage Manager Implementation Guide...
Page 243: Estimate Dbreorgstats
You should think of this as a security feature. Database backups are extremely important—you do not want to be in the situation where the last seven days of database backups are contained on one tape that, at the crucial moment when a restore is required, turns out to be unreadable.
Page 244: Summary
5.10 Summary You have now finished configuring your database and recovery log volumes to suit your environment. The next step is to do the same for storage pool volumes, and configure your storage devices. IBM Tivoli Storage Manager Implementation Guide...
Page 245: Chapter 6. Data Storage
IBM Redbook IBM Tivoli Storage Management Concepts, SG24-4877. In the following sections we discuss how IBM Tivoli Storage Manager manages data storage pools and how you can define them, query them for status, and make changes based on operational requirements.
Page 246: Example Environment
EMPTY CLIENT_2 TAPEDATA PRIVATE (LIBRARY) SCRATCH OFFDATA MIGRATION EMPTY (USED) (FREE) Return Reusable Tapes Backup Storage Pools to OFFDIRS Copy Pools Send copy to vault Figure 6-1 Storage pool hierarchy for our recommended setup IBM Tivoli Storage Manager Implementation Guide...
Page 247: Primary Storage Pools
6.1.1 Primary storage pools In our example solution we set up four primary storage pools: TAPEDATA, DISKDATA, DISKDIRS, and NONE. Storage pool TAPEDATA must be set up before storage pool DISKDATA, because DISKDATA refers to TAPEDATA as its next storage pool. The examples in this chapter set up the following storage pools: 1.
Page 248: Devices
The FILE device type of DISK is predefined in Tivoli Storage Manager and cannot be altered. Device drivers IBM supplies device drivers for each of its library and tape devices, for each operating system the device is supported on. If you will be using another IBM Tivoli Storage Manager Implementation Guide...
Page 249 On Windows 2000 and 2003, you may need to use the Tivoli Storage Manager Device Driver. – However, if you are using IBM tape devices, such as the TS3100, TS3200, or TS3500 with LTO drives, you should install the IBM-supplied tape device drivers for Windows.
Page 250 It also shows the reference sections in this chapter for completing the tasks. Note: The examples in this section deal with an automated library (SCSI). Automated libraries are the most common libraries in use. IBM Tivoli Storage Manager Implementation Guide...
Page 251 Table 6-1 Guide to setting up storage pools Order of Component Component To define the type of device below, follow each definition class component section Auto Disk stg Sequential Copy library pool disk stg stg pool pool Physical Library 6.2.1, “Defining a library”...
Page 252: Defining A Library
Example 6-1 shows an example of the define library command. Example 6-1 Defining an automated SCSI library define library 3582lib libtype=scsi shared=yes autolabel=yes tsm: ATLANTIC> ANR8400I Library 3582LIB defined. q libr f=d tsm: ATLANTIC> Library Name: 3582LIB IBM Tivoli Storage Manager Implementation Guide...
Page 253: Defining A Path To A Library
AIX users: Run the following AIX command to find the device name, for example, /dev/smc0: root@Atlantic /: lsdev -Cc tape rmt0 Available 1Z-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 1Z-08-01 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 1Z-08-01 IBM 3582 Library Medium Changer (FCP) Before defining the path, the library must already be defined, as in 6.2.1,...
Page 254 Scratch Category: WORM Scratch Category: External Manager: Shared: Yes LanFree: ObeyMountRetention: Primary Library Manager: WWN: 500308C140067006 Serial Number: 0000013108231000 AutoLabel: Yes Reset Drives: Yes Last Update by (administrator): ADMIN Last Update Date/Time: 02/22/2006 12:32:41 IBM Tivoli Storage Manager Implementation Guide...
Page 255: Defining A Drive In A Library
With the path successfully created, the query library command now provides us with some more information. We can see the SAN World-Wide Name (WWN) and the library’s serial number. 6.2.3 Defining a drive in a library Libraries with multiple drives must have each drive defined to Tivoli Storage Manager.
Page 256: Defining A Path To A Drive In A Library
ANR1720I A path from ATLANTIC to 3582LIB DR01 has been defined. q drive f=d tsm: ATLANTIC> Library Name: 3582LIB Drive Name: DR00 Device Type: LTO On-Line: Yes Read Formats: ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Write Formats: ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Element: 257 IBM Tivoli Storage Manager Implementation Guide...
Page 257 Drive State: UNKNOWN Volume Name: Allocated to: WWN: 500308C140067006 Serial Number: 1110177214 Last Update by (administrator): ADMIN Last Update Date/Time: 02/22/2006 13:59:08 Cleaning Frequency (Gigabytes/ASNEEDED/NONE): ASNEEDED Library Name: 3582LIB Drive Name: DR01 Device Type: LTO On-Line: Yes Read Formats: ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Write Formats: ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Element: 256 Drive State: UNKNOWN...
Page 258: Defining A Device Class For A Library
MOUNTWait specifies the length of time the server will wait for a tape to become available in the library (that is, either mounted in a drive for a manual library, or checked in to an automated library). IBM Tivoli Storage Manager Implementation Guide...
Page 259 Example 6-6 shows defining a device class for use with an IBM 3582 LTO2 library. Example 6-6 Defining an LTO device class define devclass LTO2-DC library=3582LIB devtype=lto format=ultrium2c tsm: ATLANTIC> estcapacity=400G mountretention=10 mountwait=20 mountlimit=drives ANR2203I Device class LTO2-DC defined. q devc lto2-dc f=d tsm: ATLANTIC>...
Page 260: Defining A Sequential File Device Class
Volumes in a sequential file storage pool are, of course, files. You can specify how big each of these files can become before the Tivoli Storage Manager server closes one and creates another. IBM Tivoli Storage Manager Implementation Guide...
Page 261: Storage Pools
As for other device classes, use the define devclass command, specifying the DEVType=FILE option. Example 6-8 defines a device class named SEQF-DC with a maximum capacity of 256 MB. We also create a sequential file device class for use with directory metadata (from the directory management class). Example 6-8 Defining a sequential file device class efine devclass seqf-dc devtype=file mountlimit=25 maxcapacity=256M tsm: ATLANTIC>d...
Page 262: Defining A Sequential Access Tape Storage Pool
Example 6-9 Defining a primary sequential tape pool efine stgpool tapedata LTO2-DC description="Primary tape pool" tsm: ATLANTIC>d reclaim=100 maxscratch=1000000 collocate=node ANR2200I Storage pool TAPEDATA defined (device class LTO2-DC). q stgp tsm: ATLANTIC> Storage Device Estimated Pct High Low Next Storage IBM Tivoli Storage Manager Implementation Guide...
Page 263: Defining A Random Access Disk Storage Pool
Pool Name Class Name Capacity Util Migr Mig Mig Pool Pct Pct ---------- ---------- --------- ---- ----- ---- --- ----------- TAPEDATA LTO2-DC 0.0 M 6.3.2 Defining a random access disk storage pool Define a primary disk storage pool using the define stgpool command with the predefined device class of DISK.
Page 264: Defining A Sequential Access File Storage Pool
Pct High Low Next Storage Pool Name Class Name Capacity Util Migr Mig Mig Pool Pct Pct ---------- ---------- --------- ---- ----- ---- --- ----------- DISKDATA DISK 0.0 M TAPEDATA DISKDIRS DIRM-DC 0.0 M IBM Tivoli Storage Manager Implementation Guide...
Page 265 DISKFILE SEQF-DC 0.0 M NONE DISK 0.0 M TAPEDATA LTO2-DC 0.0 M Operation of a sequential access FILE storage pool A sequential access storage pool with a FILE device class acts somewhat differently compared to a storage pool mapped to a physical tape or optical device.
Page 266 Migration in Progress?: No Amount Migrated (MB): 0.00 Elapsed Migration Time (seconds): 0 Reclamation in Progress?: No Last Update by (administrator): ADMIN Last Update Date/Time: 02/23/2006 09:35:08 Storage Pool Data Format: Native Copy Storage Pool(s): IBM Tivoli Storage Manager Implementation Guide...
Page 267: Defining A Copy Storage Pool
Continue Copy on Error?: CRC Data: No Reclamation Type: Threshold update stg diskfile nextstgpool=tapedata tsm: ATLANTIC> ANR2202I Storage pool DISKFILE updated. q stg diskfile tsm: ATLANTIC> Storage Device Estimated Pct High Low Next Storage Pool Name Class Name Capacity Util Migr Mig Mig Pool...
Page 268: Deleting The Default Storage Pools
Example 6-15 Deleting the default storage pools del stgpool archivepool tsm: ATLANTIC> ANR2201I Storage pool ARCHIVEPOOL deleted. del stgpool backuppool tsm: ATLANTIC> ANR2201I Storage pool BACKUPPOOL deleted. del stgpool spacemgpool tsm: ATLANTIC> ANR2201I Storage pool SPACEMGPOOL deleted. IBM Tivoli Storage Manager Implementation Guide...
Page 269: Storage Pool Volumes
In 1.1.1, “Our support material” on page 5, we show how to load a predefined macro into the Tivoli Storage Manager. The macro mac.stgdelete, which we provide to delete the default storage pools, is shown in “Delete default storage pools” on page 739. The macro deletes the four default storage pools automatically set up by the Windows installation, including an additional storage pool named DISKPOOL.
Page 270 Pool Name Class Name Capacity Util Status ------------------ ---------- ---------- --------- ----- -------- /tsm/stg/diskdata- DISKDATA DISK 2,048.0 0.0 On-Line /ddvol_01.dsm /tsm/stg/diskdata- DISKDATA DISK 2,048.0 0.0 On-Line /ddvol_02.dsm /tsm/stg/diskdata- DISKDATA DISK 2,048.0 0.0 On-Line /ddvol_03.dsm IBM Tivoli Storage Manager Implementation Guide...
Page 271: Tape Volumes
/tsm/stg/diskdata- DISKDATA DISK 2,048.0 0.0 On-Line /ddvol_04.dsm /tsm/stg/diskdata- DISKDATA DISK 2,048.0 0.0 On-Line /ddvol_05.dsm /tsm/stg/diskdata- DISKDATA DISK 2,048.0 0.0 On-Line /ddvol_06.dsm q stg diskdata tsm: ATLANTIC> Storage Device Estimated Pct High Low Next Storage Pool Name Class Name Capacity Util Migr Mig Mig Pool...
Page 272 In Example 6-18 we loaded 17 new cartridges into our IBM 3582 library. We used the label libvolume command to label and check the tapes into the library, and specified the option LABELSource=Barcode to tell the labelling process to use the barcode as the label.
Page 273 -------- ------------------- ---------------------------------------------- LABEL LIBVOLUME ANR8805I Labelling volumes in library 3582LIB; 6 volumes(s) labelled. The label libvolume process runs in the background, and you can check the status using the query process command. The labelling process can take a long time if you are labelling a whole library full of tapes.
Page 274: Replying To Messages
02/23/2006 14:57:20 ANR2017I Administrator ADMIN issued command: REPLY 001 (SESSION: 82) 02/23/2006 14:57:20 ANR8499I Command accepted. (SESSION: 82) 02/23/2006 14:58:02 ANR8430I Volume 033AKK has been checked into library 3582LIB. (SESSION: 82, PROCESS: 29) 02/23/2006 14:58:02 ANR8431I CHECKIN LIBVOLUME process completed for library IBM Tivoli Storage Manager Implementation Guide...
Page 275: Additional Commands
3582LIB; 1 volume(s) found. (SESSION: 82, PROCESS: 29) 02/23/2006 14:58:02 ANR0985I Process 29 for CHECKIN LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 14:58:02. (SESSION: 82, PROCESS: 29) The process actually starts before we answer the request, but there is no way to tell that it is waiting unless you query for requests (or have an administrative session open in console mode).
Page 276: Auditing Volume Contents
The audit volume command is especially useful when integrity errors are detected on a volume, as you can determine what, if any, files on the volume are still readable and take appropriate action to restore it from a copy storage pool. IBM Tivoli Storage Manager Implementation Guide...
Page 277 By contrast, the query content command (see 6.5.10, “Querying volume contents” on page 260) displays only the database’s view of what is stored and does not require the volume to be mounted. Example 6-22 audits a volume named 031AKK and logs any discrepancies to the activity log.
Page 278: Back Up A Storage Pool
Typically, you would define one copy storage pool for a primary storage pool hierarchy. In our setup, both DISKDATA and TAPEDATA are backed up to the IBM Tivoli Storage Manager Implementation Guide...
Page 279 copy storage pool OFFDATA. Because the backup stgpool operation is incremental, only new files in the primary pool are copied to the copy pool. If we first back up DISKDATA, then TAPEDATA, any files that might have migrated from DISKDATA to TAPEDATA after we backed up DISKDATA do not get copied a second time from TAPEDATA to OFFDATA.
Page 280: Check A Tape In To A Library
Example 6-26 shows the checkin process for scratch volumes. Example 6-26 Checking in volumes in search mode checkin libvol 3582lib search=yes checklabel=barcode status=scratch tsm: ATLANTIC> ANS8003I Process number 8 started. q pr tsm: ATLANTIC> Process Process Description Status Number -------- ------------------- --------------------------------------------- IBM Tivoli Storage Manager Implementation Guide...
Page 281 CHECKIN LIBVOLUME ANR8425I Checking in volumes in search mode in library 3582LIB. q act tsm: ATLANTIC> Date/Time Message ------------------- ---------------------------------------------------------- 02/27/2006 10:54:38 ANR8430I Volume 039AKK has been checked into library 3582LIB. (SESSION: 128, PROCESS: 8) 02/27/2006 10:54:38 ANR8430I Volume 027AKK has been checked into library 3582LIB.
Page 282 Scratch 4,106 3582LIB 031AKK Scratch 4,107 3582LIB 032AKK Scratch 4,100 3582LIB 033AKK Scratch 4,109 3582LIB 034AKK Scratch 4,098 3582LIB 036AKK Scratch 4,101 3582LIB 037AKK Scratch 4,113 3582LIB 038AKK Scratch 4,114 3582LIB 039AKK Scratch 4,115 IBM Tivoli Storage Manager Implementation Guide...
Page 283: Check Out Library Volumes
Notice that the Last Use column is blank, as these tapes were used before being checked out and back in again. The Last Use column only applies to tapes that have been used after being checked in. 6.5.5 Check out library volumes To check out library volumes, use the checkout libvol command.
Page 284 3582LIB. Check for messages When checking volumes out of a library such as an IBM 3582 with only a single slot I/O port, the checkout command will move one tape to the I/O port, issue a message, and wait for you to reply to it.
Page 285: Deleting Storage-Related Objects
6.5.6 Deleting storage-related objects To remove storage-related objects, we use variations of the delete command. To delete objects in the storage hierarchy, you must first delete objects that depend on the object you wish to delete. Suppose you want to delete a library. You must first remove any references to it. must The following objects first be removed before deleting the library:...
Page 286: Mounted Volumes
2 matches found. dismount volume 023AKK tsm: ATLANTIC> ANR8499I Command accepted. dismount volume 022AKK tsm: ATLANTIC> ANR8499I Command accepted. q mount tsm: ATLANTIC> ANR8331I LTO volume 023AKK is mounted R/W in drive DR00 (/dev/rmt0), status: DISMOUNTING. IBM Tivoli Storage Manager Implementation Guide...
Page 287: Migration
ANR8331I LTO volume 022AKK is mounted R/W in drive DR01 (/dev/rmt1), status: DISMOUNTING. ANR8334I 2 matches found. 6.5.8 Migration Migration is the process of moving data from one primary storage pool to the next storage pool specified by the NEXTstgpool attribute. Migration is performed with the migrate stgpool command.
Page 288: Moving Data
We have changed the COLlocation attribute from No to Node. The move process moves data from the single volume to three others, keeping the data from each node separate. IBM Tivoli Storage Manager Implementation Guide...
Page 289 Example 6-35 Moving data from one volume to another move data 021akk stg=tapedata tsm: ATLANTIC> ANR2232W This command will move all of the data stored on volume 021AKK to other volumes within the same storage pool; the data will be inaccessible to users until the operation completes. Do you wish to proceed? (Yes (Y)/No (N)) y ANS8003I Process number 1 started.
Page 290: Querying Volume Contents
The information provided by query occupancy is only updated when an audit license command is run. If you have not run a license audit for some time, the results from query occupancy may not reflect reality. IBM Tivoli Storage Manager Implementation Guide...
Page 291: Rename A Storage Pool
Example 6-37 on page 261 shows the output from the query occupancy command. Example 6-37 Querying occupancy q occ tsm: ATLANTIC> Node Name Type Filespace FSID Storage Number of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) ---------- ---- ---------- ---- ---------- --------- --------- --------- PARIS...
Page 292: Reclamation
The tapes that are emptied by the reclamation process are returned to scratch status for reuse. See “Data Storage” in IBM Tivoli Storage Management Concepts, SG24-4877. Reclamation is usually scheduled during a period of low activity because it can be a very intensive operation, for both the server and the tape drives.
Page 293 5, PROCESS: 1) 03/02/2006 11:00:28 ANR4931I Reclamation process 1 started for copy storage pool OFFDATA manually, threshold=85, offsiteRclmLimit=No Limit, duration=30. (SESSION: 5, PROCESS: 1) 03/02/2006 11:00:28 ANR2753I (RECLAIM_OFFDATA):ANR2110I RECLAIM STGPOOL started as (SESSION: 5) 03/02/2006 11:00:28 ANR1040I Space reclamation started for volume 032AKK, storage pool OFFDATA (process number 1).
Page 294: Sql Commands
LIBVOLUMES OWNER VARCHAR Owner LIBVOLUMES LAST_USE VARCHAR Last Use LIBVOLUMES HOME_ELEMENT INTEGER Home Element LIBVOLUMES CLEANINGS_LEFT INTEGER Cleanings Left LIBVOLUMES DEVTYPE VARCHAR Device Type LIBVOLUMES MEDIATYPE INTEGER Media Type LIBVOLUMES OLD_STATUS VARCHAR Orig Status IBM Tivoli Storage Manager Implementation Guide...
Page 295 Note that the table name is a string literal (enclosed in single quotes). The name must be supplied as it is stored in syscat.tables (that is, in uppercase). If it was supplied in lowercase, no data would have been returned. You can generate you own custom queries and create your own commands by placing the queries into server scripts.
Page 296 4882 PIERRE 61853 Notice the warning that is displayed when a potentially complex or time-consuming or space-consuming query is issued. You can answer no if you prefer to run the query at another time. IBM Tivoli Storage Manager Implementation Guide...
Page 297: Summary
Example 4 Example 6-45 shows the volumes where a node has data stored and the storage pool that the volumes belong to. Example 6-45 Querying volume usage by node select distinct node_name, \ tsm: ATLANTIC> volume_name from volumeusage where node_name='PARIS' cont>...
Page 298 IBM Tivoli Storage Manager Implementation Guide...
Page 299: Chapter 7. Data Storage Policies
In this chapter we focus on the actual storage policy implementation. Before continuing, you should have already filled out the planning sheets, and we assume that you have read and understood the IBM Tivoli Storage Management Concepts, SG24-4877. We have now covered planning through installation and customizing your storage devices.
Page 300: Recommended Setup
Obviously, your environment will have specific data protection requirements that may differ from our setup. This is the purpose of the planning process. The provided values here may give you a reasonable starting point for later customizations. IBM Tivoli Storage Manager Implementation Guide...
Page 301: Sample Policy Definitions
In 1.1.1, “Our support material” on page 5, we show how to load a predefined macro into IBM Tivoli Storage Manager. The macro mac.policy, which we provide to define the recommended policy settings in our book environment, is shown in “Define policy structure”...
Page 302: Defining Policy Domains
SPECIAL: This management class is used to store files that are being modified during backup. An application log file could be bound to this IBM Tivoli Storage Manager Implementation Guide...
Page 303 (a tape storage pool, for example). HSM or Space Management clients (using IBM Tivoli Storage Manager for Space Management) are not covered in this book, but there is a Space Management parameter in the management class definition that we must change to avoid problems.
Page 304: Defining Backup Copy Groups
RETEXTRA: The WORKSTN domain only keeps extra inactive copies for 30 days, as compared to 100 days in the SERVER domain. RETONLY: The WORKSTN domain keeps the last copy of deleted data for 30 days, as compared to 100 days in the SERVER domain. IBM Tivoli Storage Manager Implementation Guide...
Page 305 Note: For expiration control of image backups, versions deleted (VERDEL) and retain only (RETONLY) settings do not apply. Image backups are controlled by the VEREXIST and RETEXTRA options only. Nevertheless, in our example we set the values of retver/retonly verexist/verdel the same for image both management classes to avoid confusion.
Page 306: Defining The Archive Copy Group
For the sample configuration, we define archive copy groups only for the default data management classes. The management class in the SERVER domain keeps archived objects for a year, while in the WORKSTN policy domain, IBM Tivoli Storage Manager Implementation Guide...
Page 307: Verifying Policy Definitions
archives are retained for 100 days (Example 7-5). Files that are changing during archiving are not stored. If it later turned out that we had additional archive requirements, for example, to keep certain files for seven years, we could easily define a suitable archive copy group in an existing or new management class.
Page 308: Archive Copy Groups
The commands are very straightforward and have few parameters. 7.3.1 Validating the recommended policy sets The validate policyset command checks for completeness in the management class and copy group definitions. It validates these policies and makes them ready for activation. IBM Tivoli Storage Manager Implementation Guide...
Page 309: Activating The Recommended Policy Sets
Example 7-8 shows how to validate the recommended policy sets. Example 7-8 Validating policy sets validate policyset server server tsm: ATLANTIC> ANR1515I Policy set SERVER validated in domain SERVER (ready for activation). validate policyset workstn workstn tsm: ATLANTIC> ANR1515I Policy set WORKSTN validated in domain WORKSTN (ready for activation). 7.3.2 Activating the recommended policy sets The activate policyset command makes specified policy active, as the controlling policy within its policy domain.
Page 310 DIOMEDE tsm: ATLANTIC> Do you wish to proceed? (Yes/No) y ANR2061I Node DIOMEDE removed from policy domain STANDARD. ANR2129I Administrative userid DIOMEDE defined ONLY for authority over node DIOMEDE has been removed. IBM Tivoli Storage Manager Implementation Guide...
Page 311 Moving a node The update node command can be used to assign a node to a new domain. The data is bound to the management classes in the new domain during the next backup operation. The process of assigning the data to the new domain’s management classes is called rebinding.
Page 312: Enforcing Your Policy
7.5 Summary We expect that you now understand and have configured the policies for your data retention. Next we discuss user management, to provide you with an understanding of administration roles within Tivoli Storage Manager. IBM Tivoli Storage Manager Implementation Guide...
Page 313: Chapter 8. Managing Tivoli Storage Manager
Managing Tivoli Storage Chapter 8. Manager This chapter explains the creation and maintenance of users of an IBM Tivoli Storage Manager system. © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 314: Management
8.1 Management Using the information you have gathered during the planning phase, as well as the understanding you have gained from reading IBM Tivoli Storage Management Concepts, SG24-4877, you should be able now define both users and clients on your Tivoli Storage Manager server.
Page 315: Considerations
8.1.2 Considerations Creating an administrator is a two-step process: 1. Define the administrator ID. 2. Grant the necessary privileges. The register admin command explicitly creates an administrator ID with certain defined privileges. If an administrator with the same name as the client node already exists during registration of a new node, then this administrator ID is automatically updated to grant owner access to it.
Page 316: Recommended Administrators
In 1.1.1, “Our support material” on page 5, we show how to load a predefined macro into Tivoli Storage Manager. The macro mac.admins, which we provide to define administrative IDs for our book environment, is shown in “Define administrators” on page 730. IBM Tivoli Storage Manager Implementation Guide...
Page 317 In Example 8-1, we define an administrator named TSMADMIN1 and a backup named TSMADMIN2. The initial password for both administrators is TOMAZ. We grant these IDs system privilege. Example 8-1 Commands to create an administrator register admin tsmadmin1 tomaz contact="IBM Tivoli Storage Manager tsm: ATLANTIC> Administrator" ANR2068I Administrator TSMADMIN1 registered.
Page 318: Working With Administrators
Storage Manager resources. In Example 8-3 we define a support administrator named REPORT. The initial password for this administrator is MIKE. Example 8-3 Creating a reporting ID register admin report mike contact="IBM Tivoli Storage Manager tsm: ATLANTIC> Reporting" ANR2068I Administrator REPORT registered.
Page 319 Last Access Date/Time: 02/07/2006 04:33:42 Days Since Last Access: <1 Password Set Date/Time: 02/07/2006 04:33:42 Days Since Password Set: <1 Invalid Sign-on Count: 0 Locked?: No Contact: IBM Tivoli Storage Manager Client Administrator System Privilege: Policy Privilege: Storage Privilege: Analyst Privilege: Operator Privilege:...
Page 320: Changing An Administrator Password
/: IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 2.0 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Enter your user id: tsmadmin1 Enter your password: Session established with server ATLANTIC: AIX-RS/6000 Server Version 5, Release 3, Level 2.2...
Page 321: Client Nodes
remove admin admin tsm: ATLANTIC> Do you wish to proceed? (Yes (Y)/No (N)) y ANR2069I Administrator ADMIN removed. Attention: You can remove administrators from the server so that they no longer have access to administrator functions, but you cannot remove the last administrator with system privileges and you cannot remove the administrator SERVER_CONSOLE.
Page 322: Default Environment
Table 8-1 shows a layout you can use for documenting the information needed to register the clients, completed with a set of sample client information. Table 8-1 Client requirements worksheet: example Node name Contact Domain PROPAGANDA Tomaz - First Floor SERVER LOSGATOS Aline - Second Floor WORKSTN IBM Tivoli Storage Manager Implementation Guide...
Page 323 Node name Contact Domain MILES Leilla - Help Desk SERVER Example 8-10 shows the commands to create these nodes. We give all nodes the same password, SHARKS. Example 8-10 Registering a client node register node propaganda sharks domain=server userid=none tsm: ATLANTIC> contact="TAL (Tomaz Aline Leilla)"...
Page 324 An administrator can perform all client operations on behalf of the user through the Web backup-archive client. The administrator needs node authority to perform those operations. An administrative user with system privilege can grant that authority. IBM Tivoli Storage Manager Implementation Guide...
Page 325 Last Access Date/Time: 02/07/2006 18:33:42 Days Since Last Access: <1 Password Set Date/Time: 02/07/2006 18:33:42 Days Since Password Set: <1 Invalid Sign-on Count: 0 Locked?: No Contact: IBM Tivoli Storage Manager Client Administrator System Privilege: Policy Privilege: Storage Privilege: Analyst Privilege: Operator Privilege:...
Page 326 ATLANTIC> Node Name Filespace FSID Platform Filespace Is Files- Capacity Name Type pace (MB) Util Unicode? -------- ---------- ---- -------- --------- --------- -------- ----- LOSGATOS JFS2 32.0 44.9 LOSGATOS /opt JFS2 128.0 76.1 IBM Tivoli Storage Manager Implementation Guide...
Page 327 In Example 8-17 we delete the file space /opt for the client LOSGATOS. Note that we are not deleting any files on the client itself—we are deleting all records of any files backed up or archived in that file system on the Tivoli Storage Manager server.
Page 328: Client Option Sets
However, you can specify that individual options in an option set cannot be overridden in the client’s local options file, using the FORCE=YES parameter when defining the option. IBM Tivoli Storage Manager Implementation Guide...
Page 329: Default Environment
Include-exclude rules If you put include-exclude statements in the client options set, these will always override the include-exclude statements in the client options file. You can imagine that the client options set include-exclude statements are added at the bottom of the client options file, so that they are evaluated first. The sequence number attached to each include-exclude statement in the client option set determines the order in which it is added to the existing include-exclude statements at the end of the client options file.
Page 330: Working With Client Option Sets
ANR2050I DEFINE CLIENTOPT: Option COMPRESSION defined in optionset WINDOWS. define clientopt windows maxcmdretries 4 tsm: ATLANTIC> ANR2050I DEFINE CLIENTOPT: Option MAXCMDRETRIES defined in optionset WINNT_LIST. define clientopt windows verbose '' tsm: ATLANTIC> ANR2050I DEFINE CLIENTOPT: Option VERBOSE defined in optionset WINDOWS. IBM Tivoli Storage Manager Implementation Guide...
Page 331: Associating A Client Node With A Client Option Set
Example 8-21 shows how to clone the client option set named WINDOWS to another named WINDOWS_CLONE, replacing the VERBOSE option with the QUIET option. Example 8-21 Copying client option sets copy cloptset windows windows_clone tsm: ATLANTIC> ANR2055I COPY CLOPTSET: Optionset WINDOWS copied to optionset WINDOWS_CLONE. delete clientopt windows_clone verbose tsm: ATLANTIC>...
Page 332: Summary
You have now established administrative roles within your Tivoli Storage Manager server, which will allow the control, monitoring, and management of the data flow from the clients through the final storage media. Next we discuss licensing options for your environment. IBM Tivoli Storage Manager Implementation Guide...
Page 333: Chapter 9. Licensing
Licensing Chapter 9. In this chapter we describe the tasks of licensing an IBM Tivoli Storage Manager system and monitoring its compliance. We discuss the process of registering, activating, and monitoring your licenses (but not the marketing or packaging of your licenses).
Page 334: Licensed Features
Table 9-1 lists all currently available licensed features you can add on to your base IBM Tivoli Storage Manager server license at V5.3 (for V5.2 options, see 9.6, “Tivoli Storage Manager V5.2 license features”...
Page 335: Registering Licensed Features
Tip: Tivoli Storage Manager V 5.3 and newer servers that have data retention protection enabled and have access to a Network Appliance or IBM N series filer with the SnapLock licensed feature (Data ONTAP 7.1 or later) can store data in storage pools with RECLAMATIONTYPE set to SNAPLOCK. Data created on volumes in these storage pools will be managed by a retention date.
Page 336: Saving Your Licenses
Manager V5.3. You now have far fewer options. You can register licenses for server components. This includes Tivoli Storage Manager (base), Tivoli Storage Manager Extended Edition, and IBM System Storage Archive Manager. You cannot register licenses for components that are licensed on...
Page 337: Monitoring Licenses
The server issues a warning message indicating that it is not in compliance with the licensing terms. Operations fail because the server is not licensed for specific features. In either case, you must contact your IBM account representative or authorized IBM Software reseller to modify your agreement. 9.5 Monitoring licenses...
Page 338: Auditing Licenses
Number of TDP for WAS in use: 0 Number of TDP for WAS in try buy mode: 0 Is IBM System Storage Archive Manager in use ?: No Is IBM System Storage Archive Manager licensed ?: No Is Tivoli Storage Manager Basic Edition in use: Yes...
Page 339: Tivoli Storage Manager V5.2 License Features
Tivoli Storage Manager V5.2. Table 9-2 Tivoli Storage Manager 5.2 licensed features Licensed feature License files Additional backup-archive clients: The base IBM Tivoli Storage xclient.lic Manager license supports one backup-archive client; Licensing additional clients with any number of clients (replace x with valid number of clients) IBM Tivoli Storage Manager for Space Management;...
Page 340 Licensed feature License files Managed libraries library.lic Library sharing libshare.lic IBM Tivoli Storage Manager for Applications; was.lic Tivoli Data Protection for WebSphere® Application Server IBM Tivoli Storage Manager for NDMP ndmp.lic Managed System for SAN use mgsyssan.lic Managed System for LAN use mgsyslan.lic...
Page 341: Chapter 10. Administrative Client
IBM Tivoli Storage Manager servers and resources. Various graphical interfaces (GUIs) on different versions have also been available. For details on ISC and Administration Center setup, refer to IBM Tivoli Storage Manager Version 5.3 Technical Guide, SG24-6638. © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 342: Administration Center
Both products, Administration Center and Integrated Solutions Console, are distributed separately. ISC is available via regular system order, while the Administration Center is available via the normal IBM service FTP site. To install: 1. Install the ISC. 2. Install the Administration Center into ISC.
Page 343: Administration Center Interface
IBM Tivoli Storage Manager Administration Center Readme. 10.1.2 Administration Center interface To access the Administration Center, type http://<machine_name>:<port>/ibm.console in your browser, as shown in Figure 10-1. We installed the ISC and Administration center on the system DIOMEDE.
Page 344: Administration Interface Welcome Window
Health Monitor: This assists you with determining the overall status of server operations; helps you to obtain detailed information about client node schedules, the server database and recovery log, and the status of storage IBM Tivoli Storage Manager Implementation Guide...
Page 345 devices managed by the server. The Health Monitor also provides access to the server activity log, so you can view messages generated during server operations. Disaster Recovery Management : If your servers are licensed for Tivoli Storage Manager Extended Edition, you can use this function to automatically generate a disaster recovery plan and track media.
Page 346: Administrative Client
10.2 Administrative client Now we consider the Tivoli Storage Manager administrative client, which provides a command-line interface (CLI) to a Tivoli Storage Manager server. We IBM Tivoli Storage Manager Implementation Guide...
Page 347: Code Installation
explain how to install a Tivoli Storage Manager administrative client and tell you what options to configure. Some examples of the interfaces for various types of access are also included. The command-line administrative client is a tool that looks and operates the same on all supported platforms.
Page 348: Administrative Command-Line Client Customization
Client options for the administrative client are set in the client options files. Assuming a TCP/IP communications method, the only required option is the TCPSERVERADDRESS. We recommend using a DNS name instead of the dotted IP address for the TCPSERVERADDRESS. A dotted IP address is IBM Tivoli Storage Manager Implementation Guide...
Page 349 inflexible, because it creates management issues if the Tivoli Storage Manager server is moved or the addressing scheme is changed. Other useful parameters include the date, time, number, and language format options. Note that UNIX and Linux clients require the additional SERVERNAME stanza in their options files. When the TCPSERVERADDRESS option is set, the client will attempt to connect at the default TCP/IP port, 1500.
Page 350: Command-Line Interface
C:\Documents and Settings\Administrator>dsmadmc IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 2.0 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Enter your user id: admin Enter your password: ***** Session established with server ATLANTIC: AIX-RS/6000 Server Version 5, Release 3, Level 2.2...
Page 351 /: dsmadmc IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 2.0 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Enter your user id: admin Enter your password: Session established with server ATLANTIC: AIX-RS/6000 Server Version 5, Release 3, Level 2.2...
Page 352 C:\>dsmadmc -consolemode IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 2.0 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Enter your user id: admin Enter your password: ***** Session established with server ATLANTIC: AIX-RS/6000 Server Version 5, Release 3, Level 2.2...
Page 353: Summary
Tivoli Storage Manager server instances. You may build automated scripts that ease administration tasks or provide comprehensive monitoring outputs. For detailed information about dsmadmc command arguments, syntax, and features, see the IBM Tivoli Storage Manager Administrator’s Reference for your server platform. 10.3 Summary You should now understand what tasks are possible using the administrative client interfaces.
Page 354 IBM Tivoli Storage Manager Implementation Guide...
Page 355: Part 3. Operational Details
We also include more advanced operational tasks, such as server-to-server exporting, setting up Tivoli Storage Manager to send Tivoli Enterprise Console® alerts, and a rather lengthy section on performance. © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 356 IBM Tivoli Storage Manager Implementation Guide...
Page 357: Chapter 11. Client Operations
Sample commands are given for both UNIX and Windows platforms. For more information about client operations, see the IBM Tivoli Storage Manager Backup-Archive Client Installation and User’s Guide for the appropriate platform.
Page 358: Running Backup Operations
Journal-based backup is supported on Windows and AIX (at V5.3.3.0 and later) clients. If the journal engine service is installed and running, then by default, incremental backups will automatically perform journal-based backup on the selected file systems that are monitored by the journal engine service. IBM Tivoli Storage Manager Implementation Guide...
Page 359 Table 11-1 gives examples of backup operations using a UNIX backup-archive client. Table 11-1 Backup command examples: UNIX If you want to perform this operation..then this is the client command: Incremental backup of the client domain dsmc incremental Incremental backup of a file system dsmc incremental /home/ (/home)
Page 360 (for example, INCLUDE C:\WORK\*, EXCLUDE D:\TEMP\*) to avoid potential hard-to-diagnose problems, unless you have a specific requirement for files with dots in their names. The next example illustrates the relationship between wildcards in the INCLUDE/EXCLUDE statements and backup commands. IBM Tivoli Storage Manager Implementation Guide...
Page 361: Exclude Rules Preventing Some Files From Being Backed Up
Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 2.0 Client date/time: 02/20/2006 14:13:12 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Node Name: TSM_CLIENT_DEMO Session established with server LOCHNESS_SERVER1: Windows Server Version 5, Release 3, Level 2.2 Server date/time: 02/20/2006 14:13:47 Last access: 02/20/2006 14:12:56 Incremental backup of volume 'c:\tsm\*.*'...
Page 362 Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 2.0 Client date/time: 02/20/2006 14:15:15 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Node Name: TSM_CLIENT_DEMO Session established with server LOCHNESS_SERVER1: Windows Server Version 5, Release 3, Level 2.2...
Page 363: Unix Command-Line Examples And Output
Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 2.0 Client date/time: 02/20/06 15:17:55 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Node Name: ATLANTIC Session established with server LOCHNESS_SERVER1: Windows Server Version 5, Release 3, Level 2.2...
Page 364 /tsm: IBM Tivoli Storage Manager Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 2.0 Client date/time: 02/20/06 15:20:47 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. IBM Tivoli Storage Manager Implementation Guide...
Page 365 (/dev/tsm) when trying to use the backup image function on a defined JFS file system. Example 11-6 UNIX raw logical volume backup lsfs testlv00 root@Atlantic /tsm: lsfs: 0506-915 No record matching /tsm/testlv00 was found in /etc/filesystems. dsmc backup image /dev/testlv00 root@Atlantic /tsm: IBM Tivoli Storage Manager Chapter 11. Client operations...
Page 366 Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 2.0 Client date/time: 02/20/06 15:39:25 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Node Name: ATLANTIC Session established with server LOCHNESS_SERVER1: Windows Server Version 5, Release 3, Level 2.2...
Page 367 Backup Image Function Invoked. ANS1063E The specified path is not a valid file system or logical volume name. Group backup Example 11-7, Example 11-8, and Example 11-9 on page 339 show examples of commands related to and including the backup group command. Example 11-7 shows the output of the query filespace command.
Page 368 Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 2.0 Client date/time: 02/20/2006 17:40:02 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Node Name: ATLANTIC Session established with server LOCHNESS_SERVER1: Windows Server Version 5, Release 3, Level 2.2 Server date/time: 02/20/2006 17:39:19 Last access: 02/20/2006 17:16:08 Backup GROUP function invoked mode= FULL.
Page 369 Network data transfer rate: 11,954.42 KB/sec Aggregate data transfer rate: 3,551.03 KB/sec Objects compressed by: Elapsed processing time: 00:00:02 Example 11-9 is on the Tivoli Storage Manager server. It shows that a new file space is created, /tsmresidentfs, after completion of the backup group command. Notice that the file space type is TSMVFS.
Page 370 A /tsmresidents/usr/tivo li/tsm 256 B 02/20/2006 16:13:45 DEFAULT A /tsmresidents/usr/tivo li/tsm/client 256 B 02/20/2006 16:13:45 DEFAULT A /tsmresidents/usr/tivo li/tsm/client/ba 4,096 B 02/20/2006 16:13:45 DEFAULT A /tsmresidents/usr/tivo li/tsm/client/ba/bin 656 B 02/20/2006 16:13:45 DEFAULT A /tsmresidents/usr/tivo li/tsm/client/ba/bin/dsm.opt IBM Tivoli Storage Manager Implementation Guide...
Page 371 Create backup set Backup sets are created using a Tivoli Storage Manager server command, rather than via the backup-archive client. The generated backup set can be stored in a file or on sequential storage. In Example 11-11 we create a backup set of the client file space /TS onto disk storage, using a FILE device class.
Page 372: Windows Gui Backup Examples
Therefore, the first time you use the estimated Tivoli Storage Manager client and run the estimate function, the transfer time is grayed out, since there is no previous data to refer to. IBM Tivoli Storage Manager Implementation Guide...
Page 373: Estimate Function
Figure 11-2 Estimate function After the backup operation is complete, a status report similar to Figure 11-3 displays. This report contains data such as the total amount of files backed up and the transfer rate during the backup operation. The View button is available only if there errors were encountered during the operation.
Page 374: Additional Backup Options For Windows
Tivoli Storage Manager GUI. We recommend that you perform a full backup of all the components of the system object at the same time so that it is in a consistent state. IBM Tivoli Storage Manager Implementation Guide...
Page 375: Running Restore Operations
Figure 11-4 Windows 2000 system object backup 11.2 Running restore operations To restore a file, a directory, or even the whole machine, you need to know two what when things: you want to restore (file name, directory), and, optionally, from (point-in-time), if you want to restore a file version other than the most recent one.
Page 376 (or any copy of a file that no longer exists on the client), and an expired file copy is a copy to be removed from the Tivoli Storage Manager server. Only active versions are presented for restore unless you use the INACTIVE or IBM Tivoli Storage Manager Implementation Guide...
Page 377 LATEST options. The INACTIVE option instructs Tivoli Storage Manager to display and restore an inactive backup if an active one is not available, and the LATEST option restores the most recent backup version of a file, even if that backup is inactive. You cannot restore an expired file version. Table 11-3 gives some examples of restore operations using a UNIX backup-archive client.
Page 378: Unix Command-Line Examples And Output
256 /TS/charlotte [Done] Restoring 256 /TS/eduardo [Done] Restoring 256 /TS/lost+found [Done] Restoring 256 /TS/martin [Done] Restoring 4,096 /TS/norbert [Done] Restoring 256 /TS/peter [Done] Restoring 4,096 /TS/sys [Done] Restoring 1,048,576 /TS/charlotte/data1 [Done] Restoring 1,048,576 /TS/charlotte/data2 [Done] IBM Tivoli Storage Manager Implementation Guide...
Page 379 Restoring 1,048,576 /TS/charlotte/data3 [Done] Restoring 1,048,576 /TS/eduardo/data1 [Done] Restoring 1,048,576 /TS/eduardo/data2 [Done] Restoring 1,048,576 /TS/eduardo/data3 [Done] Restoring 1,048,576 /TS/martin/data1 [Done] Restoring 1,048,576 /TS/martin/data2 [Done] Restoring 1,048,576 /TS/martin/data3 [Done] Restoring 1,048,576 /TS/norbert/data1 [Done] Restoring 1,048,576 /TS/norbert/data2 [Done] Restoring 1,048,576 /TS/norbert/data3 [Done] Restoring 1,048,576 /TS/peter/data1 [Done] Restoring...
Page 380 Restore function invoked. ANS1247I Waiting for files from the server... Restoring 256 /TS/charlotte [Done] Restoring 256 /TS/eduardo [Done] Restoring 256 /TS/lost+found [Done] Restoring 256 /TS/martin [Done] Restoring 4,096 /TS/norbert [Done] Restoring 256 /TS/peter [Done] IBM Tivoli Storage Manager Implementation Guide...
Page 381 Restoring 4,096 /TS/sys [Done] Restoring 1,048,576 /TS/charlotte/data1 [Done] Restoring 1,048,576 /TS/charlotte/data2 [Done] Restoring 1,048,576 /TS/charlotte/data3 [Done] Restoring 1,048,576 /TS/eduardo/data1 [Done] Restoring 1,048,576 /TS/eduardo/data2 [Done] Restoring 1,048,576 /TS/eduardo/data3 [Done] Restoring 1,048,576 /TS/martin/data1 [Done] Restoring 1,048,576 /TS/martin/data2 [Done] Restoring 1,048,576 /TS/martin/data3 [Done] Restoring 1,048,576 /TS/norbert/data1 [Done] Restoring...
Page 382 Example 11-18 Restore group command restore group /tsmresidentfs/* -pick -showmembers tsm> IBM Tivoli Storage Manager Scrollable PICK Window - Restore Group Backup Date/Time File Size A/I Type Group ----------------------------------------------------------------------- 1.
Page 383 residentgrp Example 11-19 shows the contents of the group and the output of the restore. From the pick window, you may choose the specific file that you want to restore. In the example, we chose to restore the file data1 in the directory /home/guest.
Page 384: Windows Gui Restore Examples
Java or Web client—the look and feel is almost identical. You may select specific files, directories, or complete drives to restore. To restore inactive files, select Display inactive/active files from the view menu. Figure 11-5 Windows restore GUI IBM Tivoli Storage Manager Implementation Guide...
Page 385 The estimate function, as described in 11.1.3, “Windows GUI backup examples” on page 342, is also available when doing a restore operation. You can also choose to do a point-in-time restore if you do not want to restore the latest backup or if you want to restore files backed up on a specific date.
Page 386 You can specify other restore options, such as to prompt when a file with the same name is present in the destination path, or to restore files or folders only from the source path. Figure 11-7 shows the restore options window. Figure 11-7 Restore options IBM Tivoli Storage Manager Implementation Guide...
Page 387 After choosing the files, directories, or drives you want to restore, you will be prompted for the destination of the restore operation, as shown in Figure 11-8. You can select to restore the files you selected in the original path or to a different directory or drive.
Page 388: Restore Report
A detailed report is available after the restore operation, as in Figure 11-9 on page 358. If there were errors during the restore, click the View button to see the details. Figure 11-9 Restore report IBM Tivoli Storage Manager Implementation Guide...
Page 389: Running Archive Operations
For Windows users, you can restore the system object using the GUI, as shown in Figure 11-10 on page 359. We recommend that you restore the components of the system object together to make sure that the system state is consistent after the restore operation.
Page 390 Create a new archive package called dsmc archive /home/ -subdir=yes "PEBBLES-FILES" from a directory -description="PEBBLES-FILES" (/home). Add files from a directory (/temp) to an dsmc archive /temp/ -subdir=yes archive package called -description="PEBBLES-FILES" "PEBBLES-FILES". IBM Tivoli Storage Manager Implementation Guide...
Page 391: Unix Command-Line Examples And Output
Table 11-6 gives examples of archive operations using a Windows backup-archive client. Table 11-6 Archive command examples: Windows If you want to perform this operation..then this is the client command Archive all files from a directory (c:\tsm). dsmc archive c:\tsm\ -subdir=yes Archive files from different directories dsmc archive c:\tsm\ c:\temp\ (c:\tsm and c:\temp).
Page 392 Total number of objects failed: Total number of bytes transferred: 15.07 MB Data transfer time: 1.29 sec Network data transfer rate: 11,933.99 KB/sec Aggregate data transfer rate: 7,672.37 KB/sec Objects compressed by: Elapsed processing time: 00:00:02 tsm> IBM Tivoli Storage Manager Implementation Guide...
Page 393: Windows Gui Archive Examples
11.3.2 Windows GUI archive examples Figure 11-11 on page 363 shows the archive GUI on Windows. On other platforms, use the Java or Web client—the look and feel is almost identical. You may enter your own description for the files you want to archive. If you do not enter one, by default, the description will be the date the archive was made.
Page 394 If you do not specify a management class, the archive operation will use the archive copy group in the default management class. You can also specify to delete the files from the client system after they are successfully archived. Figure 11-12 Archive options IBM Tivoli Storage Manager Implementation Guide...
Page 395: Running Retrieve Operations
A detailed report similar to Figure 11-13 is available for viewing. It will show the archive statistics and the errors encountered, if any. Figure 11-13 Archive report 11.4 Running retrieve operations The retrieve command obtains copies of archived files from the Tivoli Storage Manager server.
Page 396: Unix Command-Line Examples And Output
256 /TS/eduardo [Done] Retrieving 1,048,576 /TS/eduardo/data1 [Done] Retrieving 1,048,576 /TS/eduardo/data2 [Done] Retrieving 1,048,576 /TS/eduardo/data3 [Done] Retrieve processing finished. Total number of objects retrieved: Total number of objects failed: Total number of bytes transferred: 3.00 MB IBM Tivoli Storage Manager Implementation Guide...
Page 397: Windows Gui Retrieve Examples
Data transfer time: 1.66 sec Network data transfer rate: 1,846.62 KB/sec Aggregate data transfer rate: 1,015.30 KB/sec Elapsed processing time: 00:00:03 tsm> 11.4.2 Windows GUI retrieve examples Figure 11-14 on page 367 shows the Tivoli Storage Manager retrieve GUI (Windows). On other platforms, use the Java or Web client. You can choose to retrieve specific files within an archive package or you can retrieve the whole archive package.
Page 398 You can specify retrieve options similar to restore options, as shown in Figure 11-15. You can choose to overwrite files without prompting you or to retrieve files or directories only from the package you selected. Figure 11-15 Retrieve options IBM Tivoli Storage Manager Implementation Guide...
Page 399 Once you have chosen the files or package you want to archive, you will be prompted for the destination of the retrieve operation, as shown in Figure 11-16. You may choose to retrieve the files back to their original location or to a different path.
Page 400: Summary
You are now familiar with the client operations, such as backup, restore, archive, and retrieve. The client command line and graphical interfaces were also discussed in this chapter. The next chapter covers the administrative and client scheduling. IBM Tivoli Storage Manager Implementation Guide...
Page 401: Chapter 12. Scheduling
Scheduling Chapter 12. Scheduling is at the core of efficient IBM Tivoli Storage Manager operations. Having a comprehensive and integrated set of schedules allows the server to run with very little intervention during normal operational periods. IBM Tivoli Storage Manager scheduling is divided into two categories: administrative scheduling and client scheduling.
Page 402 Introduced with IBM Tivoli Storage Manager Version 5.3 are different Classic schedules. Both client and administrative schedules can now be either Enhanced .
Page 403: The Wheel Of Life
12.1 The wheel of life Figure 12-1 on page 374 shows the recommended series of operations that should occur in a Tivoli Storage Manager environment and the sequence in which those operations should occur. The actual start time and duration of the various operations depend on your scheduling requirements.
Page 404: Administrative Schedules
As each administrative schedule can only run one server command, the command itself may be a command, that runs an internally defined server script containing other internal server commands. IBM Tivoli Storage Manager Implementation Guide...
Page 405 Example 12-1 shows the syntax to define an administrative schedule named DB_BACKUP for a full database backup starting at 7 a.m. every morning. Example 12-1 Defining an administrative schedule define schedule db_backup type=administrative cmd="backup db tsm: ATLANTIC> devc=lto2-dc type=full" starttime=07:00 active=yes description="Daily Database Backup"...
Page 406 Task 5 12.2.3, storage pools for from complete “Defining a next backup DISKDATA migration window. schedule” on TAPEDATA. page 382 Database space Expire None 12.2.4, management. inventory. “Defining an expiration schedule” on page 382 IBM Tivoli Storage Manager Implementation Guide...
Page 407: Defining An Off-Site Backup Schedule
Function Task Duration Task Refer to (hrs) dependency Defragment tape Reclaim None 12.2.5, volumes in volumes “Defining a sequential storage from reclamation pools. OFFDIRS. schedule” on page 383 Reclaim None volumes from OFFDATA. Reclaim None volumes from TAPEDATA. Enable statistics. Audit 0.25 None...
Page 408 “Define server scripts” on page 737. Example 12-3 Contents of “REDBOOK_OFFSITE” script /*--------------------------------------------*/ /* Script Name: REDBOOK_OFFSITE /* Description: Back up all primary storage */ IBM Tivoli Storage Manager Implementation Guide...
Page 409 pools, followed by the database. If there are active node sessions, reschedule to run again in */ 20 minutes The script will back up three storage pools named diskdirs, diskdata and tapedata to copypools named */ offdata and offdirs. /* Example: run redbook_offsite /* -----------------------------------------*/ select * from sessions where - upper(session_type)='NODE'...
Page 410: Defining The Volume History Schedules
When you back up the database, the previous database backups become obsolete. However, it is wise to save the older backup for a short time before returning them to scratch volume status for reuse. DRM will take care of IBM Tivoli Storage Manager Implementation Guide...
Page 411 database backup expiry, but if you have not licensed it, you must delete the volume history yourself. Use the delete volhistory command to do this. We recommend deleting any database backups that are older than seven days. The delete volhistory command will never delete the current database backup, so we use “today-6”...
Page 412: Defining A Migration Schedule
The client backup process handles half of the task by marking expired data references while backing up client data. The second half of the task is handled by the expire inventory command, which physically removes the marked entries from the database. IBM Tivoli Storage Manager Implementation Guide...
Page 413: Defining A Reclamation Schedule
The tapes that are emptied by the reclamation process are returned to scratch status for reuse. See “Data Storage” in IBM Tivoli Storage Management Concepts, SG24-4877. We recommend controlling when the reclamation process runs using a schedule that sets and resets the reclamation threshold for each storage pool.
Page 414 ANR2577I Schedule RECLAIM_TAPEDATA defined. q sched reclaim* t=a tsm: LOCHNESS_SERVER1> * Schedule Name Start Date/Time Duration Period - ---------------- -------------------- -------- ------ RECLAIM_OFFDATA 02/21/2006 12:00:00 RECLAIM_OFFDIRS 02/21/2006 11:00:00 RECLAIM_TAPEDATA 02/21/2006 15:00:00 IBM Tivoli Storage Manager Implementation Guide...
Page 415: Defining A Licensing Audit Schedule
12.2.6 Defining a licensing audit schedule Occasionally, you may wish to check storage statistics for your clients, that is, how much data the clients are storing on the server, and what type of data that is. The query auditoccupancy command provides information about client data usage, as shown in Example 12-11.
Page 416: Querying Administrative Events
Manager clients. It differs from an administrative schedule in that it specifies that an action be performed on the Tivoli Storage Manager client. The client scheduling system consists of a server portion and a client portion. The server IBM Tivoli Storage Manager Implementation Guide...
Page 417: Defining A Client Backup Schedule
The client scheduler is a separate process on the Tivoli Storage Manager client and provides communication between the server and client. See “Scheduling” in IBM Tivoli Storage Management Concepts, SG24-4877, for further information about the client portion of the client scheduling system.
Page 418: Defining An Enhanced Client Schedule
If we omit the SCHEDStyle, is assumed. 12.3.2 Defining an enhanced client schedule An enhanced client schedule performs the same actions as a classic client schedule, but allows you to be more specific with repetition intervals. IBM Tivoli Storage Manager Implementation Guide...
Page 419 Before Tivoli Storage Manager V5.3, there were limited options for setting the repetition parameters. You could not, for example, schedule a backup to run on the first Wednesday of each month—with enhanced schedules, you can. We wish to schedule an image backup of the C drive of our Windows workstations on the last Friday of every month, at 1 a.m.
Page 420: Enhanced Schedule Repetition, Day Of Week, Isc Panel
Figure 12-2 and Figure 12-3 show the corresponding panels from the Administration Center, selecting the day of week and week of the month. Figure 12-2 Enhanced schedule repetition, day of week, ISC panel Figure 12-3 Enhanced schedule, week of month, ISC panel IBM Tivoli Storage Manager Implementation Guide...
Page 421: Associating A Client With A Schedule
12.3.3 Associating a client with a schedule Once the schedule is defined, we need to specify which client nodes will run it. The define association command forms the link between the schedule and the node. Nodes are associated to schedules within their own domain. A node must be registered on the server before defining an association for it, but it does not necessarily have to be in contact with the server.
Page 422: Verifying The Client Schedules
Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 2.0 Client date/time: 02/21/2006 14:43:21 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Node Name: PIERRE Session established with server LOCHNESS_SERVER1: Windows Server Version 5, Release 3, Level 2.2...
Page 423 Week of Month: Expire: Never quit tsm> Chapter 12. Scheduling...
Page 424 IBM Tivoli Storage Manager Implementation Guide...
Page 425: Chapter 13. Routine Tasks
Routine tasks Chapter 13. IBM Tivoli Storage Manager, like any other software system, has to be maintained and operated in order to check that the tasks that are implemented are still working. To accomplish this, you may need to consider how many people will be dedicated to Tivoli Storage Manager.
Page 426: Operations Staff
IBM Tivoli Storage Manager Implementation Guide...
Page 427: Server Procedures
13.2 Server procedures In this section we show how to start and stop a Tivoli Storage Manager server. Tivoli Storage Manager is essentially a software program that runs as any other application in your system. This means that you can start the server and let it run continuously and uninterrupted for days, weeks, or even longer if desired.
Page 428 ANR2560I Schedule manager started. ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use. ANR2828I Server is licensed to support IBM System Storage Archive Manager. ANR2828I Server is licensed to support Tivoli Storage Manager Basic Edition. ANR2828I Server is licensed to support Tivoli Storage Manager Extended Edition.
Page 429: Tivoli Storage Manager Management Monitor Option
On Windows systems, you can also start the server in active console mode from the Tivoli Storage Manager server utilities program. Figure 13-1 shows the main Tivoli Storage Manager server utilities screen and the Launch option to start Tivoli Storage Manager in console mode. Figure 13-1 Tivoli Storage Manager management monitor option Background mode You can start the Tivoli Storage Manager server in the background, either...
Page 430 IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 2.0 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Session established with server TSM: AIX-RS/6000 Server Version 5, Release 3, Level 2.2...
Page 431: Stopping The Tivoli Storage Manager Server
Note: We recommend that you create a specific analyst administrator for this purpose so that it can only query the server. 13.2.2 Stopping the Tivoli Storage Manager server There are two ways of stopping a Tivoli Storage Manager server: Immediate stop: This brings the server down immediately. All system processes and client activity are interrupted.
Page 432 Example 13-6 Query session query session tsm: ATLANTIC> Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method State Time Sent Recvd Type ------ ------ ------ ------ ------- ------- ----- -------- --------- IBM Tivoli Storage Manager Implementation Guide...
Page 433 Tcp/Ip 261.6 K 2.3 K Admin TSMADMIN Tcp/Ip IdleW 1.1 M Node ATLANTIC Tcp/Ip RecvW 191.2 M Node ATLANTIC Tcp/Ip IdleW 10 S 1,023 1.3 K Node ATLANTIC Tcp/Ip RecvW 492.3 M Node ATLANTIC 3. Notify users: Notify any existing administrative and client node sessions that you plan to shut down the server.
Page 434: Event Monitoring
For example, prefix ANR is for server messages, and most of prefix ANS messages are from backup-archive client sessions. Details of all these messages are explained in IBM Tivoli Storage Manager Messages, GC35-0382. You can enable or disable messages for any particular receiver, except for one—you cannot disable server events from being sent to the server activity log.
Page 435: Event Receivers
The Tivoli Storage Manager activity log helps the administrator track server activity and monitor the system. The activity log contains messages generated by the server and is stored in the database. All messages sent to the server console are stored in the activity log. Examples of the types of messages stored in the activity log include: When client sessions start or end When migration starts or ends...
Page 436 Note that enabling client events to the activity log will increase the Tivoli Storage Manager database utilization. You can set a retention period for the log records by using the set actlogretention command. IBM Tivoli Storage Manager Implementation Guide...
Page 437: Health Monitoring
To enable a specific receiver (such as CONSOLE, ACTLOG, EVENTSERVER, FILE, FILETEXT, SNMP, TIVOLI, USEREXIT) use the enable events command, as shown in Example 13-11. Example 13-11 Enable events command enable events actlog all nodename=* tsm: ATLANTIC> ANR1844I ENABLE EVENTS command processed Tip for Windows: Windows also has the EVENTLOG receiver, which sends events to the application eventlog so that you can use the Windows Event Viewer to monitor a Tivoli Storage Manager system.
Page 438: Enabling The Admin_Center Account
Server Properties, as shown in Figure 13-2. 2. In the Server Properties portlet, select Administrators, and check the box next to the ADMIN_CENTER account. Figure 13-2 Server Properties view showing Administrators 3. Select Modify Administrator from the menu. IBM Tivoli Storage Manager Implementation Guide...
Page 439: Using Health Monitoring
4. Update the password if necessary and ensure that the Lock check box is checked, as shown in Figure 13-3. Figure 13-3 ADMIN_CENTER account update pwd and Lock box unchecked 13.4.2 Using Health Monitoring Using the Health Monitor, you get an overall view of how the servers and their storage devices are running.
Page 440 1. Open the Administration Center in the ISC. 2. Click Health Monitoring in the navigation tree. 3. Select Configure Health Monitoring from the menu in the Health Monitor portlet, as shown in Figure 13-4. Figure 13-4 Health monitor menu selection IBM Tivoli Storage Manager Implementation Guide...
Page 441 4. Enter the password and refresh interval to enable the Health Monitor, as shown in Figure 13-5. Click OK to complete. Figure 13-5 Defining the Health Monitor password and refresh interval 5. To display the status of a Tivoli Storage Manager Server, click Health Monitor in the navigation tree.
Page 442: Operational Reporting
Storage Manager for Windows server and is also available as a stand-alone package for a Windows server. For information about installing the stand-alone package, see “Installing the IBM Tivoli Storage Manager Operational Reporting Stand-alone Package” in the IBM Tivoli Storage Manager for Windows Administrator’s Guide.
Page 443 Operational Reporting can write data to a file that can be read by a TEC log file adapter. The log file adapter reads the information and forwards it to the Tivoli Enterprise Console. For more information about Operational Reporting, see IBM Tivoli Storage Manager Version 5.3 Technical Guide, SG24-6638.
Page 444: Daily Sanity Checks
--------- -------- --------- --------- ------- --------- --------- ----- ----- 1,024 1,024 4,096 262,144 9,409 query db format=detail tsm: ATLANTIC> Available Space (MB): 1,024 Assigned Capacity (MB): 1,024 Maximum Extension (MB): 0 Maximum Reduction (MB): 992 Page Size (bytes): 4,096 IBM Tivoli Storage Manager Implementation Guide...
Page 445 Total Usable Pages: 262,144 Used Pages: 8,361 Pct Util: 3.2 Max. Pct Util: 3.2 Physical Volumes: 2 Buffer Pool Pages: 131,072 Total Buffer Requests: 1,964 Cache Hit Pct.: 84.83 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 29.43 Percentage Changed: 90.10...
Page 446 Example 13-16. Example 13-16 Using the volume history for information about sequential volumes query volhistory tsm: ATLANTIC> Date/Time: 02/24/2006 09:24:26 Volume Type: STGNEW Backup Series: IBM Tivoli Storage Manager Implementation Guide...
Page 447: Data Storage
Backup Operation: Volume Seq: Device Class: LTO2-DC Volume Name: 022AKK Volume Location: Command: Date/Time: 02/24/2006 09:28:21 Volume Type: STGNEW Backup Series: Backup Operation: Volume Seq: Device Class: LTO2-DC Volume Name: 023AKK Volume Location: Command: Date/Time: 02/24/2006 16:55:36 Volume Type: STGNEW Backup Series: Backup Operation: Volume Seq:...
Page 448 Element Type ------------ ----------- ---------- ---------- --------- ------- ------ 3582_SHARED 020AKK Private ATLANTIC Data 4,096 3582_SHARED 021AKK Scratch 4,097 3582_SHARED 026AKK Scratch 4,102 3582_SHARED 027AKK Scratch 4,116 3582_SHARED 028AKK Scratch 4,104 3582_SHARED 029AKK Scratch 4,103 IBM Tivoli Storage Manager Implementation Guide...
Page 449 3582_SHARED 030AKK Scratch 4,106 3582_SHARED 031AKK Scratch 4,107 3582_SHARED 038AKK Scratch 4,114 3582_SHARED 039AKK Scratch 4,115 Number of scratch tapes You can use an SQL query to display the number of scratch tapes available in the library, as shown in Example 13-20. You want to be sure not to run out of scratch tapes, or backup and migration operations may fail.
Page 450 Mig Mig ge Pool Pct Pct ----------- ---------- ---------- ----- ----- ---- --- ----------- DISKDATA DISK 12 G 56.7 56.7 30 TAPEDATA DISKFILE SEQF-DC 0.0 M 70 TAPEDATA NONE DISK 0.0 M OFFDATA LTO2-DC 409,600,0- 00 G IBM Tivoli Storage Manager Implementation Guide...
Page 451: Client-Server Activity
OFFDIRS LTO2-DC 0.0 M TAPEDATA LTO2-DC 409,600,0- 00 G TAPEDATA_LF LTO2C 0.0 M Query one or more storage pool volumes Use the query volume command to display information about one or more storage pool volumes, as shown in Example 13-25. This command displays information about volumes defined to Tivoli Storage Manager.
Page 452 Date/Time Message -------------------- ---------------------------------------------------------- 02/27/2006 08:33:01 ANR0568W Session 51 for admin ADMIN (AIX) terminated - connection with client severed. (SESSION: 51) 02/27/2006 08:33:13 ANR8216W Error sending data on socket 22. Reason 32. (SESSION: 276) IBM Tivoli Storage Manager Implementation Guide...
Page 453 02/27/2006 08:43:27 ANR2121W ATTENTION: More than 28 MB of the database has changed and the last database backup was more than 24 hours ago. Use the BACKUP DB command to provide for database recovery. 02/27/2006 09:09:55 ANR8925W Drive DR00 in library 3582_SHARED has not been confirmed for use by server STA_DIOMEDE for over 900 seconds.
Page 454 This can save valuable time because these restore operations do not have to return to the beginning of the operation. The query restore command displays the restartable restore sessions. IBM Tivoli Storage Manager Implementation Guide...
Page 455 2. Restartable restore sessions lock the file space and do not allow files to be moved off of sequential volumes. The query restore command displays the restartable restore sessions and their associated file space, as shown in Example 13-31. The cancel restore command can be used to cancel a restartable restore session.
Page 456: Storage Media Management
– Movement and deletion of file spaces by an administrator. – Automatic reclamation of media. The amount of data on the volume and the reclamation threshold set for the storage pool affects when the volume IBM Tivoli Storage Manager Implementation Guide...
Page 457 is reclaimed. When the volume is reclaimed, any valid, unexpired data is moved to other volumes or possibly to another storage pool (for storage pools with single-drive libraries). When a volume becomes empty because all valid data either expires or is moved to another volume, the volume is available for reuse.
Page 458: Label And Check In Tapes
Whether to search an automated library for volumes for labeling How to assign the labels: – To prompt for volume names in SCSI libraries – To read and use the barcode label in SCSI, 349X, and ACSLS libraries IBM Tivoli Storage Manager Implementation Guide...
Page 459 Whether to check in the volume to the scratch pool or as a private volume The type of device (applies to 349X libraries only) Depending on the library that you have (349x, SCSI, or MANUAL), the command syntax may be slightly different. For further details, type: help label libvolume The label libvolume command requires at least one drive that is not in use by any other Tivoli Storage Manager process.
Page 460: On-Site And Off-Site Tape Management
Recovery Manager” on page 589. We simply summarize the process here. The distinction between on-site data and off-site data copies is a key component to successfully handling many tape management procedures and one of the key concepts for Tivoli Storage Manager. IBM Tivoli Storage Manager Implementation Guide...
Page 461: On-Site And Off-Site Distinction
For our discussion we assume that all data that is available in the company is on-site data. All data that is remotely stored in another location is off-site data. Figure 13-9 shows on-site and off-site tape volumes. Figure 13-9 On-site and off-site distinction Tapes used for on-site data are copied to different tapes to be sent to an off-site location.
Page 462: Ibm Tivoli Storage Manager And Tape Life Cycle
Figure 13-10 shows a typical tape management with enhanced control of the actual state of the tapes. Figure 13-10 IBM Tivoli Storage Manager and tape life cycle Providing that all of your primary storage pools are being backed up, then under normal conditions, the off-site tapes contain exactly the same versions of valid data that you have on-site.
Page 463: Moving Data From On-Site To Off-Site
Figure 13-11 shows how data is generically processed on tape from the moment the data is backed up until it is sent to the off-site location. IBM Tivoli Storage Manager SERVER Onsite Storage Hierarchy Recovery Plan File Database Backup Copy Storage Pool Backup...
Page 464 ANR1214I Backup of primary storage pool DISKDATA to copy storage pool OFFDATA has ended. Files Backed Up: 146, Bytes Backed Up: 12578213, Unreadable Files: 0, Unreadable Bytes: 0. query volume * stg=offdata tsm: ATLANTIC> IBM Tivoli Storage Manager Implementation Guide...
Page 465 Volume Name Storage Device Estimated Volume Pool Name Class Name Capacity Util Status (MB) ------------------------ ----------- ---------- --------- ----- -------- 044AKK OFFDATA COFFSITE 5,000.0 0.2 Filling backup stgpool diskdirs offdirs tsm: ATLANTIC> ANR2017I Administrator TSMADMIN1 issued command: BACKUP STGPOOL diskdirs offdirs ANR0984I Process 28 for BACKUP STORAGE POOL started in the BACKGROUND at 15:17:44.
Page 466 ANR8438I CHECKOUT LIBVOLUME for volume 044AKK in library 3582SHARED completed successfully. ANR0985I Process 27 for CHECKOUT LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 16:02:46. checkout libv 3582SHARED 034AKK tsm: ATLANTIC> IBM Tivoli Storage Manager Implementation Guide...
Page 467 ANR2017I Administrator TSMADMIN1 issued command: CHECKOUT libv 3582SHARED 034AKK ANR0984I Process 16 for CHECKOUT LIBVOLUME started in the BACKGROUND at 16:03:11. ANR8434I CHECKOUT LIBVOLUME: Operation for volume 034AKK in library 3582SHARED started as process 16. ANR8336I Verifying label of 3582SHARED volume 034AKK in drive RMT2 (/dev/rmt1). ANR8307I 009: Remove 3582SHARED volume 034AKK from slot with element number 25 of library 3582SHARED;...
Page 468 Number of Writable Sides: 1 Number of Times Mounted: 1 Write Pass Number: 1 Approx. Date Last Written: 02/22/06 15:18:21 Approx. Date Last Read: 02/22/06 15:18:21 Date Became Pending: Number of Write Errors: 0 IBM Tivoli Storage Manager Implementation Guide...
Page 469: Off-Site Tape Management To On-Site
Number of Read Errors: 0 Volume Location: ITSO vault Last Update by (administrator): TSMADMIN1 Last Update Date/Time: 02/22/06 15:19:21 13.7.5 Off-site tape management to on-site In this section we show how to move off-site volumes to the on-site location. These off-site volumes either have no active data on them (status of EMPTY) or are being returned to recreate damaged data in a primary storage pool.
Page 470: Checking Volumes Into A Library
Use the checklabel=yes (not NO or BARCODE) option on the checkin libvolume command when checking VolSafe volumes into a library. This is true for both ACSLS and SCSI libraries. IBM Tivoli Storage Manager Implementation Guide...
Page 471: Reclaiming Off-Site Tapes
The volumes are checked in as scratch, because they are empty. This is demonstrated in Example 13-41. We do not specify to label them because these tapes have returned from previous use, and therefore we can use their existing labels. Example 13-41 Checkin libvolume for searching and defining scratch tapes checkin libvolume 3582SHARED search=yes status=scratch tsm: ATLANTIC>...
Page 472: Database Backup Management
You can perform a backup of the database at any time by using the backup db command. For examples see 5.8, “Database backup” on page 210. This task can also be automated using a server script, as shown in Example 12-1 on page 375. IBM Tivoli Storage Manager Implementation Guide...
Page 473 Database backup volumes are tracked in a different manner than those of storage pools. Use the query volhistory command to identify tape volumes containing database backups. Alternately, you can use the activity log messages to identify those tapes. Assuming that the database backup has been done, the command to display the volumes is shown in Example 13-42.
Page 474 Example 13-44 Query for dbbackup volumes in the past nine days query volhistory type=dbbackup enddate=today-9 tsm: ATLANTIC> Date/Time: 02/13/06 16:03:24 Volume Type: BACKUPFULL Backup Series: 17 Backup Operation: 0 Volume Seq: 1 Device Class: LTO2 Volume Name: 023AKK Volume Location: Command: IBM Tivoli Storage Manager Implementation Guide...
Page 475: Error Conditions
Move the tape volumes from off-site to on-site You should move the backup volumes from your off-site location to your site. We recommend that you track the tapes in a movement log. Update the volume to scratch Use the delete volhistory command to return the database backup volumes to scratch.
Page 476: Tivoli Storage Manager Errors
Refer to Appendix B in the 'Messages' manual for recommended action. 02/23/06 00:50:03 ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=LOCATE, CC=0, KEY=03, ASC=31, ASCQ=00, SENSE=70.00.03.00.00.00.00.58.00.00.00.00.31.00.FF.0A.3A- .5E.40.51.00.01.01.31.08.0E.10.40.00.00.2B.00.00.33.3D.0- 0.00.00.00.00.00.00.00.00.00.00.00.00.DD.39.00.33.42.04.- 00.00.03.FF.00.00.DD.73.06.00, Description=An IBM Tivoli Storage Manager Implementation Guide...
Page 477: Machine Errors
undetermined error has occurred). Refer to Appendix B in the 'Messages' manual for recommended action..02/24/06 03:21:45 ANR1414W Volume 032AKK access mode is "read-only" due to previous write error. Example 13-47 on page 446 shows two library errors and one volume error. The volume error may be because of a true hardware problem or a media error.
Page 478 Example 13-50 shows another AIX errpt sample. Example 13-50 Another AIX errpt sample errpt -a root@ / > LABEL: SYSLOG IDENTIFIER:C6ACA566 Date/Time: Fri Feb 24 03:21:45 Sequence Number: 45343 Machine Id: 00D0659A00 Node Id: sm010 Class: IBM Tivoli Storage Manager Implementation Guide...
Page 479 Type: UNKN Resource Name: lmcpd Description MESSAGE REDIRECTED FROM SYSLOG User Causes OPERATOR REDIRECTED SYSLOG MESSAGES TO ERROR LOG Recommended Actions REVIEW DETAILED DATA Detail Data SYSLOG MESSAGE ERROR on 3494a, volume 024AKK, ERA 83 Library Drive Exception Windows System event viewer Tivoli Storage Manager logs error, information, and warning conditions to the Windows system application log.
Page 480: Ibm Tivoli Storage Manager Error Entries In Windows Event Viewer
Tivoli Storage Manager application. Note that not all of these may be true error conditions. You must evaluate whether it is actually a problem or simply a misconfiguration. Figure 13-12 IBM Tivoli Storage Manager error entries in Windows Event Viewer IBM Tivoli Storage Manager Implementation Guide...
Page 481: Summary
QUERY DRIVE command was executed in one of our Tivoli Storage Manager server test environments, but no drives were found since none were defined. Figure 13-13 Detailed event information of an IBM Tivoli Storage Manager error 13.9 Summary In this chapter we covered many of the ongoing tasks that should be performed to ensure that your Tivoli Storage Manager environment enjoys a long and healthy life.
Page 482 In our next chapter we move on to more advanced operational topics. IBM Tivoli Storage Manager Implementation Guide...
Page 483: Chapter 14. Advanced Operations
Reorganizing your database can provide a performance increase if the database has become fragmented. Integration with TEC provides an extra dimension to enterprise management. © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 484: Exporting Server To Server
When you export data to a target server, you must specify the server name that will import the data. IBM Tivoli Storage Manager Implementation Guide...
Page 485: Preparing To Export To Another Server For Immediate Import
For more information about enterprise configuration, see the chapter “Working with a Network of IBM Tivoli Storage Manager Servers” in the Administrator’s Guide for your server operating system platform.
Page 486 (SESSION: 252) 03/01/2006 14:41:47 ANR0986I Process 8 for EXPORT ADMIN running in the BACKGROUND processed 11 items for a total of 872 bytes with a completion state of SUCCESS at 14:41:47. (SESSION: 252) IBM Tivoli Storage Manager Implementation Guide...
Page 487: Exporting Client Node Information To Another Server
14.2.3 Exporting client node information to another server When you issue the export node command, the server exports client node definitions. Each client node definition includes: User ID, password, and contact information Name of the policy domain to which the client is assigned File compression status Whether the user has the authority to delete backed up or archived files from server storage...
Page 488: Exporting Policy Information To Another Server
Policy domain definitions Policy set definitions, including the active policy set Management class definitions, including the default management class Backup copy group and archive copy group definitions Schedule definitions Associations between client nodes and schedules IBM Tivoli Storage Manager Implementation Guide...
Page 489 Example 14-3 shows the export policy process in preview mode, and a selection of messages logged to the activity log. Example 14-3 Exporting policy domains tsm: ATLANTIC>export policy * toserver=lochness_server1 previewimport=yes ANR0609I EXPORT POLICY started as process 14. ANS8003I Process number 14 started. tsm: ATLANTIC>q act Date/Time Message...
Page 490: Exporting And Importing Server To Server
14.3.1 Moving a complete node’s data and meta data In our lab we have configured the following environment: Tivoli Storage Manager AIX server (Atlantic) Tivoli Storage Manager Windows 2003 server (Lochness) Tivoli Storage Manager Windows XP client (Paris) IBM Tivoli Storage Manager Implementation Guide...
Page 491: Server-To-Server Lab Setup
Figure 14-1 shows our setup. Lab Ethernet Lochness Sarah Atlantic 9.43.86.84 9.43.86.155 9.43.86.49 Windows 2003 AIX 5.3 Windows XP IBM Tivoli Storage IBM Tivoli Storage IBM Tivoli Storage Manager Server Manager Server Manager Client SAN Fabric 2109 FC Switch 9.43.86.159 3582 LTO Library 9.43.86.27...
Page 492 Process Process Description Status Number -------- ------------------- --------------------------------------------- 23 IMPORT (from Server ANR0648I Have copied the following: 1 Nodes 2 LOCHNESS_SERVER1) Filespaces 15109 Backup Files 1507021717 Bytes (0 errors have been detected). Current output volume(s): /stg/dirm/00000052.BFS,(168 Seconds) IBM Tivoli Storage Manager Implementation Guide...
Page 493 Once the process is complete, the results can be found in the actlog output, as shown in Example 14-8 and Example 14-9 on page 464. Example 14-8 Lochness’ activity log for the export process tsm: LOCHNESS_SERVER1>q act Date/Time Message ------------------- --------------------------------------------------------- 03/01/2006 16:13:08 ANR2017I Administrator ADMIN issued command: EXPORT NODE sarah filedata=all toserver=atlantic (SESSION: 32) 03/01/2006 16:13:08 ANR0984I Process 5 for EXPORT NODE started in the...
Page 494 0 archive files, 37859 backup files, and 0 space managed files. (SESSION: 269, PROCESS: 23) 03/01/2006 16:22:31 ANR0628I IMPORT (from Server LOCHNESS_SERVER1): Used 0 volume(s). (SESSION: 269, PROCESS: 23) 03/01/2006 16:22:31 ANR0630I IMPORT (from Server LOCHNESS_SERVER1): Copied IBM Tivoli Storage Manager Implementation Guide...
Page 495 4966809 kilobytes of data. (SESSION: 269, PROCESS: 23) 03/01/2006 16:22:31 ANR0611I IMPORT (from Server LOCHNESS_SERVER1) started by ADMIN as process 23 has ended. (SESSION: 269, PROCESS: 03/01/2006 16:22:31 ANR0986I Process 23 for IMPORT (from Server LOCHNESS_SERVER1) running in the BACKGROUND processed 37862 items for a total of 5,086,013,044 bytes with a completion state of SUCCESS at 16:22:31.
Page 496: Moving A Node's Metadata
Sarah back to the server Lochness, with all of the data. Using the merge feature of the export node command, we can ensure that the data originally on Lochness belonging to Sarah are brought up to date with IBM Tivoli Storage Manager Implementation Guide...
Page 497: Merging File Spaces
subsequent backups performed on Atlantic. Below are some details on merging of files. 14.4.1 Merging file spaces You can merge imported client backup, archive, and space-managed files into existing file spaces, and automatically skip duplicate files that may exist in the target file space on the server.
Page 498 243.42 OBJECT tsm: ATLANTIC>q occ sarah Node Name Type Filespace FSID Storage Number of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) --------- ---- ---------- ----- ---------- --------- --------- --------- IBM Tivoli Storage Manager Implementation Guide...
Page 499 SARAH Bkup \\sarah\c$ 1 DISKDATA 33,443 4,601.39 4,601.39 SARAH Bkup \\sarah\c$ 1 DISKDIRS 2,738 0.77 0.77 SARAH Bkup SYSTEM 2 DISKDATA 3,620 486.40 486.40 OBJECT We can see that on Atlantic, there are now 114 more files from C: and 1810 more files from the SYSTEM OBJECT.
Page 500 The FROMDate and FROMTime parameters only apply to client user file data. These parameters have no effect on other exported information (for example, policies). If clients continue to back up to the originating server while their data is IBM Tivoli Storage Manager Implementation Guide...
Page 501: Suggestions For Leveraging The Export Feature
being moved to a new server, you can move the backup data that was stored on the originating server after the export operation was initiated. The FROMDate and FROMTime options are available when you issue an export server or export node command. 14.4.2 Suggestions for leveraging the export feature Here are some reasons why you may want to export data: Splitting an overloaded server into two or three servers...
Page 502 ANR1697I Command 'Q SESSION ' processed by 1 server(s): 1 successful, 0 with warnings, and 0 with errors. tsm: LOCHNESS_SERVER1>redserv: q db ANR1699I Resolved REDSERV to 2 server(s) - issuing command Q DB against IBM Tivoli Storage Manager Implementation Guide...
Page 503: Reorganizing The Database
server(s). ANR1687I Output for command 'Q DB ' issued against server ATLANTIC follows: Available Assigned Maximum Maximum Page Total Used Pct Max. Space Capacity Extension Reduction Size Usable Pages Util (MB) (MB) (MB) (MB) (bytes) Pages Util --------- -------- --------- --------- ------- ------- ------ ----- ----- 1,024 1,024 4,096 262,144 8,515...
Page 504 03/02/2006 11:50:14 ANR1782W ESTIMATE DBREORG process 3 started - server performance may be degraded while this process is running. (SESSION: 12, PROCESS: 3) 03/02/2006 11:51:51 ANR1784I A database reorganization would reduce the database utilization by an estimated 89 MB. (SESSION: 12, IBM Tivoli Storage Manager Implementation Guide...
Page 505 The device configuration file includes a copy of the device class, library, and drive definitions for the server. The utility commands used for the dump and IBM Tivoli Storage load procedure need the device definitions. See the Manager Administrator’s Reference for details on the DEVCONFig option.
Page 506 You need to change the definition to this: DEFINE DRIVE 3582LIB DR00 See the IBM Tivoli Storage Manager Administrator’s Reference for details about the define library and define drive commands. 4. Before unloading the database, estimate how many tapes you will need: –...
Page 507 Because the library is defined to be a manual library, you will need to manually mount the tapes. Important: Keep track of the order in which the tape volumes are written when the database is unloaded. You must specify the volume names in the same order when you reload the database using the DSMSERV LOADDB utility.
Page 508: Tivoli Storage Manager And Tec Integration
Data Protection for IBM ESS for Oracle This section shows how to enable and configure Tivoli as an event receiver on the Tivoli Storage Manager server. See the IBM Tivoli Storage Manager Administrator’s Guide for more information about TEC configuration.
Page 509: Summary
2. Enable events for logging to the Tivoli receiver (TEC). The following enables logging for severe and error messages coming from all Tivoli Storage Manager nodes and servers to TEC. Refer to the IBM Tivoli Storage Manager Administrator’s Guide for more information about enabling and disabling events for logging.
Page 510 IBM Tivoli Storage Manager Implementation Guide...
Page 511: Chapter 15. Performance Considerations
We discuss parameters that can be tuned to get the maximum performance during backup, archive, restore, and retrieve operations. Remember that an IBM Tivoli Storage Manager implementation is typically quite complex, covering a range of variables that could affect performance.
Page 512: How To Measure Performance
Network utilization Network speed Network reliability Server hardware (CPUs, RAM, disk drives, network adapters) Server storage pool devices (disk, tape, optical) Server activity (non-Tivoli Storage Manager workload) Final output repository type (disk, tape, optical) IBM Tivoli Storage Manager Implementation Guide...
Page 513: Network Benchmarking
Clearly, with so many combinations and possibilities, it is not feasible to discuss all possible combinations of these parameters within the scope of this book. This book should be taken as advice to follow when faced with performance questions, so that you do not limit yourself to considering only the Tivoli Storage Manager tunable parameters covered here.
Page 514 >> $ftp$.cmd echo bye >> $ftp$.cmd FTP.EXE -n -s:$ftp$.cmd del $ftp$.cmd Example 15-2 Sample FTP script for UNIX ftp -n TSM-Server <<- EOF! user username password cd <targetdirectory> put <samplefile> get <samplefile> del <samplefile> EOF! IBM Tivoli Storage Manager Implementation Guide...
Page 515 So how do you launch the FTP script right before the backup occurs? By including your FTP script in a Tivoli Storage Manager client options file (or dsm.sys on UNIX/Linux) as pre-schedule (or post-schedule, or both) commands: PRESCHEDULECMD c:\temp\ftpbench.bat POSTSCHEDULECMD c:\temp\ftpbench.bat The script will then run automatically.
Page 516 Example 15-5 z/OS: FTP command without disk bottleneck C:\>ftp <system> Connected to <system>. 220-FTPD1 IBM FTP CS V1R2 at <SYSTEM>, 15:44:09 on 2006-02-27. 220 Connection will close if idle for more than 5 minutes. User (<system>:(none)): triple8 331 Send password please.
Page 517 150 Opening data connection for 500MBFile. 226 Transfer complete. ftp: 536801936 bytes sent in 52.09Seconds 10304.49Kbytes/sec. ftp> get 500MBFile 200 PORT command successful. 150 Opening data connection for 500MBFile (524288000 bytes). 226 Transfer complete. ftp: 536801936 bytes received in 57.13Seconds 9396.97Kbytes/sec. Now back up the same file from your client machine to the Tivoli Storage Manager server, as shown in Example 15-7.
Page 518: Tivoli Storage Manager Client Performance Tracing
If a problem occurs, you can always activate the trace routines to gather trace information for diagnostic purposes. Call your IBM Service Representative for assistance with diagnosing Tivoli Storage Manager problems.
Page 519 The output file name cannot be specified, but after the task is complete, you can rename it to a meaningful name, for example, YYMMDD_client_stats.txt. Example 15-10 shows the output for the backup of the 500 MB file. We have shown only the thread information that is important to this investigation. Example 15-10 Client instrumentation statistics: backup TSM Client final instrumentation statistics: Thu Feb 23 09:52:13 2006 Instrumentation class: Client detail...
Page 520 The majority of the time is spent in the section. This now could be server-related processing or indicate a communication problem between the server and the client. Before we look at the server-generated statistics in 15.1.3, “Tivoli Storage Manager server IBM Tivoli Storage Manager Implementation Guide...
Page 521 performance tracing” on page 492, we explain the sections of the client instrumentation traces: Client Setup Initial processing including signon, authorization, and queries for policy set and file system information. Process Dirs Processing directory and file information before backing up or restoring any files. For incremental backup, it includes querying the server for backup status information.
Page 522: Tivoli Storage Manager Server Performance Tracing
By default, a maximum number of 1024 threads can be instrumented. To end performance instrumentation, enter the instrumentation end command, as in Example 15-13. Example 15-13 Stop server performance instrumentation tsm> INSTrumentation End > <valid_path_and_filename> IBM Tivoli Storage Manager Implementation Guide...
Page 523 By default, the output is sent to the console or administrative display, using a pipe to redirect it to a file. We collected the server instrumentation traces for the backup and the restore attempt. Since we know we are backing up a file of 500 MB it is easy to identify the related threads from the server trace by looking at the Total KB section.
Page 524 Client Version 5, Release 3, Level 3.0 0220FB Client date/time: 02/23/06 13:46:40 (c) Copyright by IBM Corporation and other(s) 1990, 2006. All Rights Reserved. Node Name: BANDA Session established with server LOCHNESS_SERVER1: Windows Server Version 5, Release 3, Level 2.2...
Page 525: Architecture-Based Performance Tuning
Restore function invoked. Restoring 524,288,000 /home/root/500MBFile [Done] Restore processing finished. Total number of objects restored: Total number of objects failed: Total number of bytes transferred: 500.06 MB Data transfer time: 41.12 sec Network data transfer rate: 12,452.21 KB/sec Aggregate data transfer rate: 11,026.84 KB/sec Elapsed processing time: 00:00:46...
Page 526: Database And Recovery Log
The advice given in the previous section is also valid for disk storage pools, that is, you can increase performance by using multiple small volumes for disk storage pools instead of using one big volume. IBM Tivoli Storage Manager Implementation Guide...
Page 527: Versioning
Figure 15-1 on page 497 shows the side effects of placing multiple storage pool volumes on a single disk. The increased seek activity can degrade performance. 1 TSM volume per physical disk 2 TSM volumes per physical disk Volumes shown assuming all data was previously migrated.
Page 528: Client Configuration
This number indicates how often a database page request could be satisfied from the cache as opposed to requiring disk access. An optimal setting for the database buffer pool is one in which the cache hit percentage is greater IBM Tivoli Storage Manager Implementation Guide...
Page 529 than or equal to 98%. To check the cache hit percentage, use the query db f=d command, as shown in Example 15-17. This shows that our cache hit percentage is 99.89%, which is fine. Example 15-17 query db f=d tsm: LOCHNESS_SERVER1>q db format=detail Available Space (MB): 2,024 Assigned Capacity (MB): 2,024 Maximum Extension (MB): 0...
Page 530 MIRRORWRITE SEQUENTIAL to prevent exposure to partial page writes. We recommend keeping the default of YES. Database reorganization Over time, database volumes can become fragmented. You can restore the efficiency of the database and improve database performance by reorganizing IBM Tivoli Storage Manager Implementation Guide...
Page 531: Transactions
the database using database unload and reload processing. By reloading the database, you compress and reorganize it. This process is described in detail in Chapter 14, “Advanced operations” on page 453. 15.3.2 Transactions This section covers server options that influence the performance and behavior of data movement within the server.
Page 532: Communication
Tivoli Storage Manager services to the clients is reduced. Since Tivoli Storage Manager clients use multi-threading, you should consider the total number of concurrent nodes, times the number of concurrent sessions IBM Tivoli Storage Manager Implementation Guide...
Page 533 that the server must handle. If you need 10 concurrent nodes to perform backup operations and each of them has a multi-threading capability (resource utilization) of 4, then you must set maxsession to at least 40 (10 x 4). MAXSCHEDSESSIONS The MAXSCHEDSESSIONS parameter specifies the number of sessions that the server can use for processing scheduled operations.
Page 534: General Parameters
Tivoli Storage Manager processes are not occurring. To enable this, either schedule expiration once per day, or use the setopt expinterval 0 command and manually start the process with the expire inventory command at the server. IBM Tivoli Storage Manager Implementation Guide...
Page 535 Tip: If SELFTUNEbufpoolsize is set to YES, expire inventory processing will also trigger the buffer pool performance monitoring algorithm to check whether a performance improvement could be gained (based on previous server execution and available real memory). THROUGHPUT thresholds Use the THROUGHPUTTIMETHRESHOLD and THROUGHPUTDATATHRESHOLD to control how Tivoli Storage Manager handles slow performing client sessions.
Page 536: Client Node
TXNGROUPMAX option; the actual size of a transaction can be less than your limit. Once this number is reached, the client commits the transaction to the server even if the transaction byte limit is not reached. IBM Tivoli Storage Manager Implementation Guide...
Page 537 If you increase this parameter, consider that: More data per transaction will increase server recovery log requirements. Check log and log pool space to ensure that there is enough space, and remember that a larger log may increase server startup time. More data per transaction may result in more data being retransmitted if a retry occurs.
Page 538: Communication
A larger buffer will require more memory and may not improve performance. This option replaces the formerly available LARGECOMMBUFFERS option. We recommend keeping the default value unless otherwise advised by IBM support. TCPBUFFSIZE The TCPBUFFSIZE option specifies the size of the internal TCP communication buffer that is used to transfer data between the client node and the server.
Page 539: General Parameters
large buffer can improve communication performance, but requires more memory. TCPWINDOWSIZE The TCPWINDOWSIZE option specifies the size of the TCP/IP sliding window in kilobytes. This option overrides the operating system's TCP send and receive spaces. It specifies the size of the TCP sliding window for all clients, and all but MVS servers.
Page 540 The DIRMC directive in the client options file was used to bind directories to a management class pointing to this storage pool. IBM Tivoli Storage Manager Implementation Guide...
Page 541: System Design For Performance
Restore processing has changed since then: during the process directories will be created with default attributes and the correct attributes and ACL information is applied once the data is read from the media. Therefore the original reason to cache directories on disk no longer applies. Nevertheless, the DIRMC option is still useful.
Page 542: Disk Topology
RAID is insisted upon. It takes discipline to dedicate a 72 GB disk to a small 6 GB log volume, for example. Use of virtualization technologies such as the IBM TotalStorage® SAN Volume Controller can assist here, since virtual disks can be made of any size.
Page 543: Tape Devices
Gigabit technology supports jumbo frames (9000 bytes), which should be used whenever Gigabit Ethernet hardware is implemented. Unfortunately not every Gigabit hardware component implements jumbo frames. Using this feature is only practical when all elements (server, switch, and client) are capable of it. 15.5.6 Tape devices Calculation of your daily throughput for backup and archive data as well as the amount of data being sent directly to tape should lead to a minimum number of...
Page 544: File System Volumes Versus Raw Logical Volumes
By default, AIX will use up to 80% of memory as a file system cache. For machines dedicated to Tivoli Storage Manager this should be lowered. A good starting point is 50%. This parameter is called maxperm. This may be done by IBM Tivoli Storage Manager Implementation Guide...
Page 545 -o maxperm%=50 For a detailed explanation of the vmo tunables, please see VMM page replacement tuning under: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm. aix.doc/aixbman/prftungd/memperf5.htm If, after a period of time, paging still occurs, this may be lowered further. This behavior can also be avoided by using raw logical volumes for the disk storage pools.
Page 546: Use Ntfs Partitions For The Server
FAT partitions. Warning: NTFS file compression must not be used on disk volumes that are used by the Tivoli Storage Manager server, because of the potential for performance degradation. IBM Tivoli Storage Manager Implementation Guide...
Page 547: Journal-Based Incremental Backup
15.6.6 Journal-based incremental backup Using journal-based incremental backup (JBB) can provide substantially faster incremental backups of file systems with a large number of files with small daily change rates. Configuration of the journal options is done in the tsmjbbd.ini file in the client install directory.
Page 548 Network data transfer rate: 16,750.46 KB/sec Aggregate data transfer rate: 0.21 KB/sec Total number of bytes pre-compress: 89,411 Total number of bytes post-compress: 89,411 Objects compressed by: Elapsed processing time: 00:06:46 Average file size: 43.65 KB IBM Tivoli Storage Manager Implementation Guide...
Page 549 So out of the total time of 406 seconds, it takes 308 seconds to process the 35332 directories and realize that only two objects have changed. In addition, the server is queried for the objects available, resulting in a search and transfer of 82 MB worth of inventory information, as shown with producer session 134 in Example 15-23.
Page 550: Summary
All of these factors combine to move bottlenecks around your environment in an endless game of cat and mouse. IBM Tivoli Storage Manager Implementation Guide...
Page 551: Tivoli Storage Manager Tunables Overview
Figure 15-2 on page 521, while by far not complete, should give you a good starting point when reviewing your Tivoli Storage Manager tunables. server client MEMORYEFFICIENTBACKUP BUFPOOLSIZE MAXSESSIONS 25 TAPEPROMPT Network EXPIREINVENTORY 0 INCLUDE/EXCLUDE TCPWINDOWSIZE 64 (63) TXNGROUPMAX 256 TXNBYTELIMIT 2 GB TCPNODELAY YES TCPBUFFSIZE 32 KB...
Page 552 IBM Tivoli Storage Manager Implementation Guide...
Page 553: Part 4. Advanced Topics
Network Appliance file server to achieve file level restore. Also included is the Disaster Recovery Manager, bare metal machine recovery, Tivoli Data Protection complimentary products, and, finally, how to upgrade your IBM Tivoli Storage Manager server and clients. © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 554 IBM Tivoli Storage Manager Implementation Guide...
Page 555: Chapter 16. Leveraging San Environments
In this chapter we describe how to exploit your SAN environment to perform LAN-free client operations. We cover, in detail, requirements and procedures to set up LAN-free backup to tape using advanced IBM Tivoli Storage Manager features, such as library sharing, server to server communication, SAN device discovery, and more.
Page 556: Lan-Free Prerequisites
DIOMEDE running Microsoft Windows 2003 and a Tivoli Storage Manager server V5.3.2, ATLANTIC, running on AIX 5.3. Both systems are connected via LAN and SAN. We also need a shared tape library connected to IBM Tivoli Storage Manager Implementation Guide...
Page 557 SAN. This is an IBM TotalStorage 3582 Tape Library (IBM 3582) with 2 LTO2 drives and Control Path Failover (CPF) feature enabled. Note: CPF is an optional feature of the IBM 3582 that provides automatic control path failover to a preconfigured redundant control path if an HBA or control path drive fails, without aborting the current operation in progress.
Page 558: Server Setup For Lan-Free
Customizing the client for LAN-free Operations and considerations when using LAN-free data transfer For more information about operating Tivoli Storage Manager in SAN environments, see Get More Out of Your SAN with IBM Tivoli Storage Manager, SG24-6687. 16.2 Server setup for LAN-free Before setting up the server for LAN-free operations, the Tivoli Storage Manager server itself must be installed and running.
Page 559 ATLANTIC> Storage Management Server for AIX-RS/6000 - Version 5, Release 3, Level 2.2 Server Name: ATLANTIC Server host name or IP address: atlantic.itsosj.sanjose.ibm.com Server TCP/IP port number: 1500 Crossdefine: On Server Password Set: Yes Chapter 16. Leveraging SAN environments...
Page 560: Defining Library, Drives, And Associated Paths On The Server
Tip: LTO drives have an internal self-cleaning mechanism, which cleans a drive any time a tape is to be loaded. Therefore, you do not need to set the cleaning frequency in the drive definition. IBM Tivoli Storage Manager Implementation Guide...
Page 561: Defining The Device Class
16.2.2 Defining the device class In Example 16-4 we define a device class for the IBM 3582 with the appropriate tape format. Note that we set the tape retention time to 5 minutes only, to ensure that tape volumes are dismounted as soon as they are no longer required for the operation in progress.
Page 562: Defining Policy
Retain Only Version: 100 Copy Mode: Modified Copy Serialization: Shared Static Copy Frequency: 0 Copy Destination: TAPEDATA_LF Table of Contents (TOC) Destination: Last Update by (administrator): ADMIN Last Update Date/Time: 02/23/2006 14:45:26 Managing profile: Changes Pending: No IBM Tivoli Storage Manager Implementation Guide...
Page 563: Lan-Free Validation
Now we can register our client DIOMEDE to the policy domain SERVER. Note dataread datawrite that although the parameters are set to their default values ( for both), we set it explicitly in the example to show you how you can control the transfer path used by the client.
Page 564: Storage Agent Setup
16.3 Storage Agent setup Here we describe how to install and configure the Storage Agent on a Windows 2003 machine, including installing the IBM 3582 device drivers for the shared library. The Storage Agent is an interface between a client and a server. It does not itself initiate the backup or restore operation, since this is a backup-archive client responsibility.
Page 565 Since we have an LTO library, we have to use IBM tape device drivers. For non-IBM devices, you might choose either third-party device drivers or use the Tivoli Storage Manager device drivers included in the Storage Agent package. The supported devices and required device drivers are on the Tivoli Storage Manager Web site: http://www.ibm.com/software/sysmgmt/products/support/IBM_TSM_Supported_Devices_...
Page 566 After the installation, our devices are now correctly identified as IBM 3582 LTO Library and IBM ULT3580-TD2 SCSI Sequential Device (see Figure 16-3). Figure 16-3 Correctly identified devices in Windows Device Manager Important: If your environment includes an IBM LTO Ultrium tape drive and your Storage Agent will be installed on Windows 2000, you must verify and possibly change the HBA setting.
Page 567: Storage Agent Software Installation
LTO, 3592, and more. For details see IBM Tivoli Storage Manager for SAN Storage Agent User’s Guide, GC32-0785. 16.3.2 Storage Agent software installation Here we describe how to install the Windows Storage agent. For UNIX, see IBM Tivoli Storage Manager for Storage Area Network UNIX Storage Agent User’s Guide, GC32-0771.
Page 568: Storage Agent And Device Driver Installation Screen
2. Click TSM Storage Agent and a wizard will launch. Click Next. 3. Enter customer information and choose access rights to the Storage Agent application, as shown in Figure 16-6. Figure 16-6 Windows Storage Agent customer information IBM Tivoli Storage Manager Implementation Guide...
Page 569: Windows Storage Agent Setup Type
4. Choose the type of installation. In Figure 16-7 we chose Complete installation. You may choose Custom installation to select Storage Agent code installation, or console plugin installation, or both, which is the default. Our recommendation is to choose Complete installation to make sure that all components and their prerequisites are installed.
Page 570: Configuring The Storage Agent
Note: On Windows Server 2003 systems, devices are automatically controlled by the default Windows Device Driver, even if you install the IBM Tivoli Storage Manager driver (TSMSCSI). In this case, you must manually update the controlling driver for each device you want to be controlled by TSMSCSI. For details on the configuration procedure see IBM Tivoli Storage Manager for SAN for Windows Storage Agent User’s Guide, GC32-0785.
Page 571: Storage Agent Initialization Wizard
Unlike other supported platforms, the Storage Agent package on Windows provides two ways to initialize the Storage Agent—command line or using a GUI wizard. We describe both ways; however, the wizard is the preferred method, since typing commands is more error prone and (this is important) the wizard automatically configures the Storage Agent as a service in Windows.
Page 572 Storage Agent definition in the Tivoli Storage Manager server (Example 16-9 on page 540). Specifically, provide the Storage Agent name and password and TCP/IP address. Figure 16-9 Storage Agent configuration IBM Tivoli Storage Manager Implementation Guide...
Page 573: Tivoli Storage Manager Server Details
3. On the page shown in Figure 16-10, enter the Tivoli Storage Manager server details (the server name, password, server IP address, and port number) to match the definitions given in Example 16-1 on page 529. Figure 16-10 Tivoli Storage Manager server details Chapter 16.
Page 574: Storage Agent Service Configuration
4. On the page shown in Figure 16-11, set the Storage Agent service behavior. We recommend automatically starting the service on reboot, and if you require the service to run under a specific account, give the account details. Figure 16-11 Storage Agent service configuration IBM Tivoli Storage Manager Implementation Guide...
Page 575 5. On the final screen, click Back to review the entries, or complete the initialization by clicking Finish. Provided your account password was correct, the initialization wizard subsequently configures a service in Windows and starts it, as shown in Figure 16-12. Figure 16-12 Running Storage Agent service in Windows Services 6.
Page 576 (C) Copyright IBM Corporation 1990, 2004. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR1432I Updating device configuration information to defined files.
Page 577 (C) Copyright IBM Corporation 1990, 2004. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR8260I Named Pipes driver ready for connection with clients.
Page 578: Device Configuration On The Storage Agent
Storage Agent. We trimmed the description field of the command output to fit the example in the page without wrapping. Example 16-17 Device listing as seen by the Windows machine using tsmdlst utility tsmdlst /detail C:\Program Files\Tivoli\TSM\storageagent> Tivoli Storage Manager -- Device List Utility IBM Tivoli Storage Manager Implementation Guide...
Page 579 Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Computer Name: DIOMEDE TSM Device Driver: ADSMScsi - Not Running One HBA was detected.
Page 580 HBA. The output did not, however, display the serial number or WWN identifier. This is because we are using the IBM tape device drivers, rather than the Tivoli Storage Manager native device drivers. To get this information, we add the /xinquiry parameter (see Example 16-18).
Page 581 QLogic Corporation 2312 ql2312.sys 8.1.5.60 (W2K IP) 3.01.10 Looking for devices... TSM Name LUN Bus Port SSN ------------------------------------------------------------------------------- mt0.0.0.2 1110177214 500308C140067006 LTO mt1.0.0.2 1110176223 500308C140067003 LTO Completed in: 0 days, 0 hours, 0 minutes, 1 seconds. Defining paths between Storage Agent and shared drives Now we must match the tape drives with those ones defined on the Tivoli Storage Manager server.
Page 582: San Device Discovery Support
Thus, the path will not go offline. Instead, it stays online and available for the operation. On Windows platforms this option is set by default. On other platforms enable SAN discovery using the SANDISCOVERY on option in the server options file IBM Tivoli Storage Manager Implementation Guide...
Page 583: Recovering From Offline Paths
16.4.1 Recovering from offline paths Starting with Storage Agent V5.3.2, the tsmdlst utility can also help keep Tivoli Storage Manager path statements up-to-date for IBM tape devices. This can be especially useful when working with versions of the server that do not include the...
Page 584 Tivoli Storage Manager -- Device List Utility Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.
Page 585 Tivoli Storage Manager -- Device List Utility Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.
Page 586: Client Lan-Free Customization
IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 2.0 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Session established with server ATLANTIC: AIX-RS/6000 Server Version 5, Release 3, Level 2.2...
Page 587 API client options file, referenced to by the DSM_CONFIG system variable, to enable the LAN-free path. For detailed prerequisites for using LAN-free with API clients, see the IBM Tivoli Storage Manager for SAN Storage Agent User’s Guide for your platform.
Page 588: Performing Lan-Free Operations
LAN-free capable management class, it is done via SAN instead of LAN, as shown in Figure 16-14 on page 559. Figure 16-13 Backup of c:\console directory IBM Tivoli Storage Manager Implementation Guide...
Page 589 Figure 16-14 Backup status window As you can see in Figure 16-14, the positive LanFree Data Bytes value confirms that the backup was done via SAN. The difference between the Bytes Transferred and LanFree data Bytes value is because the LAN path is used for storing metadata in the server database, and thus the total value for transferred data will always be slightly greater than the LanFree Bytes value.
Page 590: Determining Whether The Data Movement Is Lan-Free
Number Method State Time Sent Recvd Type ------ ------ ------ ------ ------- ------- ----- -------- -------------------- 326 Tcp/Ip IdleW 12 S 1.9 K 679 Server Windows STA_DIOMEDE 328 Tcp/Ip IdleW 3.6 K Server Windows STA_DIOMEDE IBM Tivoli Storage Manager Implementation Guide...
Page 591 IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 2.0 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Session established with server ATLANTIC: AIX-RS/6000 Server Version 5, Release 3, Level 2.2...
Page 592: Lan-Free Data Transfer Considerations
The topology configured, and whether bandwidth is shared or dedicated The average size of the files being transferred 16.7 Summary This chapter has demonstrated the configuration of the LAN-free feature in a Tivoli Storage Manager environment. We have provided implementation details IBM Tivoli Storage Manager Implementation Guide...
Page 593 and explained how this technology might be deployed. In the next chapter we show how to configure Tivoli Storage Manager to use a server-free communication path. Chapter 16. Leveraging SAN environments...
Page 594 IBM Tivoli Storage Manager Implementation Guide...
Page 595: Chapter 17. Server-Free Data Movement
Server-free data movement Chapter 17. In this chapter we describe an IBM Tivoli Storage Manager server-free backup environment. Data is copied directly from a disk that is SAN-attached to the Tivoli Storage Manager client to a SAN-attached tape drive using an additional Data Mover component in the tape library.
Page 596: Server-Free: What It Is And Why To Use It
Tivoli Storage Manager allows clients to directly back up and restore file system images between disk storage and tape devices accessible over a Storage Area Network (SAN). An outboard datamover such as IBM SAN Data Gateway handles the server-free data movement on behalf of the Tivoli Storage Manager server.
Page 597 Figure 17-1 shows how data is actually transferred on a Storage Area Network during server-free backup/restore. LAN/W AN (TCP/IP) Backup Client Server FC Device Data Tape Data M over Data Flow Control Flow Figure 17-1 Server-free data movement Operations for server-free backup/restore are done in the following order: 1.
Page 598: Server-Free Setup Requirements
However, the setup and operation procedure for the server-to-server function has not changed substantially. To see a list of the latest hardware/software/HBA/device driver levels, see: Hardware – Tivoli Storage Manager Server: • IBM xSeries® server IBM Tivoli Storage Manager Implementation Guide...
Page 599: Server-Free Data Movement
• IBM FAStT500 Raid controller with /2 EXP 500 disk enclosures – Fabric: • 2*IBM 2109 S08 + 1 * IBM 2109 S16 cascaded • IBM SAN Fibre Channel Switch 2109 Model S08 (Kernel: 5.4, Fabric OS: v2.6.0c) – Library: •...
Page 600: Configuration Steps: Overview
1. Set up the Storage Area Network. 2. Set up FAStT 500. 3. Set up IBM 3583. Make sure the tape library has the correct firmware level. 4. Install HBAs on the client and server machines. Install the correct device driver and API for the HBAs.
Page 601: San Network
Using FAStT storage manager, make sure that you can see the disks. Also, check for the latest available firmware for the IBM 3583. Update the drive, RMU, and library firmware. Ethernet...
Page 602: San Zoning
Table 17-1 Server-free zoning Zone Members ServTape 3583, Tivoli Storage Manager Server HBA1 ServDisk FAStT 500, Tivoli Storage Manager Server HBA2 CliDisk Tivoli Storage Manager Client HBA1, FAStT 500 SDG_Disk 3583 (datamover), FAStT 500 IBM Tivoli Storage Manager Implementation Guide...
Page 603 Note: We have used soft zoning in this scenario. For more information about zoning, refer to the IBM SAN Fibre switch 2109 Model S08 Guide for managing and implementing zones in a Storage Area Network.
Page 604: Setting Up The San Data Gateway (Datamover)
In order to perform the extended copy command from the datamover built into the IBM 3583, we need to enable the datamover, as described in the following steps (if you have already done this, just proceed to the second to last step): 1.
Page 605: Configuring Tivoli Storage Manager Server
– gateway – generic – SOLARIS – Unisys – nt (default) 11.Then enable the IP port: ethEnable 12.Set the IP address: ethAddrSet "192.168.0.212","255.255.255.0" 13.Set the gateway: gateAddrSet "192.168.0.1" 14.Now issue the following command to enable the datamover agents: sncFeatureEnable "License Key String" The license key string is a unique key provided with the device.
Page 606 We only show how to define one drive. You can define others using the same procedure; the element number will increment by 1 for every new drive. You can also use the Tivoli Storage Manager server autodetect feature to detect the WWN, element number, and serial numbers. IBM Tivoli Storage Manager Implementation Guide...
Page 607 DEFINE DATAMOVER sandg1 wwn=20010060451729B6 dataformat=nonblock serial=610667 type=scsi The world wide name and serial number for the datamover can be found with IBM Tivoli Storage the q san command. There is another parameter called Manager copythreads when defining the datamover. The parameter, copythreads, specifies the number of concurrent copy operations that the datamover can support.
Page 608 ANR2017I Administrator SERVER_CONSOLE issued command: QUERY SAN type=disk f=d Device Type: DISK Vendor: IBM Product: 3552 Serial Number: 1T03510567 Device: Data Mover: No Node WWN: 201A00A0B80C00D2 Port WWN: 201A00A0B80C00D3 LUN: 0 SCSI Port: 5 SCSI Bus: 0 SCSI Target: 0 IBM Tivoli Storage Manager Implementation Guide...
Page 609: Configuring The Tivoli Storage Manager Client
13.Define paths from the datamover to the tape drives: define path sandg1 drivea srct=datamover destt=drive libr=3583_svt Define paths for all of the drives in the same way. 13.Define paths from the datamover to the disks: define path sandg1 Harddisk4 srct=datamover destt=disk node=bordeaux 17.4.5 Configuring the Tivoli Storage Manager Client Follow these steps to configure the Tivoli Storage Manager client for server-free data movement:...
Page 610: Server-Free Client Backup In Process
Figure 17-5 shows a server-free client backup in process. Figure 17-5 Server-free client backup in process Next we check the Tivoli Storage Manager server status, as shown in Figure 17-6. Figure 17-6 Server-free backup server status query IBM Tivoli Storage Manager Implementation Guide...
Page 611: Summary
After finishing the backup successfully, we can restore from the client, as shown in Figure 17-7. Figure 17-7 Tivoli Storage Manager server-free client restore in process 17.6 Summary We have shown how to configure and run a server-free client backup. In the next chapter we discuss Tivoli Storage Manager with Network Attached Storage devices, using NDMP.
Page 612 IBM Tivoli Storage Manager Implementation Guide...
Page 613: Chapter 18. Network Data Management Protocol (Ndmp)
Manager Extended Edition includes support for the use of NDMP to back up and recover NAS file servers. The latest detailed implementation information about this topic is available in the IBM Redbook Using the System Storage N Series with IBM Tivoli Storage Manager, SG24-7243.
Page 614: Ndmp Terminology
Restores can be performed of an entire file system or selected files and directories within the file system. Multiple backup and restore operations can be performed in parallel. IBM Tivoli Storage Manager Implementation Guide...
Page 615: Ndmp Support
Currently, NDMP for full or differential backups can be performed at a directory or file system level, including snapshots that are stored as either file systems or subdirectories to a Tivoli Storage Manager server running on AIX, Sun Solaris, HP-UX, Linux, or Windows. This uses NDMP to back up a full file system image and to restore an entire file system image.
Page 616 Version 6.1.1 or later. Any Ready for IBM Tivoli 5.2.2 5.2.2 5.2.2 5.2.2 Software certified NAS file server. See Additional Device Support below for more information IBM System Storage N series File 5.2.7 5.2.7 5.2.7 5.2.7 Server. 5.3.2.2 5.3.2.2 5.3.2.2 5.3.2.2...
Page 617: Multiple Nas Appliances
18.1.4 Multiple NAS appliances Multiple NAS appliances can share tape resources if they have Fibre Channel (FC) access to the drive and if backups are performed via the same Tivoli Storage Manager server. Depending on the configuration, drives can be shared with LAN-free backup/restore operations.
Page 618 IBM Tivoli Storage Manager Implementation Guide...
Page 619: Chapter 19. Disaster Recovery Manager
DRM solution. To achieve a better perspective and understanding, we encourage you to read the aforementioned IBM Redbook. © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 620: Example Of A Drm Implementation
This section contains a practical example of using Disaster Recovery Manager. In our lab we have a Windows 2003 Tivoli Storage Manager server, LOCHNESS, connected to a SAN-attached IBM 3582 Tape Library. The Tivoli Storage Manager server is called LOCHNESS_Server1. The storage pool setup is the same as our example solution in Chapter 6, “Data storage”...
Page 621: Drm Setup
Example 19-1 Registering Tivoli Storage Manager Extended Edition tsm: LOCHNESS_SERVER1>q lic Last License Audit: 02/27/2006 00:00:09 Is IBM System Storage Archive Manager in use ?: No Is IBM System Storage Archive Manager licensed ?: No Is Tivoli Storage Manager Basic Edition in use: Yes...
Page 622: Create A Copy Storage Pool
ANR2828I Server is licensed to support Tivoli Storage Manager Extended Edition. tsm: LOCHNESS_SERVER1>q lic Last License Audit: 02/27/2006 00:00:09 Is IBM System Storage Archive Manager in use ?: No Is IBM System Storage Archive Manager licensed ?: No Is Tivoli Storage Manager Basic Edition in use: Yes...
Page 623 Example 19-2 shows using the define stgpool command to create the copy storage pool OFFDATA using the device class defined for the LTO tape library. Note the value of REUsedelay=6. This is important for ensuring recovery integrity. See step 8 on page 596 for more information about how this relates to the database backup series expiration value.
Page 624: Drm Settings
C:\TSMDATA\DRM\INSTRUCTIONS\. The prefix does not need to be specified. If you do not set the directory, instructions are searched for in the server’s default path (the directory from where the instance of the Tivoli Storage Manager server is running). IBM Tivoli Storage Manager Implementation Guide...
Page 625 The recovery instruction files are user-created and should contain any site-specific instructions related to the DR process. You can create the files using any plain text editor. Be sure to include any information that is relevant to your installation. Instruction files will be automatically included in the DR plan.
Page 626 The most recent backup series of either type is never deleted. Therefore, a value of 6 will keep database backups for one week. IBM Tivoli Storage Manager Implementation Guide...
Page 627 In Example 19-11 we specify an expiration value of 6 days. To ensure that the database can be restored to an earlier level and database references to files in the storage pool are still valid, the number of days specified by this setting and the number of days specified by the REUsedelay parameter in the copy storage pool definitions should be the same.
Page 628: Verifying The Settings
1. Back up the primary storage pools to copy storage pools. 2. Back up the Tivoli Storage Manager database. 3. Perform DR tape movement commands. 4. Generate a recovery plan. 5. Physically transport media and plan off-site. IBM Tivoli Storage Manager Implementation Guide...
Page 629 The states and their life cycle are shown in Figure 19-2. DR media states are changed using move drmedia. O N S I T E O F F S I T E backup stgpool ... COURIER VAULT Storage Pools NOTMOUNTABLE IBM Tivoli Storage Expiry and Manager Reclamation Server ONSITERETRIEVE VAULTRETRIEVE backup db ...
Page 630: Back Up Primary Storage Pools To Copy Storage Pool
LOCHNESS_SERVER1>q pr Process Process Description Status Number -------- ------------------- ----------------------------------------------- 2 Backup Storage Pool Primary Pool TAPEDATA, Copy Pool OFFDATA, Files Backed Up: 6825, Bytes Backed Up: 954,088,410, Unreadable Files: 0, Unreadable Bytes: 0. IBM Tivoli Storage Manager Implementation Guide...
Page 631 Current Physical File (bytes): 24,179,840 Current input volume: 028AKK. Current output volume: 032AKK. tsm: LOCHNESS_SERVER1>q mount ANR8330I LTO volume 028AKK is mounted R/W in drive DR01 (mt1.0.0.2), status: IN USE. ANR8330I LTO volume 032AKK is mounted R/W in drive DR00 (mt0.0.0.2), status: IN USE.
Page 632 02/28/2006 13:31:24 ANR0514I Session 13 closed volume 036AKK. (SESSION: 13) 02/28/2006 13:31:24 ANR1214I Backup of primary storage pool DISKDIRS to copy storage pool OFFDIRS has ended. Files Backed Up: 5427, Bytes Backed Up: 3863586, Unreadable Files: 0, Unreadable Bytes: 0. (SESSION: 13) IBM Tivoli Storage Manager Implementation Guide...
Page 633: Backup Of Tivoli Storage Manager Database
19.3.2 Backup of Tivoli Storage Manager database After successfully backing up all primary storage pools, we can back up the Tivoli Storage Manager database. Using backup db, as shown in Example 19-18, we see the output from running the command in the foreground (wait=yes) and the activity log entries.
Page 634: Querying Dr Media
Example 19-19 shows how to tell which volumes are database backups. The query libvol output lists the database backups as 033AKK, 034AKK, and 037AKK. Therefore, the other DR media are copy pool tapes (032AKK and 036AKK). IBM Tivoli Storage Manager Implementation Guide...
Page 635: Send Disaster Recovery Media Off-Site
Before moving media off-site, we should check if any of the volumes are still mounted using query mount. If any are mounted, we dismount them with the dismount volume command, as shown in Example 19-20. Example 19-20 Dismounting a mounted volume tsm: LOCHNESS_SERVER1>query mount ANR8329I LTO volume 037AKK is mounted R/W in drive DR01 (mt1.0.0.2), status: IDLE.
Page 636 REMove=Yes option spawns a checkout libvolume for each volume, requiring an individual reply for each volume. If you have a small library with only a single slot entry/exit port, like our IBM 3582, you may wish to use REMove=No and manually export the tapes from the library’s front panel.
Page 637 We can check the media status once again with query drmedia, as shown in Example 19-22. (Note that only three of our five volumes are displayed.) Example 19-22 Querying DR media with format=detailed tsm: LOCHNESS_SERVER1>q drmedia f=d Volume Name: 032AKK State: Vault Last Update Date/Time: 02/28/2006 14:32:09 Location: Rocket Vault...
Page 638 IBM Tivoli 036AKK Storage Manager Storage Pools Server Back up Database LOCHNESS 037AKK Machinename: brazil Building: 6 Priority: 50 Move DR media VAULT Database Offsite Figure 19-3 Primary pool backup and server database backup IBM Tivoli Storage Manager Implementation Guide...
Page 639: Generate The Recovery Plan
19.3.5 Generate the recovery plan Now we are ready to generate the disaster recovery plan, as shown in Figure 19-4. Admin Client Copy DISASTER IBM Tivoli Storage Prepare Manager Server RECOVERY PLAN C:\TSMDATA\DRM\PLANS\LOCHNESS-DR. YYYYMMDD.HHMMSS Figure 19-4 Disaster recovery plan generation We generate the recovery plan using the prepare command, as shown in Example 19-23.
Page 640: Returning Expired Volumes
Send this list to the vault administrators so that they can gather the tapes for return to the primary location. When you are notified that the volumes have been given to the courier, you can change the state in DRM using: MOVE DRMedia * WHERESTATE=vaultretrieve IBM Tivoli Storage Manager Implementation Guide...
Page 641: Server Restore Setup
The media state is changed from VAULTRetrieve to COURIERRetrieve. When the courier has delivered the volumes to the primary location, change their state to ONSITERetrieve with the command: MOVE DRMedia * WHERESTATE=courierretrieve After changing the state to ONSITERetrieve the media no longer show when you use query drmedia.
Page 642: Obtain The Latest Dr Plan
Tivoli Storage Manager server when it was created. See 19.5.2, “Review the Tivoli Storage Manager macros” on page 616, and 19.4.3, “Install the operating system and the server” on page 613. IBM Tivoli Storage Manager Implementation Guide...
Page 643: Find A Replacement Server And Storage
19.4.2 Find a replacement server and storage The RECOVERY.INSTRUCTIONS.INSTALL stanza specifies local information on hardware required. The RECOVERY.DEVICES.REQUIRED stanza specifies the device type needed to read the backups. The SERVER.REQUIREMENTS stanza specifies the disk space required. 19.4.3 Install the operating system and the server Install the operating system and Tivoli Storage Manager server software on the replacement server.
Page 644 Example 19-25 Break out a DR plan on Windows C:\tsmdata\drm\plans> cscript planexpl.vbs recoveryplanfilename For AIX, the syntax is shown in Example 19-26. Example 19-26 Break out a DR plan on AIX root@Atlantic /tsm/drm/plans: awk -f planexpl.awk recoveryplanfilename IBM Tivoli Storage Manager Implementation Guide...
Page 645 For Sun Solaris, the syntax is shown in Example 19-27. Example 19-27 Break out a DR plan on Solaris root@Sol /tsm/drm/plans > nawk -f planexpl.awk recoveryplanfilename Example 19-28 shows the command output from breaking out the DR plan on the replacement server.
Page 646: Obtain The Recovery Volumes
You should review the macros contained in the recovery plan. It is possible that the volumes you have available may not be exactly the ones that the DR plan macros are expecting. For any number of reasons, volumes may still be in IBM Tivoli Storage Manager Implementation Guide...
Page 647 transit, or not yet picked up, and may have been destroyed in the disaster. Whatever the case, you need to examine and update the entries in the COPYSTGPOOL.VOLUMES.DESTROYED and COPYSTGPOOL.VOLUMES.AVAILABLE files, to reflect the current situation. If all primary volumes were destroyed, no changes are required to the PRIMARY.VOLUMES.DESTROYED script and Tivoli Storage Manager macro files.
Page 648: Review The Device Configuration
(for example, device special file names) must be updated in the device configuration file. Table 19-3 on page 619 shows the device configuration for the original and replacement machines. We can see that, as is commonly the case IBM Tivoli Storage Manager Implementation Guide...
Page 649 Tape drive mt1.0.0.2 Tape drive mt2.0.0.3 Although the IBM TS3310 is an automated library, we have to manually place the database backup volumes into the library, since there is no Tivoli Storage Manager server to check them in. We must then update the configuration information to identify the elements within the library where the volumes are located.
Page 650: Start The Restore Tivoli Storage Manager Server Scripts
ANR7800I DSMSERV generated at 09:43:13 on Dec 9 2005. Tivoli Storage Manager for Windows Version 5, Release 3, Level 2.2 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2004. All rights reserved. IBM Tivoli Storage Manager Implementation Guide...
Page 651 U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Allocated space for C:\TSMDATA\SERVER1\DB1.DSM: 1049624576 bytes. Allocated space for C:\TSMDATA\DBP\DBV_01.DSM: 1074790400 bytes. Allocated space for C:\TSMDATA\DBP\DBV_01.DSM: 1074790400 bytes. ANR0300I Recovery log format started; assigned capacity 1712 megabytes.
Page 652 (C) Copyright IBM Corporation 1990, 2004. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress.
Page 653 ANR1635I The server machine GUID, 5d.6f.87.21.95.0b.11.da.82.63.00.0d.60.49.6a- .62, has initialized. ANR2100I Activity log process has started. ANR4726I The NAS-NDMP support module has been loaded. ANR4726I The Centera support module has been loaded. ANR4726I The ServerFree support module has been loaded. ANR9969E Unable to open volume C:\TSMDATA\STG\DISKDATA\DDVOL_01.DSM. The most likely reason is that another TSM server is running and has the volume allocated.
Page 654 If you plan to stay for some time on the replacement Tivoli Storage Manager machine, you should recreate the primary storage pools and their volumes to IBM Tivoli Storage Manager Implementation Guide...
Page 655: Restore Primary Storage Pools
Example 19-37 Phase 2, defining volumes to the Tivoli Storage Manager server IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 2.0 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Chapter 19. Disaster Recovery Manager...
Page 656 IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 3, Level 2.0 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Session established with server LOCHNESS_SERVER1: Windows Server Version 5, Release 3, Level 2.2...
Page 657: Summary Of Example Disaster Recovery Plan
There are some excellent books on disaster recovery available. However, the IBM Redbook Disaster Recovery Strategies with Tivoli Storage Management, SG24-6844, is certainly one of the “must read” choices.
Page 658 Our next topic, Bare Machine Recovery, is similar, and we will discuss AIX and Windows system recovery. IBM Tivoli Storage Manager Implementation Guide...
Page 659: Chapter 20. Bare Machine Recovery
Chapter 20. In this chapter we describe Bare Machine Recovery (BMR) setup and processes for Windows and AIX systems. IBM Tivoli Storage Manager is designed to back up and recover application data. Recovering the operating system environment is not this product’s goal. That...
Page 660: Windows Bare Machine Recovery
Client system information can be imported into DRM (via scripts discussed in 20.1.3, “Store system information for DRM access” on page 633) or DRM administrators can be given access to system information IBM Tivoli Storage Manager Implementation Guide...
Page 661 collected into a text file and backed up by the Tivoli Storage Manager backup-archive client. The msinfo32 command The msinfo32 command is a feature of Windows that enables you to collect detailed system hardware and configuration data that can be used for problem determination.
Page 662 The sample batch file is shown in Example 20-3. Example 20-3 Batch file for saving machine information @echo off echo. echo SAVING MACHINE INFORMATION FOR DISASTER RECOVERY echo. IBM Tivoli Storage Manager Implementation Guide...
Page 663: Collect Partition And Logical Volume Information With Diskmap
c:\Progra~1\Common~1\Micros~1\MSInfo\msinfo32 /report c:\Progra~1\Tivoli\TSM\config\msinfo32.txt /categories +all cd c:\Progra~1\Tivoli\TSM\baclient dsmc sel c:\Progra~1\Tivoli\TSM\config\msinfo32.txt pause exit 20.1.2 Collect partition and logical volume information with diskmap The diskmap utility is a command-line disk mapping tool that allows users to view the partition and logical volume structures of the disks. It displays a map of the disk and produces a report about the disk’s configuration.
Page 664: Insert Client Machine Information Into Drm
We outline below how machine information can be inserted into DRM. We assume that the client machine is already defined as a DRM client machine (using the DEFINE MACHINE command). You can use the administrative IBM Tivoli Storage Manager Implementation Guide...
Page 665: Use Machchar.vbs To Insert Machine Reports Into Drm
command line or the Administration Center to insert the client’s machine information into DRM. Figure 20-1 shows how to use the Administration Center to insert client machine information. Figure 20-1 Insert machine characteristics using Admin Center Alternatively, you can insert machine information using the command line, as shown in Example 20-6.
Page 666 Machine information stored by DRM can also be included in the DRM plan file. This is the detailed disaster recovery file that is generated by the DRM PREPARE command. In order to include a machine’s system information or IBM Tivoli Storage Manager Implementation Guide...
Page 667 recovery instruction in the DRM plan file the defined system must be marked as adsmserver=yes on the UPDATE MACHINE command. Example 20-10 shows the command line to add our server to the DRM plan file. Example 20-10 Incorporating machine information in the DRM plan file update machine tripleeight adsmserver=yes The recovery plan file is arranged in stanzas.
Page 668: Windows Systems Additional Information
Summary BMR Procedures for Windows NT and Windows 2000 with ITSM, TIPS0102: http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/tips0102.html ?Open Using Microsoft Windows Automated System Recovery (ASR) to Recover Windows XP and Windows 2003 Systems with the IBM Tivoli Storage Manager Backup-Archive Client for Windows: http://www.ibm.com/support/entdocview.wss?uid=swg27003812 IBM Tivoli Storage Manager Implementation Guide...
Page 669: Using Sysback For Bare Machine Recovery
20.2 Using SysBack for Bare Machine Recovery In this section we explain how to use IBM Tivoli Storage Manager for System Backup and Recovery (also known as SysBack) for AIX. SysBack is a comprehensive system backup, restore, and reinstallation tool for AIX. It is simple to use and highly effective in partitioned or non-partitioned environments, as well as in a cluster environment composed of multiple pSeries systems.
Page 670 Special boot utilities These are for partitions functioning as SP nodes or IBM ^ Cluster 1600 systems. For customers whose partitions function as a part of an SP IBM Tivoli Storage Manager Implementation Guide...
Page 671: An Introduction To Sysback
IBM ^ Cluster 1600, SysBack has specific boot and install utilities to interact with Parallel System Support Program (PSSP). Quick, easy setup and use SysBack is SMIT menu driven and also enables complete command-line interaction. The most basic, initial configuration to perform a system backup takes a matter of moments.
Page 672 Pulling the backups from clients enables you to use a single machine or partition to act as a central backup server. You can script, schedule, and thereby automate all backups for an entire environment from a single location. IBM Tivoli Storage Manager Implementation Guide...
Page 673 There are 2-way and 3-way pull backups. A 2-way pull backup is when the same machine or partition initiates the client backup and stores the backup to media. Figure 20-2 illustrates the flow of a 2-way pull backup. 2-way Pull Backup The Initiator (server) initiates the backup on the Backup System (client), and then the Backup System sends its backup to the Initiator system (which also happens to be...
Page 674 This enables database users to have minimal downtime, because it is only required to halt the database while the mirrors are being split. After the backup completes, SysBack automatically resynchronizes the stale partitions while the database is active. IBM Tivoli Storage Manager Implementation Guide...
Page 675 Figure 20-4 depicts the relationship between mirrored copies after the Offline Mirror Backup feature splits them. Mirroring After Offline Mirror Split - Mirroring Before the Offline Mirror Ready for Backup of Offline Copy Backup Split Mirror Copy Offline Copy lv00 /test lv00 /test lv00 /test lv00copy00 /sbom/test...
Page 676 Recreate only the LVM structure of one or more file systems. Restore one or more individual logical volumes. Recreate only the LVM structure of one or more logical volumes. Restore individual files or directories. IBM Tivoli Storage Manager Implementation Guide...
Page 677: System Installation Options
20.2.2 System installation options SysBack provides the following installation options from a full system (installation image) backup: Full system installation This process reinstalls the system by recreating the rootvg volume group and, optionally, any non-rootvg volume groups. Recovery installation This process restores the system on the / (root) and /usr file systems after booting into maintenance mode.
Page 678: Network Boot
Note: AIX 5L Version 5.2 no longer supports the MCA or RSPC architectures. There are two types of SysBack network boots: Classic network boot NIM resource network boot IBM Tivoli Storage Manager Implementation Guide...
Page 679: Classic Network Boot Relationships
The classic network boot method relies on the / (root) and the /usr file systems of the boot server for creating the network boot image. The boot server also fulfills other processing requirements for the client during the boot and installation process.
Page 680: Multivolume Backup And Tape Device Support
Figure 20-7 NIM resource network boot relationships For customers whose partitions function as a part of an RS/6000® SP complex or an IBM ^ Cluster 1600, SysBack has specific boot and install utilities to interact with PSSP. For these utilities, SysBack utilizes existing NIM resources that are a default part of the SP or cluster configuration in order to provide a server-initiated network boot and install through the control workstation.
Page 681: Partition Backup, Recovery, And Cloning
The following examples demonstrate local and remote backups, partition recovery, and cloning. Other variations and options related to these procedures exist. Therefore, refer to the IBM Tivoli Storage Manager for System Backup and Recovery Installation and User’s Guide, along with product readme files, for more detailed information about any or all of these tasks.
Page 682 # /usr/sbin/sysback -f /dev/rmt0 datavg Note: There are several other options available for the /usr/sbin/sysback command. Refer to Appendix A, “Commands,” in the IBM Tivoli Storage Manager for System Backup and Recovery Installation and User’s Guide for more detailed information, available at: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.
Page 683 2. The partition boots to the SysBack Installation and Maintenance Main Menu. 3. Using the menus, make any needed changes to the LVM information. When finished, select the Install the System with Current Settings option. 4. The install proceeds without any further intervention. Once completed, the system login prompt opens.
Page 684 The backup will be created on the tape device (/dev/rmt0) on the server pluto. # /usr/sbin/sysback -h mars -f /dev/rmt0 datavg This backup can later be restored to the same or a different partition in the machine. IBM Tivoli Storage Manager Implementation Guide...
Page 685 Note: There are several other configurable options available for the /usr/sbin/sysback command. Refer to Appendix A, “Commands,” in the IBM Tivoli Storage Manager for System Backup and Recovery Installation and User’s Guide for more detailed information, available at: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com. ibm.itsmsbr.doc/bmrug565.htm...
Page 686 8. Press Esc to return to the main menu. 9. Select Install the System with Current Settings to begin the installation. 10.The install proceeds without any further intervention. Once completed, the system login prompt opens. IBM Tivoli Storage Manager Implementation Guide...
Page 687: Cloning Backup Images Between Partitions
20.2.7 Cloning backup images between partitions Cloning refers to creating a backup image of one machine or partition and installing a different machine or partition with that same image. This section demonstrates the basic tasks required to do the following operations: Identify resources that may need to be supported for the cloning process.
Page 688 However, should you want to run a different kernel and would like to use SysBack to switch the kernel for you during the cloning procedure, you must install both filesets on the source partition before creating the backup. IBM Tivoli Storage Manager Implementation Guide...
Page 689 Using a media device assigned to the same partition Local backups are backups that are performed to a device that is physically attached to the machine and, in this case, the partition. This type of backup is the easiest to implement. Figure 20-10 on page 659 illustrates the relationship between partitions and their respective backup devices for a cloning operation.
Page 690 For more information about how to change LVM information, refer to Chapter 11, “Changing the Volume Group, Logical Volume, and Filesystem Attributes,” in the IBM Tivoli Storage Manager for System Backup and Recovery Installation and User’s Guide, available at: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/c...
Page 691: Remote Backup, Remote Install, And Network Boot
The host name of the remote partition that has a DVD drive assigned to it is mars. – This is the partition from which the new partition is installed. Therefore, this partition is the install server to the new partition. –...
Page 692 Starting with Sysback V5.6.5.0, you can create backups with the UDF on DVD media when using AIX V5.2 and later. Issue the following command to use UDF format: # /usr/sbin/mksbcd -T “D” -t U -h mars -f /dev/cd1 -Z 2662 IBM Tivoli Storage Manager Implementation Guide...
Page 693 Note: A backup to CD/DVD has additional configuration requirements. There are also many additional flags, options, and potential considerations of the /usr/sbin/mksbcd command. For details about using this feature, refer to the /usr/lpp/sysback/README.udf.dvdcd.txt file. One-time network boot configuration To do a one-time network boot configuration, log in to pluto (boot server to the new partition) and execute the command /usr/sbin/mksbnetboot -h new_partition_hostname -d your_network_type -T chrp -k mp -S server_ip -g client_gateway -s client_subnet in order to define pluto as a network boot...
Page 694 For more information about how to change LVM information, refer to Chapter 11, “Changing the Volume Group, Logical Volume, and File system Attributes,” in the IBM Tivoli Storage Manager for System Backup and Recovery Installation and User’s Guide, available at: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/c...
Page 695: Cloning From A Stand-Alone System To A Partition
7. Press Esc to return to the main menu. Note: If you want to keep the same host name and network information as was defined on pluto in this new partition (for example, this new partition replaces pluto), you do not need to execute steps 8–12 below. Simply go to step 13.
Page 696: License Information
5.1–5.4. There are no license filesets for this version of SysBack. For detailed information related to licensing your product, refer to your product readme file located at /usr/lpp/sysback/README.txt or other documentation that accompanied your order. IBM Tivoli Storage Manager Implementation Guide...
Page 697: Documentation
Product manual readme file The manual The IBM Tivoli Storage Manager for System Backup and Recovery Installation and User's Guide is available in hardcopy and softcopy forms. Hardcopy versions of the order must be individually ordered. Softcopy versions are located at: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm...
Page 698 Hardware requirements SysBack supports the following hardware: IBM eServer pSeries and RS/6000 systems, including RS/6000 SP environments, and systems capable of the logical partitioning of AIX eServer pSeries Cluster 1600 systems using the PSSP option Software requirements The following software is required to use SysBack: AIX 5L V5.1, V5.2, or V5.3.
Page 699 If you will be using the Remote Services functions of SysBack, install the following items: – bos.rte.net – bos.net.tcp.client If you will be using the Classic Network Boot functions for the Network Installs, install bos.net.nfs.client. If you will be using the NIM Resource Network Boot functions for network installs, the NIM environment and resources must first be installed and configured in the desired locations for SysBack to use these resources.
Page 700: Basic Setup And Configuration Tasks
The password will be initialized when the Tivoli Storage Manager virtual device is created. If your password is already initialized, such as when you are using the same node name as your Tivoli Storage Manager IBM Tivoli Storage Manager Implementation Guide...
Page 701 Backup-Archive Client, it will be necessary for you to provide that password when creating the virtual device definition. Install the API client. You must install the V5.2.0 (or later) Tivoli Storage Manager 32-bit API client for use with SysBack operations. Configure the Tivoli Storage Manager options file.
Page 702: Creating A Tivoli Storage Manager Virtual Device
To access the Tivoli Storage Manager Virtual Device configuration menus: 1. Log in as the root user. 2. Type smitty sysback and press Enter. 3. Navigate TSM → TSM Virtual Device Configuration → Add a TSM Virtual Device and press Enter. IBM Tivoli Storage Manager Implementation Guide...
Page 703 Atlantic lochness | Esc+1=Help Esc+2=Refresh Esc+3=Cancel | Esc+8=Image Esc+0=Exit Enter=Do Es| /=Find n=Find Next Es+--------------------------------------------------------------------------+ Note: The list of IBM Tivoli Storage Manager server name stanzas is generated from the contents of the file /usr/tivoli/tsm/client/api/bin/dsm.sys. Chapter 20. Bare Machine Recovery...
Page 704 • Log in to the Tivoli Storage Manager server and issue the command update node nodename newpassword before attempting to create the TSM Virtual Device. Note: For more information regarding the update node command, refer to IBM Tivoli Storage Manager for AIX: Administrator’s Reference, GC32-0769. IBM Tivoli Storage Manager Implementation Guide...
Page 705: Configuring Network Boot Options For Bmr
tsm0 Example 20-14 shows that a virtual device called has been created. Example 20-14 Virtual device tsm0 created COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. Device tsm0 for TSM server lochness has been added. Esc+1=Help Esc+2=Refresh Esc+3=Cancel...
Page 706 Es+--------------------------------------------------------------------------+ Note: The SysBack network boot client definition is based on the host name of the client system. This may or may not be the same as the Tivoli Storage Manager client node name. IBM Tivoli Storage Manager Implementation Guide...
Page 707: Recovery And System Reinstallation From A Server
Example 20-16 shows the options set for the node we configured in the lab. Example 20-16 Set TSM network install client defaults Set TSM Network Install Client Defaults Type or select values in entry fields. Press Enter AFTER making all desired changes. [TOP] [Entry Fields] * Hostname...
Page 708 Once you have successfully executed a network boot, Example 20-17 shows the menu that will be displayed. Example 20-17 SysBack Installation And Maintenance menu +----------------------------------------------------------+ |IBM Tivoli Storage Manager for System Backup and Recovery | +----------------------------------------------------------+ +--------------------------------+ | Installation & Maintenence |...
Page 709 Select the desired network interface and press Enter to verify or change the network settings associated with this restore process. The screen shown in Example 20-20 will be displayed. Example 20-20 Change IBM Tivoli Storage Manager network settings menu +----------------------------------------------------------+ Change TSM Network Settings...
Page 710 Storage Manager server to obtain a list of backup objects available for restore. This is shown in Example 20-21. Example 20-21 Query the server and select the backup to restore +----------------------------------------------------------+ | IBM Tivoli Storage Manage for System Backup and Recovery +----------------------------------------------------------+ Backup ID Active...
Page 711: Chapter 21. Data Protection Configuration On The Server
IBM Tivoli Storage Manager provides support for online backup of applications through the use of complementary products such as IBM Tivoli Storage Manager for Applications, IBM Tivoli Storage Manager for Databases, IBM Tivoli Storage Manager for Enterprise Resource Planning, IBM Tivoli Storage Manager for Copy Services, IBM Tivoli Storage Manager for Advanced Copy Services, and IBM Tivoli Storage Manager for Mail.
Page 712: Basic Assumptions
Example 21-1 Define TDP management class and copygroups define mgmtclass STANDARD STANDARD TDP_CLASS tsm: ATLANTIC> ANR1520I Management class TDP_CLASS defined in policy domain STANDARD, set STANDARD. IBM Tivoli Storage Manager Implementation Guide...
Page 713: Defining A New Policy Domain
define copygroup STANDARD STANDARD TDP_CLASS type=backup tsm: ATLANTIC> verexists=7 verdeleted=2 retextra=30 retonly=60 dest=TAPEPOOL ANR1530I Backup copy group STANDARD defined in policy domain STANDARD, set STANDARD, management class TDP_CLASS. define copygroup STANDARD STANDARD TDP_CLASS type=archive tsm: ATLANTIC> retver=365 destination=tapepool ANR1535I Archive copy group STANDARD defined in policy domain STANDARD, set STANDARD, management class TDP_CLASS.
Page 714: Backing Up And Archiving Copygroup Considerations
The archive feature of the Tivoli Storage Manager backup-archive client can be used to perform operating system and file level backups of the application files. With archives, you can group files together to expire at the same time. If you IBM Tivoli Storage Manager Implementation Guide...
Page 715 choose to do this, pay attention to the archive copygroup that you are using. The archive copygroup will determine how long the objects will exist before expiring. There are also specific backup retention and version requirements for specific data protection modules. Table 21-1 summarizes the backup and archive copygroup requirements for each data protection module.
Page 716 Data Protection Set the following values so that deleted backups are Not required. for ESS immediately removed from server storage: (Oracle/DB2) verdeleted=0 Data Protection retonly=0 for DS and SVC (Oracle/DB2) IBM Tivoli Storage Manager Implementation Guide...
Page 717: Register Node
Data protection Backup copy group requirements Archive copy group module requirements Data Protection Not required. You must define a for mySAP (DB2 management class for SAP or Oracle) system data, data files, offline redo logs, and copies of offline redo logs. Data Protection for mySAP version uses its own...
Page 718: Server Configuration Considerations
Tivoli Storage Manager server to improve data protection backups and restores. Refer to the Data Protection module Installation and User’s Guide for more information. Informix To back up large Informix databases, edit the dsmserv.opt and increase commtimeout to about 300 and idletimeout to 30. IBM Tivoli Storage Manager Implementation Guide...
Page 719 Tivoli Storage Manager for Databases, Data Protection for MS SQL The collocate parameter for the storage pool assigned to the Data Protection for filespace the MS SQL client node should be set to to ensure that individual data stripes stay on separate removable volumes. The default value is no. Not doing so may require more operations to make the data for each stripe of a restore simultaneously accessible.
Page 720 IBM Tivoli Storage Manager Implementation Guide...
Page 721: Chapter 22. Tivoli Storage Manager Upgrade Considerations
Tivoli Storage Manager Chapter 22. upgrade considerations In this chapter we cover some upgrade procedures for IBM Tivoli Storage Manager environment. We describe both general considerations and specifics of upgrade procedures on AIX and Windows platforms. Linux, Solaris, and HP-UX are similar to the AIX procedures.
Page 722: General Upgrade Considerations
Storage Manager V5.3.x server. After this database upgrade, you can no longer run a previous version of the server with the database, so to revert to a previous version, you would have to restore the corresponding database. IBM Tivoli Storage Manager Implementation Guide...
Page 723: Chapter 22. Tivoli Storage Manager Upgrade Considerations
Windows clients that back up their system objects, you should take specific actions to clean up the orphaned system object entries in the database, For details see the IBM Support Web site at: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.ht FILE volumes and paths to FILE devices When the V5.3 server starts, existing FILE volumes in a FILLING state are...
Page 724: Clients And Data Protection Modules
The following Tivoli Storage Manager server operating systems supported in V5.2 were not migrated to V5.3 and are not supported in V5.3: OS/390 V2R10 and z/OS V1R1, V1R2, and V1R3 z/VM® (You may want to migrate your IBM Tivoli Storage Manager z/VM servers to Linux.) HP-UX 11.0 Red Hat Enterprise Linux Server 2.1...
Page 725 V5.2 and V5.3 command-line administrative clients can administer Tivoli Storage Manager V5.2 and V5.3 servers, and the V3.1 VM server. The Motif native GUI on UNIX clients was not migrated to V5.3. The Java GUI client should be used instead. Error log behavior change Beginning with V5.3, client applications will not run without a writable log.
Page 726 Tivoli Storage Manager servers. Macintosh 10.1, 10.2 Linux IA64 HP-UX 11.0 Linux Red Hat Advanced Server 2.1 SLES 7 NetWare 6.0 Solaris 7 OS/400 V5R1 (API client) OS/390 V2R10 and z/OS V1R1, V1R2, and V1R3 IBM Tivoli Storage Manager Implementation Guide...
Page 727: Storage Agent
Databases, which is supported in V5.2, was not migrated to V5.3 and is not supported in V5.3. The latest release of IBM Informix Dynamic Server (IDS) is automatically enabled to back up to Tivoli Storage Manager and does not require Tivoli Storage Manager for Databases.
Page 728: Server Quiesce
Note that if you already made the recommended changes to the server options file as described in the previous section, you should already have saved a copy of the file. 7. Halt your server instance. IBM Tivoli Storage Manager Implementation Guide...
Page 729: Upgrading The Server
22.2.3 Upgrading the server Once the server instance is halted, you may perform the upgrade. This procedure differs among platforms, since each supported operating system has its native way to install software packages. Nevertheless, one common approach applies to all platforms. When upgrading the server we distinguish between applying maintenance (base) and patch (fix) packages.
Page 730: Enabling Production Mode
Manager V5.2 server running on Windows 2003 and AIX 5.3 to the latest version available at the time of writing this book, which is 5.3.2.2. For more information, refer to the IBM Tivoli Storage Manager Installation Guide manual for your server platform.
Page 731: Migration On Windows
V5.3.2.2. Before upgrading our server, we checked V5.3 server-specific requirements and support on the Web site: http://www.ibm.com/support/docview.wss?rs=663&context=SSGSG7&uid=swg21064234&lo c=en_US&cs=utf-8&lang=en We used a Windows 2003 server with an IBM 3582 LTO library. Figure 22-1 shows the setup in our test environment. 9.43.86.82 DIOMEDE Windows 2003 TSM Server 5.2.7.0...
Page 732 Once you have finished the preparation phase, you may start the migration running the Tivoli Storage Manager setup wizard. Keep in mind that the base level (that is, 5.3.2) must be installed first, and then you may apply the patch (5.3.2.2). IBM Tivoli Storage Manager Implementation Guide...
Page 733 Also note that installation will be stopped and the error message shown in Figure 22-2 will display if a running server or Storage Agent process is detected. All active servers must be halted before installation can proceed. Figure 22-2 Migration failure due to running server process Generally, you should upgrade your server environment in the following sequence: 1.
Page 734 Basic Edition of the server tsmee.lic for the Extended edition of the server dataret.lic for the IBM System Storage Archive Manager The installation wizard will automatically perform conversion to the required license status, since it removes the license files first and subsequently installs a new license package.
Page 735 ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use. ANR8200I TCP/IP driver ready for connection with clients on port 1500. ANR2828I Server is licensed to support IBM System Storage Archive Manager. ANR2828I Server is licensed to support Tivoli Storage Manager Basic Edition.
Page 736 700. Finally, you should back up your storage pools and database and create a new disaster recovery plan file. Refer to the IBM Tivoli Storage Manager for Windows Administrator’s Guide, GC32-0782, for more information. IBM Tivoli Storage Manager Implementation Guide...
Page 737: Migration On Aix 5L
Our environment, as illustrated in Figure 22-6 on page 708, consists of an AIX 5.3 system called BANDA connected together with an IBM 3582 library to the SAN. The objective of the test is to describe the migration of Tivoli Storage Manager from V5.2.2.0 to V5.3.2.2.
Page 738 2 x LTO2 drives, CPF enabled Figure 22-6 AIX lab environment In any case, we recommend that you thoroughly check software and hardware requirements for Tivoli Storage Manager V5.3 on the IBM Web site: http://www.ibm.com/support/docview.wss?rs=663&context=SSGSG7&uid=swg21052220&lo c=en_US&cs=utf-8&lang=en Note: If installing Tivoli Storage Manager V5.3 on AIX V5.1, you must first upgrade the C++ Runtime for AIX to V6 (xlC.rte.6.0.0.0 and later).
Page 739 Otherwise, you can run the update library command with resetdrives=yes. More information about HACMP with Tivoli Storage Manager is in the chapter “High availability clustering” in IBM Tivoli Storage Management Concepts, SG24-4877. Chapter 22. Tivoli Storage Manager upgrade considerations...
Page 740 64-bit server filesets. If we had been using the 32-bit filesets in our 64-bit AIX kernel, we would have to uninstall those and install new appropriate filesets, as described in Table 22-1 on page 709. Example 22-3 IBM Tivoli Storage Manager Version 5.2.2.0 filesets on BANDA root@banda> lslpp -L | grep -i tivoli tivoli.tsm.devices.aix5.rte 5.2.2.0...
Page 741 Note: You do not have to record definitions for IBM 3494, 3570, 3575, 3590, LTO, and 3592-type devices. These devices use the IBM-supplied drivers, not the Tivoli Storage Manager device drivers and will not be affected by the upgrade. Also note that a migrate installation will not normally create a new database, recovery log, and storage pool volumes.
Page 742 IBM Tivoli Storage Manager tivoli.tsm.msg.en_US.devices 5.3.2.0 IBM Tivoli Storage Manager tivoli.tsm.msg.en_US.server 5.3.2.0 IBM Tivoli Storage Manager tivoli.tsm.server.aix5.rte64 5.3.2.0 IBM Tivoli Storage Manager 64 tivoli.tsm.server.com 5.3.2.0 IBM Tivoli Storage Manager tivoli.tsm.server.webcon 5.3.2.0 IBM Tivoli Storage Manager Web IBM Tivoli Storage Manager Implementation Guide...
Page 743 -L | grep -i tivoli tivoli.tsm.devices.acsls 5.3.2.2 IBM Tivoli Storage Manager tivoli.tsm.devices.aix5.rte 5.3.2.2 IBM Tivoli Storage Manager tivoli.tsm.license.aix5.rte64 5.3.2.0 IBM Tivoli Storage Manager 64 tivoli.tsm.license.cert 5.3.2.0 IBM Tivoli Storage Manager tivoli.tsm.loc.server.ela 5.3.2.0 IBM Tivoli Storage Manager tivoli.tsm.msg.en_US.devices 5.3.2.2 IBM Tivoli Storage Manager tivoli.tsm.msg.en_US.server...
Page 744 ANR0993I Server initialization complete. ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use. ANR2828I Server is licensed to support IBM System Storage Archive Manager. ANR2828I Server is licensed to support Tivoli Storage Manager Basic Edition. ANR2828I Server is licensed to support Tivoli Storage Manager Extended Edition.
Page 745: Performing Client Upgrades
22.4 Performing client upgrades In this section we discuss the steps for upgrading clients to V5.3.2 on AIX and Windows platforms. For more information, refer to the IBM Tivoli Storage Manager Backup-Archive Client Installation and User’s Manual for your platform.
Page 746: Aix 5L Client Upgrade
Our Banda machine has 32-bit 5.2.2 client filesets installed, as shown in Example 22-10. Example 22-10 Client V5.2.2 filesets root@banda> lslpp -L | grep -i tivoli | grep -iE “client|books” tivoli.tsm.books.en_US.client.htm tivoli.tsm.books.en_US.client.pdf tivoli.tsm.client.api.32bit tivoli.tsm.client.ba.32bit.base tivoli.tsm.client.ba.32bit.common tivoli.tsm.client.ba.32bit.image tivoli.tsm.client.ba.32bit.nas tivoli.tsm.client.ba.32bit.web IBM Tivoli Storage Manager Implementation Guide...
Page 747 If you try to install the JFS2 client over the old JFS client, your installation will fail, as illustrated in Example 22-11. Example 22-11 Client installation failure when installing JFS2 over JFS client Performing Pre-Installation tasks for the TSM API Client. #***************************************************************# tivoli.tsm.client.api.jfs2 and tivoli.tsm.client.api.32bit can not be installed together.
Page 748: Storage Agent Upgrade
Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 2.0 Client date/time: 03/01/06 14:42:33 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Node Name: BANDA Session established with server LOCHNESS_SERVER1: Windows Server Version 5, Release 3, Level 2.2...
Page 749: Windows 2003 Storage Agent Migration
Note: You do not have to record definitions for IBM 3494, 3570, 3575, LTO, and 3592-type devices. These devices use IBM-supplied drivers, not the Tivoli Storage Manager device drivers and will not be affected by the upgrade. 22.5.2 Windows 2003 Storage Agent migration The upgrade procedure is the same as an AIX Storage Agent migration.
Page 750 8. Once all data is migrated, you may delete the old storage pool definition. Analogous to tape library migration, you may set the migration on a single storage pool whose data resides on an old generation of tapes to another, new one. IBM Tivoli Storage Manager Implementation Guide...
Page 751: Part 5
In this part of the book we provide the following supplementary information: Appendix A, “Planning and sizing worksheets” on page 723 Appendix B, “Book support material: macros and scripts” on page 729 © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 752 IBM Tivoli Storage Manager Implementation Guide...
Page 753: Appendix A. Planning And Sizing Worksheets
In this appendix are the worksheets that we introduced and recommended in Chapter 1, “Implementation checklists” on page 3. The book support material is available in soft copy on the Internet from the IBM Redbooks Web server. Point your Web browser to: ftp://www.redbooks.ibm.com/redbooks/SG245416...
Page 754: Worksheets Grouped In Tables
Number of files archived Number of archives kept Archive frequency Archive window times Archive number of hours Number of image backups Image backup frequency Number of backup sets Backup set frequency Policy domain Client option set IBM Tivoli Storage Manager Implementation Guide...
Page 755 Table A-2 Storage policy requirements worksheet Category Example 1 Example 2 Example 3 Group name Number of backup versions Backup file retention period Number of deleted versions Last deleted file version retention period Archive retention period Off-site copies Onsite collocation Off-site collocation Image backup retention Backupset retention...
Page 756 Table A-5 Device configuration and volume history worksheet Category Size (MB) Total Table A-6 Total IBM Tivoli Storage Manager disk required worksheet Category Size (MB) IBM Tivoli Storage Manager software (dependent on platform) IBM Tivoli Storage Manager database IBM Tivoli Storage Manager recovery log...
Page 757 Number of off-site tape volumes Number of database volumes Number of scratch tapes Number of backupset tape volumes Total tape volumes required Table A-8 Administrator IDs worksheet Functions IBM Tivoli Storage Manager ID Authority Appendix A. Planning and sizing worksheets...
Page 758 IBM Tivoli Storage Manager Implementation Guide...
Page 759: Appendix B. Book Support Material: Macros And Scripts
This appendix contains listings of support material for this book. See section 1.1.1, “Our support material” on page 5, for considerations regarding this material. The book support material is available in soft copy on the Internet from the IBM Redbooks Web server. Point your Web browser to: ftp://www.redbooks.ibm.com/redbooks/SG245416 Alternatively, you can get to the same Web page at: http://www.redbooks.ibm.com...
Page 760: Macros
Support' grant authority support classes=system /*---------------------------------*/ /* System Reporting Administrators */ /*---------------------------------*/ register admin reporter reporter contact='System Reporting' /*-----------------------*/ /* Client Administrators */ /*-----------------------*/ register admin helpdesk helpdesk contact='Client Administrator' IBM Tivoli Storage Manager Implementation Guide...
Page 761: Define Client Option Sets
/* grant authority helpdesk classes=node node=* */ /* You first have to register client nodes for this command to succeed! */ /*--------------------------*/ /* Query all administrators */ /*--------------------------*/ query admin Define client option sets Example B-2 shows a Tivoli Storage Manager macro that contains the administrative commands to define our client option sets.
Page 762 "exclude *:\...\netlogon.chg" seq=2 define clientopt windows inclexcl "exclude *:\...\system32\config\...\*" seq=3 define clientopt windows inclexcl "exclude *:\...\ntuser.dat" seq=4 define clientopt windows inclexcl "exclude *:\...\ntuser.dat.log" seq=5 define clientopt windows inclexcl "exclude *:\...\temp\...\*" seq=6 IBM Tivoli Storage Manager Implementation Guide...
Page 763: Define Policy Structure
define clientopt windows inclexcl "exclude *:\...\cache\*" seq=7 define clientopt windows inclexcl "exclude *:\...\recycler\*" seq=8 define clientopt windows inclexcl "exclude *:\...\Temporary Internet Files\*" seq=9 define clientopt windows inclexcl "exclude *:\microsoft uam volume\...\*" seq=10 define clientopt windows inclexcl "exclude *:\ibmio.com" seq=11 define clientopt windows inclexcl "exclude *:\ibmdos.com" seq=12 define clientopt windows inclexcl "exclude *:\msdos.sys"...
Page 764 \ mode=modified serialization=shrstatic define copygroup workstn workstn directory type=Backup destination=DISKDIRS \ frequency=1 verexists=nolimit verdeleted=nolimit retextra=30 retonly=30 \ mode=modified serialization=shrstatic define copygroup workstn workstn special type=Backup destination=DISKDATA \ frequency=1 verexists=2 verdeleted=1 retextra=30 retonly=30 \ IBM Tivoli Storage Manager Implementation Guide...
Page 765: Define Schedules
mode=modified serialization=shrdynamic define copygroup workstn workstn image type=backup destination=diskdata \ frequency=1 verexists=2 verdeleted=2 retextra=30 retonly=30 \ mode=modified serialization=static define copygroup server server data type=Archive destination=DISKDATA \ retver=365 serialization=shrstatic define copygroup workstn workstn data type=Archive destination=DISKDATA \ retver=100 serialization=shrstatic /*----------------------*/ /* Validate policy sets */ /*----------------------*/ validate policyset server server validate policyset workstn workstn...
Page 766 SERVER domain" define schedule workstn workstn_nightly action=incremental starttime=22:00 duration=3 durunits=hours\ description="Nightly backup schedule for WORKSTN domain" define sched workstn monthly_image starttime=01:00 action=imagebackup object="C:" schedstyle=enhanced month=any weekofmonth=last dayofweek=friday description="Monthly image backup for workstations" /*--------------------------*/ IBM Tivoli Storage Manager Implementation Guide...
Page 767: Define Server Scripts
/* Query all schedules /*--------------------------*/ query schedule query schedule type=admin Define server scripts Example B-5 shows a Tivoli Storage Manager macro that contains the administrative commands to define our server scripts. Example: B-5 mac.scripts /*================================================================*/ /* Redbook Support Materials File - (mac.scripts) /* Getting Started with Tivoli Storage Manager - Implementation /* (SG24-5416) /* These scripts are supplied to help you implement a...
Page 768: Create Storage Pools
/* The MAXSCratch is set purposefully at a high value to avoid /* any misleading out of space messages. You may set it to a more */ /* meaningful value to better reflect the %util value of your /* pool when q stgpool is run. IBM Tivoli Storage Manager Implementation Guide...
Page 769: Delete Default Storage Pools
/* This file is designed to be run as an Administrative Command /* Line macro. You should use the -itemcommit parameter when you */ /* start the admin session, otherwise the macro could fail!! /*================================================================*/ define stgpool tapedata <<library device class name>> highmig=100 \ maxscratch=10000 collocate=no reclaim=100 reusedelay=1 define stgpool diskdata disk nextstgpool=tapedata highmig=70 lowmig=30 \ cache=no...
Page 770: Server Options Files
Example: B-8 AIX server options *=====================================================================* * Tivoli Server Options File - AIX Version - (dsmserv.aix) * Getting Started with Tivoli Storage Manager - Implementation * SG24-5416 *=====================================================================* *---------------* *Communications * *---------------* COMMMETHOD SHAREDMEM COMMMETHOD TCPIP IBM Tivoli Storage Manager Implementation Guide...
Page 771 SHMPort TCPNodelay TCPPort 1500 TCPADMINPort 1502 TCPWindowsize 2048 DNSLOOKUP MOVEBatchsize 1000 MOVESizethresh 2048 TXNGroupmax 1024 *--------------------------------------------* *Automated Cartridge System Library Software * *--------------------------------------------* *ACSACCESSID *ACSLOCKDRIVE *ACSQUICKINIT *ACSTIMEOUTX *---------------* * Client-Server * *---------------* COMMTIMEOUT IDLETIMEOUT RESOURCETIMEOUT *----------------* * Site Dependent * *----------------* DATEFORMAT LANGUAGE...
Page 772: Z/Os
* Tivoli Server Options File - zIS Version - (dsmserv.mvs) * Getting Started with Tivoli Storage Manager - Implementation * * SG24-5416 *===============================================================* *----------------* * Communications * *----------------* COMMMethod TCPIP TCPNodelay TCPPort 1500 TCPADMINPort 1502 IBM Tivoli Storage Manager Implementation Guide...
Page 773 TCPWindowsize 2048 DNSLOOKUP MOVEBatchsize 1000 MOVESizethresh 2048 TXNGroupmax 1024 TCPNAME TCPIP *---------------* * Client-Server * *---------------* COMMTIMEOUT IDLETIMEOUT RESOURCETIMEOUT *----------------* * Site Dependent * *----------------* DATEFORMAT LANGUAGE AMENG NUMBERFORMAT TIMEFORMAT *-------------------------* * Database & Recovery Log * *-------------------------* BUFPoolsize 262144 LOGPoolsize 10240 SELFTUNEBUFPOOLSIZE...
Page 774: Windows
* Getting Started with Tivoli Storage Manager - Implementation (SG24-5416) *==========================================================* *---------------* *Communications * *---------------* COMMMethod NAMEDPIPE COMMMethod TCPIP NAMEDpipename \\.\PIPE\TSMPIPE NPBUFfersize TCPNodelay TCPPort 1500 TCPADMINPort 1502 TCPWindowsize DNSLOOKUP MOVEBatchsize 1000 MOVESizethresh 2048 TXNGroupmax 1024 *---------------* * Client-Server * *---------------* IBM Tivoli Storage Manager Implementation Guide...
Page 775 COMMTimeout IDLETimeout RESOURCETimeout10 *----------------* * Site Dependent * *----------------* DATEformat LANGuage AMENG NUMberformat TIMEformat MAXSessions *-------------------------* * Database & Recovery Log * *-------------------------* BUFPoolsize 262144 SELFTUNEBUFpoolsize LOGPoolsize 10240 MIRRORRead DB Normal MIRRORRead LOG Normal MIRRORWrite DB Sequential MIRRORWrite LOG Sequential DBPAGEShadow DBPAGESHADOWFile "dbpgshdw.bdt"...
Page 776: Client Options Files
<<DSM.OPT Stanza name here (not hostname!!!)>> * Communications. NODename <<Client node name here>> COMMMethod TCPIP TCPBuffsize TCPNodelay TCPPort 1500 TCPServeraddress <<TSM Server Hostname here>> TCPWindowsize DISKBuffsize 1023 *------------* * Operations * *------------* COMPRESSIon ERRORLOGName "dsmerror.log" ERRORLOGRetention SCHEDLOGName "dsmsched.log" SCHEDLOGRetention IBM Tivoli Storage Manager Implementation Guide...
Page 777: Netware
PASSWORDAccess Generate SCHEDMODe Prompted MANAGEDServices Schedule Webclient *-----------------* * Include/Exclude * *-----------------* *None - specified via the Client Option Set (AIX) instead Client user options file Example B-12 shows our client user options file for AIX. This file can also be used as the basis for a client user options file for the HP/UX and Solaris platforms.
Page 778 Schedule Webclient NWPWFile NWUSer <<Servername\user:password must be FQ>> *----------------* * Site Dependent * *----------------* DATEFORMAT LANGUAGE AMENG NUMBERFORMAT TIMEFORMAT SUbdir *-----------------* * Include/Exclude * *-----------------* *None - specified via the Client Option Set (NETWARE) instead IBM Tivoli Storage Manager Implementation Guide...
Page 779: Windows
Windows Example B-14 shows our client options file for Windows. Example: B-14 Windows client options file *=====================================================================* * Redbook Client Options File - Windows Version (dsm.opt) * Getting Started with Tivoli Storage Manager - Implementation * SG24-5416 *=====================================================================* *----------------* * Communications * *----------------* NODename <<Client node name here>>...
Page 780 IBM Tivoli Storage Manager Implementation Guide...
Page 781: Glossary
SANs, and networks with dissimilar protocols. Disk group A set of disk drives that have been configured into one or more logical unit numbers. This term is used with RAID devices. © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 782 HBA See host bus adapter. data between computer devices at a data rate of up to 1 Gb. It is especially suited for connecting computer servers to shared storage devices and for interconnecting storage controllers and drives. IBM Tivoli Storage Manager Implementation Guide...
Page 783 SCSI device. For up to 126 nodes into a logical loop. All disk subsystems such as the IBM Enterprise connected nodes share the bandwidth of this Storage Server, a LUN is a logical disk drive.
Page 784 Protocols can determine low-level supports arbitrated loop devices. details of machine-to-machine interfaces, such as the order in which bits from a byte are sent. They can also determine high-level exchanges between application programs, such as file transfer. IBM Tivoli Storage Manager Implementation Guide...
Page 785 SNMP See Simple Network Management Protocol. RAID Redundant array of inexpensive or SNMP agent An implementation of a independent disks. A method of configuring network management application that is multiple disk drives in a storage subsystem for resident on a managed system. Each node high availability and high performance.
Page 786 TCP See Transmission Control Protocol. TCP/IP Transmission Control For more information about IBM terminology, Protocol/Internet Protocol. see the IBM Storage Glossary of Terms at: http://www.storage.ibm.com/glossary.htm Topology An interconnection scheme that allows multiple Fibre Channel ports to communicate. For example, point-to-point,...
Page 787: Abbreviations And Acronyms
Computer Emergency Response Team ASCII American National Standard Code for Common Gateway Information Interface Interchange CHAP Challenge Handshake Asynchronous Terminal Authentication Emulation CIDR Classless InterDomain Asynchronous Transfer Routing Mode © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 788 Resource Manager Exchange ESCON® Enterprise System DDNS Dynamic Domain Connection Name System Encapsulating Security Directory Enabled Payload Network Enterprise Storage Data Encryption Server Standard EUID Effective User Identifier Distributed File System File Allocation Table IBM Tivoli Storage Manager Implementation Guide...
Page 789 Fibre Channel Hierarchical Storage Management FDDI Fiber Distributed Data Interface HTTP Hypertext Transfer Protocol FDPR Feedback Directed Program Restructure International Business Machines Corporation Fast EtherChannel technology ICCM Inter-Client Conventions Manual FIFO First In/First Out Integrated Drive FIRST Forum of Incident Electronics Response and Security Interface Definition...
Page 790 Managed Object Class Log File Service Library (Windows NT) MPTN Multi-protocol Logical File System Transport Network (AIX) MS-DOS Microsoft Disk Low Function Terminal Operating System JNDI Java Naming and MSCS Microsoft Cluster Directory Interface™ Server IBM Tivoli Storage Manager Implementation Guide...
Page 791 Maximum Segment NSAPI Netscape Commerce Size Server's Application Modular Storage NTFS NT File System Server NTLDR NT Loader Mirror Write NTLM NT LAN Manager Consistency Network Time Protocol Network Attached NTVDM NT Virtual DOS Storage Machine Network Buffer Cache NVRAM Non-Volatile Random NetBEUI Frame Access Memory...
Page 792 Power-On Self Test RRIP Rock Ridge Internet Physical Partition Protocol Point-to-Point Protocol RSCT Reliable Scalable PPTP Point-to-Point Cluster Technology Tunneling Protocol Removable Storage PReP PowerPC® Reference Management Platform® RSVP Resource Reservation Persistent Storage Protocol Manager IBM Tivoli Storage Manager Implementation Guide...
Page 793 SACK Selective Security Reference Acknowledgments Monitor Secure Attention Key Serial Storage Architecture Security Account Manager Secure Sockets Layer Storage Area Network SUSP System Use Sharing Protocol SASL Simple Authentication and Security Layer Serviceability SCSI Small Computer TAPI Telephone Application System Interface Program Interface Software Developer's Trusted Computing...
Page 794 X/Open Portability Identifier Guide VIPA Virtual IP Address Virtual Memory Manager Virtual Processor Vital Product Data Virtual Private Network VRMF Version, Release, Modification, Fix VSM™ Virtual System Management World Wide Web Consortium Wide Area Network IBM Tivoli Storage Manager Implementation Guide...
Page 795: Related Publications
Using Tivoli Storage Manager to Back Up Lotus Notes, SG24-4534 Disaster Recovery Strategies with Tivoli Storage Management, SG24-6844 Get More Out of Your SAN with IBM Tivoli Storage Manager, SG24-6687 Backing up WebSphere Application Server with Tivoli Storage Management, REDP-0149...
Page 796: Other Publications
Storage Manager, SG24-6117 IBM Tivoli Storage Manager in a Clustered Environment, SG24-6679 Tivoli Storage Management Reporting, SG24-6109 Using the System Storage N Series with IBM Tivoli Storage Manager, SG24-7243 Other publications These publications are also relevant as further information sources: IBM Tivoli Storage Manager for AIX Quick Start V5.3, GC32-0770...
Page 797 GC32-0794 IBM Tivoli Storage Manager Using the Application Program Interface V5.3, GC32-0793 IBM Tivoli Storage Manager for System Backup and Recovery - 5.6 - Installation and User's Guide, GC32-9076 Tivoli SANergy - 2.2.4 - Administrator's Guide, GC32-0740 IBM Tivoli Storage Manager for Application Servers: Data Protection for WebSphere Application Server Installation and User’s Guide, SC32-9075...
Page 798: Online Resources
IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise Storage Server Databases (Oracle) Installation and User’s Guide, SC32-9061 IBM Tivoli Storage Manager for Hardware: Data Protection for IBM ESS for R/3 Installation and User’s Guide for DB2 UDB, SC33-8204 IBM Tivoli Storage Manager for Hardware: Data Protection for IBM ESS for R/3 Installation and User’s Guide for Oracle, SC33-8205...
Page 799 IBM Tivoli Storage Manager HSM for Windows http://www.ibm.com/software/tivoli/products/storage-mgr-hsm/ IBM Tivoli Storage Manager for Storage Area Networks http://www.ibm.com/software/tivoli/products/storage-mgr-san IBM Tivoli Storage Manager for System Backup and Recovery http://www.ibm.com/software/tivoli/products/storage-mgr-sysback IBM TotalStorage Productivity Center for Fabric http://www.ibm.com/software/tivoli/products/totalstorage-fabric/ IBM TotalStorage Productivity Center for Data http://www.ibm.com/software/tivoli/products/totalstorage-data/...
Page 800: How To Get Ibm Redbooks
Performance Management Guide http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp IBM Storage Media Product Selector http://www.storage.ibm.com/media/products.html Tape and Optical Storage http://www.ibm.com/servers/storage/tape IBM HP-UX Tape and Medium Changer Device Driver (ATDD) - readme file ftp://ftp.software.ibm.com/storage/devdrvr/HPUX/README IBM Developer Kit for AIX, Java Technology Edition http://www.ibm.com/developerworks/java/jdk/aix/index.html QLogic Technical Support http://www.qlogic.com/support/home_support.asp International Organization for Standardization http://www.iso.ch...
Page 801: Ibm Redbooks Collections
IBM Redbooks collections Redbooks are also available on CD-ROMs. Click the CD-ROMs button on the Redbooks Web site for information about all the CD-ROMs offered, as well as updates and formats. Related publications...
Page 802 IBM Tivoli Storage Manager Implementation Guide...
Page 803 DELETE FILESPACE command 280, 296 QUERY SESSION command 425 DELETE STGPOOL command 238 QUERY STATUS command 93, 197, 402, 405 DELETE VOLHISTORY command 381, 445 QUERY STGPOOL command 420 © Copyright IBM Corp. 1999, 2000, 2003, 2006. All rights reserved.
Page 804 246 considerations 285 AUDIT LICENSES command 385 create 287 automatic library 223 delete 290 automatic start scheduler 178 display 289 environment 284–285 export 455 backup ID worksheet 59 database 210 password change 290 IBM Tivoli Storage Manager Implementation Guide...
Page 805 image tapes 55 DSM_CONFIG variable 114 journal based incremental 517 DSM_DIR variable 114 LAN-free 526 DSM_LOG variable 114 objects 467 EXCLUDE option 119 tape calculation 54 exclude rules 331 trigger 198 granting node authority to administrator 295 backup copy group 274, 277 GUI 172 assigning files to backup copy group 119 INCLEXCL option 119...
Page 806 293 operations 12 most to another domain 281 planning 7 register 293 server implementation 8 storage utilization 417 CHECKOUT LIBVOLUME command 436, 443 working with 292 checkout volume 253 client option set 298 IBM Tivoli Storage Manager Implementation Guide...
Page 807 adding options to set 300 client scheduler 149, 173, 371, 386 associating client node 301 automatic start 178 associating node with set 301 manual start 174 create 300 stopping 180 default environment 299 UNIX 176 defining set 300 Windows 176 delete 302 Windows 2000 179 deleting set 302...
Page 808 QUERY VOLUME 262, 384, 421, 435, 439 control path failover 527 REGISTER LICENSE 591 COPY CLOPTSET command 300 REGISTER NODE 291–292 copy group 269, 274 REMOVE ADMIN 290 define 275 REMOVE NODE 280 display 277 IBM Tivoli Storage Manager Implementation Guide...
Page 809 serialization 275 default management class 119, 273 copy storage pool 237, 377 default server settings 94 CPF 527 define customization 91 recovery log 192 define administrative schedule 374 DEFINE ASSOCIATION command 387 DEFINE CLIENTOPT command 300 data changed DEFINE CLOPTSET command 300 percentage 20 define copy group 275 data compression 21...
Page 810 225 ENABLE EVENTS command 407 RECOVERY.INSTRUCTIONS.OFFSITE 595 encryption 693 RECOVERY.INSTRUCTIONS.STGPOOL 595 enhanced scheduling 372, 389 RECOVERY.SCRIPT.DISASTER.RECOV- environment 5 ERY.MODE 611, 620 environment data 16 RECOVERY.SCRIPT.NORMAL.MODE 611 environment variables for client 113 RECOVERY.SCRIPT.NORMAL.MODE.CMD IBM Tivoli Storage Manager Implementation Guide...
Page 811 383, 610 IBM ^ Cluster 1600 650 expire inventory 282, 504 IBM SAN Data Gateway 590 expiry interval 282, 698 IBM Tivoli Data Protection see TDP. export IBM Tivoli Enterprise Console 453 administrator information 455 IBM Tivoli Storage Manager 630...
Page 812 72 notification filters 161 server installation commands 73 service properties 163 server installation packages 72 journal-based backup 128, 328, 517 server startup 76 uninstalling the server 78 LAN-free 69, 526 normal mode 196 IBM Tivoli Storage Manager Implementation Guide...
Page 813 rollforward mode 197 performing client upgrades 715 Logical Volume Backup 16–17, 273 performing server upgrades 700 Logical Volume Snapshot Agent 344 TSM 691 logmode 502 Windows 2000 client upgrade 715 loop mode of command line interface 170, 321 Windows 2000 server upgrade 701 LVSA 344, 579 migration threshold 382 minfree 516...
Page 814 Web client 120 tape busses 511 PASSWORDACCESS 170, 179 tape devices 513 PASSWORDACCESS GENERATE 175 TCPBUFFSIZE option 504, 508 PASSWORDACCESS, client option 117, 120 TCPNODELAY option 504, 509 path 223, 552 TCPWINDOWSIZE option 509 IBM Tivoli Storage Manager Implementation Guide...
Page 815 tracing 488 transactions 501 QUERY ACTLOG command 422, 446 TXNBYTELIMIT option 506 QUERY ADMIN command 285, 289 TXNGROUPMAX option 501 QUERY AUDITOCCUPANCY command 385, 417 USELARGEBUFFER options 503 QUERY DB command 414 versioning 497 QUERY DBBACKUPTRIGGER command 199 performance tracing 492 QUERY DBVOLUME command 415 Performing 715 QUERY DEVCLASS command 212...
Page 816 REPLACE, client option 118 define administrative 374 reporting defining server script 378 operational reporting 412 disable 698 reset drive 530 enhanced 372, 389 RESET LOGCONSUMPTION command 198 execution location 371 resetdrives 530 log file 485 RESOURCEUTILIZATION 507–508 IBM Tivoli Storage Manager Implementation Guide...
Page 817 offsite backup 377 starting the program 397 pre and post commands 485 stopping the program 401 recommended scheduled operations 373 supported platforms 30 recommended schedules 375 tracing 492 server-prompted 116–117 transaction 506, 513 verify 392 VOLUMEHISTORY option 380 wheel of life 373 server architecture 30 SCHEDULE command 175 capacity 32...
Page 818 239 tsmdlst 548 storage statistics 385 storage policy requirement 26 structured query language archive retention period 28 See SQL backup file retention period 27 SUBDIR, client option 118 backup set retention 30 subfilebackup 344 IBM Tivoli Storage Manager Implementation Guide...
Page 819 subfilecachepath 344 backup calculation 54 subfilecachesize 344 considerations 50 SVC 512 control path failover 527 SysBack 639 database volumes 56 AIX client 667 device driver 613 AIX recovery and system reinstallation 677 devices 52 backup options 641 drive configuration 51 bare machine recovery 639 expired 610 central managed backups 642...
Page 820 CLI 170 define copygroup 275 client GUI 172 define dbcopy 205 console 321 define dbvolume 189–190 database 188 define drive 225 database backup 211 define grpmember 471 database recovery 196 define library 222 IBM Tivoli Storage Manager Implementation Guide...
Page 821 define logcopy 206 tsmjbbd.ini 517 define mgmtclass 273 TSMSCSI 613 define path 224 tuning methodology 481 define policy 272 TXNBYTELIMIT 506, 513 define policyset 272 TXNGROUPMAX 501, 506, 513 define schedule 387 define server 461 define servergroup 471 UNIX define stgpool 232–234 archive examples 360 define volume 239 backup examples 329...
Page 822 Windows Removable Storage Manager see RSM. client acceptor 183 wizard 82–83, 109, 120 service stop 184 worksheets 5, 18, 26, 48–49, 51, 59–60, 723 web service 141 WORM 218 wheel of life 373 WWN 225 IBM Tivoli Storage Manager Implementation Guide...
Page 823 z/OS tape management 58 zOS 200 Index...
Page 824 IBM Tivoli Storage Manager Implementation Guide...
Page 828: Back Cover
SUPPORT your job easier ORGANIZATION You will learn how to implement and operate IBM Tivoli Storage Manager. You should already have a conceptual See features for new understanding of Tivoli Storage Manager. We show you how...

This manual is also suitable for:

Tivoli storage manager

IBM E16RMLL-I - Tivoli Storage Manager Implementation Manual

Figures

Notices

Preface

Part 1. Introduction

Chapter 1. Implementation Checklists

Chapter 2. Implementation Planning

Part 2. Installation

Chapter 3. Server Installation

Chapter 4. Backup-Archive Client Installation

Chapter 5. Database and Recovery Log

Chapter 6. Data Storage

Chapter 7. Data Storage Policies

Chapter 8. Managing Tivoli Storage Manager

Chapter 9. Licensing

Chapter 10. Administrative Client

Quick Links

Front cover

Related Manuals for IBM E16RMLL-I - Tivoli Storage Manager

Summary of Contents for IBM E16RMLL-I - Tivoli Storage Manager