SG 247031
SG 247031
Use BRMS and IBM Tivoli Storage Manager for the most
complete iSeries-based multiplatform protection
Jim Cook
Dan Johansson
Steve Mann
Edelgard Schittko
Bradley Smoley
ibm.com/redbooks
International Technical Support Organization
December 2003
SG24-7031-00
Note: Before using this information and the product it supports, read the information in “Notices” on
page ix.
This edition applies to Version 5 Release 2 of Backup Recovery and Media Services for iSeries (5722-BR1)
and Version 5.1.5 and Version 5.2 of IBM Tivoli Storage Manager for OS/400 Portable Application Solutions
Environment (PASE) Server (5698-ISX).
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Part 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration . . . . 53
5.1 Starting and stopping the IBM Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . 54
5.1.1 Starting and ending the IBM Tivoli Storage Manager server for the first time. . . . 54
5.1.2 Starting IBM Tivoli Storage Manager server in batch mode . . . . . . . . . . . . . . . . . 55
5.2 IBM Tivoli Storage Manager administration interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.2.1 IBM Tivoli Storage Manager Web administrative client interface . . . . . . . . . . . . . 56
5.3 IBM Tivoli Storage Manager server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.3.1 Changing the default admin password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.3.2 Changing IBM Tivoli Storage Manager Web administrative client interface time-out
value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.3.3 Registering IBM Tivoli Storage Manager licenses . . . . . . . . . . . . . . . . . . . . . . . . 63
5.3.4 Querying IBM Tivoli Storage Manager licensed information . . . . . . . . . . . . . . . . . 65
5.3.5 Creating an IFS file structure for IBM Tivoli Storage Manager . . . . . . . . . . . . . . . 66
5.3.6 Increasing the IBM Tivoli Storage Manager database size. . . . . . . . . . . . . . . . . . 66
5.3.7 Increasing the IBM Tivoli Storage Manager recovery log size . . . . . . . . . . . . . . . 72
5.3.8 Removing the IBM Tivoli Storage Manager default database volume . . . . . . . . . 74
5.3.9 Removing the IBM Tivoli Storage Manager default recovery log volume . . . . . . . 75
5.3.10 IBM Tivoli Storage Manager server option file . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5.3.11 IBM Tivoli Storage Manager server run-time options . . . . . . . . . . . . . . . . . . . . . 77
5.3.12 IBM Tivoli Storage Manager disk storage pools . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.3.13 Increasing the IBM Tivoli Storage Manager BACKUPPOOL size. . . . . . . . . . . . 79
5.3.14 Removing the IBM Tivoli Storage Manager initial BACKUPPOOL volume. . . . . 82
5.4 Verifying the IBM Tivoli Storage Manager server is working. . . . . . . . . . . . . . . . . . . . . 83
5.4.1 Registering an IBM Tivoli Storage Manager client node to the IBM Tivoli Storage
Manager server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
5.4.2 Downloading the IBM Tivoli Storage Manager Windows client. . . . . . . . . . . . . . . 84
5.4.3 Installing the IBM Tivoli Storage Manager Windows client . . . . . . . . . . . . . . . . . . 84
5.4.4 Configuring the IBM Tivoli Storage Manager Windows client . . . . . . . . . . . . . . . . 85
5.4.5 Backing up using the IBM Tivoli Storage Manager Windows client . . . . . . . . . . . 89
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for
production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.1 Setting the correct time zone for OS/400 PASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
6.1.1 Adding an environment variable for the OS/400 PASE time zone . . . . . . . . . . . . 94
6.1.2 Restarting the IBM Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . . . 95
6.1.3 Accepting new IBM Tivoli Storage Manager server time, enabling sessions . . . . 95
6.2 IBM Tivoli Storage Manager and BRMS tape library management. . . . . . . . . . . . . . . . 97
6.2.1 IBM Tivoli Storage Manager and BRMS tape library overview . . . . . . . . . . . . . . . 97
6.2.2 Creating IBM Tivoli Storage Manager and BRMS exit programs . . . . . . . . . . . . . 98
6.2.3 Registering the IBM Tivoli Storage Manager exit programs . . . . . . . . . . . . . . . . . 98
6.2.4 Defining the IBM Tivoli Storage Manager USRDFN tape library. . . . . . . . . . . . . . 99
6.2.5 Defining the device class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
iv Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6.2.6 Verifying the IBM Tivoli Storage Manager and BRMS exit programs . . . . . . . . . 103
6.2.7 Sharing a common media pool between IBM Tivoli Storage Manager, BRMS. . 104
6.3 IBM Tivoli Storage Manager advanced storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
6.3.1 Overview of IBM Tivoli Storage Manager storage. . . . . . . . . . . . . . . . . . . . . . . . 105
6.3.2 Storage pool migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.3.3 Collocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.3.4 Reclamation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.3.5 Creating a sequential access storage pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.3.6 Updating the disk storage pool to migrate to tape. . . . . . . . . . . . . . . . . . . . . . . . 110
6.3.7 Creating a copy storage pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
6.3.8 IBM Tivoli Storage Manager disk storage pool performance improvements. . . . 112
6.4 IBM Tivoli Storage Manager policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
6.4.1 IBM Tivoli Storage Manager policy overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
6.4.2 Updating the default backup copy group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
6.4.3 Validating and activating copy group changes . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.5 IBM Tivoli Storage Manager daily maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
6.5.1 Creating a daily maintenance script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
6.5.2 Scheduling a daily maintenance script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.5.3 Scheduling disk storage pool migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.5.4 Scheduling reclamation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.5.5 Querying administrative command schedules . . . . . . . . . . . . . . . . . . . . . . . . . . 122
6.6 Disaster recovery requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
6.6.1 Backing up IBM Tivoli Storage Manager storage pools . . . . . . . . . . . . . . . . . . . 123
6.6.2 IBM Tivoli Storage Manager recovery log mode . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.6.3 IBM Tivoli Storage Manager database backup . . . . . . . . . . . . . . . . . . . . . . . . . . 124
6.6.4 Additional IBM Tivoli Storage Manager server recovery files . . . . . . . . . . . . . . . 125
6.6.5 Reusing delay for copy storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.6.6 Mirroring IBM Tivoli Storage Manager database and recovery log volumes. . . . 128
6.6.7 IBM Tivoli Storage Manager server backup with BRMS . . . . . . . . . . . . . . . . . . . 128
6.6.8 Disaster Recover Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Contents v
8.1.9 New (expired) volume or appending to one containing active data . . . . . . . . . . 172
8.1.10 Text fields are searchable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
8.1.11 Other tasks you should do . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
8.1.12 BRMS and journaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
8.1.13 BRMS environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
8.1.14 Functional usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
8.2 Performing a system backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
8.2.1 Using BRMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
8.2.2 System backup outside BRMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
8.2.3 Using SAVSTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
8.3 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
8.3.1 Saving your recovery reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
8.3.2 Making sure everything works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
8.3.3 Removing deleted records from BRMS inventory . . . . . . . . . . . . . . . . . . . . . . . . 178
8.4 Disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
8.4.1 Files in wrong order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
8.5 Creating media classes or media pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
8.6 Creating a media class (pool) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
8.7 Adding media to the pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
8.7.1 Adding media using a tape library device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
8.7.2 Removing media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
8.7.3 Manually adding media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
8.8 Save scenario examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
8.8.1 IBM Tivoli Storage Manager server example . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
8.8.2 Saving native OS/400 data to an IBM Tivoli Storage Manager server . . . . . . . . 198
8.9 Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
8.9.1 Creating locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
8.10 Move policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
8.10.1 Creating a move policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
8.10.2 Attaching the move policy to the backup policies . . . . . . . . . . . . . . . . . . . . . . . 221
8.11 Running a save of your ITSM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
8.12 Running a native data backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
8.13 Finding your backup job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
8.14 Restore scenario examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
8.14.1 Restoring the IBM Tivoli Storage Manager server environment . . . . . . . . . . . . 230
8.14.2 Restoring native OS/400 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
8.14.3 Finding your restore results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services
Application Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
9.1 Setting up the IBM Tivoli Storage Manager server for BRMS to use IBM Tivoli Storage
Manager APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
9.2 Setting up the BRMS environment for backup and restore to an IBM Tivoli Storage
Manager server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
9.2.1 First steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
9.2.2 Follow on steps using the 5250 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
9.2.3 Follow-on steps using iSeries Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
9.3 Save scenario example: Saving to an IBM Tivoli Storage Manager server . . . . . . . . 277
9.3.1 Using the 5250 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
9.3.2 Using BRMS iSeries Navigator client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
9.4 Restore scenario example: Restoring from an IBM Tivoli Storage Manager server . . 299
9.4.1 Using 5250 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
9.4.2 Using BRMS iSeries Navigator client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
vi Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
9.5 Full iSeries backup and restore on the BRMS Application Client . . . . . . . . . . . . . . . . 312
9.5.1 Full backup for system AS02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
9.5.2 Full system backup restore considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
9.6 Save-while-active implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
9.7 Setting up IBM Tivoli Storage Manager password management . . . . . . . . . . . . . . . . 327
9.8 Performance expectations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Part 4. Advanced topics for Backup Recovery and Media Services, IBM Tivoli Storage Manager . . 335
Chapter 10. Backup Recovery and Media Services movement of IBM Tivoli Storage
Manager media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
10.1 Sample programs for IBM Tivoli Storage Manager, BRMS media movement . . . . . 338
10.2 Configuring BRMS for IBM Tivoli Storage Manager media movement . . . . . . . . . . . 339
10.2.1 Creating a new BRMS location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
10.2.2 Creating a new BRMS move policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
10.3 IBM Tivoli Storage Manager volume status before running STRMNTTSM. . . . . . . . 340
10.4 Running the STRMNTTSM command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Chapter 12. Troubleshooting IBM Tivoli Storage Manager for OS/400 PASE . . . . . . 357
12.1 IBM Tivoli Storage Manager activity log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
12.2 Using the IBM Tivoli Storage Manager help command . . . . . . . . . . . . . . . . . . . . . . . 359
12.3 IBM Tivoli Storage Manager message format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
12.4 Forcing the IBM Tivoli Storage Manager server to end. . . . . . . . . . . . . . . . . . . . . . . 362
12.4.1 Ending IBM Tivoli Storage Manager from within OS/400 PASE . . . . . . . . . . . . 362
12.4.2 Ending the IBM Tivoli Storage Manager server for OS/400 PASE with the ENDJOB
command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
12.4.3 Ending the IBM Tivoli Storage Manager server for OS/400 PASE with the
ENDJOBABN command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
12.5 Displaying your IBM Tivoli Storage Manager server configuration . . . . . . . . . . . . . . 364
12.6 IBM Tivoli Storage Manager support Web page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Contents vii
Adding a new administrator to IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . 403
Sample code for the RUNTSMCMD command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Ending the IBM Tivoli Storage Manager server from a batch program . . . . . . . . . . . . . 404
Sample code for the STRMNTTSM command and programs . . . . . . . . . . . . . . . . . . . . . . 404
Sample code for STRMNTTSM program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Sample code for the STRMNTTSM command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Sample code for the TSMDBBOFF program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Sample code for the TSMVOLON program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Sample code for the TSMCPYOFF program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Sample code for the MOVMEDTSM program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
viii Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product, program, or service that does not
infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not give you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such provisions are
inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring
any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and
distribute these sample programs in any form without payment to IBM for the purposes of developing, using,
marketing, or distributing application programs conforming to IBM's application programming interfaces.
Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other
countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic
Transaction LLC.
Other company, product, and service names may be trademarks or service marks of others.
x Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Preface
IBM® Backup Recovery and Media Services (BRMS) for the IBM Eserver iSeries™ server
is the strategic solution for managing backup, recovery, media, and storage in an iSeries-only
environment. IBM Tivoli® Storage Manager server and client products are the IBM tools that
correspond to backup, recovery, media, and storage management functions in a
heterogeneous (multiplatform) environment. IBM offers a unique integrated solution by
combining the proven performance of BRMS on the iSeries server with the multiplatform
capabilities of IBM Tivoli Storage Manager.
In a multiplatform environment that includes iSeries servers, you can use the two products
independently of each other. However, by integrating the two products, you achieve a much
more powerful set of capabilities to back up and recover your mission-critical data and
applications.
Based on iSeries V5R2 BRMS and V5.2 of IBM Tivoli Storage Manager, this IBM Redbook
provides:
An overview of BRMS and IBM Tivoli Storage Manager terminology, constructs, and
capabilities
Cookbook examples to get BRMS and IBM Tivoli Storage Manager server up and running
on your iSeries server, as well as to set up your iSeries server as the BRMS Application
Client to an IBM Tivoli Storage Manager server running on the iSeries server
Troubleshooting guidance and tips for integrating BRMS and IBM Tivoli Storage Manager
server on the iSeries server
“As is” iSeries user programs and OS/400® commands to enable an iSeries system
operator to manage integrated BRMS and IBM Tivoli Storage Manager server functions
through a single user interface
Jim Cook is a Senior Software Engineer at the ITSO, Rochester Center. He leads teams that
produce iSeries Announcement presentation sets that are maintained on the iSeries and
support Web sites and presented at ITSO iSeries Forums internationally. Jim also produces
IBM Redbooks™ about OS/400 topics.
Dan Johansson is an Senior Technical Support Specialist working for IBM in Sweden. He
has over 30 years of computer experience, including 25 years working within IBM midrange
computer systems. He was part of the 1403 team sent to Germany to transfer IBM printer
manufacturing to Sweden. Dan has assisted and led several BRMS installations both with and
without IBM Tivoli Storage Manager. He is currently providing customers with overall iSeries
assistance at the Support Center. He has a degree in mechanical engineering.
Steve Mann is an iSeries Advisory I/T Specialist working for IBM Switzerland. He has 14
years experience in working with the AS/400® and iSeries servers. He is both an IBM
Certified Solutions Expert for iSeries and a Certified Tivoli Storage Manager consultant. His
areas of expertise include logical partitioning planning and implementation, system
management, BRMS, IBM Tivoli Storage Manager, and system recovery. He has extensive
Edelgard Schittko is an iSeries Advisory I/T Specialist working for iSeries Technical Sales
Support in IBM Germany. She has 12 years of experience in working with the AS/400 and
iSeries in midrange customer and large customer environments. She has been with IBM for
over 13 years, working with BRMS since 1994. Her areas of expertise include iSeries and
Storage Area Network, iSeries and tape libraries, and iSeries backup and recovery with and
without BRMS. Edelgard coauthored the first edition of the redbook Backup, Recovery, and
Media Services for OS/400: A Practical Approach, SG24-4840. She holds a degree in
mathematics from Humboldt University in Berlin, Germany.
Bradley Smoley is a Staff Software Engineer in Rochester, MN. He has over six years of
experience in the save and restore and BRMS field. He holds a degree in business computer
information systems from Saint Cloud State University, in MN. His areas of expertise include
BRMS, integrated file system (IFS), save and restore, program temporary fixes (PTFs), and
installation. He has written articles about BRMS and general save and restore topics for
iSeries Newsletter and iSeries Magazine.
xii Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
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 and/or
customers.
Your efforts will help increase product acceptance and customer satisfaction. As a bonus,
you'll develop a network of contacts in IBM development labs, and increase your productivity
and marketability.
Find out more about the residency program, browse the residency index, and apply online at:
ibm.com/redbooks/residencies.html
Comments welcome
Your comments are important to us!
We want our Redbooks to be as helpful as possible. Send us your comments about this or
other Redbooks in one of the following ways:
Use the online Contact us review redbook form found at:
ibm.com/redbooks
Send your comments in an Internet note to:
[email protected]
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. JLU Building 107-2
3605 Highway 52N
Rochester, Minnesota 55901-7829
Preface xiii
xiv Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Part 1
Part 1 Overview
This part presents a general overview of iSeries server and backup and recovery
considerations for the attached workstations. This includes on overview of the two products
addressed in this redbook:
Backup Recovery and Media Services, OS/400 V5R2 (5722-BR1)
Tivoli Storage Manager V5.2 (5698-ISX)
IBM Tivoli Storage Manager has had an iSeries product for years that, in general, supported
up to its version 3.1 capabilities. iSeries customers running this software level are integrating
IBM Tivoli Storage Manager capabilities with the “BRMS client to IBM Tivoli Storage
Manager” capabilities.
Over time, however, continued enhancements in the IBM Tivoli Storage Manager set of
products was not included into AS/400 or iSeries versions. In large multiplatform
environments, BRMS often became the iSeries-only backup recovery tool. Newer versions of
IBM Tivoli Storage Manage server and client products were used on non-iSeries platforms.
With the availability of IBM Tivoli Storage Manager Version 5.1.5 (and IBM Tivoli Storage
Manager Version 5.2) for OS/400 Portable Application Solutions Environment (PASE), the
large common set of functions is now available on all IBM Tivoli Storage Manager products.
IBM offers a rich integrated solution that gives you the most powerful recovery procedures
available.
This book also provides an overview of BRMS and IBM Tivoli Storage Manager on iSeries
terminology and capabilities. It provides sufficient examples for you to install and set up
(configure) these products. It also provides save and restore examples, using OS/400 library
and IFS objects.
Prior to reading this redbook, you must have sufficient knowledge to use the OS/400
command interface, its Windows® operating system-based graphical user interface (GUI)
This redbook provides “cookbook-oriented” information to enable you to get these products
up and running on your iSeries server. You achieve this by using V5R2 iSeries BRMS
together with IBM Tivoli Storage Manager Version 5.2 for OS/400 PASE. This gives you a
comprehensive storage management capability in your iSeries environment.
With the focus on cookbook content, detailed coverage of BRMS and IBM Tivoli Storage
Manager for OS/400 PASE capabilities is beyond the scope of this redbook. You must have
access and refer to the following documents, as well as to IBM education courses and other
sources, for both products that deliver this coverage:
IBM Tivoli Storage Management Concepts, SG24-4877
Backup Recovery and Media Services for OS/400: A Practical Approach, SG24-4840
Backup Recovery and Media Services for iSeries, SC41-5345
IBM Tivoli Storage Manager Implementation Guide, SG24-5416
A Practical Guide to Implementing Tivoli Storage Manager on AS/400, SG24-5472
SG24-5472 is based on IBM Tivoli Storage Manager Version 3.1. However, it thoroughly
covers IBM Tivoli Storage Manager terminology and constructs on AS/400 (iSeries), an
overview of AS/400 (iSeries) architecture (such as object terminology, the library, and IFS
structure), and the OS/400 command interface. Read this redbook for more background
information about the iSeries server and general Tivoli Storage Manager on iSeries
capabilities and to see sample backup scenarios.
Tivoli Storage Manager Version 5.1 Technical Guide, SG24-6554
This book covers IBM Tivoli Storage Manager Version 5 capabilities on all platforms.
Backup Recovery and Media Services for OS/400: More Practical Information, REDP0508
IBM Tivoli Storage Manager for OS/400 PASE Administrator’s Guide, GC23-4694
IBM Tivoli Storage Manager for OS/400 PASE - Administrator’s Reference Guide,
GC23-4695
IBM Tivoli Storage Manager for OS/400 PASE Quick Start, GC23-4696
We recommend that you also participate in a BRMS or IBM Tivoli Storage Manager IBM
education course if you are new to either of these products. See “Education” on page 12, for
more information about IBM education in this area.
4 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Notes:
You can divide an iSeries server into logical partitions (LPAR). All references to an
iSeries server in this redbook relate to a system with no partitions or a single partition
within that system running OS/400.
Throughout this redbook, we use the acronym TSM at times when the software
interface uses TSM as a parameter.
6 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
– Using the Tivoli Storage Manager APIs for BRMS, you can configure your iSeries
server to run BRMS as an iSeries BRMS Application Client to perform save and restore
functions to any IBM Tivoli Storage Manager server product.
All of this is possible to any IBM Tivoli Storage Manager server product, including the IBM
Tivoli Storage Manager for OS/400 PASE server.
Running the IBM Tivoli Storage Manager server on the iSeries also means that you have tape
and disk resources available in your iSeries server. When you use both BRMS and IBM Tivoli
Storage Manager with these tape devices, you must plan and configure appropriately your
tape management procedures.
You may have enough tape drive resources to let IBM Tivoli Storage Manager and BRMS run
in parallel with separate devices or your need to share the same tape devices. You can
schedule each product’s use of a shared device so that, when one product is finished using
the device, it is available for use.
You can use BRMS as an IBM Tivoli Storage Manager tape manager, which allows BRMS to
handle IBM Tivoli Storage Manager’s tape inventory. When you use BRMS and IBM Tivoli
Storage Manager on the same system, we recommend that you have BRMS perform all tape
management. To do this, you must have defined the IBM Tivoli Storage Manager tape
BRMS does the mounting, demounting, and expiring of volumes on request from IBM Tivoli
Storage Manager.
Figure 1-1 shows the set of IBM Tivoli Storage Manager server and client products through
December 2003.
IBM
AIX
OS/400
BULL DIGITAL Linux zSeries
DPX/2 OpenVMS TANDEM HEWLETT- OpenEdition MVS MICROSOFT
PACKARD Windows 98
300 zOS
B.O.S.
NAS
NDMP
(SSSI)
Tru64
Guardian
(ETI)
HP-UX Linux pSeries
Windows ME
Windows XP
Supported Networks
DPX/20 Linux iSeries
APPLE
Windows NT Server/WS
Windows 2000
APPC
Macintosh
Windows 2003 IPX/SPX
Named pipes
DB2
Shared memory
NOVELL
TCP/IP
INFORMIX
Tivoli Storage Manager Client Platforms NetWare
3270 emulation
LOTUS
DOMINO
MICROSOFT
z/VM
Exchange LINUX Linux
Server ORACLE Red Hat
NUMA-Q
SQL Server
SAP IBM ESS DYNIX/PTX
SuSE OS/400
TurboLinux
R/3 SYBASE WebSphere SUN SILICON DB2 z/OS
(BMC) Application Solaris GRAPHICS DB2/R3
ITSM for Mail SunOS IRIX with
Server FlashCopy AIX
Lotus Notes on AIX
Solaris
Lotus Notes on Windows NT
HP-UX
Domino on AIX ITSM for ERP
Backup Restore Interface (BACKINT) Windows
Domino on Windows NT 2000 and
for Oracle
Microsoft Exchange Server 2003 Disk
IBM CommonStore
ITSM for Databases Optical
Support for Informix, MS SQL Server,
Microsoft SQL Server DB2
Tape
Oracle Backup on AIX ITSM for Hardware
Oracle Backup on HP-UX IBM ESS
Tivoi Storage
Oracle Backup on Sun Solaris Manager Storage Hierarchy
ITSM for Application Servers
Informix
Websphere Application Server
Servers
IBM DB2 (included in DB2)
Figure 1-1 Summary of IBM Tivoli Storage Manager server and client products
http://www-3.ibm.com/software/tivoli/products/storage-mgr/platforms.html
8 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Examples of user objects are OS/400 user profiles and any object in most OS/400 libraries
and Integrated File System folders/directories. Examples of system objects include OS/400
and iSeries microcode, and objects needed by the operating system residing in special
OS/400 libraries, such as QSYS and QSYS2.
From a backup and recovery viewpoint, the primary distinctions between system and user
data are:
To save most system data, your iSeries server must be in a restricted state.
In a disaster recovery process, you must have much of the system data restored first to
restore any user data.
See 2.3, “Differences between user data and system data” on page 23, for more complete
information about these two types of data. As implemented in OS/400 V5R2, the IBM Tivoli
Storage Manager server cannot run in the iSeries restricted state. Therefore, IBM Tivoli
Storage Manager alone cannot be used exclusively to back up a complete iSeries server.
OS/400 IFS
You can use the IFS to assist you with the backup examples shown later in this redbook. You
can also use it to plan your backup and recovery process.
All data, programs (except microcode), and other OS/400 objects are stored within the IFS
libraries or folders and directories. The IFS enables the iSeries to support several different file
systems that can be stored and used within the iSeries server. Much of the OS/400 interface
accesses objects within the library or QSYS.lib file system. Other supported files systems are
the UNIX-like and Windows operating system-like hierarchy of directories (folders) with which
many are familiar.
QSYS.lib appears within the directory or folder hierarchy as a higher level directory.
Note: With all data and objects stored in the OS/400 IFS, saving the entire IFS is not
sufficient to back up the entire iSeries server. Certain OS/400 save functions are required
for specific sets of system data (such as system configuration data) to enable a full system
save. This is sufficient for a disaster recovery.
The iSeries server offers the Work with Links (WRKLNK) command interface and an iSeries
Navigator interface to the IFS. Figure 1-2 shows two windows of an IFS structure on one of
the iSeries server used for this redbook.
In the left pane, notice the QSYS.lib directory and the Root directory. Expanding QSYS.lib
shows all the OS/400 libraries on the system. Expanding Root in the left pane shows, in the
right pane, many directories, such as QIBM. These directories have many subdirectories that
include directories for cross-platform product software, such as HTTP Server for iSeries
powered by Apache and WebSphere® Application Server Version n.n.
In the right pane, we expanded the tsmvol directory to display its subdirectories. The directory
names should be familiar to those of you who have used IBM Tivoli Storage Manager before.
Consider a Windows operating system that is installed on an Integrated xSeries® Server for
iSeries (formerly called the Integrated Netfinity® Server) hardware feature. In this case, the
IFS contains directories that have an iSeries network storage object that defines the Windows
operating system and any virtual disks used by the Windows operating system. You can also
see, within the IFS directory structure, the associated objects used by a Linux guest partition.
For example, directory QNTC contains a directory used by Windows 2003 if it is installed on
an Integrated xSeries Server. You must vary on the associated OS/400 network storage
object to access this directory.
For special customer-determined reasons, specific disk drives can be assigned to a specific
ASP, pool numbers 2 through nnn. Objects are placed into one of the user disk pools, and any
associated data is restricted to the assigned disk devices. Object data placed within a
non-system ASP cannot normally overflow into disks outside an ASP.
10 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
ASP so that the associated disk arms are never moved by requests for other objects, such
as OS/400 code, or other data used by other applications.
The system ASP and any dependent ASPs are considered part of *SYSBAS. Any data
within *SYSBAS, assuming acceptable OS/400 object authority, is accessible by any
system function or application on the system.
Private disk pool (independent ASP (IASP)): Similar to dependent disk pools, disk
devices are assigned to an IASP. An IASP must be varied on for its resources to be
accessible. There are two primary purposes for placing objects and associated data into
an IASP:
– Partition objects with the same name, and perhaps the same library, into separate
name spaces so that a form of consolidation onto the same iSeries server or partition
can be implemented without moving to LPAR configurations.
Objects and data created or restored into an IASP normally remain in the partition and
cannot be accessed by normal application access requests. the OS/400 Set ASP
Group (SETASPGRP) command or a job description Initial ASP Group (INASPGRP)
parameter can identify the IASP to use. Assuming normal OS/400 object access
authority, the application can access the objects within *SYSBAS and the specified
IASP.
– Partition objects on disks within a physical input/output (I/O) tower (or within an iSeries
I/O processor (IOP) within LPAR partitions) to be switchable between systems or
partitions. This is used as a way to implement a form of limited high availability
between configured iSeries servers. You use OS/400 commands or iSeries Navigator
to vary off the IASP, switch the IASP from one system to the other, and vary on the
switched IASP on the receiving system. After a few minutes, the switched I/O hardware
and data are available to applications on the receiving system.
"ITSM Client" ITSM Client Version 5.2 IBM 3584 with 12 attached
OS/400 V5R2 Windows 2000 OS/400 V5R2 LTO Ultrium2 drives, three
BRMS with ITSM Backup and BRMS connected to AS27 via
ITSM APIs V5.2 Archive Client V5.2 OS/400 PASE Fibre Channel
SAN
Switch
2109 SAN
LAN
Location A Location B
Figure 1-3 System setup
1.3 Education
As mentioned earlier, you should have sufficient knowledge about the iSeries server, its
Operations Navigator client, and some basic skill for using BRMS and IBM Tivoli Storage
Manager.
For those of you who are new to either BRMS or ITSM, we recommend that you contact IBM
Education and register for BRMS class AS28 and the IBM Tivoli Storage Manager
implementation class TS572. You should also consider taking the following IBM BRMS and
Tivoli education courses.
For more information, go to the following Web site and select iSeries and AS/400:
http://www-3.ibm.com/services/learning/index2.html
For IBM Tivoli Storage Manager classes, the following courses are available:
5.1.5 for iSeries (self-paced)
IBM Tivoli Storage Manager 5.2 Automating Client Operations (self-paced)
IBM Tivoli Storage Manager 5.2 Configuring the Client and Managing Client Data
(self-paced)
IBM Tivoli Storage Manager 5.2 Defining Policies; Configuring Database and Recovery
Log Volumes (self-paced)
IBM Tivoli Storage Manager 5.2 Implementation (classroom)
IBM Tivoli Storage Manager 5.2 Monitoring and Event Logging, Plus Protecting the
Database (self-paced)
IBM Tivoli Storage Manager 5.2 Overview and Installation (self-paced)
IBM Tivoli Storage Manager 5.2 Total Integration (classroom)
http://www-3.ibm.com/software/tivoli/education/edu_prd.html
12 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
1.4 Organization of this redbook
To facilitate your use of this redbook, review the following outline:
Part 1: Overview
– Introduction to integration
– BRMS general overview
– IBM Tivoli Storage Manager general overview
Part 2: Tivoli Manager details
– Installing IBM Tivoli Storage Manager as a server on iSeries server
– Basic server configuration
– Getting the IBM Tivoli Storage Manager server into production mode
Part 3: Backup, Recovery, and Media Services details
– Installing and setting up BRMS
– Getting BRMS into production mode
– Setting up the iSeries BRMS Application Client to use the IBM Tivoli Storage Manager
as a server
There is no IBM Tivoli Storage Manager Backup and Archive Client for iSeries.
However, with the use of BRMS-provided Tivoli Storage Manager APIs and
documentation in this redbook, you can perform iSeries-oriented backup and archive
functions to an IBM Tivoli Storage Manager server.
Part 4: BRMS and IBM Tivoli Storage Manager advanced topics
The advanced topics focus on getting these products up and running, rather than how to
use the most advanced capabilities of these two products. The topics that are covered
include:
– BRMS movement of IBM Tivoli Storage Manager media
This chapter contains “as is” programs that provide a single iSeries interface to control
IBM Tivoli Storage Manager movement of media through BRMS. The movement is
based on sample interface programs which are not supported by IBM. They provide a
single interface to the user, rather than requiring the use of separate interfaces for
BRMS and IBM Tivoli Storage Manager.
– Backup Recovery and Media Services troubleshooting
– IBM Tivoli Storage Manager troubleshooting
Part 5: Appendixes
– General backup and recovery considerations
– Backup Recovery and Media Services reports
BRMS reports are invaluable when actually performing a recovery process on an
iSeries server.
– AIX administrative client in OS/400 PASE and sample programs
There is no IBM Tivoli Storage Manager administrative client function on the iSeries
server. However, this appendix shows how to use IBM AIX-based IBM Tivoli Storage
Manager administrative client software under OS/400 PASE to perform corresponding
administrative client functions. Sample programs are provided “as is”, although they
are already in use in actual customer environments. iSeries source programs are
provided for modification to specific customer requirements.
You can perform attended or unattended backups and schedule backups using the native
OS/400 job scheduler or the Advanced Job Scheduler (5722JS1). BRMS gives you the ability
to control subsystems, job queues, the signing off of interactive users, initial program loads
(IPLs) and other work-management type operations. It automatically records what is saved
and the physical location of the tapes that contain the data. It also provides detailed reports
with instructions that explain how to recover your system.
Figure 2-1 shows a typical flow of how BRMS implements your backup and recovery solution.
16 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
BRMS process requirements Policies
supported through policies for:
iSeries
Delete
Archived Media Backup
Copies Interim Inventory Interim Copies
Save Files Save Files
BRMS contains default values so you can begin using it immediately or you can customize
your backups to fit your backup strategy. There are two interfaces to BRMS:
5250 interface (green screen): Within this client, there are two ways to navigate around
within BRMS as explained in 2.1.1, “5250 emulation interface” on page 18.
BRMS iSeries Navigator client interface: See 2.1.2, “BRMS iSeries Navigator client” on
page 21, for more information.
There are some differences between the 5250 interface and BRMS iSeries Navigator client.
Within the BRMS iSeries Navigator client, you can set policy properties to perform functions
that you cannot set using control group attributes through the 5250 interface, including:
Ending integrated Windows servers before backup.
Ending hosted logical partitions before backup. Through V5R2, a hosted partition runs
Linux with access to a set of input/output (I/O) devices shared and a hosting OS/400
partition.
Unmounting of user-defined file systems (UDFS) before backup.
Starting integrated Windows servers after backup.
Starting hosted logical partitions after backup.
You cannot perform some functions on the 5250 emulation interface with the BRMS iSeries
Navigator client:
Advanced functions, such as hierarchical storage management
BRMS network support
Deletion of the BRMS configuration of the IBM Tivoli Storage Manager application
programming interfaces (APIs)
Table 2-1 Terminology differences between BRMS 5250 and iSeries Navigator client interfaces
BRMS iSeries Definition
Navigator client term
Backup history A list that contains information about each object saved as part of a backup done with BRMS.
The backup history includes any items backed up using a backup policy. In the 5250 emulation
interface, this is media information.
Backup policy A group of defaults that controls what information is backed up, how it is backed up, and where
it is backed up. A backup policy in iSeries Navigator is a combination of a backup control group
and a media policy in the 5250 emulation interface.
Global policy Settings that are used, in conjuction with values you specify in your backup policies, to enable
properties you to control how BRMS operates in your environment. In the 5250 emulation interface, this
is known as a system policy.
Media pool A grouping of media by similar characteristics, such as density or capacity. In the 5250
emulation interface, this is a known as a media class.
18 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
BRMS Backup Recovery and Media Services for iSeries
System: AS02
Select one of the following:
1. Media management
2. Backup
3. Archive
4. Recovery
5. Migration
10. Scheduling
11. Policy administration
12. Reports
Selection or command
===> 2
BRMBKU Backup
System: AS02
Select one of the following:
1. Backup planning
2. Perform backup
3. Display backup activity
4. Start console monitor
Selection or command
===> 1
Selection or command
===> 2
You now see the Work with Backup Control Group display (Figure 2-5). It lists all of the control
groups.
Bottom
F3=Exit F5=Refresh F7=Work with BRM scheduled jobs
F9=Change backup policy F23=More options F24=More keys
You can access this same display using the Work with Control Groups (WRKCTLGBRM)
command. If you need to see a list of all BRMS commands, you can issue the GO CMDBRM
command. From the BRMS Commands display (Figure 2-6), you enter the WRKCTLGBRM
command. This takes you to the Work with Backup Control Group display which is the same
as the one shown in Figure 2-5.
20 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
CMDBRM BRMS Commands
System: AS02
Select one of the following:
Table 2-2 lists some of the more frequently used BRMS commands.
WRKPCYBRM Allows you to work with different BRMS policies (med, arc, bku, mov, mgr, rcy,
rtv, sys)
WRKCLSBRM Allows you to work with or create media classes within BRMS
WRKDEVBRM Allows you to work with devices that BRMS knows about
WRKLNKBRM allows you to work with objects that were saved within the IFS
WRKLBRM Allows you to work with or create save lists within BRMS
After you successfully install the BRMS plug-in, you are ready to use the BRMS iSeries
Navigator client. For example, in iSeries Navigator (Figure 2-7), expand server name (in
which you installed the BRMS plug-in)-> Backup Recovery and Media Services-> Backup
Policies. Then you see a list of the BRMS backup policies in the right pane.
Note: For complete information about the BRMS iSeries Navigator client, see the student
guide located on the Web at:
http://www-1.ibm.com/servers/eserver/iseries/service/brms/pdf/
StudentGuide52.pdf
22 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
– You can use the SAVLIBBRM command to save to a save file using the SAVF
parameter. Note that *SAVF in not a valid value for the DEV (Device) parameter on the
SAVLIBBRM command. You can specify DEV(*NONE) and then SAVF(save-file
-name) on this command to save to the named save file.
– You can use the Save a Save File BRMS (SAVSAVFBRM) command to save a save file
to a tape device. If you use the Display Tape command later on the media containing
the saved save file, the media appears as though the save was performed by the
SAVLIB command and not the SAVSAVFBRM command.
Physical media
Physical media is the most popular type of media used with BRMS. It is used because
BRMS has the function to control tape libraries, making backups almost operator free.
BRMS supports all media that is supported by OS/400, excluding DVD and optical. Among
the tape device types that are supported are *MLR3, *SLR100, *QIC4GB, *QIC4DC,
*QIC5010, *SLR7, *ULTRIUM1, *ULTRIUM2, *FMT3590H, *FMT3590E, *FMT3590,
*QIC120, *QIC150, *QIC525, *QIC1000, *QIC2GB, *QIC2DC, *FMT3570, *FMT3570E,
*FMT3480, and *FMT3490E.
IBM Tivoli Storage Manager server
IBM developed IBM Tivoli Storage Manager APIs for iSeries (LPP 5733-197). BRMS
integrates the functions provided by the IBM Tivoli Storage Manager APIs. When the APIs
are installed with BRMS, you can configure the iSeries server as the BRMS Application
Client to use an IBM Tivoli Storage Manager server as a device for saving and restore user
data. The IBM Tivoli Storage Manager server manages the storage of the saved data until
BRMS requests the data to be restored or deleted from the IBM Tivoli Storage Manager
server.
The other main difference between user data and system data is that, to save most system
data, your iSeries server must be in a restricted state. This means that you must end all
subsystems (SBS) and you need to run on the main console to issue any commands. For
We recommend that you always perform a full system save. We realize that doing a full
system save everyday is not an option for most customers, so we list some examples of save
strategies that you can use:
Use BRMS to perform a full system save. This is the best and most secure option if a
disaster occurs.
Create a user control group to tailor your backups.
– Perform a full system save on the weekend and then save your user data every night.
– Perform a full system backup once a month and perform a full save of your user data
once a week. Then do incremental saves of your user data everyday.
– Remember most system data does not change unless you upgrade or install program
temporary fixes (PTFs), so saving it once a month may be sufficient.
– Save user data only and never save Licensed Internal Code (LIC), OS/400 or LPPs.
We do not recommend this. However if edited IBM-supplied objects, the time it takes to
reinstall LIC, OS/400, and LPPs from the original media, and applying all PTFs is not
important to you, this may be an option.
Use BRMS save commands to save data that is needed for recovery.
Do not use BRMS. Use the Save and Restore commands provided with OS/400 and
perform your own backup and recovery management tasks.
For a small iSeries server with a simple application environment change activity, this is
reasonable. As the application environment change activity increases, this requires much
human resource to keep up with the change activity, manual tracking of backup activity,
programming development to automate the backup process, and testing to ensure
recoverability.
24 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Customer feedback on BRMS packaging of features and customer value over the years
clearly demonstrate that you should use BRMS in all but simple environments. To
appreciate what BRMS provides, start by reviewing Backup and Recovery, SC41-5304.
In addition to what we already covered, BRMS also gives you the ability to back up a hosted
Linux environment and any integrated Windows servers running on an Integrated xSeries
Server or Integrated xSeries Server Adapter. Both Linux and integrated Windows servers use
storage space objects within the IFS. BRMS backs up the Linux storage space and the
Windows server storage space. You can also save the Windows server while it is varied on,
which includes saving the QNTC file system.
When an application makes changes to an object during a save-while-active job, the server
uses one image of the object pages to make the changes. At the same time, the server uses
the other image to save the object to the media. The image that the server saves does not
have the changes that you made during the save-while-active job. The image on the media is
as it existed when the server reached a checkpoint.
Despite the name, save while active, you cannot change objects at any time during the save
operation. The server allocates (or locks) objects as it obtains checkpoint images. Some of
the operations that are prevented during checkpoint processing are:
Changing an object
Deleting an object
Renaming an object
Moving an object to a different library or folder
Changing the ownership of an object
Compressing or decompressing an object
In addition, the following object types have operations that are restricted after checkpoint
process is complete. An attempt to perform one of these operations results in a message
indicating that the object is in use:
FILE-PF (physical file)
– Using the Change Physical File (CHGPF) command with the parameter specifications
of SRCFILE, ACCPTHSIZ, NODGRP, or PTNKEY to change a physical file
– Using an SQL Alter Table statement to change a physical file
JRN (journal)
– Deleting a journal with an associated journal receiver
– Using the Work with Journal (WRKJRN) interface to recover a journal that has an
associated journal receiver you are saving
JRNRCV (journal receiver)
– Deleting or moving the journal receiver
– Attaching or detaching the journal receiver from a journal
– Deleting the journal with which the receiver is associated
– Using the WRKJRN interface to recover a damaged journal receiver
PRDLOD (product load)
– Deleting, moving, or renaming the product load
2.5.3 Synchronization
When you save more than one object, you must choose when the objects will reach a
checkpoint in relationship to each other. This is called synchronization. There are three kinds
of synchronization:
Full synchronization: With full synchronization, the checkpoints for all of the objects
occur at the same time. The checkpoints occur during a time period in which no changes
can occur to the objects. We strongly recommend that you use full synchronization, even
when you are saving objects in only one library.
Library synchronization: With library synchronization, the checkpoints for all of the
objects in a library occur at the same time.
System-defined synchronization: With system-defined synchronization, the server
decides when the checkpoints for the objects occur. The checkpoints for the objects may
occur at different times, resulting in complex restore procedures.
The recommended way to use the save-while-active function is to end your applications that
change objects. However, if you are in a restricted state, the save-while-active function is
ignored. You can restart the applications after the server reaches a checkpoint for those
26 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
objects. You can choose to have the save-while-active function send a notification when it
completes the checkpoint processing. Within a backup control group exit, you can use the
Monitor Save While Active (MONSWABRM) command to monitor your save-while-active
message queue for checkpoint completion messages (CPI3710 and CPI3712). After one of
these messages is found to be in the message queue, the MONSWABRM command can run
another command or send a message to users stating that checkpoint was made.
After the save-while-active function completes checkpoint processing, it is safe to start your
applications again. When you use the save-while-active function in this way, the save-outage
time can be much less than with normal save operations. If you cannot end your applications,
you can still use the save-while-active function, although it affects the performance and
response time of your applications. You should also use journaling or commitment control for
all of the objects you are saving. If applications are running and they are using commitment
control, the save-while-active job ends. A good example of this is when the management
central server (*MGTC) is active and there commits are being done to library QUSRSYS. This
is documented in Informational Authorized Program Analysis Records (APAR) II12473, which
you can locate on the Web at:
http://www-912.ibm.com/n_dir/nas4apar.nsf/$$Search?openform
You see a CPF377C message in the job log and the save ends. Also a CPI8365 message is
in QSYSOPR message queue stating which job was stopping the save-while active function
from completing.
For more information about the save-while-active function and BRMS, see Chapter 7 in the
Backup Recovery and Media Services, SC41-5345.
Lotus developed a command that allows you to save everything within a Domino database
even when the server is online. This command is the Save Domino Server Using BRMS
(SAVDOMBRM) command. You can only run it within a BRMS control group inside of an exit.
When using BRMS commands or the SAVDOMBRM command, you can save your Domino
databases to physical media (tapes), save files (SAVF), or an IBM Tivoli Storage Manager
server.
For more information about BRMS and saving Domino servers, see:
Domino 6 for iSeries Best Practices Guide, SG24-6937
The BRMS Web site at:
http://www-1.ibm.com/servers/eserver/iseries/service/brms/
For other sources of information about full system save, see the following sections:
8.1.8, “Full versus incremental backups” on page 172
9.5.1, “Full backup for system AS02” on page 313
9.5.2, “Full system backup restore considerations” on page 324
Some applications are already setup to perform full system saves. If you prefer, you can
create your own Command Language Program (CLP).
When you choose to back up your iSeries server without BRMS, you typically have a system
environment that has only a few things to back up and restore when necessary. Or you have a
more complex operating environment with an available human resource that is focused on
system backup and recovery.
Since this redbook is focused on integrating BRMS with IBM Tivoli Storage Manager,
Figure 2-8 shows the BRMS *SYSTEM control group that is already set up to perform a full
system save.
Group . . . . . . . . . . : *SYSTEM
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backs up the entire system
Bottom
Press Enter to continue.
28 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
You can also run two control groups to achieve the same results. The *SYSGRP shown in
Figure 2-9 saves all the IBM-supplied data (excluding IBM IFS data).
Group . . . . . . . . . . : *SYSGRP
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backs up all system data
Bottom
Press Enter to continue.
The second group that you need to run is *BKUGRP. This saves all of your user data as
shown in Figure 2-10.
Group . . . . . . . . . . : *BKUGRP
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backs up all user data
Bottom
Press Enter to continue.
When using BRMS to perform a full system recovery, you can follow the recovery report
created with the Start Maintenance for BRMS (STRMNTBRM) command shown in
Figure 2-11 with Print recovery reports (PRTRCYRPT) parameter set to *ALL. The report is
generated as a spooled file and is named QP1ARCY.
Bottom
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys
Figure 2-11 Generating all BRMS reports using the STRMNTBRM command
Another way to get the recovery reports is to use the Start Recovery Using BRMS
(STRRCYBRM) command with the action parameter set to *report as shown in Figure 2-12. If
your save strategy includes saving to save files (SAVFs) or an IBM Tivoli Storage Manager
server, you need to change the parameters on the STRRCYBRM command to include those
saves as well.
Note: When you create recovery reports, we recommend that you create two copies, one
on site for day-to-day restores and one off site in case of a disaster.
30 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The advantage of using the BRMS recovery report is that it gives you detailed instructions
about which command to issue, which tape to use, and where the tape is located.
Bottom
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys
When performing a full system recovery to a system that has a different local control point
name, which is found by using the Display Network Attributes (DSPNETA) command, there
are some additional considerations as explained in Informational APAR II12462, which you
can search for at:
http://www-912.ibm.com/n_dir/nas4apar.nsf/$$Search?openform
For a complete recovery report, see Appendix B, “Backup Recovery and Media Services
reports” on page 375.
2.9.1 Advantages
The advantages of using BRMS to save to an IBM Tivoli Storage Manager server are:
You can use BRMS policies to save non-system objects across a network for storage on
any server in the IBM Tivoli Storage Manager family.
You can reduce the amount of media that is required at the off-site location, increasing the
level of backup automation.
You can reduce the amount of time that is spent managing media.
You can minimize device purchases on the off-site system.
2.9.2 Restrictions
When saving to an IBM Tivoli Storage Manager server, consider the following restrictions:
Save-while-active *SYNCLIB is not supported when saving libraries to an IBM Tivoli
Storage Manager server.
You cannot save iSeries system data to an IBM Tivoli Storage Manager server.
– The iSeries and BRMS architecture only allows save of system data to local media so
that you are protected if you need to recover your system. Only after OS/400 is
restored, communication with an IBM Tivoli Storage Manager server can be
established for restoration of the user data that is stored on the server.
– Any user data that you can save to a save file, you can also save to an IBM Tivoli
Storage Manager server, except user data that is required to restore OS/400 to a
functional level. This includes security data, configuration data, IBM-supplied libraries,
licensed program products, IBM-supplied libraries that are considered user data such
as QGPL, QUSRSYS, QUSRBRM, and BRMS media information.
You cannot schedule operations from an IBM Tivoli Storage Manager server. However,
you can schedule your BRMS operations at the client using the native OS/400 job
scheduler or Advanced Job Scheduler LPP.
BRMS uses its own media policies to manage the retention and expiration of data that is
stored on the IBM Tivoli Storage Manager server. IBM Tivoli Storage Manager policies are
not used for this purpose.
You can only use BRMS to restore data saved to an IBM Tivoli Storage Manager server.
32 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3
This chapter introduces IBM Tivoli Storage Manager capabilities, terminology, and constructs.
As stated elsewhere, this redbook does not address the entire range of IBM Tivoli Storage
Manager capabilities. Refer to the following chapters for more information about installing IBM
Tivoli Storage Manager on iSeries servers and how to get the IBM Tivoli Storage Manager
server up and running on an iSeries server.
Most of the iSeries servers with Enterprise Editions now have an IBM Tivoli Storage Manager
server and five IBM Tivoli Storage Manager clients included in their software package. Check
the following Web page to see if IBM Tivoli Storage Manager software is bundled with your
iSeries server:
http://www-1.ibm.com/servers/eserver/iseries/hardware/editions/
IBM Tivoli Storage Manager server manages the storage hardware. It provides a secure
environment, automation, and reporting and monitoring functions. It also implements the
storage management policies and stores all object inventory information in the IBM Tivoli
Storage Manager database.
IBM Tivoli Storage Manager client software and complementary products implement data
management functions. Such functions include data backup and recovery, archival,
hierarchical space management, or disaster recovery.
The iSeries IBM Tivoli Storage Manager server uses the OS/400 Portable Application
Solutions Environment (PASE) to run the server. OS/400 PASE is an optional licensed
program product (LPP) for OS/400 (option 33 5722-SS1). It is included in the standard
OS/400 distribution software package at V5R2M0.
By default, the IBM Tivoli Storage Manager server performs its primary functions using IP port
1500. You can run multiple IBM Tivoli Storage Manager servers on the same system. Each
server requires a unique port number.
34 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The IBM Tivoli Storage Manager server can run on multiple platforms. See the IBM Tivoli
Storage Manager Web home page for a detailed list of all supported IBM Tivoli Storage
Manager server platforms:
http://www-3.ibm.com/software/tivoli/products/storage-mgr/platforms.html
All policy information, logging, authentication, and security, media management, and object
inventory are managed through this database. Most of the fields are externalized using IBM
Tivoli Storage Manager high-level administration commands, SQL SELECT statements, or for
reporting purposes, an ODBC driver.
The recovery log contains information about database updates that are not yet committed.
Changes to the database are recorded in the recovery log to maintain a consistent database
image.
On the iSeries server, the IBM Tivoli Storage Manager database and recovery log are stored
in the integrated file system (IFS). They can consist of multiple database and recovery log
volumes, which are individual streamed files (STMF), that can be combined to create and
extend these storage entities.
IBM Tivoli Storage Manager uses its own model of storage to view, classify, and control these
storage devices, and to implement its storage management functionality. IBM Tivoli Storage
Manager storage management concentrates on managing data objects instead of managing
and controlling backup tapes. This is the main difference between the storage management
approach of IBM Tivoli Storage Manager and other commonly used systems. Data objects
can be files or directories that are backed up from the client systems. They can be objects,
such as tables or records from database applications, or simply a block of data that a client
system wants to store on the server storage.
A storage pool is built from one or more storage pool volumes. Disk storage pool volumes are
individual stream files in the OS/400 IFS. In the case of a tape storage pool, a storage pool
volume is a single physical tape cartridge.
To describe how IBM Tivoli Storage Manager can access those physical volumes to place the
data objects on them, IBM Tivoli Storage Manager has another logical entity called a device
class (for tape storage pools). A device class is connected to a sequential tape storage pool
and specifies how volumes of this storage pool can be accessed. IBM Tivoli Storage Manager
organizes storage pools in one or more hierarchical structures.
Figure 3-1 shows the flow of client backup data in the our test IBM Tivoli Storage Manager
configuration used throughout this redbook. The flow occurs as explained here:
Throughout this process, the IBM Tivoli Storage Manager database keeps track of where the
clients backup data resides.
Client data flow through IBM Tivoli Storage Manager Storage Pools
OFFSITE LOCATION
COPYLTO
iSeries - AS27
TAPE
LTO TAPE
LTO
ITSM SERVER
TAPE LTO
LTO TAPE
ITSM Database
Move copy
offsite
/tsmvol/database/dbvol01.dsm
ITSM Client
/tsmvol/database/dbvol01.dsm ( STMF )
/tsmvol/database/dbvol02.dsm
4
ITSM storage pools
ITSM Recovery Log
/tsmvol/rlog/rlog01.dsm
/tsmvol/database/dbvol01.dsm ( STMF ) TAPE
LTO TAPE
LTO
LTO
LTO TAPE
TAPE
BACKUPPOOL
Copy client
Send Client
/tsmvol/backuppool/bkpvol01.dsm BACKUPLTO
data
3
data
/tsmvol/backuppool/bkpvol02.dsm
/tsmvol/backuppool/bkpvol03.dsm
Migrate client TAPE TAPE
data
1 /tsmvol/backuppool/bkpvol04.dsm
LTO
LTO TAPE
TAPE
2
3584 LTO LIBRARY
36 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The Web administrative client interface is also commonly referred to as a Tivoli Storage
Manager administrative client.
Figure 3-2 IBM Tivoli Storage Manager Web administrative client interface
By default, the IBM Tivoli Storage Manager administrative client performs its primary
functions using IP port 1580. You can run multiple IBM Tivoli Storage Manager servers on the
same system and manage them using this interface.
There is no IBM Tivoli Storage Manager administrative client product that runs natively on the
iSeries server. See Appendix C, “AIX administrative client in OS/400 PASE sample programs”
on page 399, for details about porting the AIX client to the OS/400 IFS.
See Chapter 4, “Using Commands Based on Privilege Class” in IBM Tivoli Storage Manager
for OS/400 PASE Administrator’s Reference, GC23-4695, about more functions that are
allowed from different levels of administrators.
38 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Backup-archive
The backup process creates a copy of the file or application data that can be recovered if the
original data is lost or destroyed. Unlike other backup applications, IBM Tivoli Storage
Manager implements a progressive backup methodology to move data quickly and reliably.
Using progressive backups, the storage administrator can specify the number of file versions
maintained by IBM Tivoli Storage Manager and the length of time they are retained.
Backups can be scheduled, performed manually from the IBM Tivoli Storage Manager client
interface, or performed remotely using a Web-based interface. The restore process transfers
a backup data copy from IBM Tivoli Storage Manager storage hierarchy into a designated
machine.
Data protection
The IBM Tivoli Storage Manager data protection client, also called an application client,
allows for the backup and restoration of data used by various business applications, such as
common industry databases, mail, and application servers. The IBM Tivoli Storage Manager
data protection client receives backup and restore requests from the business application and
translates them for IBM Tivoli Storage Manager server processing. Backup and restore
processing can be done while the business application is online.
V5.1 clients not migrated that can be used with V5.2 servers include:
AIX 4.3.3
Solaris 2.6
Macintosh 9
Windows 98
This list of supported IBM Tivoli Storage Manager clients can change overtime. Refer to the
following Web site for the latest information:
http://www-3.ibm.com/software/tivoli/products/storage-mgr/platforms.html
Other backup products require an initial full backup, followed by regular incremental or
differential backups (usually once a day), and then additional periodic full backups (usually
once a week). This less-efficient backup method results in redundant weekly full backups of
files that have not changed, wasting both network and media resources. The multistep restore
process of such products requires restoration of the last full backup, along with more recent
incremental or differential backups, to recover the latest version of a file or an entire system.
At any time, IBM Tivoli Storage Manager enables the creation of a complete set of client files
(backup set) on the server system using the most recent backup versions stored in the server
storage repository. You can use these backup sets to retain a snapshot of all client files for a
longer period of time (Instant Archive). Simply copy this backup set to portable media and
restore is locally (Rapid Recovery).
File archive means that you create a copy of a file as a separate object in the storage
repository to be retained for a specific period of time. Typically you use this function to create
an additional copy of data to be saved for historical purposes. Vital records (data you keep for
legal or other business reasons) are likely candidates for the archive process. You can specify
to delete the original copy of the data on the source system after the archive copy is created
on the server. Therefore, you can use an archive to make additional space available on the
IBM Tivoli Storage Manager client system. However, do not think of an archive as a complete
space management function, because transparent automatic recall is not available.
You can access archived data by using retrieve to return it to the IBM Tivoli Storage Manager
client, if the data is needed at some future time. To locate the archived data within the storage
repository, IBM Tivoli Storage Manager allows you to add a description to the data and to form
archive packages of related files. You can then use this description to search the server
database for matching packages to determine which data to retrieve. Therefore, the
difference between backup and archive is that backup creates and controls multiple backup
versions that are directly attached to the original file. Archive creates an additional file that is
normally kept for a specific period of time, as in the case of vital records.
40 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3.3.1 IBM Tivoli Storage Manager Disaster Recovery Manager and disaster
recovery
Disaster recovery is the process of restoring operations of a business or organization in the
event of a catastrophe. There may be many aspects related to the restoration, including
facilities, equipment, personnel, supplies, customer services, and data. A valuable business
asset is the critical data that resides on the computer systems throughout the company. The
recovery of this data needs to be a primary focus of the disaster recovery plan. IBM Tivoli
Storage Manager, along with Tivoli Disaster Recovery Manager (DRM), can assist you in the
technical steps that you need to make your data available to users after a widespread failure.
IBM Tivoli Storage Manager Disaster Recovery Manager is a feature of the IBM Tivoli Storage
Manager Extended Edition. IBM Tivoli Storage Manager DRM helps coordinate and automate
the process of recovering from a disaster. It provides for off-site media management,
automated restore of the IBM Tivoli Storage Manager server, and managed client recovery. It
complements the robust protection features of IBM Tivoli Storage Manager and automates
many already facilitated protection functions.
Note: The newer iSeries servers, Models 825, 870, and 890, include a software packaging
option called the Enterprise Edition, with a package feature number unique for an 825,
870, or 890. This iSeries Enterprise Edition software package provides several software
products and includes the IBM Tivoli Storage Manager Extended Edition. If you do not
have this iSeries Enterprise Edition software, you must purchase the IBM Tivoli Storage
Manager Extended Edition separately.
DRM automatically captures information required to recover the IBM Tivoli Storage Manager
server after a disaster. It assists in preparing a plan that allows recovery in the most expedient
manner. This disaster recovery plan contains information, scripts, and procedures needed to
automate server restoration. It also helps to ensure quick recovery of your data after a
disaster.
DRM manages and tracks the movement of off-site media to reduce the time required to
recover in the event of a disaster. It can track media that are stored on site, in transit, or off
site in a vault, regardless of whether it is a manual or electronic vault, so your data can be
easily located if disaster strikes.
DRM can also capture client recovery information. You can use this information to assist in
identifying what clients need to recover, in what order, and what is required to recover them.
This includes data and media that are not managed by IBM Tivoli Storage Manager.
With logical partitioning, the iSeries server enables OS/400 applications to be extended with
Linux on a single server. Linux applications can access DB2® Universal Database™ (UDB)
as well as OS/400 programs and services through one of 16 high-speed Virtual Ethernet
LANs that interconnect the partitions. These connections can provide 1 Gb of performance
and do not require local area network (LAN) adapters, switches, or physical networks.
If IBM Tivoli Storage Manager for OS/400 PASE is installed in another partition on the same
iSeries server, you can take advantage of the internal high-speed (1 GB) Virtual Ethernet
LAN to transport the Linux backup data.
For a level of performance that is balanced across both backup and restore operations, the
best method is to use progressive incremental backup with collocation set on in the storage
pool. By using collocation, you reduce the number of volume mount operations required when
users restore or retrieve many files from the storage pool. When collocation is set, IBM Tivoli
Storage Manager attempts to use at least one tape volume for each client. Therefore using
collocation also requires more volumes and the capacity to store these additional volumes in
an automated library. However, if restore times are critical, collocation can provide a
significant time saving recovering client data.
42 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Part 2
This part provides more details about using IBM Tivoli Storage Manager for OS/400 Portable
Application Solutions Environment (PASE). It covers the following topics:
IBM Tivoli Storage Manager overview
Installing IBM Tivoli Storage Manager as a server on an iSeries server
Quick start for IBM Tivoli Storage Manager, including getting your IBM Tivoli Storage
Manager server up and running with basic capabilities
IBM Tivoli Storage Manager save and restore function scenario examples
Disk Storage Pool Enough space to back up one day’s worth of changed
client data per workstation.
Your disk space requirements change as you expand the scope of your system.
The database size is largely determined by the number of client files and versions of those
files being stored on the server storage. As you add clients, you must increase your database
size.
Storage pool space is largely determined by number and size of client files (including
versions) and the backup destination (disk or sequential access media). You should reserve
enough disk space to hold each day’s changed data and to allow migration to tape.
PASE is an optional function of the OS/400 licensed program product (Option 33, 5722-SS1).
It provides a UNIX-like environment where the IBM Tivoli Storage Manager server for OS/400
PASE will run. However, OS/400 PASE is not a UNIX operating system on OS/400. It is
designed to run AIX programs on OS/400 with little or no change.
Verify that OS/400 PASE is installed on your iSeries server by using the OS/400 Display
Software Resources (DSPSFWRSC) command. If the OS/400 Option 33, licensed program
product (LPP) is not installed and your OS/400 level is at V5R2M0, then you can restore it
from the OS/400 B29xx_05 CD (included in your standard iSeries V5R2M0 software
distribution).
If your OS/400 level is at V5R1M0, then you must order this chargeable feature from IBM.
46 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
4.2.2 Program temporary fix requirements
In addition to the OS/400 PASE software, you must install and apply the OS/400 program
temporary fixes (PTFs) listed in Table 4-2.
SI04612 MF30253
SI04626 MF30371
SI03939 MF30245
MF28967
SI01968
MF27490
MF27780
MF28208
The PTFs listed in this table were used while writing this redbook. By the time you read this
redbook, these PTFs may have been updated. Refer to the iSeries software support Web site
to determine if any of these PTFs are updated with newer PTFs. Go to:
http://www.ibm.com/eserver/iseries/support
When you reach this Web site, click the Search Technical Databases link. Then select PTF
Cover Letters on the next page. Search for a PTF number. Any corequisite or prerequisite
PTFs are included in the search results.
Chapter 4. Installing IBM Tivoli Storage Manager server for OS/400 PASE 47
• If you want to use the OS/400 system language feature for the IBM Tivoli Storage
Manager server, enter *PRIMARY.
• If you want to use a different language feature than that of the operating system,
then enter the required language feature number (for example 29xx).
The installation process places most of the IBM Tivoli Storage Manager software in the
iSeries integrated file system (IFS) under directory /usr/tivoli/tsm/server/. It also creates a
QTSM library that basically holds the IBM Tivoli Storage Manager product information for
OS/400.
6. Verify that the licensed program is installed by selecting option 10 (Display installed
licensed programs) and then option 50 (Display History) from the GO LICPGM OS/400
menu.
Tip: With the iSeries Announcement of 5 September 2003, there is a new installation
possibility for these IBM Tivoli Storage Manager APIs and other software, called iSeries
Enterprise Editions Installation Assistant (5733-ED1). It is for customers with systems 825
or higher with Enterprise Edition. Installation Assistant uses the V5R2 iSeries Virtual
Media Installation (VMI) function. You can learn more about these and other iSeries
Announcements on the Web at:
http://www-1.ibm.com/servers/eserver/iseries/announce/
48 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Patches are intended to provide relief for critical problems when local circumvention is
unavailable. Although the patches are tested by development, we strongly recommend that
you perform additional testing before you place a patch into a production environment.
Patches are included in the next maintenance level PTF.
Be sure to read both the README and README.INSTALL files that are available with every
patch and maintenance level for detailed information about the installation and issues
addressed with each PTF.
Important: You must end the IBM Tivoli Storage Manager for OS/400 PASE server before
you install any maintenance or patch PTFs.
You can download the latest IBM Tivoli Storage Manager fixes by using one of the methods
presented in the following sections.
Chapter 4. Installing IBM Tivoli Storage Manager server for OS/400 PASE 49
3. For the login ID, enter anonymous.
4. For the guest password, enter your e-mail address.
5. Set the FTP session in to binary mode:
bin
6. Go to the relevant PASE directory:
– For IBM Tivoli Storage Manager patches, go to the patch directory:
cd /storage/tivoli-storage-management/patches/server/PASE
– For IBM Tivoli Storage Manager maintenance fixes, go to the maintenance directory:
cd /storage/tivoli-storage-management/maintenance/server/vXrY/PASE
Here X is the IBM Tivoli Storage Manager server version level and Y is the IBM Tivoli
Storage Manager release level.
7. To list the fix subdirectories that are available, enter the following command:
ls -l
8. Change to the required directory by entering the command:
cd
9. Download the required fix by using the get command as shown here:
get Q52001SR.savf QGPL/Q52001SR (replace
10.End the FTP session by entering quit or pressing F3.
http://www-3.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html
You must be a registered IBM support user or you must register before you can download any
IBM Tivoli Storage Manager fixes.
Ensure that you end the IBM Tivoli Storage Manager server before you apply the PTF. This
does not apply to a new installation of the IBM Tivoli Storage Manager server.
1. Load the IBM Tivoli Storage Manager PTF using the OS/400 command:
LODPTF LICPGM(5698ISX) DEV(*SAVF) SELECT(52001SR) SAVF(QGPL/Q52001SR)
2. Apply the IBM Tivoli Storage Manager PTF using the OS/400 command:
APYPTF LICPGM(5698ISX) SELECT(52001SR)
50 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. Verify that the PTF is applied by typing the following OS/400 command (see Figure 4-2):
DSPPTF LICPGM(5698ISX)
PTF IPL
Opt ID Status Action
52001SR Temporarily applied None
Bottom
F3=Exit F11=Display alternate view F17=Position to F12=Cancel
4. The applied PTF may have been modified the IBM Tivoli Storage Manager Web
administrative client interface (see 5.2.1, “IBM Tivoli Storage Manager Web administrative
client interface” on page 56). Perform the following steps to update the Web administrative
client interface with any new changes:
a. Start an OS/400 PASE session. From an OS/400 command line, enter:
call qp2term
b. Change to the IBM Tivoli Storage Manager server's directory:
cd /usr/tivoli/tsm/server/bin
c. Enter the following command to regenerate the IBM Tivoli Storage Manager server
Web pages:
dsmserv runfile /usr/tivoli/tsm/server/webimages/dsmserv.idl
You must wait for the return of the dollar sign ($) prompt (indicates that the script has
completed). Then press F3 to exit.
Chapter 4. Installing IBM Tivoli Storage Manager server for OS/400 PASE 51
Figure 4-3 shows an example of an OS/400 PASE session after successfully running
the dsmserc.idl script.
/QOpenSys/usr/bin/-sh
===>
Figure 4-3 OS/400 PASE session update of the Web administrative client interface
5. If this is a new installation, then continue with Chapter 5, “First steps: IBM Tivoli Storage
Manager server basic configuration” on page 53. Otherwise you may restart the IBM Tivoli
Storage Manager server now.
52 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
5
5.1.1 Starting and ending the IBM Tivoli Storage Manager server for the first
time
As mentioned, the IBM Tivoli Storage Manager for iSeries runs in OS/400 PASE, which
provides an AIX-like environment for the IBM Tivoli Storage Manager server. Initially, we start
the IBM Tivoli Storage Manager server through an interactive OS/400 PASE session,
although the IBM Tivoli Storage Manager server normally runs in batch mode. This is
discussed later in the following section.
1. To start an OS/400 PASE session, enter the following command from an OS/400
command line:
call qp2term
Program qp2term runs the IBM Tivoli Storage Manager server on your iSeries server as a
job in the same OS/400 subsystem as the job calling qp2term (terminal).
2. Change to the IBM Tivoli Storage Manager server's directory:
cd /usr/tivoli/tsm/server/bin
3. Set the IBM Tivoli Storage Manager server home environmental variable:
export DSMSERV_DIR=/usr/tivoli/tsm/server/bin
4. When it is started, the IBM Tivoli Storage Manager server looks for a control file
(dsmserv.opt) in the IBM Tivoli Storage Manager server code directory. A sample file
(dsmserv.opt.smp) is provided that you should copy and use as a good starting point. To
copy the file, enter the following command:
cp dsmserv.opt.smp dsmserv.opt
5. To start the IBM Tivoli Storage Manager server interactively, enter:
dsmserv
A display similar to the one shown in Figure 5-1 is shown as the IBM Tivoli Storage
Manager server starts. The IBM Tivoli Storage Manager server is now active in OS/400
PASE. By running in OS/400 PASE through a 5250 job (the call to program qp2term), the
iSeries implementation runs the IBM Tivoli Storage Manager server on your iSeries server
as a job in the same OS/400 subsystem as the 5250 workstation job calling qp2term
(terminal).
Attention: Do not press F3 (exit the PASE interface) on this display. Otherwise, you will
lose your interactive session interface to the OS/400 PASE server job.
The time given to your IBM Tivoli Storage Manager server may be incorrect at this point.
Continue with the following sections since we address this in 6.1, “Setting the correct time
zone for OS/400 PASE” on page 94.
54 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
/QOpenSys/usr/bin/-sh
ANR8200I TCP/IP driver ready for connection with clients on port 1500.
ANR2803I License manager started.
ANR8190I HTTP driver ready for connection with clients on port 1580.
ANR2560I Schedule manager started.
ANR0984I Process 1 for EXPIRATION started in the BACKGROUND at 16:18:38.
ANR0811I Inventory client file expiration started as process 1.
ANR0993I Server initialization complete.
ANR0812I Inventory file expiration process 1 completed: examined 0 objects,
deleting 0 backup objects, 0 archive objects, 0 DB backup volumes, and 0
recovery plan files. 0 errors were encountered.
ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use.ANR0985I
ROUND completed with completion state SUCCESS at 16:18:38.
TSM:TSM>
===>
F3=Exit F6=Print F9=Retrieve F11=Truncate/Wrap
F13=Clear F17=Top F18=Bottom F21=CL command entry
6. End the IBM Tivoli Storage Manager server. Enter the halt command to end the IBM Tivoli
Storage Manager OS/400 PASE server. Do not press F3 on this display to exit. We restart
the server in batch mode as explained in the following section.
7. When you receive the message “ANR0991I Server shutdown complete”, press F3 to return
to the OS/400 command line.
To start the IBM Tivoli Storage Manager server in batch mode, you must create a simple
Command Language Program (CLP), which you can call from the OS/400 Submit Job
(SBMJOB) command or add to the iSeries startup program. Use the sample code in
Example 5-1 to compile into a CLP, for example, QGPL/STRTSMSRV.
Note: The following code is case sensitive. You must type the directory references in lower
case as shown in Example 5-1. When using Start Program Development Manager
(STRPDM) or SEU, press F13 to change the session defaults and set the Uppercase input
only value to N.
Example 5-1 Sample code to start IBM Tivoli Storage Manager server in batch
PGM
/*STRTSMSRV*/
ADDENVVAR ENVVAR(DSMSERV_DIR) +
VALUE('/usr/tivoli/tsm/server/bin')
ADDENVVAR ENVVAR(DSMSERV_CONFIG) +
VALUE('/usr/tivoli/tsm/server/bin/dsmserv.o+
pt')
/**/
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 55
CHGCURDIR DIR('/usr/tivoli/tsm/server/bin')
/**/
CALL PGM(QP2SHELL) +
PARM('/usr/tivoli/tsm/server/bin/dsmserv')
/**/
ENDPGM
The following SBMJOB command calls our STRTSMSRV program created in the previous
step and submits it to the QSYSWRK subsystem via the QSYSNOMAX jobq. You can also
create your own IBM Tivoli Storage Manager subsystem and JOBQ and run the IBM Tivoli
Storage Manager server there instead.
SBMJOB CMD(CALL PGM(QGPL/STRTSMSRV)) JOB(TSMPASESRV) JOBQ(QSYSNOMAX) ALWMLTTHD(*YES)
Note: You must set the Allow multiple threads (ALWMLTTHD) parameter on the SBMJOB
command to *YES.
Instead, we recommend that you use either the Tivoli Storage Manager Web
Administrative client (browser interface) or the Tivoli Storage Manager Command Line
client as the interface to the Tivoli Storage Manager OS/400 PASE server. This section
describes these interfaces.
There are two administration interfaces for the IBM Tivoli Storage Manager OS/400 PASE
server. There is a Web administrative client interface, Tivoli Storage Manager Web
Administrative client, which you can access from a Web browser. And there is a command
line interface, which you must start from an IBM Tivoli Storage Manager client.
You can optionally install the IBM Tivoli Storage Manager administrative client with the
backup-archive client. (As previously stated, keep in mind that there is no iSeries
backup-archive client product.) A non-iSeries administrative client package consists of the
Tivoli Storage Manager server command line, which you can use to remotely manage a Tivoli
Storage Manager server from a network-attached machine.
All IBM Tivoli Storage Manager server configuration steps and examples in this redbook are
performed using only the IBM Tivoli Storage Manager Web Administrative client interface.
56 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The active IBM Tivoli Storage Manager server behaves as a Web page server for the IBM
Tivoli Storage Manager Web administrative client interface. A specific HTTP Web server
configuration is not required. You can access the IBM Tivoli Storage Manager Web
administrative client interface from a Web browser by using:
http://itsmservername:1580
Here itsmservername is either the host name of the iSeries server or the numeric IP address.
1580 is the default port for the IBM Tivoli Storage Manager Web administrative client
interface. See Figure 5-2. The installation default for the IBM Tivoli Storage Manager
administrator is user ID admin and password admin.
Figure 5-2 IBM Tivoli Storage Manager Web administrative client interface signon page
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 57
After you log in, you see the IBM Tivoli Storage Manager Web administrative client interface
main page as shown in Figure 5-3.
Figure 5-3 IBM Tivoli Storage Manager Web administrative client interface
Also available in the IBM Tivoli Storage Manager Web administrative client interface is a
Server Command window. This enables users to type IBM Tivoli Storage Manager commands
rather than clicking the left tree structure of the Web administrative client interface.
58 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
To access the Server Command window, from the Options list in the top right corner of the
browser window, select Show command line. See Figure 5-4.
Server Command
window
If you know the relevant IBM Tivoli Storage Manager commands, then using the Server
Command window can save you time. You can find all the IBM Tivoli Storage Manager server
commands in the IBM Tivoli Storage Manager for OS/400 PASE - Administrator’s Reference,
GC23-4695. The following sections show examples of using the Server Command window.
The following examples show how to change the password from either the Web administrative
client interface tree structure or the Server Command window.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 59
1. On the left side of the page, in the Web tree structure, expand Object view and select
Administrators (see Figure 5-5).
2. On the Administrators panel, select the ADMIN user ID from the list of administrators
(Figure 5-6).
60 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. From the Operations list, select Update an Administrator as shown in Figure 5-7.
4. On the Update an Administrator panel (Figure 5-8), in the Password field, enter the new
admin password. Scroll to the end of the panel. Ignore the other fields and click Finish to
process the update.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 61
IBM Tivoli Storage Manager Server Command window
The following step shows how to change the ADMIN ID password using the IBM Tivoli
Storage Manager Web Server Command window with the IBM Tivoli Storage Manager update
admin command.
1. In the Server Command window at the bottom of the page (Figure 5-9), type:
update admin admin xxxxxxxx
Here xxxxxxxx is the new password given to the admin user ID.
Figure 5-9 IBM Tivoli Storage Manager Server Command window: Using the update admin command
62 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
2. Click Submit to process the command. The page shown in Figure 5-10 displays a
message indicating the update of the admin user ID was successful.
Figure 5-10 IBM Tivoli Storage Manager Server Command window: Successful update
Depending on your iSeries server model, you may already have five Tivoli Storage Manage
backup-archive client licenses (mgsyslan.lic) included in the iSeries Enterprise Edition
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 63
packaging. These licenses should be registered. Initially the IBM Tivoli Storage Manager
server only has one registered client after the product is installed.
Table 5-1 shows all of the licensed files that are available to IBM Tivoli Storage Manager.
domino.lic Each managed system that uses IBM Tivoli Storage Manager for Mail
drm.lic IBM Tivoli Storage Manager Extended Edition (disaster recovery manager)
emcsymm.lic Each managed system that uses IBM Tivoli Storage Manager for Hardware
(EMC Symmetrix)
emcsymr3.lic Each managed system that uses IBM Tivoli Storage Manager for Hardware
(EMC Symmetrix R/3)
ess.lic Each managed system that uses IBM Tivoli Storage Manager for Hardware
(ESS)
essr3.lic Each managed system that uses IBM Tivoli Storage Manager for Hardware
(ESS R/3)
informix.lic Each managed system that uses IBM Tivoli Storage Manager for
Databases (Informix®)
lnotes.lic Each managed system that uses IBM Tivoli Storage Manager for Lotus
Notes
mgsyslan.lic Each managed system that uses IBM Tivoli Storage Manager Managed
System for LAN
msexch.lic Each managed system that uses IBM Tivoli Storage Manager for MicroSoft
Exchange Databases
mssql.lic Each managed system that uses IBM Tivoli Storage Manager for
Databases (MS SQL Server)
oracle.lic Each managed system that uses IBM Tivoli Storage Manager for
Databases (Oracle)
r3.lic Each managed system that uses IBM Tivoli Storage Manager for Enterprise
Resource Planning
spacemgr.lic Each managed system that uses Tivoli Storage Manager for Space
Management
was.lic Each managed system that uses IBM Tivoli Storage Manager for
Application Servers (WebSphere)
With the exception of the drm.lic and library.lic, you can specify any number of license files to
register. Always specify the total number of licenses you want to register. If you enter
number=0 for a particular license, the license is unregistered. If you have 20 licenses and
require 10 additional licenses, you must register 30.
To register five IBM Tivoli Storage Manager Backup-Archive Clients to the IBM Tivoli Storage
Manager server, choose one of the following methods:
64 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Use the IBM Tivoli Storage Manager Web tree structure by following these steps:
a. Expand Object view-> Server and select License Information. This displays the
current licensed information of the IBM Tivoli Storage Manager server.
b. From the Operations list, select Register License.
c. On the Register License panel (Figure 5-11), in the Licensed File field, type
mgsyslan.lic. In the Number to License field, type 5. Click Finish.
d. Click Return.
Use the IBM Tivoli Storage Manager Web Server Command window by entering the
command:
register license file=mgsyslan.lic number=5
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 65
Figure 5-12 Web administrative client interface: Licensed information
5.3.5 Creating an IFS file structure for IBM Tivoli Storage Manager
The default installation places all the IBM Tivoli Storage Manager volumes in the IBM Tivoli
Storage Manager server integrated file system (IFS) directory (/usr/tivoli/tsm/server/bin/). You
can get the IBM Tivoli Storage Manager server up and running with this single directory.
However, it is good practice to create a new directory structure for the various IBM Tivoli
Storage Manager storage volumes and files that are created during the server configuration,
rather than keeping them all in the same /usr/tivoli/tsm/server/bin directory.
Dividing the IBM Tivoli Storage Manager volumes into different directories gives a more
structured approach to the IBM Tivoli Storage Manager server installation and provides a
more manageable environment. We recommend that you start with at least five directories.
You can create them by entering the following commands from an OS/400 command line:
CRTDIR DIR('/tsmvol/')
CRTDIR DIR('/tsmvol/database')
CRTDIR DIR('/tsmvol/rlog')
CRTDIR DIR('/tsmvol/backuppool')
CRTDIR DIR('/tsmvol/files')
These new directories are used in the following IBM Tivoli Storage Manager server
configuration sections.
66 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The database does not store client data. Instead, the database points to the locations of the
client files in the various storage pools. The size of the database depends on many factors,
such as number of client files, number of versions kept, and any copies made for off site. See
Chapter 17, “Managing the Database and Recovery Log” in the IBM Tivoli Storage Manager
for OS/400 PASE Administrator’s Reference, GC23-4695, for sizing the IBM Tivoli Storage
Manager database.
The IBM Tivoli Storage Manager database created by the installation process has, by default,
one database with a size of 16 MB. The IBM Tivoli Storage Manager database can consist of
numerous database volumes. This can be compared to OS/400 single level storage, where
data is spread over multiple physical disks and OS/400 is responsible for the data
management. The following example increases the IBM Tivoli Storage Manager database by
2 GB. It creates two 1 GB database volumes, and the IBM Tivoli Storage Manager server
spreads data evenly over these two new volumes.
Each database volume created requires 1 MB extra space for overhead. Therefore, in our
example, we create each volume as 1025 MB (1024 MB for the IBM Tivoli Storage Manager
database data + 1 MB overhead).
Again you can perform this from both the IBM Tivoli Storage Manager Web administrative
client interface tree structure and the IBM Tivoli Storage Manager Server Command window.
You must first define the database volume and then extend the database by performing the
following steps:
1. Expand Object view-> Database and select Database Volumes. You see the 16 MB
database volume created during the IBM Tivoli Storage Manager installation as shown in
Figure 5-13.
2. From the Operations list, select Define Database Volume.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 67
3. On the Define Database Volume panel (Figure 5-14), enter the IBM Tivoli Storage
Manager database volume name and size. The database volume name must include the
fully qualified path and the format size of the required volume in MB. In our example, as
shown in Figure 5-14, we entered:
– Volume Name: /tsmvol/database/dbvol01.dsm
– Format Size: 1025
– Wait: No (the process runs as a batch process rather than interactively)
Figure 5-14 Web administrative client interface: Defining the database volume
Note: You can replace steps 1 through 4 by entering the following command in the
Server Command window:
define dbvolume /tsmvol/database/dbvol01.dsm formatsize=1025
5. You see an Operation results message similar to the following example stating that the
volume create process is starting:
“ANR2491I Volume Creation Process starting for tsmvol/database/ dbvol01.dsm, Process Id
8.”
68 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. The process now runs as a batch job and may take several minutes to complete. Each
process is assigned a unique process number. You can see the IBM Tivoli Storage
Manager active processes (see Figure 5-15) by using one of the following methods:
– IBM Tivoli Storage Manager Web administrative client interface tree structure by
expanding Object view-> Server and selecting Processes.
– IBM Tivoli Storage Manager Web administrative client interface Server Command
window by entering either of the following commands:
query process
q pr
7. When the process is finished, check the IBM Tivoli Storage Manager messages to ensure
that the process completed successfully. Use one of the following methods:
– IBM Tivoli Storage Manager Web administrative client interface tree structure by using
these steps:
i. Expand Object view-> Server and select Activity Log.
ii. On the Query panel, scroll down the page leaving all the parameters as default and
click Finish.
– IBM Tivoli Storage Manager Web Server Command window by entering either of the
following commands:
query actlog
q act
All IBM Tivoli Storage Manager messages are posted to the IBM Tivoli Storage Manager
activity log. This log is IBM Tivoli Storage Manager equivalent of the iSeries system history
log QHST. You can see the IBM Tivoli Storage Manager activity log from both the IBM
Tivoli Storage Manager Web administrative client interface tree structure and the IBM
Tivoli Storage Manager Server Command window. By accepting the default parameters on
both methods, all messages generated during the last hour are displayed.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 69
Regardless of the method you use, the resulting panel appears as shown in the example
in Figure 5-16. You can see message ANR0986I, which shows that our new database
volume has a completion status of SUCCESS.
Figure 5-16 Web administrative client interface: Querying the activity log
70 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
9. Query the IBM Tivoli Storage Manager database to see the new database configuration as
shown in Figure 5-17. Use one of the following methods:
– IBM Tivoli Storage Manager Web administrative client interface tree structure by
expanding Object view and selecting Database.
– IBM Tivoli Storage Manager Web Server Command window by entering the following
command:
query db
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 71
10.The Assigned Capacity is still 16 MB, which is the original installation database volume.
Now we have a Maximum Extension value of 2048 MB.
Use one of the following methods to extend the IBM Tivoli Storage Manager database to
use the newly created IBM Tivoli Storage Manager database volumes:
– IBM Tivoli Storage Manager Web administrative client interface tree structure by
following these steps:
i. Expand Object view and select Database.
ii. From the Operations list, select Extend.
iii. In the Extend panel (Figure 5-18), in the Extension (MB) field, type 2048.
iv. Click Finish.
– IBM Tivoli Storage Manager Web Server Command window by entering:
extend db 2048
11.Query the IBM Tivoli Storage Manager database to see the new Assigned Capacity (MB)
of 2064 by using one of the following methods:
– IBM Tivoli Storage Manager Web administrative client interface tree structure by
expanding Object view and selecting Database.
– IBM Tivoli Storage Manager Web Server Command window by entering:
query db
5.3.7 Increasing the IBM Tivoli Storage Manager recovery log size
The initial IBM Tivoli Storage Manager installation automatically creates the IBM Tivoli
Storage Manager recovery log for you. The recovery log contains information about IBM Tivoli
Storage Manager database updates that are not yet committed. Updates can include such
activities as defining a management class, backing up a client file, and registering a client
node. Changes to the database are recorded in the recovery log to maintain a consistent
database image. The more that log utilization increases, the more active the server is.
72 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The size of the recovery log depends on the number of concurrent client sessions and the
number of background processes executing on the server. The maximum number of
concurrent client sessions is set in the server options. See Chapter 17, “Managing the
Database and Recovery Log” in the IBM Tivoli Storage Manager for OS/400 PASE
Administrator’s Reference, GC23-4695, to size the IBM Tivoli Storage Manager recovery log.
The IBM Tivoli Storage Manager recovery log created by the installation process has, by
default, one recovery log volume of 8 MB. The IBM Tivoli Storage Manager recovery log can
be made up of numerous recovery log volumes. Compare this to OS/400 single-level storage,
where data is spread over multiple physical disks and OS/400 is responsible for the data
management.
The following example increases the IBM Tivoli Storage Manager recovery log by 257 MB by
creating one 257 MB recovery log volume.
Each recovery log volume created requires 1 MB extra space for overhead. Therefore, in this
example, you create a volume as 257 MB (256 MB for the IBM Tivoli Storage Manager
recovery log data + 1 MB overhead).
This process is similar to increasing the IBM Tivoli Storage Manager database. Only this time
we use the define logvolume and extend log IBM Tivoli Storage Manager commands.
1. Expand Object view-> Recovery Log and select Recovery Log Volumes. This shows
the 8 MB assigned capacity recovery log volume created during the IBM Tivoli Storage
Manager installation.
2. From the Operations list, select Define Recovery Log Volume.
3. Enter the IBM Tivoli Storage Manager recovery log volume name and size. The recovery
log volume name must include the fully qualified path and the format size of the required
volume in MB. In this example, we entered:
– Volume Name: /tsmvol/rlog/rlogvol01.dsm
– Format Size: 257
– Wait: No (the process runs as a batch process rather than interactively)
4. Click Finish to submit the request.
Note: You can replace steps 1 through 4 by entering the following command in the
Server Command window:
define logvolume /tsmvol/rlog/rlogvol01.dsm formatsize=257
5. The process now runs as a batch job and may take several minutes to complete.
Use the q pr and q act IBM Tivoli Storage Manager commands in the IBM Tivoli Storage
Manager Server Command window to ensure that the recovery log volume is successfully
created.
6. Extend the IBM Tivoli Storage Manager recovery log to use our newly created recovery log
volume (/tsmvol/rlog/rlogvol01.dsm). The Assigned Capacity is still 8 MB (this is the
original installation recovery log volume). Now we have a Maximum Extension of 256 MB.
Use one of the following methods to extend the size of the IBM Tivoli Storage Manager
recovery log:
– IBM Tivoli Storage Manager Web administrative client interface tree structure by
following these steps:
i. Expand Object view and select Recovery Log.
ii. From the Operations list, select Extend.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 73
iii. On the Extend panel, in the Extension (MB) field, type 256.
iv. Click Finish.
– IBM Tivoli Storage Manager Web Server Command window by entering the following
command:
extend log 256
5.3.8 Removing the IBM Tivoli Storage Manager default database volume
You increased the IBM Tivoli Storage Manager database size. Now you can remove the
default 16 MB database volume that was created during the installation process.
Before you can delete the original 16 MB database volume (/usr /tivoli/ tsm/server/bin/
db.dsm), you must first reduce the IBM Tivoli Storage Manager database by 16 MB.
1. Expand Object view and select Database.
2. From the Operations list, select Reduce.
3. On the Reduce panel (Figure 5-19), in the Reduction (MB) field, type 16.
4. Click Finish.
5. When you delete a database volume, it moves all valid database data that is still on the
volume to the newly created database volumes (in this example, this is
/tsmvol/database/dbvol01/dbvol02).
a. Expand Object view-> Database and select Database Volumes.
b. From the list of volumes, select /usr /tivoli/tsm/server/bin/db.dsm.
c. From the Operations list, select Delete Database Volume.
d. Click Finish to process the request.
74 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Note: You can replace steps 1 through 5 by entering the following commands in the
Server Command window:
reduce db 16
delete dbvolume /usr /tivoli/ tsm/server/bin/ db.dsm
6. The database volume /usr /tivoli/ tsm/server/bin/ db.dsm is deleted from IBM Tivoli Storage
Manager, but the volume still exists as a stream file (STMF) in the OS/400 IFS.
To delete the file, enter the following command on an OS/400 command line:
RMVLNK OBJLNK('/usr/tivoli/tsm/server/bin/db.dsm')
5.3.9 Removing the IBM Tivoli Storage Manager default recovery log volume
You increased the IBM Tivoli Storage Manager recovery log size. Now you can remove the
default 8 MB recovery log volume that was created during the installation process.
Before you can delete the original 8 MB recovery log volume (/usr /tivoli/ tsm/server/bin/
log.dsm), you must first reduce the IBM Tivoli Storage Manager recovery log by 8 MB:
1. Expand Object view and select Recovery Log.
2. From the Operations list, select Reduce.
3. In the Reduction (MB) field, type 8.
4. Click Finish.
5. When you delete a recovery log volume, it moves all valid recovery log data that is still on
the volume to the newly create recovery log volumes (in our example /tsmvol/rlog/
rlogvol01).
a. Expand Object view-> Recovery Log and select Recovery Log Volumes.
b. Select Recovery Log Volume /usr /tivoli/ tsm/server/bin/ log.dsm.
c. From the Operations list, select Delete recovery log volume.
d. Click Finish to process the request.
Note: You can replace steps 1 through 5 by entering the following commands in the
Server Command window:
reduce log 8
delete logvolume /usr /tivoli/ tsm/server/bin/ log.dsm
6. The recovery log volume /usr /tivoli/ tsm/server/bin/ log.dsm has been deleted from IBM
Tivoli Storage Manager, but the volume still exists as a stream file in the OS/400 IFS.
To delete the file enter, the following command on an OS/400 command line:
RMVLNK OBJLNK('/usr/tivoli/tsm/server/bin/log.dsm')
To see the current IBM Tivoli Storage Manager server option settings, use one of the following
methods:
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 75
IBM Tivoli Storage Manager Web administrative client interface tree structure by
expanding Object view-> Server and selecting Server Options
IBM Tivoli Storage Manager Web Server Command window by entering the command:
q option
There are many available options in this file. See Chapter 6 “Server Options Reference” in the
IBM Tivoli Storage Manager for OS/400 PASE Administrator’s Reference, GC23-4695, for a
full list of all possible settings. Table 5-2 shows some of the common settings for the IBM
Tivoli Storage Manager server.
LANGuage AMENG AMENG This is the locale used for default language on the server. See
Chapter 6 “Server Options Reference” in the IBM Tivoli Storage
Manager for OS/400 PASE Administrator’s Reference, GC23-4695,
for the supported languages.
DATEformat 1 See description The date format for the IBM Tivoli Storage Manager server. Choose
the required value.
1 = MM/DD/YYYY / 2 = DD-MM-YYYY
BUFPoolsize 2048 131072 This is the database buffer pool in kilobytes. A large buffer pool
means that database pages remain longer in memory cache, and
Storage Manager requires fewer input/output operations to server
storage. This value also depends on the amount of real iSeries
memory available to IBM Tivoli Storage Manager.
LOGPoolsize 512 2048 The size, in KB, of the recovery log buffer pool. A large buffer pool
may increase the rate by which recovery log transactions are
committed to the database, but it also requires more memory.
MOVEBatchsize 40 1000 Specifies the number of client files that are to be moved and
grouped together in a batch, within the same server transaction.
MOVESizethresh 500 500 Specifies, in MB, a threshold for the amount of data moved as a
batch, within the same server transaction.
TXNGroupmax 40 256 Specifies the number of files that are transferred as a group between
a client and the server between transaction commit points.
EXPQUiet No Yes The server sends only minimal messages during the expiration
process.
We recommend that you change the default values for all the options shown in Table 5-2 as
an ideal starting point for your IBM Tivoli Storage Manager server. Although we do not show
the editing of the dsmserv.opt file in this redbook, you can edit the dsmserv.opt file by using
the following OS/400 command:
EDTF STMF('/usr/tivoli/tsm/server/bin/dsmserv.opt')
Important: You must restart the IBM Tivoli Storage Manager server before you activate the
new dsmserv.opt settings.
76 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
5.3.11 IBM Tivoli Storage Manager server run-time options
There are also IBM Tivoli Storage Manager server run-time options which are stored in the
IBM Tivoli Storage Manager server database.
To see the current IBM Tivoli Storage Manager server runtime settings, use one of the
following methods:
IBM Tivoli Storage Manager Web administrative client interface tree structure by
expanding Object view-> Server and selecting Server Status
IBM Tivoli Storage Manager Web Server Command window by entering:
q status
Table 5-3 shows some recommended settings, which may vary depending on your location’s
requirements. See Chapter 15 “Managing Server Operations” in the IBM Tivoli Storage
Manager for OS/400 PASE Administrator’s Guide, GC23-4694, for detailed information about
all available server runtime settings.
You can modify these options using the IBM Tivoli Storage Manager Web administrative client
interface. Or you can do this by entering the IBM Tivoli Storage Manager set command in the
IBM Tivoli Storage Manager Server Command window.
The following examples show how to change the IBM Tivoli Storage Manager server activity
log retention from the default value of 1 to 7. Changing this value ensures that you keep at
least one week’s worth of IBM Tivoli Storage Manager activity log history. Use one of the
following methods to change your IBM Tivoli Storage Manager server:
IBM Tivoli Storage Manager Web administrative client interface tree structure by following
these steps:
a. Expand Object view-> Server and select Server Status.
b. From the Operations list, select Set Activity Log Retention.
c. In the Set Activity Log Retention panel (Figure 5-20), enter the new retention period in
number of days. In our example, we entered 7.
d. Click Finish to process the request.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 77
IBM Tivoli Storage Manager Web Server Command window by entering the following
command:
set actlogretention 7
In this example configuration, you use the predefined disk storage pool BACKUPPOOL and
increase its size to 20 GB by adding four 5 GB storage pool volumes. Normally the disk pool
should be large enough to hold a customers total daily incremental data changes. To learn
more about sizing a disk storage, see Chapter 8 “Managing Storage Pools and Volumes” in
the IBM Tivoli Storage Manager for OS/400 PASE Administrator’s Guide, GC23-4694.
To see the current IBM Tivoli Storage Manager disk storage pools, use one of the following
methods:
IBM Tivoli Storage Manager Web administrative client interface tree structure by following
these steps:
a. Expand Object view-> Server Storage-> Storage Pools and select Query storage
pools.
b. On the Query Storage Pools panel, you can specify different views of the disk storage
pool information. Use the defaults and click Finish. This displays the disk storage pool
information.
IBM Tivoli Storage Manager Web Server Command window by entering either of the
following commands:
query storage
q stg
78 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The Operations Results panel (Figure 5-21) opens.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 79
3. On the Define a Disk Storage Volume panel (Figure 5-22), select the required storage pool
and enter the IBM Tivoli Storage Manager volume name and size. The storage pool
volume name must include the fully qualified path and the format size is the size of the
required volume in MB. In our example, we enter:
– Storage Pool Name: BACKUPPOOL
– Volume Name: /tsmvol/backuppool/bkpvol01.dsm
– Format Size: 5120
– Wait: NO (the process runs as a batch process rather than interactively)
Important: The IBM Tivoli Storage Manager server checks that sufficient disk space is
available on the iSeries server before it creates the disk storage pool volume. If you
don’t have enough disk space, you receive message “ANR7860W Insufficient Space
Available for file......” in the IBM Tivoli Storage Manager servers activity log.
Figure 5-22 Web administrative client interface: Defining a new storage pool volume
Note: You can replace steps one through four by entering the following command in the
Server Command window:
define volume backuppool /tsmvol/backuppool/bkpvol01.dsm formatsize=5120
5. The process now runs as a batch job and may take several minutes to complete. Check
the IBM Tivoli Storage Manager active processes by using one of the following methods to
see when the volume definition has finished:
– IBM Tivoli Storage Manager Web administrative client interface tree structure by
expanding Object view-> Server and selecting Processes
– IBM Tivoli Storage Manager Web Server Command window by entering either of the
following commands:
query process
q pr
80 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. When the define volume process has completed, check the IBM Tivoli Storage Manager
activity log to ensure that the process completed successfully.
Use one of the following methods to access the IBM Tivoli Storage Manager activity log:
– IBM Tivoli Storage Manager Web administrative client interface tree structure by
expanding Object view-> Server and selecting Activity Log
– IBM Tivoli Storage Manager Web Server Command window by entering either of the
following commands:
query actlog
q act
Figure 5-23 shows an example of the completion messages you should see.
Figure 5-23 Web administrative client interface: Extending the disk storage pool
Note: We recommend that you wait for each individual storage pool volume to be
created before you define another volume. Submitting multiple define storage pool
volumes at the same time may cause a degradation in your server’s performance.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 81
9. To see the individual IBM Tivoli Storage Manager storage pools volumes defined, use one
of the following options:
– IBM Tivoli Storage Manager Web administrative client interface tree structure
i. Expand Object view-> Server Storage-> Storage Pools and select Query
storage pool volumes.
ii. On the Query Storage Pools panel, you can specify different views of the disk
storage pool information. Use the defaults and click Finish. See Figure 5-24.
– IBM Tivoli Storage Manager Web Server Command window by entering either of the
following commands:
query volume
q vol
5.3.14 Removing the IBM Tivoli Storage Manager initial BACKUPPOOL volume
You increased the total IBM Tivoli Storage Manager BACKUPPOOL storage pool by 20 GB.
Now you can remove the default 8 MB storage pool volume
(/usr/tivoli/tsm/Server/bin/backup.dsm) that was created during the installation process.
Normally before you remove a storage pool volume, you must ensure that no client data
resides on the volume. Since this storage pool volume has never been used, we can simply
delete this volume. Otherwise you have to move any remaining data to another storage pool
volume or specify “discard data” when deleting the storage pool volume. See “Managing
Storage Pools and Volumes” in the IBM Tivoli Storage Manager for OS/400 PASE
Administrator’s Guide, GC23-4694, for more information.
To remove the IBM Tivoli Storage Manager initial BACKUPPOOL volume, use one of the
following options:
82 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
IBM Tivoli Storage Manager Web administrative client interface tree structure by following
these steps:
a. Expand Object view-> Server Storage-> Storage Pools-> Disk storage pools and
select Volumes.
b. From the list of currently available storage pool names and associated volume names,
select the storage pool volume /usr/tivoli/tsm/server/bin/backup.dsm.
c. From the Operations list, select Delete storage pool volume.
d. Click Finish to process the request.
IBM Tivoli Storage Manager Web administrative client interface Server Command window
by entering the following command:
delete volume /usr/tivoli/tsm/server/bin/backup.dsm
Important: Deleting any of these IBM Tivoli Storage Manager storage pool volumes later
using the IBM Tivoli Storage Manager administration interface does not delete the actual
byte stream file that contains the data within the OS/400 IFS. Use the IBM Tivoli Storage
Manager administration interface to delete the pool from IBM Tivoli Storage Manager
control information. Then, to free iSeries disk space, you must use an interface to the
OS/400 to delete the byte stream file that represents the storage pool volume. You do this
by using one of the following methods:
From a PC workstation, use the Windows operating system network drive interface to
delete the file.
From an OS/400 5250 command screen, enter the Work with Link (WRKLNK)
command. Select 5 (Display) for tsmvol, which lists several subfolders including
backuppool. Within this folder, select one of the four subfolders, for example
-bkpvol04.dsm. Specify to delete this file.
5.4.1 Registering an IBM Tivoli Storage Manager client node to the IBM Tivoli
Storage Manager server
You must register any client node that is sending data to the IBM Tivoli Storage Manager
server first. In this example, we use a Windows 2000 server as our preferred IBM Tivoli
Storage Manager client, although the registration process is the same for all IBM Tivoli
Storage Manager clients.
Using the IBM Tivoli Storage Manager Web tree structure, follow these steps:
1. Expand Object view-> Clients and select Client Nodes.
2. From the Operations list, select Register a new node.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 83
3. On the Register a new node panel (Figure 5-25), enter a node name and password for the
Windows 2000 server. The node name must be any unique name, but is normally the
Windows 2000 computer name. We keep the node name and password the same here,
but normally you assign a secure password. For this example, we entered
ITSMWINCLIENT for both the node name and password.
4. Leave all other fields with their default values.
5. Scroll down the page and click Finish. The client node is added for this server.
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client
We downloaded the EXE file in the /v5r2/Windows/Win32/LATEST/ directory for our example
IBM Tivoli Storage Manager Windows 2000 client node.
84 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. On the Setup Type panel, choose the Typical option and click Next to continue.
7. On the Ready to Install the Program panel, click Install. The installation process takes a
few minutes to complete.
8. When you see the Install Shield Wizard Completed panel, click Finish.
The IBM Tivoli Storage Manager Windows Client is now installed and ready for configuration
Continue with the following section.
Note: If you already installed the IBM Tivoli Storage Manager Windows Client on the
window system, then we recommend that you rename the dsm.opt file normally found in
C:\Program Files\Tivoli\TSM\baclient before you continue with the following steps.
Figure 5-26 IBM Tivoli Storage Manager client configuration: Invalid TCP/IP host
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 85
3. On the TSM Client Configuration Wizards window (Figure 5-27), select the Help me
configure the TSM Backup Archive Client check box and click Next.
4. On the Option File Task panel (Figure 5-28), select the Create a new options file button
and click Next.
86 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
5. On the TSM authentication panel (Figure 5-29), enter the TSM node name for this
Windows server. This is the client node name used in 5.4.1, “Registering an IBM Tivoli
Storage Manager client node to the IBM Tivoli Storage Manager server” on page 83. In
our example, we entered ITSMWINCLIENT. Click Next to continue.
6. On the ITSM Client/Server Communications panel (Figure 5-30), select TCP/IP, and click
Next.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 87
7. On the TCP/IP Parameters panel (Figure 5-31), enter the server address and port of the
IBM Tivoli Storage Manager server. The server address is the IP address or name of the
iSeries server that is running the IBM Tivoli Storage Manager for OS/400 PASE server. In
our configuration, we entered AS27 for the server address and kept the default port of 1500.
Click Next to continue.
8. On the Domain and include/exclude list panel (Figure 5-32), accept the defaults and click
Next.
Figure 5-32 TSM Client Configuration Wizard: Domain and include/exclude lists
88 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
9. On the Completing the TSM Client Configuration Wizard panel (Figure 5-33), click Finish.
10.The IBM Tivoli Storage Manager client connects to the IBM Tivoli Storage Manager for
OS/400 PASE server on the iSeries server. It prompts for an IBM Tivoli Storage Manager
user ID and password (Figure 5-34). We enter ITSMWINCLIENT for both.
11.This completes the basic ITSM client configuration. You must exit and restart the ITSM
client before you can perform any client backups. This is required to activate the new ITSM
client configuration changes made during this configuration.
5.4.5 Backing up using the IBM Tivoli Storage Manager Windows client
This section explains how to back up a test file from a Windows c:\temp directory. This
exercise is only designed to show that the IBM Tivoli Storage Manager server is functioning.
1. Create a test file using Windows Notepad. Place the file in c:\temp on the IBM Tivoli
Storage Manager Windows client system. We created the c:\temp\testfile.txt file.
2. On Windows, select Start-> Programs-> Tivoli Storage Manager-> Backup Archive
GUI.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 89
3. Click Backup on the IBM Tivoli Storage Manager Backup-Archive Client (Figure 5-35).
90 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 5-36 IBM Tivoli Storage Manager Windows client backup: Selecting a file
5. The c:\temp\testfile.txt is now sent to the IBM Tivoli Storage Manager server and placed in
the disk storage pool BACKUPPOOL that was discussed in 5.3.12, “IBM Tivoli Storage
Manager disk storage pools” on page 78. When the Backup Completed window appears,
click OK.
6. A Detailed Status Report shows the statistics for the backup. Exit the status report by
closing the window (click the x box in the upper right corner).
This concludes the basic configuration of the IBM Tivoli Storage Manager server. Continue
with Chapter 6, “Next steps: Getting the IBM Tivoli Storage Manager server ready for
production” on page 93, to configure you IBM Tivoli Storage Manager server further.
Chapter 5. First steps: IBM Tivoli Storage Manager server basic configuration 91
92 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6
In this chapter, you perform further configuration steps to help prepare the IBM Tivoli Storage
Manager server for a production environment.
By our definition, “getting the IBM Tivoli Storage Manager server ready for production” means
that we are describing realistic and meaningful backup functions and at least covering
detailed disaster recovery requirements. We use this phrase to set boundaries around the
scope and details of IBM Tivoli Storage Manager server capabilities that we can cover in a
book such as this one, that is focused on IBM Tivoli Storage Manager server and Backup
Recovery and Media Services (BRMS) integration. We imply similar boundaries through the
wording of the title of Chapter 8, “Backup Recovery and Media Services up and running” on
page 155.
If you changed the QUTCOFFSET system value, then you need to perform the following
actions to set the correct time zone within PASE:
1. Add the environment variable for the OS/400 PASE time zone.
2. Restart the IBM Tivoli Storage Manager server.
3. Accept the new IBM Tivoli Storage Manager server time and enable sessions (depends on
your time zone setting).
6.1.1 Adding an environment variable for the OS/400 PASE time zone
You must set the UNIX TZ environment variable within OS/400 PASE to correctly display local
time. You can set a system-wide variable for OS/400 PASE by using the OS/400 Add
Environment Variable (ADDENVVAR) command. The following example shows how to set the
local time for U.S. Central time zone. All time adjustments shown are based upon the
Coordinated Universal Time (CUT) or Greenwich Mean Time (GMT).
ADDENVVAR ENVVAR(PASE_TZ) VALUE('CST6CDT') LEVEL(*SYS)
You need to use the relevant PASE_TZ values from Table 6-1 for your own local time zone.
94 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
PASE_TZ value Time zone CUT/GMT adjustments
You can use the following command to view PASE_TZ and any other environment variables
on your iSeries server:
WRKENVVAR LEVEL(*SYS)
You should not change any other environment variable unless directed to do so by your
system administrator. The environment variables automatically shipped with OS/400 are used
by iSeries Navigator-based functions and are set for maximum efficiency by default.
6.1.3 Accepting new IBM Tivoli Storage Manager server time, enabling
sessions
Depending on your new OS/400 PASE time-zone setting, the IBM Tivoli Storage Manager
server may disable backup-archive client access to the server. It may issue the error message
“ANR0110E An unexpected system date has been detected” in the activity log.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 95
View the IBM Tivoli Storage Manager messages in the activity log by using one of the
following methods:
IBM Tivoli Storage Manager Web administrative client interface tree structure by following
these steps:
a. Expand Object view-> Server and select Activity Log.
b. The Query panel that opens shows several parameters that you can use to specify the
activity log entries to be queried. Accept the default query parameter values.
c. Scroll down the Query window and click Finish. This brings up the selected log entries.
IBM Tivoli Storage Manager Web Server Command window by entering either of the
following commands:
query actlog
q act
Figure 6-1 shows an example of the error messages you may receive in the IBM Tivoli
Storage Manager server activity log. If you do not see these error messages, then this
completes the setting of the OS/400 PASE time zone.
Figure 6-1 Web administrative client interface: OS/400 PASE time setting messages
If you receive messages similar to those in Figure 6-1, then continue with the following steps:
1. In the IBM Tivoli Storage Manager Server Command window, enter the following
command:
accept date
You should receive message “ANR0894I Current system has been accepted as valid.”
2. In the IBM Tivoli Storage Manager Server Command window, enter the following
command:
enable sessions
You should receive message “ANR2096I Server now enabled for backup/archive client
access.”
96 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
This completes the setting the OS/400 PASE time zone.
6.2.1 IBM Tivoli Storage Manager and BRMS tape library overview
IBM Tivoli Storage Manager can use tape devices for storing client backed-up, archived, and
space-managed data and saving the IBM Tivoli Storage Manager database. These devices
must first be configured in OS/400 before they can be used by IBM Tivoli Storage Manager.
There are several different ways to use tape devices with IBM Tivoli Storage Manager:
Manual library: This is IBM Tivoli Storage Manager using a tape library that is not in
library mode (non-BRMS).
Automated library: This is used when using a tape library in library mode (non-BRMS).
Manual drives: This is for all tape drives that do have the ability to be a tape library
(non-BRMS).
USRDFN library: This type of library (used in this chapter) is defined when IBM Tivoli
Storage Manager is going to use a tape management program such as BRMS to manage
their tape inventory.
We focus only on using BRMS as IBM Tivoli Storage Manager’s tape management system in
this redbook Refer to Chapter 4 “Configuring Storage Devices” in the IBM Tivoli Storage
Manager for OS/400 PASE Administrator’s Guide, GC23-4694, for information about using
IBM Tivoli Storage Manager without BRMS.
Important: We assume that you already installed and configured BRMS on your system at
this point. See Part 3, “Backup Recovery Media Services details” on page 131, which
explains how to install and configure BRMS.
A main benefit to using BRMS as the IBM Tivoli Storage Manager tape manager is that it
allows IBM Tivoli Storage Manager administrators to avoid dealing with checking in volumes,
managing categories, and managing scratch volumes in automated libraries on an iSeries
server. BRMS controls all of these administration tasks.
We create a user-defined (USRDFN) library in IBM Tivoli Storage Manager, which interacts
with the BRMS tape management through a set of user-written exit programs. Sample exit
programs are provided with the IBM Tivoli Storage Manager code that you can use with
BRMS without modification.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 97
EXPIRATION: This exit is used by IBM Tivoli Storage Manager to tell the media
management system that a volume previously registered to IBM Tivoli Storage Manager is
now empty and available for use.
The following section explains how to set up the BRMS exit programs and configure IBM
Tivoli Storage Manager to use the BRMS media management system.
6.2.2 Creating IBM Tivoli Storage Manager and BRMS exit programs
IBM Tivoli Storage Manager comes with default exit programs in both C language and Control
Language (CL) source that are needed to use a tape management program such as BRMS.
They are included in source physical file QAANRSMP in library QTSM after you install
licensed program product (LPP) 5698-ISX. The following section explains how to set up IBM
Tivoli Storage Manager and BRMS exit programs.
From on an OS/400 command line in your IBM Tivoli Storage Manager server iSeries server,
perform the following steps:
1. Create a new library called TSMEXITS:
CRTLIB LIB(TSMEXITS) TYPE(*PROD) TEXT('ITSM exit programs')
2. Copy the exit programs from file QAANRSMP in library QTSM into TSMEXITS.
As stated earlier, these source programs are coded in both C and Control Language (CL).
Using these source file members as a base, you can customize the programs or create
your own. In this environment, we use the CL program examples as is (no changes).
a. Create a duplicate file of QAANRSMP:
CRTDUPOBJ OBJ(QAANRSMP) FROMLIB(QTSM) OBJTYPE(*FILE) TOLIB(TSMEXITS)
When you create this duplicate object all of the members are copied but are empty (no
source statements). Since we are only going to be using the control language (CL)
programs you may want to delete the C member names from the duplicated source file.
b. Copy the CL source exit programs into the duplicated source file:
CPYSRCF FROMFILE(QTSM/QAANRSMP) TOFILE(TSMEXITS/QAANRSMP) FROMMBR(DELETECL)
CPYSRCF FROMFILE(QTSM/QAANRSMP) TOFILE(TSMEXITS/QAANRSMP) FROMMBR(DISMOUNTCL)
CPYSRCF FROMFILE(QTSM/QAANRSMP) TOFILE(TSMEXITS/QAANRSMP) FROMMBR(EXPIRECL)
CPYSRCF FROMFILE(QTSM/QAANRSMP) TOFILE(TSMEXITS/QAANRSMP) FROMMBR(MOUNTCL)
3. Enter the Programming Development Manager (STRPDM) command for library TSMEXITS
and file QAANRSMP.
4. For all four exit programs located in this file, you need to change the type to CLP.
5. Type 14 (Compile) next to each exit program and compile them.
6. Verify that the programs compiled successfully. You can do this by looking for messages
on your 5250 workstation message queue or by using the Work with Submitted Jobs
(WRKSBMJOB) command.
98 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. From the Operations list, select Define Exit Program.
4. On the Define Exit Program panel (Figure 6-2), enter the name of the library, TSMEXITS
in our example, and the exit program, MOUNTCL that we created previously. Click Finish.
Repeat this process for each of the four exit programs: MOUNTCL, DELETECL, EXPIRECL,
and DISMOUNTCL.
6.2.4 Defining the IBM Tivoli Storage Manager USRDFN tape library
The following steps show how to define a user-defined tape library to IBM Tivoli Storage
Manager:
1. The library name used in IBM Tivoli Storage Manager must match the name of the BRMS
tape library location. To verify BRMS device information, on an OS/400 command line,
enter the Work with Devices (WRKDEVBRM) command. You see the Work with Devices
display (Figure 6-3) in BRMS.
2. Type option 5 in the Opt column next to the required tape library. In this example, we select
TAPMLB05 and press Enter.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 99
Work with Devices AS27
In our example, the iSeries device is called TAPMLB05. The BRMS location associated
with this device is also called TAPMLB05.
3. Go to the IBM Tivoli Storage Manager Web administrative client interface tree structure
and follow the next steps:
a. Expand Object View-> Server Storage-> Libraries and Drives and select USRDFN
Libraries.
b. From the Operations list, select Define USRDFN Library.
c. In the USRDFN Library panel (Figure 6-5), in the Library Name field, enter the name of
your tape library name. The library name must be the same name as your BRMS tape
library location (see Figure 6-4). In this example, we enter TAPMLB05.
d. Leave the drive selection parameter as the default of EXIT.
e. Click Finish to create the library definition.
100 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 6-5 Defining a USRDFN library
We strongly recommended that you create a new media class in BRMS for use only by IBM
Tivoli Storage Manager. This makes managing your run-time environment much easier than
trying to reuse another BRMS media class. See 6.2.7, “Sharing a common media pool
between IBM Tivoli Storage Manager, BRMS” on page 104, for further details.
1. On an OS/400 command line, enter the following command and press Enter:
WRKCLSBRM *MED
2. Enter 1 (Add) in the Opt field and the new BRMS media class name in the Class field.
3. The Add Media Class display (Figure 6-6) opens. Since our example configuration is using
LTO2 cartridges in an IBM 3584 tape library, we call our new BRMS media class
ITSMLTO2. Enter the required density for your tape library media and a relevant text
description. Leave all other fields with their default values. Press Enter to create the BRMS
media class.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 101
Add Media Class
4. Create an ITSM media class with the same name. Go to the IBM Tivoli Storage Manager
Web administrative client interface tree structure and follow these steps:
a. Expand Object view-> Server Storage and select Device Classes. The left tree area
lists the class of devices that may be on your system.
b. Select the type of tape device you have. In this example, we clicked LTO Device
Classes. In the right panel, you can define the LTO Device Classes. We use a 3584
tape library with LTO2 drives inside.
c. From the Operations list, select Define Device Classes.
d. Enter the following parameter values:
• Device Class Name: The device class name must match the BRMS media class
that was created in step 3.
• Library Name: Select the library name from the list. The name should be the same
as the library name used in 6.2.4, “Defining the IBM Tivoli Storage Manager
USRDFN tape library” on page 99.
• Mount Retention: This parameter indicates is how long (in minutes) the IBM Tivoli
Storage Manager allocates the drive after a completed operation. Because this
drive is shared, with BRMS, you want to specify a number that is small enough so
native BRMS saves can allocate the drive if needed.
• Mount Limit: This parameter defines how many drives in the tape library are
available to IBM Tivoli Storage Manager. For example, you may have a tape library
which has six drives available in BRMS, but only wants a maximum of two to ever
be used by IBM Tivoli Storage Manager. In this case, you set Mount Limit to 2.
In this example configuration, we enter the following values as shown in Figure 6-7:
• Device Class Name: ITSMLTO2
• Library Name:TAPMLB05
• Mount Limit: 2
• Mount Retention: 1
102 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 6-7 Web administrative client interface: Defining the device class
Refer to the define devclass command in Chapter 5 “Command Reference” in the IBM Tivoli
Storage Manager for OS/400 PASE Administrator’s Reference, GC23-4695, for further details
about the parameters that are available when you create an IBM Tivoli Storage Manager
device class.
6.2.6 Verifying the IBM Tivoli Storage Manager and BRMS exit programs
You are now ready to verify that you can use the tape library with the IBM Tivoli Storage
Manager and BRMS exit programs. You must first ensure that you have expired BRMS media
available for your IBM Tivoli Storage Manager media class. You can check this by using the
Work with Media using BRM (WRKMEDBRM) command. Refer to 8.7, “Adding media to the
pool” on page 181, for information about adding media to BRMS. The following example
explains how to perform a full online IBM Tivoli Storage Manager database backup using the
new BRMS media class.
Go to the IBM Tivoli Storage Manager Web administrative client interface tree structure and
follow these steps:
1. Expand Object view and select Database.
2. From the Operations list, select Backup Database.
3. On the Backup Database panel (Figure 6-8), follow these steps:
a. Select the new device class created in the previous section. For Device Class, we
select ITSMLTO2 and for Type, we select FULL.
b. Leave all other fields with their default values.
c. Click Finish to submit the backup.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 103
Figure 6-8 Backing up the IBM Tivoli Storage Manager database
Note: If you are using the Server Command window (not shown in Figure 6-8) of the
IBM Tivoli Storage Manager Administration browser interface, you can enter the q act
or query actlog command to view the same contents of the activity log instead of using
the tree structure interface as described here.
6.2.7 Sharing a common media pool between IBM Tivoli Storage Manager,
BRMS
We recommend that you create a separate media class for your IBM Tivoli Storage Manager
server. Do not share media between IBM Tivoli Storage Manager and BRMS for these
reasons:
IBM Tivoli Storage Manager does not use data retention the same way that BRMS uses
data retention. IBM Tivoli Storage Manager give all volumes it uses a *PERM expiration
date so BRMS never expires IBM Tivoli Storage Manager server tapes, except through the
expirecl exit program. We define this in 6.2.2, “Creating IBM Tivoli Storage Manager and
BRMS exit programs” on page 98.
It is possible for both applications to own the same tape volume. For example, if you use
IBM Tivoli Storage Manager to perform a save to BRMS tape using the media class that
you created for IBM Tivoli Storage Manager, it writes to the volume and enters an
expiration date of *PERM on it. Now BRMS can do a save with append set to *YES using
the same media class. If all the append criteria is met, BRMS writes to the next sequence
number. Now both applications have data on the tape.
104 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
When IBM Tivoli Storage Manager expires the volume, because the IBM Tivoli Storage
Manager data is no longer needed, it tells BRMS to expire it. The volume displays as
expired. Now the volume can be written to again, starting with sequence number 1.
Because IBM Tivoli Storage Manager does not check to see if there is any BRMS data on
the volume when it expires the tape, any data that BRMS still needs is overwritten if
something uses that expired volume. You do not want this to happen and later try to use
the media to recover.
IBM Tivoli Storage Manager storage pools can be further classified as primary storage pools
and copy storage pools. This takes into account the fact that data can be duplicated within the
storage hierarchy for disaster recovery purposes. The duplication is performed at the storage
pool level, rather than at the individual storage pool volume level.
Primary storage pools are the place where the original IBM Tivoli Storage Manager client
data is stored on a backup function. They are normally on-site storage pools, either on the
iSeries disk (IFS) or in a tape library. In this example configuration, this is a 3584 tape library.
Copy storage pool volumes can be defined as on site (in a tape library) or off site (ejected and
placed in a secure location for disaster recovery). Each pool is categorized by type and format
with an IBM Tivoli Storage Manager device class. The device class describes how to access
and use the storage pool volumes. Tape device classes tell IBM Tivoli Storage Manager which
tape library to use on the iSeries server, the number of drives in that library that are available
to IBM Tivoli Storage Manager and the tape format that is used.
In the example configuration used throughout this redbook (shown in Figure 6-9), we created
a 20 GB disk storage pool called BACKUPPOOL. This storage pools consists of four storage
pool volumes that reside in the OS/400 IFS. Each volume is defined as a 5 GB IFS streamed
file in the /tsmvol/backuppool/ directory on the iSeries server (shown on the left side of
Figure 6-9). This is the first step in our IBM Tivoli Storage Manager storage hierarchy
configuration.
Client data can now be saved to the iSeries disk. But how do we migrate that data to tape?
Simple, we create additional storage pools.
In our environment, we create two additional storage pools. The first storage pool we create is
a sequential access storage pool called BACKUPLTO. This storage pool uses tape cartridges
(known as storage pool volumes in IBM Tivoli Storage Manager) in our 3584 tape library.
These tapes contain all the IBM Tivoli Storage Manager client data migrated from the
BACKUPPOOL disk storage pool and remain available in the 3584 tape library.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 105
The second storage pool we create is a copy storage pool called COPYLTO. This storage
pool also uses tape cartridges in the 3584 tape library, but these tapes are ejected each day
and sent off site for disaster recovery purposes.
COPYLTO
Tape Tape
Tape Tape
iSeries - AS27
ITSM
storage pool
volumes
ITSM server
Each disk storage pool has a high and low threshold value, which represents a percentage of
the disk space used or filled with IBM Tivoli Storage Manager client data. Figure 6-10 shows
the migration values of our BACKUPPOOL disk storage pool. The high threshold value is set
to 90 percent and the low is set to 70 percent (see the top tier in Figure 6-10). This means
that client data continues to be sent to the disk BACKUPPOOL until 90 percent of the disk
pool is full, at which point, data is then migrated to the next storage pool defined. In our
example configuration, this is the BACKUPLTO storage pool in the 3584 tape library. Data is
migrated from the disk pool until the low migration threshold value is reached. Again in our
example configuration, this is 70 percent.
Migration can also be forced by an IBM Tivoli Storage Manager administrator by lowering
these storage pool threshold values. Figure 6-10 shows the IBM Tivoli Storage Manager
storage pool BACKUPPOOL at approximately 60 percent full. When the high and low
threshold values are set to 20 and 10 respectively (see the middle tier in Figure 6-10), data
starts to migrate to the BACKUPLTO storage pool in the 3584 tape library. Data continues to
migrate until the low threshold of 10 is met (see the bottom tier in Figure 6-10).
106 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Disk storage pool Migration Threshold
BACKUPPOOL BACKUPLTO
Hi = 90 %
BACKUPPOOL BACKUPLTO
Start Tape Tape Tape
Migration
Hi = 20%
Tape Tape Tape
Lo = 10%
BACKUPPOOL BACKUPLTO
End
Tape Tape Tape
Migration
Hi = 20%
Tape Tape Tape
Lo = 10%
We can also define a maximum file size that is allowed in the disk storage pool. Although, this
is not used in our configuration, we can, for example, define a maximum file size limit of
300 MB. This means any file greater than 300 MB is not sent to the disk storage pool
BACKUPPOOL. Instead it is sent directly to the BACKUPLTO storage pool in the 3584 tape
library.
All of these “conditions” can be set up. Also the IBM Tivoli Storage Manager database keeps
track of where all the client data resides within the storage hierarchy.
6.3.3 Collocation
Collocation is a parameter on the sequential access storage pools definition. This function is
used to keep the same client’s data on a minimum number of tape volumes. The main
purpose of this feature is to help reduce client data restore times. A disadvantage of this
function is that the total number of tape cartridges used in the storage pool increases.
Figure 6-11 shows an example of three clients data spread over a disk storage pool. When
the client data is migrated to the sequential access storage pool, provided enough tapes are
available in the pool, IBM Tivoli Storage Manager attempts to keep all of the data for Client A
on one tape volume, all of the data for Client B on another tape volume, and all of the data for
Client C on a third tape volume.
All of the examples in our test configuration do not use the IBM Tivoli Storage Manager
collocation feature.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 107
Disk Storage Pool
Hi thresh
Lo thresh
A B A
B C
C A B
A Client A
Migration
B Client B
C Client C
CLIENT A CLIENT B CLIENT C
C
A
A A B B B C
6.3.4 Reclamation
Space on a sequential volume becomes reclaimable as files expire or are deleted from the
volume. For example, files become obsolete because of aging or limits on the number of
versions of a file.
In reclamation processing, the server rewrites files on the volume being reclaimed to other
volumes in the storage pool, making the reclaimed volume available for reuse. The server
reclaims the space in storage pools based on a reclamation threshold that you can set for
each sequential access storage pool. When the percentage of space that can be reclaimed
on a volume rises above the reclamation threshold, the server reclaims the volume.
Figure 6-12 shows a sequential storage pool with four storage pool volumes. After week 1,
tapes 1 through 3 are full with client data and tape 4 is empty (scratch tape). After week 2,
client data has expired on the tape volumes. Tape 1 has only 25% of valid client data; tape 2
has 15% of valid client data; and tape 3 has 90% of valid client data. If the reclamation
threshold of the storage pool is set to 60, which means reclamation is started when 60% or
more of the tape volume contains expired client data, then valid client data is copied to
another storage pool volume. In this example, active data from tape 1 and 2 is automatically
copied to the empty tape 4. Also tapes 1 and 2 are reclaimed and become empty volumes
(scratch tapes) available for reuse.
108 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Tape 1 Tape 2 Tape 3 Tape 4
Week 1
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 109
IBM Tivoli Storage Manager Web Server Command window by entering the following
command:
define stgpool backlto2 itsmlto maxscratch=10
Figure 6-13 Web administrative client interface: Creating a sequential storage pool
110 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 6-14 Web administrative client interface: Updating the disk storage pool
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 111
IBM Tivoli Storage Manager Web Server Command window by entering the following
command:
define stgpool copylto itsmlto2 pooltype=copy maxscratch=30 reusedelay=5
Figure 6-15 Web administrative client interface: Defining the copy storage pool
To improve the I/O performance of the IBM Tivoli Storage Manager disk storage pool
volumes, perform the following actions:
1. Load and apply PTF MF30245 for OS/400 V5R2M0.
2. Enter the following command for each IBM Tivoli Storage Manager disk storage pool
volume in the OS/400 IFS:
CHGATR OBJ('/path/stgpoolfile') ATR(*MAINSTGOPT) VALUE(*MINIMIZE)
This enhancement allows greater write speed to the IBM Tivoli Storage Manager disk
storage pool volumes. Therefore, it improves the IBM Tivoli Storage Manager backup
performance.
In this example configuration, we entered the following commands for the four disk storage
pool volumes in our BACKUPPOOL disk storage pool:
CHGATR OBJ('/tsmvol/backuppool/bkpvol01.dsm') ATR(*MAINSTGOPT) VALUE(*MINIMIZE)
CHGATR OBJ('/tsmvol/backuppool/bkpvol02.dsm') ATR(*MAINSTGOPT) VALUE(*MINIMIZE)
CHGATR OBJ('/tsmvol/backuppool/bkpvol03.dsm') ATR(*MAINSTGOPT) VALUE(*MINIMIZE)
CHGATR OBJ('/tsmvol/backuppool/bkpvol04.dsm') ATR(*MAINSTGOPT) VALUE(*MINIMIZE)
112 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6.4 IBM Tivoli Storage Manager policies
This section discusses the use of IBM Tivoli Storage Manager policies only at a very high
level. For a more detailed explanation, see Chapter 11 “Implementing Policies for Client Data”
in the IBM Tivoli Storage Manager for OS/400 PASE Administrator’s Guide, GC23-4694.
The IBM Tivoli Storage Manager server organizes clients (nodes) and client data by the
following IBM Tivoli Storage Manager policy definitions:
Policy domain: A client system, or node, can be grouped together with other nodes into a
policy domain. In a domain, all clients are managed using the same data management
rules. Normally you divide your clients by system type or organizational structure. In our
example configuration, we use the default policy for the Windows test client.
Policy set: The policy domain links the nodes to a policy set, which consists of
management classes. Only one policy set can be active within a policy domain. However,
you can have many more sets of policies inactive in your policy domain.
Management class: A management class contains rules called copy groups that it links to
the specific data. When the data is linked to particular rules, it is said to be bound to the
management class that contains the rules. This can happen at the object (file) level, but
you can also do this at the directory or filespace level. You can link data explicitly or
implicitly by using the default management class.
Copy group: The copy group defines where data is stored, the number of versions that
are kept, and how long they are retained. Normally there are two copy groups per
management class. There is a backup copy group and an archive copy group.
IBM Tivoli Storage Manager has a default policy, called STANDARD, that is configured when
the product is installed. The STANDARD policy is good for testing your backup environment.
However, you may need to either update this policy or create your own polices to organize
your backup strategy.
The STANDARD policy allows up to two backup versions of a file from the client’s system.
Theses files are first stored in the disk storage pool BACKUPPOOL. The most recent backup
version is retained for as long as the original file is on the clients file system. All other versions
are retained for up to 30 days after they become inactive. Any deleted files from the client
system are kept for an additional 60 days.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 113
b. Two copy groups are displayed, one with a policy set name of ACTIVE and another
called STANDARD. It is not possible to change an active policy set. Instead you must
modify the STANDARD policy set. Then you must validate it and reactivate it for any
changes to take effect. Select the non-active copy group STANDARD (circled in
Figure 6-16).
114 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 6-17 Web administrative client interface: Updating the copy group
Figure 6-18 shows the ACTIVE copy group with the original Version Data Exists value of 2
and the modified copy group with the new setting of 10.
Figure 6-18 Web administrative client interface: Querying the copy group
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 115
You can validate and activate the policy set by using one of the following methods:
IBM Tivoli Storage Manager Web administrative client interface tree structure by following
these steps:
a. Expand Object view-> Policy Domains and select Policy Sets.
b. Select the STANDARD policy set name.
c. From the Operations list, select Validate Policy Set and click Finish.
d. You see the message “ANR1515I Policy set STANDARD validated in domain
STANDARD (ready for activation)”. Click Return to go back to the Policy panel.
e. To activate the policy set, from the Operations list, select Activate Policy Set and click
Finish.
Now you see the message “ANR1514I Policy set STANDARD activated in policy domain
STANDARD”. This completes the validation and activation of the default policy set.
IBM Tivoli Storage Manager Web Server Command window by entering the following
commands:
validate policyset standard standard
activate policyset standard standard
The IBM Tivoli Storage Manager server also provides an administrative command scheduler.
This scheduler allows daily routine administrative tasks to be scheduled as individual
commands or combined in to server command scripts. Some of the common routine tasks
are:
Creating a copy of the previous night’s client backup data for off-site storage
Forcing client data migration from disk to sequential access storage pools
Backing up the IBM Tivoli Storage Manager database
Deleting old IBM Tivoli Storage Manager database backups
Expiration of client data
Reclaiming expired data from sequential storage pool volumes
The following sections shows examples of creating server command scripts and server
command schedules that are used in our IBM Tivoli Storage Manager test configuration to
help automate the daily administrative tasks. If you need more information about automating
server functions, see Chapter 16 “Automating Server Operations” in the IBM Tivoli Storage
Manager for OS/400 PASE Administrator’s Guide, GC23-4694.
116 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
IBM Tivoli Storage Manager commands are entered in the script as though they are issued
from an IBM Tivoli Storage Manager command line or window. These commands are
processed sequentially by adding the WAIT TAG to the end of the command line.
Example 6-1 Sample IBM Tivoli Storage Manager server command script
backup stgpool BACKUPPOOL COPYLTO wait=yes
backup stgpool BACKUPLTO COPYLTO wait=yes
backup db type=full devcl=ITSMLTO2 wait=yes
delete volhist type=dbb todate=-5
expire inventory
The following steps show how to create an IBM Tivoli Storage Manager command script. to
do this, you can use either the IBM Tivoli Storage Manager Web administrative client interface
tree structure or the IBM Tivoli Storage Manager Server Command window:
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 117
IBM Tivoli Storage Manager Web administrative client interface tree structure
a. Expand Operation view and select Automate operations-> Define a command
script
b. In the Define a command script panel (Figure 6-19), follow these steps:
i. Enter a valid name for the command script in the name field. The name cannot
contain any spaces. In this example, we enter DAILY_MAINT.
ii. In the Description field, enter an informative name. In this example, we enter ITSM
Daily Maintenance.
iii. In the large script window enter the IBM Tivoli Storage Manager commands to be
performed. In this example, we entered the following information:
backup stgpool BACKUPPOOL COPYLTO wait=yes
backup stgpool BACKUPLTO COPYLTO wait=yes
backup db type=full devcl=ITSMLTO2 wait=yes
delete volhist type=dbb todate=-5
expire inventory
c. Click Finish to process the request. See the following section to schedule this IBM
Tivoli Storage Manager command script.
IBM Tivoli Storage Manager Web Server Command window by entering the following
commands in the order shown:
define script DAILY_MAINT "backup stgpool BACKUPPOOL COPYLTO wait=yes"
desc="ITSM Daily Maintenance"
update script DAILY_MAINT "backup stgpool BACKUPLTO COPYLTO wait=yes"
update script DAILY_MAINT "backup db type=full devcl=ITSMLTO2 wait=yes"
update script DAILY_MAINT "delete volhist type=dbb todate=-5"
update script DAILY_MAINT "expire inventory”
Figure 6-19 Web administrative client interface: Creating the server command script
118 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6.5.2 Scheduling a daily maintenance script
The IBM Tivoli Storage Manager server includes an administrative command schedule. You
can use this schedule to automate the processing of IBM Tivoli Storage Manager server
commands at specific time periods. The following example shows how to configure a
command schedule to run the DAILY_MAINT script at 05:00 each day. To do this, you can use
either the IBM Tivoli Storage Manager Web administrative client interface tree structure or the
Server Command window configuration method.
IBM Tivoli Storage Manager Web administrative client interface tree structure by following
these steps:
a. Expand Operation view-> Automate operations and select Define an
administrative command schedule.
b. In our example, to schedule the DAILY_MAINT script to run each day at 05:00, we
entered the following information as shown in Figure 6-20:
• Schedule Name: DAILY_MAINT
• Command: run DAILY_MAINT
• Active?: YES
• Description: ITSM Daily Maintenance
• Start time: 05:00
See the “Tailoring Schedules” section in Chapter 16 of the IBM Tivoli Storage Manager
for OS/400 PASE Administrator’s Guide, GC23-4694, for a detailed explanation about
each of the available parameters.
IBM Tivoli Storage Manager Web Server Command window by entering:
define schedule daily_test type=administrative cmd="run daily_maint" active=yes
starttime=05:00 description="ITSM Daily Maintenance"
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 119
6.5.3 Scheduling disk storage pool migration
In our IBM Tivoli Storage Manager server configuration, client data is sent to the disk storage
pool BACKUPPOOL. The high and low migration threshold values are set to 90% and 70%
respectively. If the disk storage pool is correctly sized, then all of the evening’s backup data
remains in the BACKUPPOOL disk storage pool.
To force the migration of the BACKUPPOOL storage pool, we must lower the storage pool
migration thresholds values by using the update stgpool command. This command forces
the storage pool to immediately migrate data to their next level storage pool. The migration
process continues until the low migration threshold is reached.
We need to create two administrative command schedules that will run each day:
START_MIGR: This command schedule is run at 15:00 and sets both the high and low
migration threshold values to 0. This forces all data residing in the disk storage pool to
migrate to next level storage pool BACKUPLTO.
The schedule can be created by using either the Web administrative client interface tree
structure or the Server Command window (as in the previous section). You can enter the
following IBM Tivoli Storage Manager command in the Server Command window to create
the schedule:
define schedule start_migr type=administrative cmd="update stg backuppool hi=0 lo=0"
active=yes starttime=15:00 description="Start BACKUPPOOL Migration"
END_MIGR: This command schedule is run at 18:00 and resets the high and low
migration threshold values back to 90% and 70% respectively. If the storage pool
threshold values are not reset, then the next client backups write directly to the
BACKUPLTO storage pool and defeat the purpose of using the disk storage pool.
You can enter the following IBM Tivoli Storage Manager command in the Server
Command window to create the schedule:
define schedule end_migr type=administrative cmd="update stg backuppool hi=90 lo=70"
active=yes starttime=18:00 description="End BACKUPPOOL Migration"
The server reclaims the space in storage pools based on a reclamation threshold that you
can set for each sequential access and copy storage pool. When the percentage of space
that can be reclaimed on a volume rises above the reclamation threshold, the server reclaims
the volume.
We recommend that you control when the reclamation process runs by using schedules that
set and reset the reclamation threshold for the storage pools. This way you can be sure that
reclamation doesn’t interfere with other IBM Tivoli Storage Manager server processes or IBM
Tivoli Storage Manager client backups.
Reclamation of BACKUPLTO
We need to create daily command schedules to start and stop the reclamation process for the
BACKUPLTO storage pool:
120 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
START_BACKLTO_REC: This command schedule is run at 09:00 and sets the
reclamation threshold to 60%. This forces all tapes in the BACKUPLTO storage pool,
which has 60% or more free space to be reclaimed.
You can create this schedule by using either the Web administrative client interface tree
structure or the Server Command window (as in the previous section). You can enter the
following IBM Tivoli Storage Manager command in the Server Command window to create
the schedule:
define schedule start_backuplto_rec type=administrative cmd="update stg backuplto
rec=60" active=yes starttime=09:00 description="Start BACKUPLTO Reclamation"
END_BACKUPLTO_REC: This command schedule is run at 11:00 and resets the
reclamation threshold value back to 100% (disables the reclamation process).
You can enter the following IBM Tivoli Storage Manager command in the Server
Command window to create the schedule:
define schedule end_backuplto_rec type=administrative cmd="update stg backuplto rec=100"
active=yes starttime=11:00 description="End BACKUPLTO Reclamation"
Reclamation of COPYLTO
IBM Tivoli Storage Manager cannot physically move the data from one of these volumes to
another. That is because they are normally in an off-site vault and, therefore, are not available
in the tape library. IBM Tivoli Storage Manager manages reclamation for an off-site copy pool
(COPYLTO) by obtaining the active data from a primary storage pool
(BACKUPLTO/BACKUPPOOL). These active files are then written to a new tape in the
COPYLTO storage pool and the off-site volume is expired. The new volume is moved to the
off-site location. The off-site volumes, whose active data is now combined, is moved back to
the scratch pool on site and made available for reuse.
We now create a weekly command schedule to start and stop the reclamation process for the
COPYLTO storage pool. We decided to perform the COPYLTO as a weekly schedule rather
than a daily one. In our configuration, we move any newly created COPYLTO tapes off site
every day, but only return tapes tape on site once a week. In your configuration, you may run
these schedules daily.
START_COPYLTO_REC: This command schedule is run at 11:00 and sets the
reclamation threshold to 60%. This forces all tapes is the COPYLTO, which have 60% or
more free space to be reclaimed.
You can create the schedule by using either the Web administrative client interface tree
structure or the Server Command window (as in the previous section). You can enter the
following IBM Tivoli Storage Manager command in the Server Command window to create
the schedule:
define schedule start_copylto_rec type=administrative cmd="update stg backuplto rec=60"
active=yes starttime=11:00 description="Start COPYLTO Reclamation" day=su
END_COPYLTO_REC: This command schedule is run at 15:00 and resets the
reclamation threshold value back to 100% (disables the reclamation process).
You can enter the following IBM Tivoli Storage Manager command in the Server
Command window to create the schedule:
define schedule end_copylto_rec type=administrative cmd="update stg copylto rec=100"
active=yes starttime=15:00 description="End COPYLTO Reclamation" day=su
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 121
6.5.5 Querying administrative command schedules
Each scheduled administrative command is called an event. All scheduled events, including
their status, are tracked by the server. An event record is created in the server database
whenever processing of a scheduled command is created or missed.
You can check when the schedule is projected to run and whether it ran successfully by using
the IBM Tivoli Storage Manager Web administrative client interface tree structure. Or you can
do this by entering the query event command in the Server Command window.
To help manage schedules for administrative commands, you can request information about
scheduled and completed events. For information about past and projected scheduled
processes, use a general query. If the time range you specify includes the future, the query
output shows which events should occur in the future based on current schedules.
For example, to see all the administrative command schedules that ran the previous day, we
can use one of the following methods. Figure 6-21 shows the resulting panel of these steps.
IBM Tivoli Storage Manager Web administrative client interface tree structure by following
these steps:
a. Expand Operation view-> Automate operations and select View events for
administrative schedules.
b. Enter the data and time range that you want to query. In this example, we want to query
all administrative events from 05:00 to 19:00 on the previous day. We used -1 as the
begin date. If you want to see future events, you can enter +1 for the date parameters.
IBM Tivoli Storage Manager Web Server Command window by entering the following
command:
query event * type=admin begindate=-1 begintime=05:00
122 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
See Chapter 21 “Protecting and Recovering Your Server” in the IBM Tivoli Storage Manager
for OS/400 PASE Administrator’s Guide, GC23-4694, for a comprehensive guide on
protecting the IBM Tivoli Storage Manager server.
In the event of a media failure or complete disaster, some or all of the IBM Tivoli Storage
Manager clients data can be lost. We can help protect this data by performing daily backups
of the primary storage pools to an IBM Tivoli Storage Manager copy pool and then moving
these copy pool volumes off site. You can back up the primary storage pools by using the IBM
Tivoli Storage Manager server backup stgpool command.
We added the following lines to the IBM Tivoli Storage Manager Daily Maintenance script
created in 6.5.1, “Creating a daily maintenance script” on page 116:
backup stgpool BACKUPPOOL COPYLTO wait=yes
backup stgpool BACKUPLTO COPYLTO wait=yes
The backup stgpool operation is incremental so it only copies files that arrived in the primary
storage hierarchy since the previous backup stgpool execution. When the backup completes,
move the copy pool volumes off site. See Chapter 10, “Backup Recovery and Media Services
movement of IBM Tivoli Storage Manager media” on page 337, for details about IBM Tivoli
Storage Manager media movement.
We can use the IBM Tivoli Storage Manager set logmode command to set the mode for
saving recovery log records. The log mode determines how long IBM Tivoli Storage Manager
saves records in the recovery log and the kind of database recovery you can use. The two log
modes are:
NORMAL: IBM Tivoli Storage Manager only keeps records in the recovery log until they
are committed. IBM Tivoli Storage Manager deletes any unnecessary records from the
recovery log. Changes made to the database since the last backup cannot be recovered.
Any backup versions of the database created by entering the backup db command can
only be used to perform point-in-time recovery. In NORMAL log mode, you may need less
space for the recovery log, because IBM Tivoli Storage Manager does not keep all records
already committed to the database.
ROLLFORWARD: IBM Tivoli Storage Manager saves all recovery log records that contain
changes made to the database since the last time it was backed up. IBM Tivoli Storage
Manager deletes recovery log records only after a successful database backup. The
recovery log records can be used to restore a database to its most current state
(roll-forward recovery) after loading the most current database backup series. A database
backup series created in ROLLFORWARD mode can be used for either point-in-time
recovery or roll-forward recovery.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 123
We recommend that you enable ROLLFORWARD log mode if your site requires a high level
of availability for the IBM Tivoli Storage Manager server. ROLLFORWARD log mode may
require a significant amount of space to record all activity.
Important: If you change the IBM Tivoli Storage Manager database to use the
ROLLFORWARD mode, then you may need to increase the recovery log pool size. To
estimate the new value, reset the cumulative consumption value using the administrative
command reset logconsumption. Then monitor the cumulative consumption over a
number of days. Divide the cumulative consumption by the number of days since you reset
the value to get are presentative value. A safe size for the log pool is around 30 to 40
percent larger than this figure.
To change the recovery log mode from normal to rollforward, use the following IBM Tivoli
Storage Manager command:
set logmode rollforward
Use the backup db command to back up an IBM Tivoli Storage Manager to sequentially
access storage volumes. You can use this command to run one of the following types of
backup:
Full backup (type=full): Copies the entire IBM Tivoli Storage Manager database.
Incremental backup (type=incremental): Copies only those database pages that were
added or changed since the last time the database was backed up. The maximum number
of incremental backups you can run between full backups is 32.
DBSnapshot (type=dbsnapshot): Specifies that you want to run a full snapshot database
backup. The entire contents of the database are copied. A new snapshot database backup
is created without interrupting the existing full and incremental backup series for the
database.
IBM Tivoli Storage Manager can perform full and incremental backups of the database to tape
while the server is up and running and available to clients.
Important: A new volume or tape is used each time you back up an IBM Tivoli Storage
Manager database. It is not possible to appended IBM Tivoli Storage Manager database
backups on the same volume. This ensure that, in the event of a media failure, not all IBM
Tivoli Storage Manager database backups are lost.
The following example shows how to perform a full backup using our ITSMLTO2 device class:
backup db type=full devclass=ITSMLTO2
124 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
We perform a full database backup each day in our DAILY_MAINT script that we created in
6.5.1, “Creating a daily maintenance script” on page 116. After a full backup, you can perform
incremental backups, which copies only the changes to the database since the previous
backup. To perform an incremental backup of the database to the ITSMLTO2 device class,
enter the following command:
backup db type=incremental devclass=ITSMLTO2
To make a snapshot backup of the database to our ITSMLTO2 device class, enter the
following command:
backup db type=dbsnapshot devclass=ITSMLTO2
Important: Snapshot database backups should not replace full and incremental backups.
If the server’s recovery log is in ROLLFORWARD mode, and a snapshot database backup
is performed, the recovery log keeps growing. When full and incremental backups are
performed with ROLLFORWARD mode enabled, the recovery log is restarted each time a
full backup is performed.
Volume history
Every volume or tape that is used by IBM Tivoli Storage Manager, including the volumes used
for the IBM Tivoli Storage Manager database backups, are tracked within the server
database. You can access this information while the server is up by using the query
volhistory command. The volume history information is important because it tells you which
volume holds your most recent database backup. In the event of loss or corruption of the
server database, you need to know this to restore your database automatically. However if the
database is not available, you cannot retrieve the information from there. IBM Tivoli Storage
Manager database volume history can be copied to an external IFS streamed file by using the
VOLUMEHISTORY option in the dsmserv.opt file.
Example 6-2 shows an extract from our test IBM Tivoli Storage Manager server options file
(/usr/tsm/tivoli/server/bin/dsmserv.opt) after we updated it with the VOLUMEHISTORY entry.
Example 6-2 Extract from our test IBM Tivoli Storage Manager server options file
* VOLUMEHISTORY
* ********************************************************************
VOLUMEHistory /tsmvol/files/volhist.out
*
* Specifies the name of a file that should contain sequential
* volume history information when it is changed by the server.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 125
* Sequential information is used by the administrator
* and server processes during server database recovery.
Example 6-3 shows an extract from the /tsmvol/files/volhist.out file from our IBM Tivoli
Storage Manager server. You can see the third line from the bottom of the file has an entry for
a full database backup on volume LB0705.
You can also back up the volume history information at any time, by entering the backup
volhistory command.
The volume history file is used in IBM Tivoli Storage Manager recovery to find the IBM Tivoli
Storage Manager database backups. You can recover the database without a copy of the
volume history file, but you must know where and which are your IBM Tivoli Storage Manager
database backups.
Device configuration
The IBM Tivoli Storage Manager device configuration information is stored in the database,
but during a database restore, it is not available from there. Therefore, to perform a restore,
the server must get the information from an external device configuration file. You can copy
the device configuration information to an external IFS streamed file by using the
DEVCONFIG option in the dsmserv.opt file.
The text shown in Example 6-4 is an extract from our test IBM Tivoli Storage Manager server
options file (/usr/tsm/tivoli/server/bin/dsmserv.opt) after we updated it with the DEVCONFIG
entry.
126 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Example 6-4 Extract from our test IBM Tivoli Storage Manager server options file
* DEVCONFIG
* ********************************************************************
DEVCONFig /tsmvol/files/devconfig.out
*
* Specifies the name of a file that should contain device
* configuration information when it is changed by the server.
* Device configuration information is used by the
* server processes during server database recovery or load and
* DSMSERV DUMPDB processing.
Example 6-5 shows a copy of the /tsmvol/files/devconfig.out file from our IBM Tivoli Storage
Manager server. You can see the device class, library definition, and server name in this file.
The device information must match the devices configured on the system where the restore is
performed. You may must edit those commands in an existing file so that they match. For
example, you may have a single manual tape drive rather than a library at your recovery
location.
Example 6-5 IBM Tivoli Storage Manager device configuration file for AS27
/* Device Configuration */
DEFINE DEVCLASS ITSMLTO2 DEVTYPE=LTO FORMAT=DRIVE ESTCAPACITY=102400000K MOUNTLIMIT=2
MOUNTWAIT=60 MOUNTRETENTION=1 PREFIX=ADSM LIBR
SET SERVERNAME AS27
DEFINE LIBRARY TAPMLB05 LIBTYPE=USRDFN DRIVESELECTION=EXIT
DEFINE EXIT MOUNT TSMEXITS/MOUNTCL
DEFINE EXIT DISMOUNT TSMEXITS/DISMOUNTCL
DEFINE EXIT DELETION TSMEXITS/DELETECL
DEFINE EXIT EXPIRATION TSMEXITS/EXPIRECL
You can also enter the backup devconfig command to back up the device configuration
information at any time.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 127
after they no longer contain any files. Volumes remain in the pending state for as long as
specified with the REUSEDELAY parameter for the storage pool to which the volume belongs.
Delaying reuse of volumes can be helpful under certain conditions for disaster recovery.
When IBM Tivoli Storage Manager expires, deletes, or moves files from a volume, the files are
not actually erased from the volumes. The database references to these files are removed.
Therefore, the file data may still exist on sequential volumes if the volumes are not
immediately reused.
A disaster may force you to restore the IBM Tivoli Storage Manager database using a
database backup that is old or is not the most recent backup. In this case, some files may not
be recoverable because IBM Tivoli Storage Manager cannot find them on current volumes.
However, the files may exist on volumes that are in a pending state. You may be able to use
the volumes in pending state to recover data.
You should set the REUSEDELAY parameter on your copy storage pool to delay the reuse of
volumes for as long as you keep your oldest database backup. In our test configuration, we
keep five copies of the IBM Tivoli Storage Manager database. Therefore, we set the
REUSEDELAY parameter on our COPYLTO copy storage pool to 5 (see 6.3.7, “Creating a
copy storage pool” on page 111).
6.6.6 Mirroring IBM Tivoli Storage Manager database and recovery log
volumes
The database contains information about the client data in your storage pools. The recovery
log contains records of changes to the database. If you lose the recovery log, you lose the
changes that were made since the last database backup. If you lose the database, you lose
all your client data.
Due to the iSeries single-level storage architecture, most iSeries customers already have disk
RAID5 or mirrored protection on their systems. You can further protect the IBM Tivoli Storage
Manager database and recovery log by mirroring them to volumes in a separate user auxiliary
storage pool (ASP) on the iSeries server. However, mirroring does not protect against a
disaster or a hardware failure that affects the loss of the entire system.
We don’t mirror the IBM Tivoli Storage Manager database or recovery log in our test
configuration. You can refer to Chapter 21 “Protecting and Recovering Your Server” in the IBM
Tivoli Storage Manager for OS/400 PASE Administrator’s Guide, GC23-4694, for more details
about mirroring IBM Tivoli Storage Manager database and recovery log volumes.
128 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
daily maintenance process, so the last backup of the client data is saved to the copy storage
pool volumes.
After the BRMS control group backup finishes, you can move both sets of tapes off site as a
complete recovery package. The control group history, movement, and expiration are
managed by BRMS, and not by IBM Tivoli Storage Manager. In case of a disaster, you can
recover the complete IBM Tivoli Storage Manager environment in one simple step.
Important: You must stop the IBM Tivoli Storage Manager server to perform a complete
save of the IBM Tivoli Storage Manager server environment using a BRMS control group.
In our example configuration, we create a BRMS control group that saves the following
objects:
TSMEXITS: IBM Tivoli Storage Manager exits library
/tsmvol/: IFS directory for IBM Tivoli Storage Manager devconfig/volhist files, database, or
recovery log and disk storage pool volumes
/usr/tivoli/tsm/server: IFS directory for the IBM Tivoli Storage Manager server code and
dsmserv.opt file
Figure 6-22 show an example of a BRMS control group used to save the IBM Tivoli Storage
Manager server environment. We created commands to stop and start our IBM Tivoli Storage
Manager server which you can see as BRMS *EXIT entries. The TSMEXIT library and
BACKUPITSM *LNK list are added to save the IBM Tivoli Storage Manager data.
See 8.8.1, “IBM Tivoli Storage Manager server example” on page 187, for detailed steps to
create this BRMS control group.
Group . . . . . . . . . . : BACKUPITSM
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backup data needed for the ITSM server
Backup
Seq Items Exit command
10 *EXIT ENDTSMSRV
20 TSMEXITS
30 BACKUPITSM
40 *EXIT STRTSMSRV
Bottom
Press Enter to continue.
Important: The saving of IBM Tivoli Storage Manager via a BRMS control group should
not replace, but complement, your daily online backup of the IBM Tivoli Storage Manager
database (backup db). If your recovery log is in ROLLFORWARD mode and the IBM Tivoli
Storage Manager database is corrupted, then you can use the normal IBM Tivoli Storage
Manager database backup to recover the database back to its most current state.
Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 129
6.6.8 Disaster Recover Manager
IBM Tivoli Storage Manager Disaster Recovery Manager is an optional IBM Tivoli Storage
Manager module. It is included in the IBM Tivoli Storage Manager Extended Edition provided
with the new iSeries Enterprise Editions.
DRM can help you configure, control, and automatically generate a disaster recovery plan.
This plan contains the information, scripts, and procedures needed to automate restoration.
DRM can also help ensure quick recovery of your data after a disaster.
See Chapter 22 “Using Disaster Recovery Manager” in the IBM Tivoli Storage Manager for
OS/400 PASE Administrator’s Guide, GC23-4694, for a full description of IBM Tivoli Storage
Manager DRM.
130 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Part 3
Note: We recommend that you install MSE before you install BRMS. If you install
BRMS first and then MSE, you must run the Initialize BRMS (INZBRM) command with
OPTION(*DATA) parameter after MSE is successfully installed. MSE is a fee option of
OS/400 and requires a license key. You can learn more about the INZBRM command in
8.1.3, “lnitializing BRMS” on page 159.
134 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
1. Sign on as QSECOFR or with a user profile with this authority.
2. Enter the DSPSYSVAL command to check the following system values:
– QALWUSRDMN set to *ALL
– QSYSLIBL including library QSYS2
3. Install the BRMS licensed program product:
Note: BRMS for iSeries is a fee (additional cost) license program product (LPP). It has
a base part (option *BASE). It has two additional features (OPTION 1, BRMS - Network
Feature, and OPTION 2, BRMS - Advanced Functions Feature). Both features are
available at an additional cost and are separately orderable in addition to the base part.
Most iSeries servers with the Enterprise Edition package of software have BRMS with
the Network Feature and one server license available for installation. If you do not have
the Enterprise Edition package or need more than one server license, you must
specifically order this option.
Before your installation, verify for which parts of BRMS you have licenses and which
you intend to install now. You must install the *BASE option before you install any other
options. If you don’t have license keys for BRMS (*BASE, OPTION 1, OPTION 2), you
can use it for the 70-day trial period.
Notes:
Although running the INZBRM command is not mandatory, it is useful for an initial
setup in many customer environments. This is because, between installing the
licensed program and setting it up, there may be some time. During that time, there
can be normal system changes. BRMS needs to know the latest information before
you perform the first BRMS setup.
INZBRM has several options. Before you press Enter to run this command, use
caution and read the help text. Normally you use either the INZBRM command with
OPTION(*DATA) or OPTION(*DEVICE).
Parts of the following section are taken from the BRMS iSeries Navigator client Student Guide
- V5R2M0. You can find this guide on the Web at:
http://www-1.ibm.com/servers/eserver/iseries/service/brms/pdf/StudentGuide52.pdf
136 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
7.3.1 Installing the BRMS iSeries Navigator client
There are three ways to install the BRMS iSeries Navigator client:
Install using the iSeries Navigator Install Plug-ins icon
Install using iSeries Navigator Rescan Plug-ins function
Install using Selective Setup in iSeries Access for Windows
This section explains the third method of installing the BRMS iSeries Navigator client using
Selective Setup in iSeries Access for Windows.
1. Check the prerequisites for installation using Selective Setup in iSeries Access for
Windows. You must install the following prerequisite hardware and software on the
workstation (PC) and on the iSeries before you install the BRMS iSeries Navigator client:
– Workstation (PC)
• Processor: 450 MHz is recommended
• Memory: 128 MB minimum is recommended
• Disk space: 1 GB or more of unused direct access storage device (DASD)
• Display: Minimum resolution of 800 x 600 (1024 x 768 is recommended)
• Operating system: Windows 98, Millennium, NT, 2000, XP, or 2003
• IBM iSeries Access for Windows installed on your PC
– iSeries
• Operating System/400 (5722-SS1) installed
• Operating System/400 Option 18, Media Storage Extensions installed
• IBM iSeries Access for Windows (5722-XE1) installed
• Backup Recovery and Media Services (5722-BR1) with the latest BRMS PTFs
2. Install BRMS iSeries Navigator client.
a. Map a network drive to this iSeries server, where your PC is connected and where
BRMS is installed. On your desktop, right-click the Network Neighborhood icon or the
My Network Places icon and select Map Network Drive.
b. On the Map Network Drive window (Figure 7-2), in the Path or Folder field, type
\\system name\qibm, where system name is the name, or the IP address, of the
system on which the BRMS product (5722-BR1) is installed. Click Finish.
ix. On the Start Copying Files panel, under Add components, you should see Backup,
Recovery and Media Services listed. Click Next.
x. On the Install Completed panel, deselect the View the README file and Add
program folder check boxes. Click Next.
xi. On the Setup Complete panel, click Finish.
xii. Restart your PC.
3. The BRMS iSeries Navigator client requires a Management Central central system to
perform job scheduling functions. This requires two setup functions. They ensure that the
Management Central server is started on that system. They also assign that system as
your Management Central central system on your BRMS iSeries Navigator client PC
workstation.
a. You can start, or if necessary stop and then restart, the Management Central server on
your central system using either the 5250 workstations command interface or an
iSeries Navigator session.
138 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The Management Central server (two underlying jobs, QYPSJSVR and QYPSSRV)
runs in IBM-provided subsystem QSYSWRK. If you are unsure if these jobs are active,
you can, from a 5250 workstations command line, enter the following command:
STRTCPSVR(*MGTC)
Observe the associated messages. Normally you see a message stating the server is
started.
Depending on what other Management Central activity is already occurring, you may
need to end and then restart the Management Central server by entering:
ENDTCPSVR SERVER(*MGTC)
STRTCPSVR SERVDER(*MGTC)
To use the iSeries Navigator interface, follow these steps:
i. Expand My Connections-> system name-> Network-> Servers-> TCP/IP.
ii. On the right panel, locate Management Central and note the current status, which
should be Stopped or Started.
iii. Right-click Management Central and select Start. Or, if necessary as described
using the 5250 command interface, select Stop, and after the status changes, click
Start to start the Management Central TCP/IP server on your system.
After a few seconds, the status should indicate Started.
Note: There may be times when the Management Central server shows a status of
Started and some functions may not work as expected. You can look at the job logs
of the two Management Central server jobs, QYPSJSVR or QYPSSRV, to look for
messages that may identify the problem. Several interfaces are available to examine
these job logs, two of which are:
From a 5250 command interface, enter the following command:
WRKSBSJOB SBS(QSYSWRK)
Page down to find jobs YPSJSVR or QYPSSRV. Select the options to display the
job and its job log.
From an iSeries Navigator interface, expand My Connections-> system
name-> Network-> Servers-> TCP/IP. On the right panel, locate Management
Central. Right-click and select the Server jobs menu item. Select the option to
display the job and its job log.
b. Define your Management Central central system from your BRMS iSeries Navigator
client PC workstation session:
i. In the top of the left iSeries Navigator pane, right-click Management Central and
select the Change Central System menu item.
ii. Browse the list of systems (there may be only one). Select the system you want as
your central system and click OK.
Figure 7-4 Example for one system: AS02 is central system and managed system
140 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 7-5 shows an example where your central system (AS02) is different from the one
performing backup operations (AS27).
Figure 7-5 Example for two systems: AS02 is central system and AS27 is managed system
The setup is now complete so you can use the BRMS iSeries Navigator client. For more
information about setting up a BRMS environment using BRMS iSeries Navigator client, see
Chapter 8, “Backup Recovery and Media Services up and running” on page 155.
Tip: Using the BRMS iSeries Navigator client and Management Central defaults to using
the OS/400 job scheduler for scheduled BRMS functions. You can install the additional fee
(cost) product Advanced Job Scheduler (5722-JS1) as a plug-in, instead of using the basic
OS/400 job scheduler functions.
For more information about the 5722-JS1 product, see Job Scheduler for OS/400,
SC41-5324. For more information about iSeries Navigator plug-ins and Management
Central, see Managing OS/400 with Operations Navigator V5R1 Volume I: Overview and
More, SG24-6226, or refer to the iSeries Information Center at:
http://www.ibm.com/eserver/iseries/infocenter
You can download the free IBM Tivoli Storage Manager APIs directly to your iSeries server by
accessing the IBM FTP server from your system:
1. Create an OS/400 savefile QANSAPI to receive the IBM Tivoli Storage Manager APIs on
the iSeries server by entering the following command:
CRTSAVF FILE(QGPL/QANSAPI)
2. Use an FTP session to download the APIs:
a. On an OS/400 command line, enter the following command:
FTP RMTSYS(FTP.SOFTWARE.IBM.COM)
Note: This FTP server qualified host name may change over time. Contact IBM if
you cannot successfully use the name shown here.
b. For the login ID, enter anonymous. For the guest password, enter your e-mail address.
c. Place the FTP session in binary mode. Enter:
bin
d. Go to the relevant directory:
cd /storage/tivoli-storage-management/maintenance/client/v5r2/OS400/v520/
142 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Note: While writing this redbook, we used OS/400 V5R2 and IBM Tivoli Storage
Manager APIs V5.2.
Now you have the IBM Tivoli Storage Manager APIs as a savefile (SAVF) QANSAPI in library
QGPL on your system. You are ready to install these IBM Tivoli Storage Manager APIs on
your iSeries server.
To install these IBM Tivoli Storage Manager APIs on your iSeries server, use the Restore
Licensed Program (RSTLICPGM) OS/400 command. Because these APIs are available in
English only, you must specify LNG(2924) in the RSTLICPGM command, if your system has
another primary language installed. You install the IBM Tivoli Storage Manager APIs as IBM
License Program Product 5733-197:
RSTLICPGM LICPGM(5733197) DEV(*SAVF) LNG(2924) SAVF(QGPL/QANSAPI)
Verify that the installation is complete by either reviewing the job log (DSPJOBLOG) or
Display Install History (using GO LICPGM option 50).
To set up IBM Tivoli Storage Manager APIs in an BRMS environment, see 9.1, “Setting up the
IBM Tivoli Storage Manager server for BRMS to use IBM Tivoli Storage Manager APIs” on
page 250.
Tip: With the iSeries Announcement from 05 September 2003, there is a new installation
possibility for these IBM Tivoli Storage Manager APIs and other software, named iSeries
Enterprise Editions Installation Assistant (5733-ED1). This option is for customers with
iSeries Models 825 or higher with Enterprise Edition. Installation Assistant uses Virtual
Media Installation (VMI). You can learn more about these and other iSeries
announcements on the Web at:
http://www-1.ibm.com/servers/eserver/iseries/announce/
Figure 7-6 iSeries Fixes Web page showing PTF Ordering and Fix Central
144 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Click the Fix Central link in Figure 7-6 to see the page shown in Figure 7-7.
From the list of available options, we selected iSeries, AS/400, and OS/400 in this example.
With the larger PTFs, groups, and cumulative fixes, you must use the new FTP download
capability. You use the FTP function to also download the newer Customized Cumulative PTF
Package option.
Before you can use the Fix Central functions, you must complete a set of registration steps.
Notes:
To register, you must have a regular Support Line contract with IBM or be an IBM
employee.
While this redbook was being written, the Internet PTF (iPTF) terminology for iSeries
PTF downloads was being reformatted and new Fix Central terminology was being
introduced. Some of the page examples shows, starting out with Fix Central
terminology, still show iPTF terminology as well. Consistent updated terminology will
occur in 2004.
1. Register on the Registration Web page. To access this page, under the Key links area of
the Fixes window (Figure 7-6 on page 144), click the Register link. During this process,
Now you can order and download the PTFs using the Internet.
For this redbook, we use an example of ordering the most current BRMS PTF SI09241, which
is the newest PTF for BRMS V5R2M0 (5722-BR1), at the time this redbook was written. We
followed these steps:
1. Using the initial Fix Central page in Figure 7-7, select iSeries, AS/400, OS/400, the
individual fixes option, and release level V5R2. Click Continue (not shown).
2. A Security Information page opens. Read the text and select Yes.
3. A signon window opens. Enter your Fix Central user ID and password. Click Continue.
4. The Security Alert page opens. Click Yes.
5. The Select Fixes page (Figure 7-8) opens. Enter SI09241 and click the Add to my
download list link. You can enter multiple individual PTF numbers separated by a comma
per use of the Add to my download list link.
146 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. When you are done adding selected fixes (we use only one here), click Continue.
7. The Packaging options page (Figure 7-9) opens. Several options are already filled in.
Carefully review the options before continuing. Use the links in the left navigation bar to
find more detailed descriptions of the packaging considerations. In our example, we
selected:
– PTFS and Cover Letters
– Include all requisite PTFS
– For FTP Download or CD-ROM media...
– Reorder the PTFs even if they exist on the system
Click Continue.
Tip: You can order multiple PTFs with one order. Use care when selecting delivery
options. Consider network speed and size of the PTFs that you are ordering.
Fix Central (iPTF) allows you to download fixes via HTTP (which has a size
limitation), FTP (which has a larger size limitation), or CD-ROM. For large PTFs,
such as the BRMS PTF, group PTFs, or cumulative fixes, that you want
electronically, you must use the FTP method. The HTTP method will fail due to the
large size.
– For Where is the target system installed?, we selected Western Hemisphere: Central
America...
Click Continue.
9. An overlay page opens that discusses Internet security considerations. Click Yes to
continue.
10.After a few seconds, another page (not shown) appears. On this page, enter:
– The target iSeries fully qualified system name or its IP address
– You user ID and password on that system
148 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Optionally, select the check box indicating whether you want to view or update your
shipping information.
Click Next on this page.
11.On the next page, click YES to accept the security certificate.
12.After a few seconds, you see a verification message that the contact information and
e-mail address are correct. You may need to re-enter your e-mail address. Click Next.
13.After approximately 60 seconds, you see a summary page (not shown here). In our case,
the summary page includes text that states the FTP server will be used and you will
receive further instructions at your e-mail address.
If you select immediate download and the set of PTFs was within the immediate download
maximum size limit, you download and apply the PTFs on your target iSeries server now.
When complete, the status is shown in your browser session.
In our case, using the FTP server, we can close your browser until we receive and carry
out the complete download instructions.
14.You receive two e-mail messages in your e-mail inbox. The first one confirms your PTF
order. The second one contains detailed instructions for applying the ordered PTF to your
system. Print this second e-mail message and review the instructions carefully.
15.Follow the instructions from this second e-mail, which includes FTP instructions and tips
for using iSeries Navigator.
We recommend that you create your own IFS directory for the PTFs you download from
the Internet. In this example, we use the iSeries Navigator session to system Deber170 to
define this new directory as ptfsv5r2m0add in the root directory. On the General page of
the iSeries NetServer File Share Properties window (Figure 7-11), we define Share name
as PTFS, Description as ptfsv5r2m0add, and for Access, select Read/Write.
17.Let us assume that you successfully ordered and downloaded to your system the .bin file
for PTF SI09241, which in our example is iptf0030.bin. See Figure 7-13. The other file that
is shown is ilst0030.txt, which is a readme file for this fix.
150 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Next you must load and apply the PTF to 5722BR1 BRMS V5R2. There are several
interfaces to install (load and apply) one or more fixes on an iSeries server. They include:
– Using the 5250 GO PTF menu interface that includes several options such as Load a
program temporary fix, Apply a program temporary fix, Install a program temporary fix
from a list, and more. The best source of information is on the V5R2 Information Center
at:
http://www.ibm.com/eserver/iseries/infocenter
In the Search field, enter “fixes AND install”. One of the first search items titled
“Install fixes received electronically” provides a good overview of the steps required.
– Using the iSeries Navigator Install Fixes wizard by expanding My Connections->
system name-> Configuration and Service-> Fixes Inventory. Right-click a licensed
program and select the Install menu option. For BRMS, you can select 5722BR1.
Follow the wizard interface instructions.
In addition to Information Center documentation about this topic, consider the following
Redbooks:
• General Management Central fix inventory capabilities: Managing OS/400 with
Operations Navigator V5R1 Volume 1: Overview and More, SG24-6226
• Specific Management Central fix and fix inventory capabilities: Managing OS/400
with Operations Navigator V5R1 Volume 3: Configuration and Service, SG24-5951
The following section discusses a new method of installing fixes and PTFs, using the Virtual
Media Installation option, introduced during V5R2.
http://publib.boulder.ibm.com/html/as400/infocenter.html
This section uses this new VMI function to install downloaded PTFs, using our example PTF
SI09241. We begin by creating the needed catalog objects. If these are already created on
your system, you can use them. Otherwise continue with these steps, which you must
perform from an OS/400 command line:
1. Create a virtual device, such as VRTOPT, or any name you want to call your virtual optical
device.
CRTDEVOPT DEVD(VRTOPT) RSRCNAME(*VRT) ONLINE(*NO) TEXT('xxx')
This creates a device description VRTOPT with type 632B.
2. Vary on this newly created device description VRTOPT:
VRYCFG CFGOBJ(VRTOPT) CFGTYPE(*DEV) STATUS(*ON)
3. Create an image catalog. In this example, we create an image catalog called
PTFSV5R2M0, but you can name yours anything you want.
CRTIMGCLG IMGCLG(PTFSV5R2M0) DIR('/ptfsv5r2m0add') CRTDIR(*NO) TEXT(fixImg) AUT(*USE)
a. Set the CRTDIR parameter to *NO, because you use your IFS directory, where
iptf0030.bin file is downloaded. See Figure 7-11 on page 149 and Figure 7-13.
b. Use care when you enter the AUT parameter. We set it to *USE, but you can also set it
to *EXCLUDE or *CHANGE. It depends on your organization’s security policies.
5. In this example, we have only one PTF to install, so we load the image catalog:
LODIMGCLG IMGCLG(PTFSV5R2M0) DEV(VRTOPT) OPTION(*LOAD)
6. Use the Work with Image Catalog Entries (WRKIMGCLGE) command to verify the image
catalog status, which should be Ready. Also the iptf0030.bin file should be mounted. See
Figure 7-15.
If you press F11, you see a modified screen (Figure 7-16), which shows the volume
number.
152 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Work with Image Catalog Entries
Figure 7-16 Work with Image Catalog Entries after pressing F11
7. Install PTF SI09241 on your system. You do this by using GO PTF and selecting option 8.
The only difference now is that, for the device parameter, you type in your newly defined
virtual drive VRTOPT. This now uses the mounted volume C4835657_01, which we see
under image catalog PTFSV5R2M0. For more details, see the readme file in our example
file ilst0030.txt.
8. Verify that the PTF is temporarily applied:
DSPPTF LICPGM(5722BR1)
Figure 7-17 shows that the PTF is temporarily applied.
System:
Product ID . . . . . . . . . . . . . : 5722BR1
IPL source . . . . . . . . . . . . . : ##MACH#B
Release of base option . . . . . . . : V5R2M0
9. Perform VMI maintenance on your system by entering the following commands in the
order shown:
LODIMGCLG IMGCLG(PTFSV5R2M0) DEV(VRTOPT) OPTION(*UNLOAD)
WRKIMGCLGE
Select option 9 to unload the image catalog entry.
RMVIMGCLGE IMGCLG(PTFSV5R2M0)IMGCLGIDX(1)
Note: This command only removes the entry in your image catalog. File iptf0030.bin
itself is still available.
Note: Future PTF installations using VMI will have fewer steps, because all catalog objects
are now created. However, you can create numerous catalog objects but can only have
one virtual optical. It can only be allocated to one image catalog at a time.
154 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
8
To assist in your backup and recovery processes, BRMS keeps track of which objects you
have not included in your backup strategy. Those left out are found in the BRMS log. In
addition, there is a separate exception report.
8.1.1 Policies
BRMS uses policies that define a set of standards. In many levels of definition within BRMS,
you find the same parameter. If specified, BRMS selects the parameter value specified at the
lowest level. If nothing is specified at a lower level, BRMS tries to find a value for that
parameter at the next level until it reaches the top level for that parameter. A parameter’s top
level can be in any of the policies that are defined. An example is the weekly activity. Its
ending point is the backup policy. Nothing is found about weekly activities in the highest level,
which is the system policy.
Figure 8-2 shows how this works. It also shows a run-time priority order that is embedded.
The selection order is:
1. Item overrides
2. Control groups
3. Backup, Archive, Recovery, Retrieve, Migration policies
4. System policy
156 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
System Policy (one per operating system)
Recommended media class
Recommended media policy and device(s)
User notification and sign-off controls
IPL controls, presentation controls
Systems that share the media inventory
Start of day time
Media Monitor on/off
License information
Control Groups
(as many as needed, override policies)
User sign-off controls
Media policy and device(s)
Weekly activity
Operation specific controls
Note: As for all the other policies, some specifications are only found here. Others are
defaults if not specified elsewhere.
System policy
– Should we sign off interactive users
– Who is allowed to stay active
– Ending subsystems
– Presentation controls such as which is the first day of the week, etc.
– During what time of day an IPL is allowed
– When a backup day logically starts
– Default media class
– Default media policy
– Default backup device
– Network definitions
Backup policy
– Media policy
– Backup devices
– Default activity
• Full backup
• Incremental backup
• No activity at all
158 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
• Creation date
• Last used
• Last changed
However, since we use the BRMS iSeries Navigator client interface for most of the examples
in this redbook, it is important to note that this graphical interface to BRMS functions often
performs additional functions than what is apparent using the graphical interfaces. For
example, creating a BRMS location is one of the functions that is not explicitly selected
through the BRMS iSeries Navigator client.
Whether you choose the OS/400 command interface or iSeries Navigator interface, your
setup is the same when it is completed.
Note: From a full function BRMS viewpoint, the OS/400 command interface provides
interfaces to the full range of functions. The BRMS iSeries Navigator client interface
provides an interface to almost all of the BRMS functions. We discuss some of these
differences, depending on the topic being covered, throughout this redbook. However, for
the most complete description, review Backup Recovery and Media Services for iSeries,
SC41-5345.
The INZBRM command can also add a system to a BRMS network group, using the Network
feature.
INZBRM has an OPTION parameter with several option values and associated functions. For
full details of its capabilities, enter the INZBRM command on a 5250 workstation. Press F4 to
prompt and then, with the cursor positioned on the OPTION parameter, press F1 for help.
8.1.4 Media
Writing to, and reading from, tape media and managing that process has many
considerations. This section addresses most of them when running under BRMS.
Important:
Always initialize a tape volume using the same name as its outside label specifies. If
you don’t, you will experience some trouble. When using a tape library device with a
barcode or any other kind of automatic reader, this is important. BRMS can read, but
never write to, such a volume.
Under normal operating conditions, BRMS protects a tape volume that contains active
saved data from being overwritten. BRMS cannot provide this protection if an active
tape volume is used in conjunction with the Save Storage (SAVSTG) command. This is
due to the Media and Storage Extension (MSE) interfaces to BRMS not being active
when you run the SAVSTG command. Never use active BRMS volumes if you use the
SAVSTG command.
To prevent calling for a volume that is not in an accessible tape location, do not allow
that volume to expire.
Only IBM Tivoli Storage Manager can restore a volume written by IBM Tivoli Storage
Manager. After OS/400 data is saved to IBM Tivoli Storage Manager, IBM Tivoli Storage
Manager must be up and running and BRMS must request IBM Tivoli Storage Manager to
bring back the data.
Tape locations
When integrating BRMS and IBM Tivoli Storage Manager, you must consider carefully the
subject of tape location. Tapes are physical media and must exist somewhere. The first
logical step in BRMS is to define where you store your tape volumes, a tape location. What
you setup depends how you need to move your tapes between these locations. You may be
able to operate without this process and setup, but things will work more smoothly if you set
up a location.
When you create locations, carefully consider when the location setup allows a volume to
expire. When a volume’s retention period is over, the volume is considered expired. It
becomes a scratch tape and is then available for writing to. When a volume with expired
retention is moved to a location that allows tapes to expire, BRMS does not automatically
expire the tape.
160 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
There is one exception. If you use a tape library device with a barcode reader, BRMS
automatically detects the volume and does the operation for you.
You expire tape volumes by using the Start Expiration for BRM (STREXPBRM) command, the
Work with Media using BRM (WRKMEDBRM) option 7 on the volume number of the tape, or
the Start Maintenance for BRMS (STRMNTBRM) command with the EXPMED parameter set
to *YES.
Model location
Consider creating locations similar to this example. You can create locations with
10-character names that are meaningful to you. You can create as many locations as you
need using Option 1 (Add) from the Work with Storage Locations display. To do this, you use
the Work with Locations using BRMS (WRKLOCBRM) command. Here is an example set of
locations:
COMPROOM: Use this location for storage of active volumes being managed by a
third-party courier or off-site vault.
FREE_TAPES: Use this location for scratch tape volumes. Its name is intended to make it
easier for the operators to find expired volumes. Such a location depends on your tape
move setup. This can be in a specific place inside the ordinary tape library. Ideally, free
volumes are returned to the tape library device if it can hold the volumes.
NOT_MOVED: Use this location for volumes that do not move. Volumes can end up here
in case the system policy Home location for media parameter points to NOT_MOVED. If
you leave the default setup unchanged, they are placed in the *HOME/ location.
ARCHIVE: Use this location for volumes with data that must be saved over an extended
time period.
DO_NOT_USE: Use this location for volumes indicating read/write problems but still
holding active data. After a volume becomes inactive, destroy it and do not re-use its
volume name.
LOST: Use this location in case you lose track of what a tape volume was used for. In this
case, you have provide a place for it so someone can decide what to do with it. This name
can serve as a reminder to check any tapes in this location.
You can have a location for tapes sent to other companies. However, we recommend that you
handle such volumes outside BRMS. In case of restore, BRMS calls the latest version of
every object. It is not good if it points to a volume outside your control.
Home location
When tape volumes rotate between locations, the move policy specifies where they should
return after the expiration time has passed by looking at the Home location prompt of the
move policy assigned to the volume.
The home location of a move policy can have a value of *SYSPCY. This value indicates that
the Home location for media prompt on the System Policy is used for the move policy home
location. It can be convenient to specify a location named NOT_MOVED in the System Policy
Home location for media prompt.
Important: When there are tape device changes, run the INZBRM command with the
*DEVICE option.
Important: A tape volume cannot expire until all of its retention days are passed and noted
for a location that allows expiration.
162 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
A specific media class can also be defined to always target a set of volumes. Assume that
you have log files that, for legal reasons, need to be stored over a long period of time and you
want them to go to the same volume. After you create your media class, you add two tape
volumes to the class. You may also need a media policy that points to this media class and
need a control group that references the media policy. When it is time to go live, you initialize
both volumes if necessary. Then you place one of them in your tape library device and the
other one easily reachable outside. You may also find it practical to have a specific media
location named for such volumes. When you back up files like this, BRMS only finds one
available volume and places it at the end, one after the other. Sooner or later, the volume is
full. When you reach the end of reel, you see a message stating that you have to mount next
volume. You mount your prepared tape and continue. Of course, you then need to replace
your spare with a new tape volume.
In cases similar to this one, it is important to remember that there is no need to keep track of
any detailed information about what is on those volumes. Only those BRMS log files can be
on the volumes. Also, there is no need to store the BRMS inventory files in such a backup job.
In case of a restore, it is relatively easy to display the volume and determine in which
sequence the number corresponds to a certain save date. Log files are normally not vital to
running your business. Therefore, do not consume valuable disk space only for referencing
them. You may never use this.
Separating media when BRMS, IBM Tivoli Storage Manager share the
same tape library
When an IBM Tivoli Storage Manager server is sharing a device that is also attached to an
iSeries running BRMS, you must follow some considerations in regard to media:
If IBM Tivoli Storage Manager is not going to use BRMS as its tape management program,
you need to ensure that the tapes that IBM Tivoli Storage Manager uses are not enrolled
within BRMS.
If IBM Tivoli Storage Manager is going to use BRMS as its tape management program,
you need to create a media class just for IBM Tivoli Storage Manager within BRMS. To
create a media class within BRMS, you need to:
a. On an OS/400 command line, enter the Work with Media Classes (WRKCLSBRM)
command.
b. Select option 1 to add a new media class as shown in Figure 8-3.
Figure 8-3 Creating a new media class for IBM Tivoli Storage Manager
c. Specify the tape density that you want to use with this media class and whether you
want to share the media that is associated with this media class. Figure 8-4 shows the
two parameters with which you should be concerned. You use the Shared media
parameter only if your iSeries is in a BRMS network (using the Networking feature of
BRMS). If you specify *YES for shared media and you are in a network, it allows other
systems to use the media that are associated with that media class.
More...
F3=Exit F4=Prompt F12=Cancel
Creating this media class allows IBM Tivoli Storage Manager to use BRMS-enrolled volumes.
164 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Recommendations on hardware configuration sharing the same tape library
The ideal situation is to have BRMS and IBM Tivoli Storage Manager share the same tape
library. To do this, we recommend that you use a minimum of three tape drives inside of the
tape library. Because of this, you are limited to device type 3494, 3584, or 3583. The real
minimum number of drives in a tape library is two for efficient implementation of IBM Tivoli
Storage Manager's copy function.
However, you need to consider that, when IBM Tivoli Storage Manager is using the drives,
BRMS cannot allocate them. For example, if you are using IBM Tivoli Storage Manager to
migrate the data from disk to tape, it needs two drives to accomplish this. If at the same time
you need to restore an object using BRMS, you need to wait until IBM Tivoli Storage Manager
is done before restoring the object.
Note: You certainly can share a single tape drive (for example, a 3581) between BRMS
and IBM Tivoli Storage Manager when IBM Tivoli Storage Manager is using BRMS as its
tape manager. Of course, both products cannot use the same tape device at the same
time. The product that starts performing its function first allocates the device until the
function is finished.
We recommend that you use multiple drives to help with the IBM Tivoli Storage Manager
reclamation function in IBM Tivoli Storage Manager. Otherwise, you must copy data from
tape back to disk and then back to tape again (rather than tape to tape with multiple
drives).
Although possible to set up, BRMS and IBM Tivoli Storage Manager should never share the
same physical volumes. Even though you are pointing to the same media type, both need
their own media class (or media pool as named in the iSeries Navigator).
The command to add tape volumes is the Add Media to BRM (ADDMEDBRM) command.
Then you point at a media class and location. You also specify whether you want the volume
physically initialized.
When mounting new (or unknown) volumes in a tape library, take advantage of the tape
library commands such as Work with Media Libraries (WRKMLBBRM), which makes adding
easier.
Copying media
If there is a need to always have the latest copy of an object immediately accessible for
restore, then you must keep the current save in the tape drive. This is not good from a safety
aspect. A better alternative is to copy the volume. You can do this at any time of the day,
assuming you have enough tape drives available.
Moving media
To have BRMS move media, you need to specify if and how long a tape volume should reside
in a location. Assume you have a location that is ten minutes away called SUBOFFICE, and
you want to store your hot tapes there for a week. Then return them to the computer room
safe for the rest of the period. Your move policy can look like this:
SUBOFFICE 7
COMPSAFE *EXP
In this example, every volume with this move policy stays in SUBOFFICE seven days, but the
time they spend in COMPSAFE varies depending on what was written to them. When the last
expiration date is passed, nothing actually happens until BRMS runs a move task. In this
case, you perform the following tasks:
1. Check whether the location allows the expiration flag to set.
– Yes, the expiration flag is set.
– No, the expiration flag will not go on even though the volume is essentially free.
2. Check whether the information over what is on the volume should be retained or deleted.
3. Print a report showing which volumes need to be moved.
4. Check whether a move verification is needed.
– If not, BRMS inventory logically moves volumes to their new location.
– If yes, an extra verification step is needed using the Verify Media Moves
(VFYMOVBRM) command.
After a tape is expired, the next (last) location is determined by the move policy Home location
parameter.
Moving volumes
To move tapes logically in BRMS, use the STRMNTBRM command and set the move media
parameter to *YES. If you want to run the move manually, you use the MOVMEDBRM
command or open the WRKMEDBRM display and use option 8 to move a volume.
When a move is performed and you want to run it for all locations, the move process validates
that every volume is where it should be. For those that it can move automatically, it does by
issuing a library device command. If you have a tape library, it ejects all tapes that should not
be there. It does not matter if they are in the library because nothing is done after the last
backup, or if you reinserted a volume for some reason. If it should not be there, it is forced
out. Volumes that need a physical action are listed on the Volume Movement Report. It shows
where the tapes should go.
Note: With a tape library, if you want some action to take place and you set VFYMOVBRM,
refer to Informational Authorized Program Analysis Records (APAR) II09882, which you
can search for on the Web at:
http://www-912.ibm.com/n_dir/nas4apar.nsf/$$Search?openform
166 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Move verification
Tape volumes that require move verification do not appear in their new location until the
VFYMOVBRM command has completed. This is an interactive command and you have to
respond to each volume.
The example in Figure 8-5 shows that these volumes should be moved to location
SUBOFFICE.
If you do not have the Move Media Report on hand and want to know their previous location
(current logical location), you type:
WRKMEDBRM VOL(17AAC1 17AA20 2C5536)
Sometimes you are denied because other settings prohibit that. For example, you cannot
expire a volume in a location that is specified as Allow Volumes to Expire = *NO. You must
first move them to the correct place.
You may run an extra STREXPBRM command just before you launch your backups in case
someone forgot to actually expire the volumes that were moved or changed.
Assume the working days calendar holds Monday to Friday, and you have a pickup service
Tuesday and Thursday. Then the move operation considers which moves actually can take
place on a given day. In addition, you may have a Holidays calendar that tells on which dates
not to perform a move even if it matches the other calendars.
Volume retention
BRMS always physically writes all tape labels as permanent. You cannot see the expiration
date when you display a tape volume written by BRMS. Which volume and when a tape is
considered expired is controlled strictly by the BRMS database. The purpose is to protect
volumes from accidentally being overwritten if mounted outside of BRMS control.
Volume protection
When BRMS is in control, you may natively add to a volume owned by BRMS. However, you
cannot overwrite or initialize it. Your attempt is cancelled with an error message.
Attention: BRMS cannot prohibit its volumes from being destroyed by the SAVSTG
command.
Remember that the main purpose of backing up your data is the possibility to get it back if
needed. BRMS always tries to show you the most recent copy of your system and its data as
possible, regardless of how a backup was taken.
You have the ability to select on which drives you want this function active. In the BRMS
device description is the Auto enroll media field, which normally points to the System Policy. It
can also be *YES or *NO.
168 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Saving by generations (versions) instead of days
BRMS has the ability to store volumes by generations (versions) instead of days. We do not
recommend this because of the way it works. LIBA, LIBC, and LIBC are saved in a control
group. The first save is version 1, the next is version 2, and so on.
If LIBD is added to the control group, the next save is version 1 again. If the media policy says
to retain five versions and only four versions were saved before library D was added, you
never get the fifth version of libraries LIBA, LIBB, and LIBC unless LIB D is removed from the
control group. This works the same way for removing a library or using generics and
*ALLUSR etc. You may end up with tape volumes that never expire.
Attention: We do not recommend versioning unless you have a static group of libraries
that you are saving. Saving by levels is excluded from the BRMS iSeries Navigator client.
Depending on which servers install, specific control groups are created for some of those
servers. Some automatically created control groups cannot be altered, but they can be
copied. For a complete copy of your system, they ignore any system-wide excludes that you
set up.
Restriction: You cannot save anything from an independent auxiliary storage pool (IASP)
unless you vary it on.
Creating control groups is a huge concept, but it depends on what your backup and recovery
looks like. In essence, you create a list of things you may want to back up, either by specific
names, generic names, by a list, by type, or in the manner you find practical.
To help you design your backup control group, see “Consideration before you begin” on
page 370.
170 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Deleting a backup policy (control group) through the wizard
From the iSeries Navigator client, you do not find a control group. You work with Backup
policies, so the wizard asks if it should also delete objects related to your backup policy.
Since a backup policy may use objects common to other Backup policies, use care before
you respond to the following question. Although the item referred may not be in use right now,
you may want to take advantage of it in the future.
In the example shown in Figure 8-7, you cannot select the Delete check box because the list
it is referring to is in use by another backup policy.
General excludes
If you want to take advantage of the IBM-delivered control groups, but need to always
exclude specific items, you may do so using the 5250 Backup policy menu interface. On a
5250 session, complete these steps:
1. Go to the Backup Planning menu by entering the following command:
GO BRMBKUPLN
2. Enter option 1 (Backup planning).
3. Enter option 1 (Work with backup policy).
4. Enter option 2 (Work with items to omit from backup).
5. Before you take any further action, press F1 (Help) and F2 (Extended Help). Carefully
review the help text.
Important: Work with help text for the items to omit from backup. As stated, carefully
review the entire extended help text to understand the need to be careful when omitting
(excluding) items. The following excerpt is the first part of this important help text:
“This display is used to add or remove backup items when processing the *ASPnn,
*ALLUSR, and *IBM special values in a backup operation. For example, an entry for
*ALLUSR excludes an item from being backed up when the *ALLUSR special value is
specified in any control group.”
Full backups
The advantages of performing a full backup are:
It’s easy to restore since all objects are there.
You only need one or a linked set of tape volumes.
Restore time is quicker.
It’s the best choice if you do not have a tape library or must perform a manual restore.
Incremental backups
Incremental backups are divided into:
All changes since last full backup (cumulative incremental)
All new changes (incremental)
New volume
The advantages of a new volume are:
With one retention period only, the volume is not locked up by other backups.
With data on different volumes, you can do concurrent restores.
Cartridge damage only affects one save.
172 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The disadvantages of a new volume are:
Low volume saves can be an issue with tape cartridges that can store much data.
You may need a tape library device that can hold many cartridges.
Tape volume utilization is low (volumes only partially filled up).
You need more tape volumes.
You may find your backup jobs cancelled if scratches are not available.
The disadvantages of appending to a volume that already holds active data are:
For certain tape devices, save and recovery time is longer, and sometimes much longer.
Tapes may be locked if saves with different retention periods exist on the same volume.
Restore needs to handle more volumes.
Restore time is longer.
You may need a tape library device to use this function.
There is a sequence limit for tape labels.
You can also override that text field when you submit the job. Text is one of the fields in the
Add Job Scheduler Entries (ADDJOBSCDE) command that plugs directly into the BRMS
information database. This comes in handy when you use the same control group for different
purposes.
Recovery contacts
You should create a list of which people to contact in case of recovery. You need to know who
they are and how you reach them outside office hours.
You can find this information by using the GO BRMS command. On the window that opens,
select Recovery. On the next window, select Work with Recovery Contacts.
Recovery list
When you are done setting up the people to contact, create the activity to be carried out to
prepare for actually restoring your data. For each activity, you can point to the contact
persons that you previously created.
You can find this information by using the GO BRMS command. On the window that opens,
select Recovery. On the next window, select Work with Recovery Activities.
The list shows the order of activities that are needed to produce the shortest recovery time
possible. Many of the activities can and should be carried out in parallel.
However keep in mind that the journaled files used in your applications are not always backed
up. When doing a full save, journaled files are always saved. When saving changed objects
(an incremental save in BRMS), journaled files, by default, are not saved. If you want
journaled files to be saved during incremental saves, you need to change the Journaled
objects parameter in the control group attributes, or the backup policy, to *YES.
Start of day
Start of day is a parameter in the system policy. It is primarily used to define a “working day”
rather than follow the ordinary clock, changing the day at midnight. Before you start using this
parameter, you must clearly identify what you mean by referencing. For example, for a
“Wednesday backup”, do you mean a backup taken early Wednesday morning, which in fact
is the data from Tuesday? Or is it really Wednesday’s data you want?
Keep in mind that you will find different information depending on where you look. In most
places in BRMS, but unfortunately not everywhere, you see the working day date. In the
operating system-related information, such as job logs, tape volume labels, etc., you find the
actual time and day the data was written.
Note that the job schedulers also follow the system clock and are not related to any BRMS
start-of-day clock.
Allowing IPL
You may set up your control groups to automatically launch an IPL when completed. To
protect accidental IPLs, parameters in the System control group allow you to specify between
which hours an IPL is allowed.
174 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
This is convenient when backups are run outside of their normal running scheme. A
BRM1100 message is posted stating “Current time xx.yy is not within the limit of
xx.yy to xx.yy” and then this step is skipped.
With the 5250 interface, you set this from the Work with System Policy (WRKPCYBRM *SYS)
panel. In the iSeries Navigator client, to change it, right-click the Backup Recovery Media
Services folder and select Global Policy Properties. Then select the Global Policy
Properties Power Down tab.
Message notification
Another function is to specify which message queue BRMS targets for its messages. The
default is QSYSOPR. To change this, right-click the Backup Recovery Media Services
folder and select Global Policy Properties. Then select the Global Policy Properties
Notification tab.
The Set User Usage for BRM (SETUSRBRM) command via the 5250 interface has more of
an overall functionality. To set up a tailored environment, you use the BRMS iSeries Navigator
client.
The outcome is not the same in every part of BRMS. Users that are excluded may find certain
functions removed from the BRMS panels. If they try to use the underlying command directly,
they receive an error message.
For more information, see Chapter 11 in Backup Recovery and Media Services for iSeries,
SC41-5345.
Attention: The iSeries operating system is divided in two parts: the OS/400 and its
microcode. The two parts interact closely so there is great risk in taking them from different
backups. You cannot predictable what such a system may run into when production starts.
The simple way is to use a BRMS control group that is already included in the product. This
assumes you have no special routines to take down your applications. If you have, make a
copy of the control group, name it something meaningful, and edit it using the steps needed to
bring down your applications in a proper manner.
In attended mode
In attended mode, you follow these steps:
1. Sign on the system console with a user profile with *SAVSYS and *IOCFG authority.
2. Enter the GO BRMS command.
3. On the displays that follow, select the following options in the order shown:
a. Select option 2 (Backup).
b. Select option 2 (Perform backup)
c. Select *SYSGRP.
4. Enter the following command:
STRBKUBRM CTLGRP(*SYSGRP)
Running unattended
To run BRMS in unattended mode, follow these steps:
1. Submit a job to a console for monitoring:
SBMJOB CMD(STRBKUBRM CTLGRP(*SYSGRP) SBMJOB(*CONSOLE)) JOB(SYSBACKUP) JOBQ)(QCTL)
SCDDATE(XXXXXX) SCDTIME(YYYYYY)
2. From the system console, sign on with a profile that has *SAVSYS and *IOCFG authority.
Make sure the device does not sign you off automatically (QINACTITV timer) and that it
does not have the QSYSOPR message queue in break mode.
3. Enter the GO BRMS command.
176 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
4. On the displays that follow, select the following options in the order shown:
a. Select option 2 (Backup).
b. Select option 4 (Start console monitor).
5. Leave the console in that state until the backup operation is complete.
6. To return the console to normal operation, you need to know the password for the user
profile with which you signed on.
You can back up the system outside BRMS by following these steps:
1. Shut down your applications properly.
2. Shut down your communications if needed by using the Vary Configuration (VRYCFG)
command ... STATUS(*OFF) or perform the vary off as an option from the Work with
Configuration Status (WRKCFGSTS) command interface for your communication objects
that are in varied on or active status.
3. Shut down your system to a restricted state by entering the following command:
ENDSBS *ALL OPTION(*IMMED or *CNTRLD)
4. Make a tape drive ready and enter the Save System (SAVSYS) command. As an
alternative, you can use a menu by entering:
GO CMDSAV
Then select option 19 (Save system).
5. Start up everything again.
SAVSTG copies everything bit-by-bit to tape in big blocks. The advantage is that it is fast and
easy. The disadvantage is that it can only come back “as is”. Single object restore is not
possible. The system must be exactly as it was when you made the save. No changes to the
configuration are allowed.
Attention: Under normal operating conditions BRMS protects a tape volume containing
active saved data from being overwritten. BRMS cannot provide this protection if an active
tape volume is used in conjunction with the SAVSTG command. This is due to the MSE
interfaces to BRMS not being active when the SAVSTG command is run. Never use active
BRMS volumes if you use the SAVSTG command.
On daily basis, you must manage the volumes that are holding information about all your
saves. This information is automatically placed on tape after each backup job unless you
deliberately prohibit it from doing so.
With Version 5 Release 2, the BRMS STRMNTBRM maintenance command performs this
cleanup.
178 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
8.4 Disaster recovery
What must be done in case of a disaster recovery depends on what happened, the time it
happened, and the time and resources you have available. Basically you follow the recovery
list, which identifies the preparation steps and who to contact. For the actual recovery, follow
the Recovering Your Complete System and Recovery Volume Summary Report. Their print
file names are QP1ARCY and QP1ARCY2 respectively. You can find examples in
Appendix B, “Backup Recovery and Media Services reports” on page 375. Make sure you
have access to the latest recovery reports.
You may run into a situation where you have no application to help you restore your system.
Make sure that you always have access to the latest recovery reports. They contain every
step in sequence to bring back your system in operation.
Restoring your data is also done in alphabetical order. A file that references a file that is not
yet restored, does not restore since its pointers cannot be resolved. In this case, you receive
a CPF3756 or a CPF3773 message.
In a disaster recovery situation, you do not want to run into such a situation. Therefore, plan
for it in advance. The easiest way to know is to run a query over the file QADBFDEP in QSYS.
Then check if the field BDFLIB is less than DBFLDP. If you find such relations, you must take
precautions. To enhance the query, you can exclude system libraries in your selection. Cross
referencing problems in those parts of the system is sorted out by the operating system.
To get around the files being in the wrong order, you can:
Restore the affected files once more.
Change the order for how you back up your libraries. That is you have a strict one-to-one
relation and you do not have a cross-reference situation.
Save the affected files one more time, and then BRMS makes sure they are restored last.
If they are big, exclude and place them last in your backup or in a separate job.
Tape volumes must still be defined in BRMS for the data that cannot be placed on the IBM
Tivoli Storage Manager server. For ease of operation, you should have a separate media
class for managing the IBM Tivoli Storage Manager volumes. In case of disaster recovery, it is
practical to have a media class to save the actual IBM Tivoli Storage Manager server
environment.
Note: When BRMS is initialized, it automatically creates media classes related to the
hardware that is installed.
Note: Using the BRMS 5250 interface mode, creating a media class is an option from the
Work with Classes menu. It is not a command. You will not find an Add option under the
iSeries Navigator client Media pools icon.
1. Launch the BRMS iSeries Navigator client and log on to the iSeries server.
2. Expand Backup, Recovery and Media Services-> Media. Select Media Pools.
3. In the right panel, right-click the media pool icon that matches your media type and select
New Based on (see Figure 8-8).
Figure 8-8 Selecting New Media Class based on for the media pool
180 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
4. In the New Media Pool Based on window (Figure 8-9), enter a name and description for
the media pool.
Note that you only select the Share media across systems option if you are in a BRMS
network. When complete, click OK.
5. You return to the Media Pools window shown in Figure 8-8. Press F5 to refresh the
window.
6. Repeat this procedure until you create all your media pools.
Note: If you select a pool that does not have a library device, the next window does not
appear. Then you must manually add tape volumes.
4. In this example, there is a tape library device. On the Add Media - Display Media Library
Volumes window (Figure 8-12), select Yes and choose a library device if you have more
than one. Click Next.
182 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 8-12 Add Media - Display Media Library Volumes window
5. After you physically insert your volumes, you can take advantage of the library. On the Add
Media - Specify Media Library Category window (Figure 8-13), select All inserted
volumes, which is the default (for example, those with the Category INSERTED). Click
Next.
6. On the Add Media - Select Media Library volumes window (Figure 8-14), select each
volume to add and click Add.
8. On the Add Media - Summary window (Figure 8-16), review the summary details. If you
change your mind about some of the details, you may click Back to change them. Since
you are done adding media, click Finish.
184 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
8.7.2 Removing media
To remove volumes from BRMS, follow these steps as shown in Figure 8-17:
1. Select Backup, Recovery and Media Services-> Media-> Tape Volumes.
2. Right-click Tape volumes and select Remove Backup, Recovery and Media Services->
Media-> Tape Volumes. Right-click Tape Volumes and select Remove.
3. Confirm the removal.
Note: Volumes do not have to exist when you add them. However, BRMS assumes that
they exist in the location specified.
2. On the Add Media - Select the Media Pool window (Figure 8-19), select your media pool.
Click Next.
186 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. On the Add Media - Add Volumes window (Figure 8-20), in the Volume name or prefix
field, type the volume name or volume prefix characters. Click Next.
4. After you add the volumes, you see a window that provides the option for you to initialize.
5. Follow and complete the steps for the remaining windows until you finish manually adding
the media volumes.
Backup control group versus backup policy: The BRMS iSeries 5250 interface
uses the term backup control group. The BRMS iSeries Navigator client uses the term
backup policy.
2. On the New Backup Policy - Backup Policy Name window (Figure 8-22), enter a name and
description. Click Next.
3. On the New Media Pool Based on window (Figure 8-23), enter a media pool name and
description. Select the density. For Media capacity, select Use media format. Click Next.
188 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
4. On the New Backup Policy - Select Items for Backup window (Figure 8-24), from the IFS
tree, select the directories /tsmvol and /usr/tivoli/tsm/server as shown. Click Next.
Figure 8-24 New Backup Policy - Select Items for Backup window
6. On the New Backup Policy - Backup Order window (Figure 8-26), confirm the items that
you want to back up. Click Next.
190 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
7. On the New Backup Policy - Backup Activity window (Figure 8-27), select whether you
want a full backup, incremental backup, or both. In this example, we select Full backup
and Changes since last full backup (cumulative). Click Next.
8. On the New Backup Policy - Media Retention window (Figure 8-28), specify the retention
period. Click Next.
Note: Remember that we are not saving any data to be sent to the IBM Tivoli
Storage Manager server, but the IBM Tivoli Storage Manager server itself.
Therefore, we choose a suitable media pool for tape.
Figure 8-29 New Backup Policy - Select Backup Devices window (Part 1 of 2)
b. Under Available devices, select a tape drive for this media pool and click Add. In this
example, we selected TAPMLB05 (our tape library device). See Figure 8-30.
c. Click Next.
Figure 8-30 New Backup Policy - Select Backup Devices window (Part 2 of 2)
192 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
10.On the New Backup Policy - Add Media window (Figure 8-31), specify whether you want to
add media. Click Next.
11.On the New Backup Policy - Summary window (Figure 8-32), review the summary details.
Click Back if you need to make any changes, or click Finish.
194 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
4. On the Properties - During Backup window (Figure 8-35), click Add to add a new entry. In
this example, the line that contains Backupitsm is highlighted. You also have the option to
remove this entry.
5. The Add button opens the Add Backup Items wizard. On the wizard window (not shown),
we chose Select specific items for backup. Click Next to see the iSeries IFS folders.
6. On the Select Items for Backup window (Figure 8-36), scroll down and expand QSYS.LIB.
Figure 8-36 Add Backup Items - Select Items for Backup window (Part 1 of 2)
Figure 8-37 Add Backup Items - Select Items for Backup window (Part 2 of 2)
8. Review the Summary window (Figure 8-38). Click Back to modify your settings or click
Finish.
9. On the Properties - During Backup window (Figure 8-39), you can see the Backupitsm
item that we added. Click OK and you return to the Backupitsm Properties window
(Figure 8-34 on page 194).
Figure 8-39 Backupitsm example: Properties - During Backup with the new item added
You are done with the During Backup activities. You may want to check the options on the
other tabbed pages in case you want to change anything at this point.
196 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
The properties on the TSM Server Retention tab do not really apply, considering the following
points:
In this control group, we do not save data to the IBM Tivoli Storage Manager server to
store it for us.
The IBM Tivoli Storage Manager server is actually running on the iSeries server.
We intend to save the IBM Tivoli Storage Manager server configuration.
Note: In our example, our command has no parameters. ENDTSMSRV is user created.
If the command is outside your library list, you also have to specify where it is to be
found. In our example, this is TSMEXITS/ENDTSMSRV.
3. On the Backupitsm Properties window (Figure 8-34 on page 194), click the After button.
4. You may only need to specify to start the IBM Tivoli Storage Manager server after the
backup is finished. In the Backupitsm Properties - After Backup window (Figure 8-41), in
The control group is complete and ready to run. However, there is no move policy attached to
it yet. If this setup is going to run regularly, attach a move policy. Since no locations are
specified yet, it is too early to attach a move policy.
8.8.2 Saving native OS/400 data to an IBM Tivoli Storage Manager server
In this example, you create a control group that saves all AS03 libraries. You can do this either
to tape or to an IBM Tivoli Storage Manager server.
Due to the BRMS iSeries Navigator client logic, it always starts creating an environment for
tape. If at this point you do not have an IBM Tivoli Storage Manager server running, you must
keep the setup for tape and skip steps 14 on page 206 through 17 on page 207. Later you
can change the group from tape to IBM Tivoli Storage Manager.
Note: The BRMS iSeries Navigator client is not restricted to selecting one item at a time.
You can do it all in one flow. This example only shows how to save a group of iSeries
libraries.
1. As shown in Figure 8-42, select Backup, Recovery and Media Services-> Backup
Policies.
2. Right-click Backup Policies and select New Policy.
198 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 8-42 Selecting Backup Policies-> New Policy
3. On the New Backup Policy - Backup Policy Name window (Figure 8-43), enter a name and
description. Click Next.
5. On the New Backup Policy - Customize IBM Data or User Data window (Figure 8-45),
specify the type of information you want to back up. In this example, the AS03 libraries are
user data so we selected User data. Click Next.
Figure 8-45 New Backup Policy - Customize IBM Data or User Data window
200 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. On the New Backup Policy - Customize User Data window (Figure 8-46), you can select
the user data to back up or you can select specific items to backup up. Since we are
saving a range of ordinary iSeries libraries, we selected the Select specific items for
backup option. Click Next.
Figure 8-47 New Backup Policy - Select Items for Backup window
8. On the New Backup Policy - Specify Generics window (Figure 8-48), you select the
generic name of the objects to back up or omit from the backup. In this example, we select
Libraries. Click OK.
202 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
9. On the New Backup Policy - Specify Generics for Libraries window (Figure 8-49), enter the
library prefix AS03. Click Add. AS03* is now placed in the generic library list area.
You can enter other library prefixes and click Add each time. When you are finished
adding the library entries, click OK and then click Next.
Figure 8-49 New Backup Policy - Specify Generics for Libraries window
10.On the New Backup Policy - Backup Order window (Figure 8-50), verify what you selected
to back up. Click Next.
12.On the New Backup Policy - Media Retention window (Figure 8-52), specify the retention
days. Again, select Allow overrides to retention when policy is run or scheduled.
Click Next.
Up to this point, creating a backup policy is the same for defining a backup policy for
saving to OS/400 media and saving OS/400 data to an IBM Tivoli Storage Manager
server. However, by selecting a media pool, BRMS chooses a different path before it
returns to the main flow. You can select to:
– Store data on the IBM Tivoli Storage Manager server
– Store data directly to tape
– Store data in a save file
204 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Note: More options are available. Depending on what is installed, you can find such
options as archiving. Since this is a quick start guide, we do not explain this further.
Here, we create a backup to be sent to the IBM Tivoli Storage Manager server. Since we
use the iSeries Navigator client, it bundles actions that we do not see. For that reason, we
cannot select the IBM Tivoli Storage Manager server at this point. We must first use an
existing media pool for tape. When the backup policy is created with all the linking needed,
we have to change it to point at the IBM Tivoli Storage Manager server.
13.On the New Backup Policy - Select Backup Devices window (Figure 8-53), select the
media pool.
Figure 8-53 New Backup Policy - Select Backup Devices window (Part 1 of 2)
As shown in Figure 8-54, under Available devices, select the device or devices to back up
to and click Add to move them to the Backup devices pane. When you are finished, click
Next.
Figure 8-54 New Backup Policy - Select Backup Device window (Part 2 of 2)
15.On the New Backup Policy - Summary window (Figure 8-56), click Back if you need to
make changes or click Finish if you are done. Then you see window indicating that your
backup policy is being created.
206 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
16.After your backup policy is created, you see the New Backup Policy - Policy Created
window (Figure 8-57). It shows the Run Now, Schedule, and Done buttons. In our
example, we cannot run this policy since we have to make further adjustments to back up
to an ITSM server. Click Done.
17.You return to the main Backup Policies window. You have now defined:
– What to back up
– Where to back up
– What program to call before and after the backup runs
Press F5 to refresh the window.
Final adjustments
AS03 contains the production libraries, so we do not allow any users to stay active. We
assume that there are no special considerations, so we can have BRMS bring the subsystem
down and up again.
Currently our backup policy is pointing to a tape device and we need to make it point to an
IBM Tivoli Storage Manager server. The following steps show how we change this. In this
example, we assume that all interactive users run in the QINTER subsystem and that no
special program is needed to bring down their applications. Therefore, we do not discuss
holding job queues and other advanced possibilities.
4. On the Properties - Before Backup window (Figure 8-59), on the General page, select
Sign off interactive users. Deselect Shut down integrated servers, because you do not
want that to happen.
208 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. On the Job Queues page (Figure 8-60), there is no job queue to hold, so we leave this
page as is.
Figure 8-60 Final adjustments: Properties - Before Backup Job Queues page
Tip: By selecting Delay until job end, the subsystem does not have to wait that 5
minutes you allowed your users to stay active. After the last user signs off, the
subsystem goes down.
If you did not select the Sign off interactive users option on the General page, you must
specify a value here or use *IMMEDIATE. Otherwise the subsystem waits until the last
interactive user signs off.
This completes the Before button activities. Although you are setting the properties for the
Before button, you will see what to do after the backup is finished (for example, the After tab).
For ease of use, many of these tabs overlay each other.
Click the Advanced button on the What page, which opens the window in Figure 8-63.
Click OK and click OK again on the Properties - During Backup window.
3. You return to the Properties - During Backup window shown in Figure 8-64. Selecting the
Where tab on this during backup window has several important parameters, including the
Where to backup and the Append to available media parameters.
If you are saving to tape, you already selected a tape device. However, on the Where page,
you can change the selection and address another drive. Typically if you have a media
library, you do not specify a specific drive but the tape library itself. You let the library select
one for you. You can also use more than one tape drive to perform a parallel save. And you
can specify an append here. This can be helpful for conserving tape volumes.
Attention: Avoid placing objects in a tape volume that drastically extends its expiration
date. The outcome may be the exact opposite to what you wanted to achieve. You may
lock a whole volume only because of a single save.
Our Backup policy is complete except for changing from a tape drive to the IBM Tivoli
Storage Manager server. Click the Where tab.
4. On the Where page (Figure 8-64), for Where to back up, select TSM server.
210 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 8-64 Final adjustments: Properties - During Backup Where page
5. Notice how the Where page changes after we select TSM server. Figure 8-65 shows the
changes. Select your TSM server name. Under Full backups and Changes-only backups,
select the connection name and storage location.
Figure 8-65 Final adjustments: Properties - During Backup Where page for TSM server
6. Skip the Media Retention tab if you don’t have any changes to the media retention
periods. You can also skip the Save File Retention tab if you don’t plan to save to savefiles
in this setup.
7. Click the TSM Server Retention tab.
8. On the TSM Server Retention page (Figure 8-67), you must identify a TSM Management
Class in the IBM Tivoli Storage Manager server. This name must match what is set up on
the IBM Tivoli Storage Manager server. As shown in Figure 8-67, for TSM management
class, we enter brms.
Figure 8-67 Final adjustments: Properties - During Backup TSM Server Retention page
9. Click the Activity tab. On this page, you specify whether you want a full or incremental
backup. You also specify on which day you want to do it.
212 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
10.In this example, we use the customization function by clicking the Customize tab on the
Activity window (not shown). On the first Activity window, select the customize type of
backup activity and click the Customize button.
11.The Activity - Customize window (Figure 8-68) opens. In the lower part of the window, you
see Legend for backup types. In this example, we assume full backups on Sunday, no
backup on Saturday, and changes only for all other days. For each day, select the box until
the correct icon as referenced by the legend as shown. Click OK.
12.Click OK twice to return to the Properties window (Figure 8-58 on page 208). Remain on
this window to select the After button for this backup policy, which is explained in the
following section. You can click OK on the Properties window to return to the primary
iSeries Navigator window, which shows all backup polices in a list within the right pane
(similar to Figure 8-33 on page 194).
You are now finished setting the During Backup properties. You may go back and select more
options if necessary.
Figure 8-70 Final adjustments: Properties - After Backup Power Down page
214 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
5. Click OK to save your changes and return to the Properties window (Figure 8-58 on
page 208). This completes the activities to be done before, during, and after the backup.
6. Click OK. Now you return to the BRMS iSeries Navigator client window.
Your backup policy is now ready to run. Since we expect that you are targeting an IBM Tivoli
Storage Manager server, you do not need to worry about the actual media on which our
backup is stored.
8.9 Locations
If your setup points to tape, you need to specify what you plan to do with the tape volumes
that will result from your save. You also need to create locations and, via the move policy,
define how long the volumes should stay in each place.
Launch the BRMS iSeries Navigator client and log on to the iSeries server.
If you save to an IBM Tivoli Storage Manager server, the procedure ends here. However, for
your convenience, we explain how to create locations using the iSeries Navigator client.
We discuss volumes without a move policy in “Home location” on page 161. We start with that
location here.
2. As shown in the Manage Locations window (Figure 8-72), if you have a tape library device,
notice that it is already created. In this example, our tape library device is Tapmlb05.
a. Select your tape library. In this example, we select Tapmlb05. Click Edit.
216 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
b. In the Edit Storage Location window (Figure 8-73), notice that the Allow volumes to
expire option is already selected. In this example, we replace the words “Automatically
created” with ITSM Server AS27 or something more meaningful.
c. Click OK.
Retrieval time: Specifying the retrieval time may seem to be a rather minor activity.
However, it may play a key factor in case of disaster recovery. During such an event,
you must perform several activities in parallel so that the recovery time is the shortest
possible. If you do not specify any retrieval time, the recovery procedure assumes there
is no wait time to consider and everything can be done in sequence without waiting.
Create all the other locations that you need in the same manner. Make sure that you correctly
set the Allow volumes to expire option.
218 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 8-75 Selecting Move Policies-> New Policy
5. On the New Move Policy - Duration window (Figure 8-78), for each location, enter the
duration of how long a volume will stay at that location. Click Next.
220 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. On the New Move Policy - Verify Moves window (Figure 8-79), specify whether you want to
verify your moves. Click Next.
The New Move Policy - Select Backup Policies window (Figure 8-80) opens.
The new move policy is complete. You can associate your move policy with any Backup policy
already created as explained in the following section.
Note: If you start with a new installation, you find only the IBM-provided backup policies
already listed.
1. Connect your backup policy to your move policy. You can use one move policy for several
backup policies. And you can combine Full and Changes Only as necessary.
On the New Move Policy - Select Backup Policies window (Figure 8-80), highlight your
backup policy. Select how you want to use the new move policy: full, changes only, or both.
Click Next.
3. You attached your move policy to your backup policy. After a few seconds you see the
Move Policy Created window (not shown) on which you can specify whether you want to
run the policy now or later by using the click Schedule button. Or you can exit by clicking
the Done button. In our example, we click Done.
In the following section, we run a backup that consists of saving our IBM Tivoli Storage
Manager environment.
222 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 8-82 Choosing to run the backup policy now
3. The Backup Activity Override window (Figure 8-83) opens. It shows the Use policy
setting and Full back up already selected. You can leave the setting as is or select the
Override policy setting, which activates the window (not available in our example window)
where you can select either Full or Changes only (not shown) from the list. We used Use
policy settings in our example. Click OK.
Figure 8-83 Run Backup Policy Backupitsm - Backup Activity Override window
4. The Run Backup Policy - Retention Override window (Figure 8-84) opens. On this window,
you can choose one of the following actions:
– Click OK to continue.
– Click Override policy settings, which enables you to specify how long to retain any
override settings you already made.
5. When you are finished with this second override window, click OK.
6. This runs the backup policy immediately as part of your iSeries Navigator session. If your
are already logged on to the iSeries, the save automatically starts. If you are not logged
onto the iSeries server, you must sign on to launch your save.
Note: This is the first time we ran this backup. It is Wednesday and we selected to back
up changes only. BRMS does not allow this. We have not performed any full backup
yet, so BRMS makes sure that we do that first, so the policy is automatically set to Full.
224 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. The first Backup Activity Override window (Figure 8-86) opens. We do not elaborate on the
following window example steps because the override windows, steps, and possible
override considerations are essentially identical to the ones described in 8.11, “Running a
save of your ITSM environment” on page 222. We include an example of signing on to the
iSeries servers.
On the Run Backup Policy - Backup Activity Override window, select the type of backup
activity you want to perform for all backup items. Click OK.
4. On the Run Backup Policy - Retention Override window (Figure 8-87), specify the how
long you want to retain the backup information. Click OK.
5. Sign on to the system, if necessary, by entering your user ID and password. Click OK.
Attention: The way this is setup actually contains a pitfall. Active users that are
excluded from signoff, such as a user signed on to the system console device (DSP01)
or signed on as QSYSOPR and QSECOFR, keep QINTER waiting until they sign off.
2. After the backup is completed, you can review the log. As shown in Figure 8-90, right-click
the task and select Backup and Recovery Log.
Figure 8-90 Selecting Backup and Recovery Log for AS03libs backup
226 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. On the Backup and Recovery Log - Include window (Figure 8-91), for Entry type, select
Backup. Change the time and date if necessary. Click OK.
5. You can check to see what was backed up. To do this, select the AS03libs task, right-click,
and select Backup History.
6. On the Backup History - Include window (Figure 8-94), you can see what was included in
the backup. You can make changes to subset the history information that you will see. We
228 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
recommend that you select the All defaults as shown unless you have a specific reason to
subset the history information you want to look at. When you finish determining what
history information to include, click OK.
7. On the Backup History window (Figure 8-95), you can select an item for further details.
Figure 8-96 Detailed information in the Backup History window for policy AS03libs
Restriction: At the time this redbook was written, the BRMS iSeries Navigator client is
only usable for restoring single entities. If you want to revert to the backup policy used for
the save and use it for restore, we recommend that you use the 5250 interface.
As mentioned earlier, the IBM Tivoli Storage Manager server environment consist of three
parts. In this example, we restore one using iSeries Navigator.
Note: Alternatively, you can start this set of steps using the iSeries Navigator Taskpad
area (showing Backup Recovery and Media Services Tasks). Select Restore iSeries
data (circled in the lower pane in Figure 8-97). The succeeding windows launch the
Restore wizard.
230 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 8-97 iSeries Navigator: Starting a restore function
2. The Restore wizard opens. On the first wizard window, click Next.
3. On the next window, select Restore using backup history and click Next.
4. The Select Type of Information window (Figure 8-98) opens. Select the A directory or its
files option. Click Next.
6. The Restore - Restore Entire Directory window (Figure 8-100) opens. Select the Restore
directory and all files option and the Include subdirectories check boxes. Click Next.
232 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
7. In this example, we do not want to change location. On the Restore - Restore to Same
Location window (Figure 8-101), select the Yes, restore to same location option. Click
Next.
8. Since we have a tape library device, there is no value in selecting a specific tape drive on
the next window. On the Restore - Use Backup History Device window (Figure 8-102),
select Yes, automatically select a device. Click Next.
If the volume is not in the tape library device, you must insert it. Otherwise you are finished.
The restore starts. You must repeat these steps to restore everything.
Attention: The objects that you are about to restore are saved on the same physical tape
volume. Make sure that you do not submit your restore jobs concurrently.
Restoring IBM Tivoli Storage Manager server using the 5250 interface
In this example, we use the 5250 interface and the backup policy used to save the IBM Tivoli
Storage Manager server. In the 5250 interface, the iSeries Navigator backup policy is named
(backup) control group.
We restore using our example backup control group defined via the iSeries Navigator client.
Important: Before you restore any IBM Tivoli Storage Manager data, make sure the IBM
Tivoli Storage Manager server is ended.
We show examples interactively using the 5250 interface and as a batch job.
234 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Select Recovery Items
Bottom
F3=Exit F5=Refresh F9=Recovery defaults F12=Cancel
F14=Submit to batch F16=Select all
Figure 8-104 5250 restoring IBM Tivoli Storage Manager environment using the latest save
5. Follow the steps presented in the screens that follow. You see similar restore options as
the ones explained in “Restoring the IBM Tivoli Storage Manager server using iSeries
Navigator” on page 230. Reply to the options in a similar manner.
6. Start the IBM Tivoli Storage Manager server as explained in 5.1, “Starting and stopping
the IBM Tivoli Storage Manager server” on page 54.
Position to Date . . . . .
Bottom
Figure 8-105 5250 restore IBM Tivoli Storage Manager environment using available saves
4. Reply to the displays that follow to specify further restore information, according to your
specific save activity.
Using the iSeries Navigator client, restoring data is a fairly easy and straightforward task
when you start. Most of the parameter values you enter or option choices you make are also
straightforward. In this book, we describe several restore examples.
We provide this example as a reference to show additional options. We expect that you
followed our example backing up As03xxx libraries described in 8.8.2, “Saving native OS/400
data to an IBM Tivoli Storage Manager server” on page 198.
In this example, we use the Taskpad area with Backup Recovery and Media Services Tasks
heading within the iSeries Navigator window shown in Figure 8-97 on page 231 to start this
restore example.
1. Select Restore iSeries data as shown in Figure 8-106.
236 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
2. The Restore - Welcome wizard window (Figure 8-107) opens. Click Next.
3. On the Restore - Restore from Backup History or Device window (Figure 8-108), select
how you want to restore, by using backup history or by specifying media. We chose
Restore using backup history. Click Next.
5. On the Restore - Specify Library window (Figure 8-110), enter the name or use the
Browse button to select from a list. In this example, click Browse.
238 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. On the Restore - Browse Libraries window (Figure 8-111), select library As0304lib from
the list. Click OK.
7. Back on the Restore Specify Library window (Figure 8-112), you see that the library name
is filled in. Click Next.
In this example, we show the Disk Pool list for information purposes. We select the
System and disk base pools option, but you can optionally specify All disk pools. The
All disk pools option adds any optionally defined independent disk pools (also called
IASPs), to the system and any optionally defined base (dependent ASPs) storage pools.
9. As you can see on the Restore - Select the Date of the Save window (Figure 8-114), we
selected the backup that was taken on 9/2/03 at 12:01 PM.
240 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Click the Details button, and you see the Backup Details window with the General and
Media pages as shown in Figure 8-115.
Click OK.
10.Back on the Restore - Select the Date of the Save window, click Next.
11.On the Restore - Restore Entire Library window (Figure 8-116), in our example, we select
Select objects in the library to restore option.
If there is detailed information, you see the list of objects shown in the Restore - Select
Objects window showing each object, its object type, and its date saved information as
shown in Figure 8-118. You can select one or more objects. In our example, we select
Final and click Next.
242 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
12.The Restore - Restore to Same Location window (Figure 8-119) opens. You can change
the target library if you desire. Click Next.
13.Using an IBM Tivoli Storage Manager server, the final window that you see is the
Summary window (not shown).
For a reference, we provide the windows that open when you restore from tape. One way to
follow this set of windows is to select Specify media on the window shown in Figure 8-108 on
page 237. This opens the following sequence of tape device-related windows:
1. In the selecting a device window, select a tape device automatically or manually as shown
in Figure 8-120. In our example, there are four tape devices and the tape library device
(Tapmlb05) known to BRMS. We select Tap09 (not shown).
If you have only one tape device known to BRMS, the tape device and Volumes needed
parameter may be on a different wizard window.
Tap09
Lb0714
244 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. On the Restore - Advanced Options window (Figure 8-122), you can select the End of
tape action, allow or not allow object differences (when restoring the same object name
and type already existing on the system), and several database member restore options.
Tap09
Lb0714
5. Clicking the Schedule button opens the Management Central Scheduler window shown in
Figure 8-124. You must enter the time, date, and whether there is a one-time restore or
you want repetitive scheduling. The current system time and date are defaulted so be
careful to specify the time and date values that are right for your operating environment.
246 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Note: If you optionally installed the separately priced Advance Job Scheduler product
(5722-JS1) and included it as an optional plug-in to your iSeries Navigator session, you
see a different scheduling window than the one shown here.
When you are done specifying your scheduling information click OK and exit the Restore
wizard.
First, you may have run the restore immediately from the Restore - Summary window shown
in Figure 8-121 on page 244 or scheduled it to run later (from the Restore - Summary window
shown in Figure 8-123). When that function runs, it is performed within one of the OS/400
pre-started host server “central server jobs” with the prefix QZRCSRVS in subsystem
QUSRWRK. You can see these jobs by issuing the Work with Subsystem Jobs
(WRKSBSJOB) command for QUSRWRK or the Work with Active Jobs (WRKACTJOB)
command (shown in Figure 8-125).
The job that runs the restore is determined at run time and may be any one of these
prestarted jobs within IBM-provided subsystem QUSRWRK. When this function is performed,
it sends status messages to message queue QSYSOPR, which identify the job doing the
restore.
Figure 8-125 WRKACTJOB for subsystem QUSRWRK running BRMS restore example
To see the restore results using the BRMS iSeries Navigator client, complete the following
steps. These steps are based on Figure 8-89 on page 226 as a reference, and the windows
flow similar to those in 8.13, “Finding your backup job” on page 226.
1. At the top of the main iSeries Navigator window left pane, expand Management Central->
Task Activity. Click Backup, Recovery and Media Services.
2. In the right pane, view all the BRMS tasks that you started. Find your “Restore Items”
entry as shown in our example in Figure 8-126. Note the information in the rightmost area
(including Started and Last Changed columns).
4. You return from the workstation back to the Task Activity: Backup, Recovery and Media
Services right pane. Right-click your restore items entry and select Backup and
Recovery Log. Click OK.
5. You see the details of your BRMS activity. Scroll down to find your appropriate time
stamped restore entries. Using our AS0304lib library example, you see a message similar
to the one shown in Figure 8-128 that lists the object or objects that are restored.
This concludes our overview of getting BRMS up and running. We did not cover the complete
set of backup and recovery capabilities available using the Backup, Recovery and Media
Services, 5722-BR1, product. Refer to Backup Recovery and Media Services for iSeries,
SC41-5345, for complete coverage.
Chapter 9, “Setting up an iSeries server as the Backup Recovery and Media Services
Application Client” on page 249, provides more details about setting up and using BRMS as a
client to the IBM Tivoli Storage Manager server, when the product IBM Tivoli Storage
Manager for OS/400 PASE (5698-ISX) is installed and set up on an iSeries server.
248 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
9
In addition, this chapter explains full backup and restore for an iSeries considering the BRMS
Application Client to an IBM Tivoli Storage Manager server. Plus it discusses Save While
Active (SWA) implications and IBM Tivoli Storage Manager password management.
Although complete coverage of performance is beyond the scope of this redbook, this chapter
provides performance scenarios. These scenarios use the BRMS Application Client to an
iSeries IBM Tivoli Storage Manager server between two logical partitions (LPAR), using the
Virtual Ethernet local area network (LAN) between partitions.
There is no IBM Tivoli Storage Manager Backup-Archive Client type of product on the iSeries
server. The BRMS Application Client provides several backup and archive client-like functions
in relation to an IBM Tivoli Storage Manager server. These are sometimes referred to as an
IBM Tivoli Storage Manager client. However, it is not an IBM Tivoli Storage Manager
Backup-Archive Client. For general considerations, see 2.9, “System backup strategies to an
IBM Tivoli Storage Manager server” on page 31.
This chapter assumes that you successfully installed BRMS on your iSeries, as described in
7.2, “Installing the BRMS software” on page 134. It also expects that you installed IBM Tivoli
Storage Manager APIs (5733-197) on your iSeries server, as described in 7.4, “Downloading
and installing no-charge IBM Tivoli Storage Manager APIs” on page 142.
Although it is not required, we strongly recommend that you define your own IBM Tivoli
Storage Manager environment for an iSeries server. This assures that the IBM Tivoli Storage
Manager server expires objects soon after they are deleted by BRMS. Also, IBM Tivoli
Storage Manager copy-group retentions are not used.
IBM Tivoli Storage Manager server setup for an iSeries as the BRMS Application Client is
different from setting up other IBM Tivoli Storage Manager Backup-Archive Clients and your
own IBM Tivoli Storage Manager environment helps make this setup easier.
Each of the following tasks show the IBM Tivoli Storage Manager Web administrative client
interface to perform the step, followed by the IBM Tivoli Storage Manager command interface.
Perform these tasks on the IBM Tivoli Storage Manager server side. If you are not familiar
with IBM Tivoli Storage Manager, consider asking your IBM Tivoli Storage Manager
administrator to perform these steps. For more details about IBM Tivoli Storage Manager
server in this book, see Chapter 5, “First steps: IBM Tivoli Storage Manager server basic
configuration” on page 53.
Notes: In the steps in this chapter, we use the name “BRMS” for most of our IBM Tivoli
Storage Manager definitions. In most cases, this is the required value for parameters that
specifically enable the BRMS Application Client to work successfully to any IBM Tivoli
Storage Manager server. Other BRMS-oriented chapters in this redbook identify when the
value “BRMS” is required. To avoid any problems, use this value as shown in the examples
in this chapter.
250 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 9-1 Policy Domain panel
Using the IBM Tivoli Storage Manager Web Server Command window, enter:
DEFine DOmain BRMS DESCription=”Domain for BRMS Application Clients” BACKRETention=365
ARCHRETention=0
In both cases, you receive the message “ANR1500I Policy domain BRMS defined”.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 251
2. Define an IBM Tivoli Storage Manager policy set.
Using the IBM Tivoli Storage Manager Web administrative client interface tree structure,
follow these steps:
a. Expand Object view-> Policy Domains-> Policy Domains-> Policy Sets.
b. From the Operations list, select Define Policy Set.
c. The Define Policy Set panel (Figure 9-3) opens.
i. For Policy Domain Name, select BRMS in parameter. We created this domain in the
previous step.
ii. For Policy Set Name, type BRMS.
iii. In the Description field, type your own text, for example Policy Set for BRMS
Application Client.
iv. Click Finish.
Using the IBM Tivoli Storage Manager Web Server Command window, enter:
DEFine POLicyset BRMS BRMS DESCription=”Policy set for BRMS Application Clients”
In both cases, you see the message “ANR1510I Policy set BRMS defined in policy
domain BRMS”.
252 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. Define an IBM Tivoli Storage Manager management class.
Using the IBM Tivoli Storage Manager Web administrative client interface tree structure,
follow these steps:
a. As shown in Figure 9-4, expand Object view-> Policy Domains-> Policy Domains->
Policy Sets-> Management Classes.
b. From the Operations list, select Define Management Class.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 253
c. The Define Class Management panel (Figure 9-5) opens.
i. In the Policy Domain Name field, select BRMS.
ii. In the Policy Set Name field, select BRMS, which was created in the previous step.
iii. In the Mgmt Class Name field, type BRMS.
iv. In the Description field, enter meaningful text, for example, Management Class for
BRMS Application Clients.
v. Leave the other parameters as the default values.
vi. Click Finish.
Using the IBM Tivoli Storage Manager Web Server Command window, enter:
DEFine MGmtclass BRMS BRMS BRMS DESCription=”Management Class for BRMS Application
Clients”
In both cases, you see the message “ANR1520I Management class BRMS defined in
policy domain BRMS, set BRMS”.
4. Define an IBM Tivoli Storage Manager copy group.
Using the IBM Tivoli Storage Manager Web administrative client interface tree structure,
follow these steps:
a. Expand Object view-> Policy Domains-> Policy Sets-> Management Classes.
Select Backup Copy Groups.
b. From the Operations list, select Define Backup Copy Groups.
c. The Define Backup Copy Group panel (Figure 9-6) opens.
i. For the Policy Domain Name, Policy Set Name, and Management Class Name
fields, select BRMS.
ii. For Copy Destination, select BACKUPPOOL.
254 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
iii. Change the following parameters from their defaults to values as indicated in
parentheses:
• Versions Data Exists (2 to 1)
• Versions Data Deleted (1 to 0)
• Retain Extra Versions (30 to 0)
• Retain Only Version (60 to 0)
iv. Leave the other parameters with defaults.
v. Click Finish.
Using the IBM Tivoli Storage Manager Web Server Command window, enter:
DEFine COpygroup BRMS BRMS BRMS STANDARD Type=Backup DESTination=BACKUPPOOL VERExists=1
VERDeleted=0 RETExtra=0 RETOnly=0
In both cases, you see the message “ANR1530I Backup copy group STANDARD defined in
policy domain BRMS, set BRMS, management class BRMS”.
5. Assign the defined IBM Tivoli Storage Manager management class (for example, BRMS)
as the default management class.
Using the IBM Tivoli Storage Manager Web administrative client interface tree structure,
follow these steps:
a. Expand Object view-> Policy Domains-> Policy Sets-> Management Classes.
b. From the list of defined management classes that appear in the right panel, select
BRMS and, under Management Class Name, click BRMS.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 255
c. The Management Classes panel (Figure 9-7) opens. From the Operations list, select
Assign as Default Management Class. Review this panel and click Finish.
Figure 9-7 Assigning a management class BRMS as the default management class
Using the IBM Tivoli Storage Manager Web Server Command window, enter:
ASSign DEFMGmtclass BRMS BRMS BRMS
In both cases, you see the message “ANR1538I Default management class set to BRMS
for policy domain BRMS, set BRMS”.
Note: You can verify your management class, BRMS, by using the IBM Tivoli Storage
Manager Web administrative client interface tree structure. The Default Management
Class parameter should now be Yes, where it is shown in Figure 9-7 before the change.
256 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. Activate a policy set (for example, BRMS).
Using the IBM Tivoli Storage Manager Web administrative client interface tree structure,
follow these steps:
a. Expand Object view-> Policy Domains-> Policy Domains-> Policy Sets.
b. As shown in Figure 9-8, in the right panel, you see all defined policy sets. Under Policy
Set Name, click BRMS.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 257
c. The Policy Sets panel (Figure 9-9) opens. In the Operations list, select Activate Policy
Set.
d. On the panel that appears, click Finish.
Using the IBM Tivoli Storage Manager Web Server Command window, enter:
ACTivate POLicyset BRMS BRMS
In both cases, you see the following two messages:
ANR1554W DEFAULT Management class BRMS in policy set BRMS BRMS does not have an ARCHIVE
copygroup: files will not be archived by default if this set is activated.
258 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Communication protocol used: Normally TCP/IP is used. However Advanced
Peer-to-Peer Network (APPN) is also supported for the BRMS Application Client.
APPC/Advanced Program-to-Program Communication (APPC) was the original
implementation.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 259
8. Register your iSeries as an IBM Tivoli Storage Manager node.
Using the IBM Tivoli Storage Manager Web administrative client interface tree structure,
follow these steps:
a. As shown in Figure 9-11, expand Operation view-> Work with client nodes and
select Register a new node.
b. The Register a new node panel opens:
i. For Node Name, type the name, which is AS02 in our example.
ii. Type the values for the Password and Contact fields.
iii. In the in Policy Domain Name field, select BRMS.
iv. For the Client compression setting, select No.
v. For Backup Delete Allowed?, select Yes.
vi. Leave all other parameters with defaults.
vii. Scroll down and click Finish.
Using the IBM Tivoli Storage Manager Web administrative client interface Server
Command window, enter:
Register Node AS02 password CONtact=text DOmain=BRMS COMPression=NO BACKDELete=Yes
In both cases, you see the following two messages:
ANR2060I Node AS02 registered in policy domain BRMS.
ANR2099I Administrative user id AS02 defined for OWNER access to node AS02.
You can use the IBM Tivoli Storage Manager Web administrative client interface tree
structure to verify your IBM Tivoli Storage Manager node environment. As shown in
Figure 9-12, you expand Object view-> Clients-> Client Nodes.
260 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 9-12 View from IBM Tivoli Storage Manager server over both clients in our test scenario
Important: Remember the following three definitions for the next section:
The defined management class name, in our example BRMS
The node name and password, in our example AS02 with password ......
The kind of communication protocol, in our example TCP/IP
When you complete these actions, you are ready to set up the BRMS environment for backup
and restore to an IBM Tivoli Storage Manager server.
Note: The options file is used to specify some runtime environment parameters for the
IBM Tivoli Storage Manager server. See 5.3.10, “IBM Tivoli Storage Manager server
option file” on page 75, for more details.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 261
2. Set up a *LOCALE object pointed to by OS/400 system value QLOCALE.
3. Set up environment variable DSMI_LOG.
Following the completion of these steps, we perform the follow-on setup steps that are shown
using the following interfaces:
The OS/400 5250 command interface (9.2.2, “Follow on steps using the 5250 interface” on
page 265)
The iSeries Navigator interface (9.2.3, “Follow-on steps using iSeries Navigator” on
page 269)
Notes:
Through 2003, using a non-QSYS.LIB option file is not supported in this BRMS
Application Client environment.
There are other scenarios, where using a non-QSY.LIB option file works. See Domino 6
for iSeries Best Practices Guide, SG24-6937, for an example.
If you are not using default IBM Tivoli Storage Manager server port 1500, you must
also modify the TCPPORT parameter in this options file.
262 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
*************** Beginning of data **********************************************************
*SERVERNAME XXXX 030819
* COMMMETHOD TCPIP 030819
* TCPPORT 1500 030819
TCPSERVERADDRESS xxx.xxx.xxx.xxx 030825
NODENAME AS02 030819
****************** End of data *************************************************************
iv. Press F3 (Exit) and type Y (Yes) in the Change/create member parameter. Press
Enter.
Note: Do not change the default value for the program Type parameter in the Work
with Members Using PDM display. The default type is “blank”. Leave this as blank.
See Figure 9-14.
File . . . . . . QOPTADSM
Library . . . . QANSAPI Position to . . . . .
2. Set the OS/400 system value parameter QLOCALE. Verify the Locale parameter in your
user profile.
Tip: We recommend that you set system value QLOCALE appropriately as explained.
Then set the Locale parameter of the user profile who normally runs BRMS operations
to the IBM Tivoli Storage Manager servers to *SYSVAL. This technique prevents error
messages, such as “MCH3601 Pointer not set for location referenced”, from
appearing during backups to an IBM Tivoli Storage Manager server.
You can use other techniques to use the appropriate *LOCALE object, but our
recommendation is less error prone.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 263
c. Enter option 2 to change this value. On the Change System Value display
(Figure 9-15), for a U.S. English environment, type /QSYS.LIB/en_US.LOCALE.
Locale . . . /QSYS.LIB/en_US.LOCALE
iSeries servers ship with a locale object for each of the supported languages. If
OS/400 Option 21, Extended NLS Support, is installed, you can modify default
locale object settings by editing language-specific locale source file members for file
QLOCALESRC in library QSYSLOCALE.
For more information about OS/400 support for locales, see the iSeries V5R2
Information Center and search on “locale”:
http://www.ibm.com/eserver/iseries/infocenter
For an overall description of locale support, scroll down through the search results
and click the Locale categories link. Select the links listed under the Locale
categories Web page.
d. Use the Display User Profile (DSPUSRPRF) command to verify that the LOCALE
parameter value in your user profile specifies *SYSVAL. See Figure 9-16.
Scroll down or page down the user profile. The Locale parameter is toward the bottom
of the user profile information.
Locale . . . . . . . . . . . . . . . . . . : *SYSVAL
264 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Although this is optional, we recommend that you set an environment variable DSMI_LOG
for a path to the error log file dsierror.log. This speeds up any troubleshooting that you may
need to perform.
Use the OS/400 Add Environment Variable (ADDDENVVAR) command to define in the
VALUE parameter, a target directory for this error log file, dsierror.log. We use the default
API installation directory, /usr/tivoli/tsm/client/api/bin, as the path for error log file
dsierror.log in our example. See 7.4, “Downloading and installing no-charge IBM Tivoli
Storage Manager APIs” on page 142.
ADDENVVAR ENVVAR(DSMI_LOG) VALUE('/usr/tivoli/tsm/client/api/bin') level(*SYS)
Figure 9-17 shows the error log file dsierror.log content. For an interpretation of this log
information, ask your IBM Tivoli Storage Manager server administrator.
Browse : /usr/tivoli/tsm/client/api/bin/dsierror.log
************Beginning of data**************
08/19/03 16:02:59 GetHostnameOrNumber(): gethostbyname(): errno = 0.
08/19/03 16:02:59 TcpOpen: Could not resolve host name.
08/19/03 16:02:59 sessOpen: Failure in communications open call. rc: -53
08/19/03 17:02:34 sessSendVerb: Error sending Verb, rc: -50
08/20/03 18:29:11 ANS1005E TCP/IP read error on socket = 1, errno = 3426,
reason : 'A connection with a remote socket was reset by
that socket.'.
08/28/03 10:12:41 sessRecvVerb(): Invalid verb received.
08/28/03 10:12:41 sessRecvVerb(): length=680f, verb=eb,magic=16
************End of Data********************
The following two sections cover the same set of follow-on steps, using either the 5250
command interface or the iSeries Navigator interface. We recommend that you review both
interfaces to determine which one you will normally use.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 265
i. Optionally enter meaningful text into the address fields and the description field.
ii. Leave the other parameters as the defaults.
iii. Press Enter.
d. You should see the message “BRM1269: Location ITSMSERVER added”.
2. Create a BRMS media policy. In our example, we use ITSM. See Figure 9-18 and
Figure 9-19. The following steps use the IBM Tivoli Storage Manager management class
(BRMS) specified in step 3 on page 253. They also use the iSeries IBM Tivoli Storage
Manager “client” (AS02) and associated password specifications specified in step 7 on
page 258:
a. Enter the BRMS Work with Policies using BRMS (WRKPCYBRM) command:
WRKPCYBRM TYPE(*MED)
b. On the Work with Media Policies display, in the Opt field, enter 1 (Add).
c. In the Policy field, type the new media policy name (ITSM in our example) and press
Enter.
d. The Create Media Policy display opens.
i. For the Move policy, Media class, and Secure media parameters, enter the value
*ADSM. This is the older product identifier that is also used for the newer IBM Tivoli
Storage Manager product.
ii. For the Storage Location parameter, type ITSMSERVER. This corresponds to the
name we used in the first step, which created the new storage location.
iii. Optionally you can leave the default vales or change following parameters on this
page:
• Retention type: We leave the default value of 2.
• Retain media: We leave the default value of 35.
iv. In the Text parameter, enter a meaningful description for this ITSM media policy. We
use Media Policy for ITSM in this example.
More...
266 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
vi. Enter the following values as shown in Figure 9-19:
• TSM management class BRMS
• TSM node AS02
• TSM password for your node
If you leave a default value as the node name, for example APPN.AS02, this is useful
only in a Systems Network Architecture (SNA)-based APPN environment.
vii. Press Enter.
e. Verify that you see the message “BRM1171: Policy ITSM created”.
3. Create a BRMS device for your IBM Tivoli Storage Manager server. We use
ITSMSERVER in our example and the TCP/IP protocol and IBM Tivoli Storage Manager
server (AS27) as previously specified for our test environment (see Figure 1-3 on
page 11).
IBM Tivoli Storage Manager server Internet address: Assuming TCP/IP is being
used in your environment, you need the Internet (IP) address of the IBM Tivoli Storage
Manager server to perform the following steps. Ask your IBM Tivoli Storage Manager
administrator for this information.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 267
Manager server’s default port of 1500 here. You can specify a different port if your
IBM Tivoli Storage Manager server administrator chose a different port number.
vi. Press Enter.
d. Verify that you receive the message “BRM1292: Device Entry ITSMSERVER added”.
e. You can perform additional verification using the Display Physical File Member
(DSPPFM) command for file QUSRBRM/QA1AOPT MBR(ITSMSERVER), which
should be automatically created during the adding of the ITSMSERVER device. See
Figure 9-21.
Important: You need the following iSeries BRMS Application Client database files on your
iSeries server that is defined as the BRMS Application Client to an IBM Tivoli Storage
Manager server:
QANSAPI/QOPTADSM MBR(APIOPT)
QUSRBRM/QA1AOPT MBR(ITSMSERVER)
The member file name depends on the name you gave your IBM Tivoli Storage Manager
server Device as a Net Device in BRMS. In our example, this is ITSMSERVER.
268 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Now you are ready to use (with modifications) an existing BRMS backup control group for
saves to IBM Tivoli Storage Manager server. Or you can create a new BRMS backup control
group. See 9.3, “Save scenario example: Saving to an IBM Tivoli Storage Manager server” on
page 277, for an example.
You may skip the following section if you do not want to use the iSeries Navigator interface. If
this is the case, proceed to 9.3, “Save scenario example: Saving to an IBM Tivoli Storage
Manager server” on page 277.
You can define your iSeries as BRMS Application Client to an IBM Tivoli Storage Manager
server using BRMS iSeries Navigator client interface.
IBM Tivoli Storage Manager server Internet address: Assuming TCP/IP is used in your
environment, you need the Internet (IP) address of the IBM Tivoli Storage Manager server
to perform the following steps. Ask your IBM Tivoli Storage Manager administrator for this
information.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 269
b. The Backup Policies, Move Policies, and Media items appear in the right pane (see
Figure 9-22).
c. In the task pad area at the bottom of the window, click Manage TSM servers.
Note: This section uses the acronym “TSM,” instead of IBM Tivoli Storage Manager,
because TSM is the acronym used in the iSeries Navigator interface to the IBM
Tivoli Storage Manager.
270 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
2. The TSM Servers window (Figure 9-22) opens. Create a TSM server description. We use
ITSMServer in this example.
Delete restriction: Currently within the BRMS iSeries Navigator client interface you can
“create” a new TSM server description. However, there is no delete TSM server or
delete TSM server Connection Name interface. You can use the Delete function via the
5250 interface. Therefore, you should carefully select your TSM Server Description and
Connection Name, described in the following steps.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 271
b. The New TSM Server window (Figure 9-24) opens. Define a new Net device by typing
or verifying the following parameter values:
i. For Net device, type ITSMServer.
ii. For Type, select TCP/IP.
iii. For Buffer size, type 512 (we choose the largest value in KB for improved
performance)
iv. For Internet address, type the xxx.xxx.xxx.xxx of your IBM Tivoli Storage Manager
server. In our example, this is the IP address for system AS27.
v. For Description, you can optionally enter a meaningful description for this device, for
example, ITSM Server Device.
vi. Leave IBM Tivoli Storage Manager server’s Internet port parameter as the default
1500. We assume you are using the iSeries IBM Tivoli Storage Manager server’s
default port of 1500 here. You can specify a different port if your IBM Tivoli Storage
Manager server’s administrator chose a different port number or specify APPC if it
is used instead of TCP.
Note: The default value for Location is “Use TSM server name”. In the Net
device example, creating a new BRMS location results in the new TSM server
named ITSMServer being automatically created. We verify this later.
272 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
After the new server creation completes, you see a new entry in the TSM Servers window
(Figure 9-25). In this case, whether the new TSM Server is in uppercase or lowercase is
not important.
Important: In this case, use of uppercase and lowercase is very important. The
password is case sensitive using the iSeries Navigator interface.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 273
Figure 9-26 shows the newly defined connection (AS02) in the Connection Name box.
274 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
4. Verify that the BRMS Location (Itsmserver) is created.
a. Using iSeries Navigator, expand My Connections-> system name (AS02)-> Backup
Recovery and Media Services.
b. In the lower right panel of iSeries Navigator (Figure 9-27), select Backup, Recovery
and Media Services Tasks, expand Movement Tasks and select Manage locations.
c. In the Manage Locations window (Figure 9-27), select the Itsmserver location and
click the Edit button.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 275
d. The Edit Storage Location Itsmserver - AS02 window (Figure 9-28) opens. Notice that
the Location name Itsmserver is not available. Enter any meaningful text into the
Description, Address, and Contact name fields.
Leave the Retrieval time and Allow volumes to expire at this location with their default
values as shown. Remember you can use the Help button or help ? parameter function
on any of these iSeries Navigator windows. Click the Advanced button
e. The Edit Storage Location Itsmserver - Advanced window (Figure 9-29) opens. In this
example, we leave all default values at zero as shown. Zero values are valid because,
in a BRMS location for an IBM Tivoli Storage Manager server, there is no media. The
media is on the IBM Tivoli Storage Manager server system. Click OK.
f. On the Edit Storage Location Itsmserver - AS02 window (Figure 9-28), click OK.
Verification of our BRMS location Itsmserver setup is finished. Now you are ready to modify a
existing BRMS backup control group for saves to IBM Tivoli Storage Manager server or you
276 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
could create a new BRMS backup control group. See 9.3, “Save scenario example: Saving to
an IBM Tivoli Storage Manager server” on page 277, for an example.
During your setup steps, the file QUSRBRM/QA1AOPT MBR(ITSMSERVER) on your iSeries
server was created. Do not delete this file.
iSeries BRMS Application Client and database files: You need the following files on
your iSeries server that is defined as the BRMS Application Client to an IBM Tivoli Storage
Manager server:
QANSAPI/QOPTADSM MBR(APIOPT)
QUSRBRM/QA1AOPT MBR(ITSMSERVER)
The member file name depends on the name you gave your IBM Tivoli Storage Manager
server Device as a Net Device in BRMS. In our example, this is ITSMSERVER.
The objects saved in the 5250 interface and the BRMS iSeries Navigator client topics are
different. You should read both sections for maximum coverage of BRMS and IBM Tivoli
Storage Manager integration for backup (save) functions.
Group . . . . . . . . . . : TESTSAVE
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backup of library ITSMLIB
Here are BRMS details for some of the column headings in Figure 9-30:
Auxiliary Storage Pool Device: Every OS/400 system comes with a system auxiliary
storage pool. By default, all configured disk devices are assigned to this storage pool. And
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 277
all system and user data reside in this system ASP. Optionally an administrator can assign
specific disk devices to either a user-defined dependent ASP (user ASP) or a user-defined
independent auxiliary storage pool (IASP). Data and objects can be specifically placed
into any of these non-system ASPs.
An IASP can be switched to another iSeries server as part of a high availability
configuration. The term *SYSBAS represents the OS/400 system auxiliary storage pool
and any, optionally defined, user ASPs. It does not include any IASPs.
In addition to the *SYSBAS data space, an IASP can be optionally added to an OS/400 job
through either the appropriate job description object Initial ASP Group parameter or the
OS/400 Set ASP Group (SETASPGRP) command. A job always has access to *SYSBAS.
Optionally it can also have access to a single ASP group. Technically an IASP can consist
of a primary IASP and one or more secondary IASPs.
Note that some OS/400 commands, such as the save and restore set of commands, may
also support an ASP group-related parameter.
Weekly Activity: The weekly activity for Monday through Sunday uses the default activity
as defined elsewhere in BRMS
Retain Object Detail: This column applies to the BRMS save Automatically backup media
information parameter, which we more fully discuss in 9.5, “Full iSeries backup and restore
on the BRMS Application Client” on page 312. *OBJ for the Automatically backup media
information parameter says to keep full BRMS saved object-level information in a specific
set of BRMS database files. This full level of information is required for a full iSeries
system recovery using the BRMS recovery process. This level of information and its
saving is analogous to saving the IBM Tivoli Storage Manager database so it can perform
its full set of functions. For a summary of the IBM Tivoli Storage Manager database, see
“IBM Tivoli Storage Manager database and recovery log” on page 35.
Save While Active: *YES means that you can save the objects within library ITSMLIB
while they are “active” (in use by some program). You can learn more about Save While
Active in 2.5, “Save-while-active function” on page 25, and 9.6, “Save-while-active
implications” on page 325.
SWA Message Queue: This SWA message queue receives any important messages that
occur during a save, while active jobs or programs may be accessing the object being
saved.
Detailed coverage of BRMS capabilities is beyond the scope of this book. In this redbook, see
the following chapters for overall BRMS capabilities:
Chapter 2, “Backup Recovery and Media Services” on page 15
Chapter 7, “Installing Backup Recovery and Media Services” on page 133
Chapter 8, “Backup Recovery and Media Services up and running” on page 155
iSeries Backup Recovery and Media Services Version 5, SC41-5345, describes all BRMS
capabilities, including the auxiliary storage pool (ASP) support.
It is important to note that this backup control group can be easily changed to a backup
control group for saves to an IBM Tivoli Storage Manager server. Before we show this,
however, we must understand our control group attributes from the backup control group
TESTSAVE.
Follow these steps to modify this backup control group and perform the actual BRMS backup:
1. Enter the BRMS Work with Control Groups (WRKCTLGBRM) command.
2. On the display that appears, to view the backup control group attributes, enter option 8
next to TESTSAVE.
278 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. The Change Backup Control Group Attribute display opens. It shows the TESTSAVE
control group attributes (see Figure 9-31 and Figure 9-32).
Group . . . . . . . . . . . . . . . . : TESTSAVE
More..
Group . . . . . . . . . . . . . . . . : TESTSAVE
Automatically backup
media information . . . . . . . . . *OBJ *LIB, *OBJ, *NONE, *BKUPC
Save access paths . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Save contents of save files . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Data compression . . . . . . . . . . . . *BKUPCY *DEV, *YES, *NO, *BKUPCY
Data compaction . . . . . . . . . . . . *BKUPCY *DEV, *NO, *BKUPCY
Target release . . . . . . . . . . . . . *BKUPCY *CURRENT, *PRV, *BKUPCY
Clear . . . . . . . . . . . . . . . . . *BKUPCY *NONE, *ALL...
Object pre-check . . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Append to media . . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
End of tape option . . . . . . . . . . . *BKUPCY *UNLOAD, *REWIND...
Journaled objects . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Use optimum block size . . . . . . . . . *BKUPCY *BKUPCY, *DEV, *YES, *NO
Text . . . . . . . . . . . . . . . . . . Backup of library ITSMLIB
More...
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 279
4. Verify what you must change to back up library ITSMLIB to an IBM Tivoli Storage Manager
server using backup control group TESTSAVE. Complete the following checklist:
a. Is a backup of ITSMLIB to an IBM Tivoli Storage Manager server allowed?
Yes, because it is a user library and user data is allowed.
b. Is a backup with Save While Active allowed?
Yes, because we don’t use *SYNCLIB, which is not allowed. See 9.6,
“Save-while-active implications” on page 325.
5. Determine which backup control group attributes to change, referring to Figure 9-33 and
Figure 9-34. We note the values that we entered for this example.
a. Media policy: Specify ITSM, which was created in 9.2, “Setting up the BRMS
environment for backup and restore to an IBM Tivoli Storage Manager server” on
page 261.
b. Backup devices: Specify ITSMSERVER, which was created in 9.2, “Setting up the BRMS
environment for backup and restore to an IBM Tivoli Storage Manager server” on
page 261.
c. Automatically backup media information: Specify *NONE. To understand why we
must specify *NONE here, see 9.5, “Full iSeries backup and restore on the BRMS
Application Client” on page 312.
Our changed backup control group attributes for TESTSAVE are now shown in
Figure 9-33 and Figure 9-34.
Group . . . . . . . . . . . . . . . . : TESTSAVE
Figure 9-33 Backup control group attributes for TESTSAVE after change (Part 1 of 2)
280 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Change Backup Control Group Attributes
Group . . . . . . . . . . . . . . . . : TESTSAVE
Automatically backup
media information . . . . . . . . . *NONE *LIB, *OBJ, *NONE, *BKUPCY
Save access paths . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Save contents of save files . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Data compression . . . . . . . . . . . . *BKUPCY *DEV, *YES, *NO, *BKUPCY
Data compaction . . . . . . . . . . . . *BKUPCY *DEV, *NO, *BKUPCY
Target release . . . . . . . . . . . . . *BKUPCY *CURRENT, *PRV, *BKUPCY
Clear . . . . . . . . . . . . . . . . . *BKUPCY *NONE, *ALL...
Object pre-check . . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Append to media . . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
End of tape option . . . . . . . . . . . *BKUPCY *UNLOAD, *REWIND...
Journaled objects . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Use optimum block size . . . . . . . . . *BKUPCY *BKUPCY, *DEV, *YES, *NO
Text . . . . . . . . . . . . . . . . . . Backup of library ITSMLIB
More...
Figure 9-34 Backup control group attributes for TESTSAVE after change (Part 2 of 2)
6. Use this backup control group TESTSAVE for a backup of library ITSMLIB to our IBM
Tivoli Storage Manager server. Activate this save job using the Start Backup with BRMS
(STRBKUBRM) command:
STRBKUBRM CTLGRP(TESTSAVE)
In the STRBKUBRM command, we used SBMJOB(*YES) as the default value. This
means that our job will run in batch. Press Enter. Job TESTSAVE is now running on AS02.
7. In addition to job TESTSAVE, which is now running on our iSeries AS02 in subsystem
QBATCH, by default, on the IBM Tivoli Storage Manager server side (AS27 in our
example), you see a session from the IBM Tivoli Storage Manager server administration
point of view.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 281
On AS27, use the IBM Tivoli Storage Manager server Web administrative client interface
Server Command window and enter q ses. Click Submit. The session information for
AS02 and any other currently active sessions as shown in Figure 9-35.
Figure 9-35 Query sessions for save from BRMS Application Client
282 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
8. Verify that the backup on AS02 completed successfully using the following two BRMS
commands:
a. Enter the Display BRM Log Information (DSPLOGBRM) command. You see a Display
BRM Log Information display similar to the one shown in Figure 9-36.
The message “Control group TESTSAVE bypassed automatic save of media information.” is
normal, because we used the Automatically backup media information parameter with
the value *NONE (Figure 9-34 on page 281).
Press Function key 1 (help) to see the message details for the messages indicated by
the arrows. The details include time stamps. Using the time stamps, you can
approximate the time it took to complete the backup function.
b. Enter the Work with Media using BRM (WRKMEDBRM) command.
As shown in Figure 9-37, library ITSMLIB is saved with Save Type *FULL and with
Volume Serial *ADSM. This means that our backup to IBM Tivoli Storage Manager
server AS27 was successful. For additional details, you can enter option 5 (Display)
next to ITSMLIB in the Work with Media Information display (Figure 9-37).
Note: *ADSM is the old term for the IBM Tivoli Storage Manager server used in
previous releases.
You can also select option 9 (Work with saved objects) to see a different set of
additional information.
The value 0 for the File Sequence parameter is normal, because our backup target is
an IBM Tivoli Storage Manager server and no tape.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 283
Work with Media Information AS02
Position to Date . . . . .
Notice that with either the DSPLOGBRM or WRKMEDIBRM commands, we received results
information. We can gather more information using the WRKMEDIBRM command.
Later this chapter shows a restore for library ITSMLIB from IBM Tivoli Storage Manager
server using this backup, created with the backup control group TESTSAVE.
Note: We do not provide details about general OS/400 and BRMS capabilities related to
OS/400 system ASP and user-defined ASPs or save while active. However, you can
specify these capabilities using the BRMS iSeries Navigator client interface. See the
beginning of 9.3.1, “Using the 5250 interface” on page 277, for additional information about
these subjects.
Using iSeries Navigator, follow these steps to perform a backup using the backup policy
Saveifps:
1. Sign on to the iSeries server (AS20 in this example).
2. Expand My Connections-> server name (AS02)-> Backup, Recovery and Media
Services and select Backup Policies as shown in Figure 9-38.
3. In Saveifsp, we defined a save one integrated file system (IFS) path (TSMAIXCLIENT) to a
QIC tape, which is BRMS media. In this example, we modify this Saveifsp backup policy to
back up to our IBM Tivoli Storage Manager server.
Tip: We recommend that you use the BRMS iSeries Navigator client to define backups
where non-QSYS.LIB files (objects) in the IFS are saved. This is because using the
BRMS iSeries Navigator client interface makes it easy to access, select, and specify
the directory paths to back up these objects via the Browse option through IFS.
284 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Using the Backup Policies window (Figure 9-38), right-click Saveifsp and select
Properties.
4. The Saveifsp Properties window (Figure 9-39) opens. Click the During button.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 285
5. In the Properties - During Backup window (Figure 9-41), verify what you must change, if
anything, to back up the IFS objects using the Saveifsp backup policy. Complete the
following steps:
a. As shown in Figure 9-41, select Saveifsp and click the Details button for more
information.
286 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Does the backup of TMSAIXCLIENT directory include all subdirectories and files? Yes,
as shown in the Details window (Figure 9-41), the Include parameter specifies All
directories and subdirectories.
You can add and remove directories and file paths using this window.
Review your selections. Click Cancel to return without making changes or click OK to
include any changes (we are not making changes). You are back at the Saveifsp
Properties - During Backup window (Figure 9-40).
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 287
b. Is backup with the Save While Active option allowed? On this window, click Save While
Active to find out. This opens the Save While Active window shown in Figure 9-42. You
see Yes specified for Save While Active and a Save message queue.
In the windows that are not shown for this example, we selected the Saveifsp item,
which enabled the Browse Message Queues button. From the browse list, we selected
message queue Save in library QUSRBRM. See 9.6, “Save-while-active implications”
on page 325, for more information about using a message queue.
Since we added the Save message queue, click OK.
288 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
6. You return to the Saveifsp Properties - During Backup window (Figure 9-40 on page 286).
Which additional properties of the Saveifsp backup policy should we change?
In Saveifsp Properties - During Backup window, click the Where tab.
On the Where page (Figure 9-43), for the Where to back up setting, change the value from
Media (serial) to another value. In this example, we select TSM server.
Figure 9-43 Where page before changing the Where to back up parameter
As shown in Figure 9-44, several other properties automatically change to reflect this
value. Note the following values on the TSM server window:
• The TSM server name is Itsmserver.
• Under Full backups, Connection name is AS02 and Storage location is Any
location.
• Under Changes-only backups, Connection name is As02 and Storage location is
Any location.
• The Manage TSM Servers button is enabled.
The TMS server name and connection name values are those we specified during IBM
Tivoli Storage Manager server name (Itsmserver) and connection name (AS02)
definitions in 9.2.3, “Follow-on steps using iSeries Navigator” on page 269.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 289
We leave these as specified defaults, but you can change them by clicking the Manage
TSM Servers button.
Figure 9-44 Where page after changing the Where to back up parameter
Attention: Do not click the OK button on the Saveifsp Properties - During Backup
window yet. If you click OK too soon, you see the error message shown in
Figure 9-45.
c. On Saveifsp Properties - During Backup window, click the TSM Server Retention tab.
290 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
d. On the TSM Server Retention page (Figure 9-46), you see empty fields for both TSM
management class parameters. In this example, we enter BRMS for both TSM
management class parameters. This is the management class that we defined in step
3 on page 253 to define an IBM Tivoli Storage Manager management class (Figure 9-5
on page 254).
Figure 9-46 Entering the IBM Tivoli Storage Manager management class names
e. Click OK to save all your changes for the Saveifsp Properties - During Backup window.
7. You return to the main Saveifsp Properties window (Figure 9-39 on page 285). Click OK
on this window.
8. You return to the main iSeries Navigator window, which shows BRMS backup policies in
the right pane (Figure 9-38 on page 285).
Note: The BRMS iSeries Navigator client changes the Automatically backup media
information parameter to *NONE when you change a backup policy from a tape device
to an IBM Tivoli Storage Manager server. Therefore, you do not have to perform
another step as when using the 5250 interface.
For additional information, see 9.5, “Full iSeries backup and restore on the BRMS
Application Client” on page 312.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 291
9. Use the Saveifsp backup policy to back up the IFS path TSMAIXCLIENT to the IBM Tivoli
Storage Manager server. To activate this backup, in the Backup Policies window
(Figure 9-38 on page 285), right-click the Saveifsp policy and select Run Now.
10.The Run Backup Policy Saveifsp - Backup Activity Override window (lower part of
Figure 9-47) opens. You can run the policy as is or specify the overrides here. In this
example, we run the policy unchanged. Click OK.
Figure 9-47 Running the backup policy with the iSeries Navigator client interface
11.The Run Backup Policy Saveifsp - Retention Overrides window opens (not shown). Click
OK.
12.The the iSeries Navigator window opens showing your Management Central assigned
backup activity name with instructions on how to find out its task activity status (using the
next step). This means the task is running now. Click OK to return to your window showing
Backup policies.
292 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
13.In iSeries Navigator as shown in Figure 9-48, expand Management Central (As02)->
Task Activity-> Backup, Recovery and Media Services. In the panel on the right, you
see the BRMS task with a status of Started. After the backup successfully completes, you
see the status Completed.
Tip: It is possible that you may see a status of Failed (as shown in Figure 9-48 for a
previous task). Typically this is because your Management Central central system is not
correctly setup. To set up Management Central, see 7.3.1, “Installing the BRMS iSeries
Navigator client” on page 137.
Figure 9-48 Task Saveifsp with the Started status in Management Central (As02)
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 293
14.While the backup job is running in OS/400 subsystem QBATCH (by default) on system
AS02, you see the associated work happening on the IBM Tivoli Storage Manager server
(AS27 in our example) as a node session from the IBM Tivoli Storage Manager server
administration point of view.
On AS27, in the IBM Tivoli Storage Manager server Web administrative client interface
(Figure 9-49), in the Server Command window at the bottom of the page, enter:
q ses
Click Submit.
Figure 9-49 Using the q ses IBM Tivoli Storage Manager command to see the AS02 session
294 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
15.After the backup has completed (the Management Central Task Activity task status is
Completed), verify the save results for Saveifsp backup policy, which backed up IFS path
TSMAIXCLIENT and all its subdirectories and data.
There are two ways to do this. You can start both ways using the Backup, Recovery and
Media Services Tasks taskpad for system AS02, as shown in the bottom panel in
Figure 9-50. To open this window, click My Connections-> AS02-> Backup, Recovery
and Media Services.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 295
Then you can choose from one of the following ways to verify your save results:
– View backup history
i. Under Backup, Recovery and Media Services Tasks, click View backup history in
the taskpad area.
ii. The Backup History-Include window (Figure 9-51) opens. For the Policy parameter,
select Saveifsp. Depending on your environment, use the various include
parameters to include history information for all backups or use the lists to
selectively include history information to be shown. In our example, we selected to
display All information about the local system from September 4 through
September 12.
Click OK.
296 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
f. Now you see an initial level of information in a window similar to the one shown in
Figure 9-52. Under Backed Up Item, you can see summary information for Saveifsp.
This information includes the time of running (3:58:09 PM), backup type (Full), the kind
of volume (TSM Server), and the number of objects saved (124). Double-click
Saveifsp.
g. The Backup History window in the background of Figure 9-53 opens, showing the next
level of backup details of what was actually saved in the path TSMAIXCLIENT. You can
see another lower level of backup history information for each backed up item. For
example, we opened the background item /TSMAIXCLIENT to see the more detailed
history information in the Backup History window shown in the lower right foreground in
Figure 9-53.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 297
– Display backup and recovery log
The BRMS iSeries Navigator client has the capability to view the backup and recovery
log. Here is a fast way to access this backup and recovery log for our save with backup
policy Saveifsp.
i. From the Backup, Recovery and Media Services Tasks taskpad area (see
Figure 9-50 on page 295), click Display backup and recovery log.
ii. The Backup and Recovery Log - Include window opens. Enter the actual dates in
the From and To fields for the specific dates. Click OK.
iii. The Backup and Recovery Log - AS02 window (Figure 9-54) opens. This log can
contain many entries. Review the messages area to find, for example, all eight
entries associated with the Saveifsp backup. Note that, in this log, Saveifsp is
shown in uppercase, SAVEIFSP.
It is normal to see the “Brm1644 Control group SAVEIFSP bypassed automatic save
of media information.” message. This is because the BRMS iSeries Navigator
client automatically sets the Automatically backup media information parameter
value to *NONE. See step 6 on page 281 to determine which backup control group
attributes you must change. Also see 9.5, “Full iSeries backup and restore on the
BRMS Application Client” on page 312.
Click to select one of the messages for more details. In this example, we select
Cpc370d.
298 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
iv. You see the Detailed Message Information window (Figure 9-55). Review the
information and click OK.
Regardless of the method you use to verify your save, you see similar information. Our
backup for IFS path TSMAIXCLIENT with all subdirectories and files using backup policy
Saveifsp with BRMS iSeries Navigator client was successful. Keep in mind that the View
backup history method provides additional details.
Later, in 9.4.2, “Using BRMS iSeries Navigator client” on page 304, you see how to restore
parts of IFS path TSMAIXCLIENT from our IBM Tivoli Storage Manager server using this
backup, created with the Saveifsp backup policy.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 299
9.4.1 Using 5250 interface
Prior to reading this section, you must have done a backup for user library ITSMLIB to IBM
Tivoli Storage Manager server, using the backup control group TESTSAVE as described in
9.3.1, “Using the 5250 interface” on page 277. You must also have restores library ITSMLIB to
AS02 from IBM Tivoli Storage Manager server on AS27, because library ITSMLIB was
deleted but now must be used again on AS02.
We do the restore by using BRMS. There are several different ways using BRMS to perform
this restore. We prefer to use the Work with Media Information (WRKMEDIBRM) command.
To restore library ITSMLIB from the IBM Tivoli Storage Manager server on AS27 to system
AS02 perform following steps:
1. On AS02, enter the following command:
WRKMEDIBRM LIB(ITSMLIB)
2. This opens the Work with Media Information display (Figure 9-56). Position the cursor to
the most recent entry for ITSMLIB (September 9 at 18:01 in our example). Validate that
this newest entry has the following values:
– Save Type is *FULL. All objects in library ITSMLIB were backed up successfully.
– Volume Serial is *ADSM. The backup was to an IBM Tivoli Storage Manager server
and saved, which means that it was a successful backup of ITSMLIB.
Enter option 7 (Restore) next to this IBM Tivoli Storage Manager entry. Press Enter.
Note: We specify option 7 (Restore), because we want to restore the entire contents of
library ITSMLIB. Option 9 (Work with saved objects) allows you to select specific
objects of the saved ITSMLIB library to be restored.
Position to Date.. . . .
300 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
3. The Select Recovery Items display appears as shown in Figure 9-57. Note that option 1
(Select) is already entered for the ITSMLIB entry. Press Enter.
Tip: You can go directly to this Select Recovery Items display by using the Start
Recovery using BRMS (STRRCYBRM) command as shown here:
STRRCYBRM OPTION(*LIB) ACTION(*RESTORE) LIB(ITSMLIB) USEADSM(*YES)
When you use this command, option 1 (Select) is not already entered next to ITSMLIB.
Bottom
F3=Exit F5=Refresh F9=Recovery defaults F12=Cancel
F14=Submit to batch F16=Select all
Note: Several items of information and other options are available through the Work
with Media Information and the Select Recovery Items displays. When you use these
interfaces, select the various options such as Function key 1 (F1) help, and the other
function keys shown, for example on the bottom of the Select Recovery Items display.
For example, you can perform a restore function in batch mode, by using F14 (Submit
to batch).
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 301
4. The Display Recovery Items panel (outlined by “dots”) in Figure 9-58, overlays the Select
Recovery Items display. Notice the “Restoring library ITSMLIB from TSM (ADSM) device
ITSMSERVER.” message at the bottom of the display.
Important: You must wait, until the Display Recovery Items display (Figure 9-58)
changes from showing the “restoring library” message to showing the message “4
objects restored from ITSMLIB to ITSMLIB” (as shown in Figure 9-59).
Place your 5250 cursor on this message and use F1 to see message CPC3703 details.
We verify this restore of library ITSMLIB later in this section.
Position to Date . . . . .
302 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
As shown in 9.3, “Save scenario example: Saving to an IBM Tivoli Storage Manager
server” on page 277, if you are fast enough, you can use the IBM Tivoli Storage Manager
server Web administrative client interface Server Command window. In this field, you enter
q ses (query sessions) to see on the IBM Tivoli Storage Manager server (on AS27) the
status for all active IBM Tivoli Storage Manager server sessions, including this restore
function.
In Figure 9-60, contrast the Session State SendW status for restore here with the Sess
State RecW shown in Figure 9-35 on page 282 for the corresponding backup (save) of
ITSMLIB.
Figure 9-60 Query sessions for restore from BRMS Application Client
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 303
5. Verify the restore results. After the restore has completed, use the Display Object
Description (DSPOBJD) command to verify that the ITSMLIB library exists and shows the
latest time stamp of the restore:
DSPOBJD OBJ(ITSMLIB) OBJTYPE(*LIB) DETAIL(*FULL)
Scroll down to the display shown in Figure 9-61.
Save/Restore information:
Save date/time . . . . . . . . . . : 09/09/03 18:01:02
Save active date/time . . . . . . : 09/09/03 18:01:02
Restore date/time . . . . . . . . : 09/10/03 16:26:59
Save command . . . . . . . . . . . : SAVLIB
Device type . . . . . . . . . . . : Save file
Save file . . . . . . . . . . . . : QTEMP/QANE079704
304 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Each restore using BRMS iSeries Navigator client starts by selecting the Restore iSeries data
in the Backup, Recovery and Media Services Tasks taskpad area. To access this taskpad
area, click My Connections-> AS02-> Backup, Recovery and Media Services
(Figure 9-62).
To restore the entire TSMAIXCLIENT path on system AS02 from the IBM Tivoli Storage
Manager server on AS27, perform the following steps:
1. Under Backup, Recovery and Media Services Tasks, select Restore iSeries data.
2. On the Restore wizard Welcome window, read the text. Click the Help button if necessary.
Then, click Next.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 305
3. On the Restore - Restore from Backup History or Device - As02 window (Figure 9-63),
leave the default as selected and click Next.
306 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
4. On the Restore - Select Type of Information - As02 window (Figure 9-64), select A
directory or its files and click Next.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 307
5. On the Restore - Specify the Directory - As02 window (Figure 9-65), type the path name
/TSMAIXCLIENT (path name must start with /) and click Next.
6. On the Restore - Specify the Saved Version to Restore - As02 window (not shown), leave
the default (Restore the most current). Click Next.
308 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
7. On the Restore - Restore Entire Directory - As02 window (Figure 9-66), you see a
summary of all selections that were previously made and to which the backup (according
to the Date Saved and Time Saved column values) will be restored. In this example, this is
the full directory /TSMAIXCLIENT. Therefore, you select Restore directory and all files
as well as Include subdirectories. Click Next.
8. On the Restore - Restore to Same Location - As02 window, leave the default as Yes,
restore to same location. We select this option because, in our example path,
/TSMAIXCLIENT does currently not exist and we want to restore it. Click Next.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 309
9. On the Restore - Summary - As02 window (Figure 9-67), review the text, including the
option to schedule the restore for a later time (Schedule button). Optionally you can click
the Details button to see additional information. Notice that Volume needed is not
available because we are restoring from an IBM Tivoli Storage Manager server, not a
device. Click Finish to begin the restore now.
10.The next window informs you about starting a Management Central task to do the
Restore. Click OK.
11.You now return to the general iSeries Navigator window. In the left hierarchy tree pane,
select Management Central (As02)-> Task Activity-> Backup, Recovery and Media
Services. You see a task with the name Restore Items and status Started, as shown in
Figure 9-68.
310 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
12.During the restore, you can use the IBM Tivoli Storage Manager Web Administrative client
interface to the IBM Tivoli Storage Manager server system (AS27) to see the session
status with system AS02. As discussed in similar “in progress” situations earlier in this
book, you can see this session and all other active sessions by entering the q ses
command in the Server Command window of the browser interface. See session number
743 in Figure 9-69.
After Restore is completed, the task status in Management Central (As02) changed from
Started (see again Figure 9-68) to Completed.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 311
13.There are several ways to validate a successful restore of the TSMAIXCLIENT path. As an
example, we use the following two steps. If you see the path (directory/folder)
TSMAIXCLIENT by using the As02 iSeries Navigator Integrated File System function, we
know the restore was successful:
a. On the main iSeries Navigator window, expand My Connections-> As02-> File
Systems-> Integrated File System. Select the Root directory.
Using the right pane, you can see a list of all directories and files in Root. You can see
folder/directory TSMAIXCLIENT, as shown in Figure 9-70.
Note the new restore date (11 September) under the Changed column. As it should be, this
date is different from the Date Saved entry (09 September 2003) in Figure 9-66 on page 309.
We have now explained how to set up the BRMS Application Client to an IBM Tivoli Storage
Manager server. We also included some save and restore scenarios. With the powerful
functions in iSeries BRMS and IBM Tivoli Storage Manager server and client products, there
are many more capabilities and ways to accomplish them. We cannot provide complete
coverage of these methods. However, for an iSeries system recovery situation, you must
understand the important considerations for recovering both user data and system data,
when using both BRMS and IBM Tivoli Storage Manager server functions on that system.
312 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
9.5.1 Full backup for system AS02
In our network, we use iSeries server AS02 as the BRMS Application Client to our IBM Tivoli
Storage Manager server on iSeries server AS27. AS02 itself has no connected tape libraries,
but it has its required (on all iSeries servers) an internal tape drive for media using a
Quarter-inch Cartridge (QIC) tape device and its media. On selective 810 systems, this can
be an internal VXA-2 tape device and its media. Using the internally attached VXA-2 80GB
internal tape drive is a recent capability. This section uses the QIC tape device that has been
available for several years.
For the backups to an IBM Tivoli Storage Manager server, our defined environment uses:
Media policy ITSM
Device ITSMSERVER
Location ITSMSERVER
Prior to reading this section, you must be familiar with the information presented in this
chapter up to this point. You should especially know the information in 9.2, “Setting up the
BRMS environment for backup and restore to an IBM Tivoli Storage Manager server” on
page 261.
Objects not allowed: These are objects that OS/400 does not allow to be backed up to an
IBM Tivoli Storage Manager server. You cannot save iSeries system data to an IBM Tivoli
Storage Manager server. Any user data that you can save to a save file, you can save to
an IBM Tivoli Storage Manager server, except user data that is required to restore OS/400
to a base operating level. This includes:
OS/400 security data
iSeries configuration data
IBM-supplied libraries and licensed program products: IBM-supplied libraries are
considered this class of “user data” including QGPL, QUSRSYS, QUSRBRM, and
BRMS media information.
Because backup of the specific IBM objects to an IBM Tivoli Storage Manager server is not
allowed, we omit four libraries (QGPL, QSYS2, QUSRBRM, and QUSRSYS) from save type
*ALLUSR using the 5250 command interface:
GO BRMBKUPCY
On this display, you select option 2 (Work with Items to Omit from Backup). This opens the
Work with Items to Omit from Backup display (Figure 9-71).
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 313
Work with Items to Omit from Backup AS02
*ALLUSR QGPL
*ALLUSR QSYS2
*ALLUSR QUSRBRM
*ALLUSR QUSRSYS
When you back up to an IBM Tivoli Storage Manager server, for each of the items listed, enter
option 1 (Add). This adds the backup item to the omit backup item list. You can use F1 for
online help in understanding this window.
If you forget to omit any one of these items, you see the BRMS message BRM2228 or
BRM2250 when trying to perform a backup to an IBM Tivoli Storage Manager server of one of
these not allowed objects.
In addition to the libraries QGPL, QSYS2, QUSRBRM, and QUSRSYS that are not allowed,
there are OS/400-provided control group entries *SAVSYS, *SAVCFG, *SAVSECDTA, and
*IBM that cannot be saved to an IBM Tivoli Storage Manager server.
We set up to save the entire AS02 system with five BRMS backup control groups:
ITSMSAVE1
ITSMSAVE2
ITSMSVFRI1
ITSMSVFRI2
SAVSYSPLUS
Figure 9-72 shows these backup control groups along with others on our AS02 system.
314 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Work with Backup Control Groups AS02
We created two backup control groups ITSMSAVE1 and ITSMSAVE2 from the backup control
group ITSMSAVE (see 9.6, “Save-while-active implications” on page 325), because we run
backups ITSMSAVE1 and ITSMSAVE2 as concurrent saves for a best performance. See 9.8,
“Performance expectations” on page 329.
We also created backup control groups ITSMSVFRI1 (based upon ITSMSAVE1) and
ITSMSVFRI2 (based upon ITSMSAVE2). These control groups have similar content but
require different parameter values. ITSMSVFRI1 and ITSMSVFRI2 run only on Friday, and
they do not use the save-while-active function. ITSMSAVE1 and ITSMSAVE2 both specify
Save While Active.
In our local backup control group - SAVSYSPLUS, we include backing up the four *ALLUSR
libraries (QGPL, QSYS2, QUSRBRM, and QUSRSYS) that we omitted earlier from our
backup policy (Figure 9-71). In the Work with Backup Control Groups display (Figure 9-72)
enter option 5 (Display) next to control group SAVSYSPLUS. Then you see the details of the
Edit Backup Control Group Entries display (Figure 9-73).
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 315
Edit Backup Control Group Entries AS02
Group . . . . . . . . . . : SAVSYSPLUS
Default activity . . . . . *BKUPCY
Text . . . . . . . . . . . Backup SYSDATA and NON-ITSM / with IPL
10 *EXIT *DFTACT
20 *SAVSYS *DFTACT
30 *IBM *DFTACT *NO *NO
40 QGPL *SYSBAS *DFTACT *YES *NO
50 QUSRSYS *SYSBAS *DFTACT *YES *NO
60 QUSRBRM *SYSBAS *DFTACT *YES *NO
70 QSYS2 *SYSBAS *DFTACT *YES *NO
80 *EXIT *DFTACT
See the detailed entries for backup control groups ITSMSAVE1 and ITSMSAVE2 in
Figure 9-74 and Figure 9-75.
For the SWA Message Queue parameter, note the SAVE entry. SAVE is a message queue
that we created in library QUSRBRM for all messages regarding checkpoint processes during
save-while-active backup activities. The first entry *EXIT in ITSMSAVE1 clears this message
queue for upcoming new backups.
You can read more about the save-while-active function for an iSeries as it applies to the
BRMS Application Client to an IBM Tivoli Storage Manager server in 9.6, “Save-while-active
implications” on page 325.
Group . . . . . . . . . . : ITSMSAVE1
Default activity . . . . . *BKUPCY
Text . . . . . . . . . . . Backs up all userdata to ITSM without *LINK
10 *EXIT *DFTACT
20 *ALLUSR *SYSBAS *DFTACT *YES *YES SAVE
30 SAVSPL *SPL *DFTACT
40 *ALLDLO *DFTACT *NO *NO
50 *EXIT *DFTACT
316 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Display Backup Control Group Entries AS02
Group . . . . . . . . . . : ITSMSAVE2
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backup *LINK to ITSM
Our backup control groups ITSMSVFRI1 and ITSMSVFRI2 have the values as shown in
Figure 9-76 and Figure 9-77.
Group . . . . . . . . . . : ITSMSVFRI1
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backup all userdata to ITSM without *LINK
Group . . . . . . . . . . : ITSMSVFRI2
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backup *LINK to ITSM
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 317
Details of the backup control group for ITSMSAVE1 are shown in Figure 9-78 and
Figure 9-79. Notice that they are the same for ITSMSAVE2, ITSMSVFRI1, and ITSMSVFRI2.
Group . . . . . . . . . . . . . . . . : ITSMSAVE1
More..
F3=Exit F4=Prompt F12=Cancel
Figure 9-78 Attributes ITSMSAVE1 same for ITSMSAVE2, ITSMSVFRI1, ITSMSVFRI2 (Part 1)
Group . . . . . . . . . . . . . . . . : ITSMSAVE1
Automatically backup
media information . . . . . . . . . *NONE *LIB, *OBJ, *NONE, *BKUPCY
Save access paths . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Save contents of save files . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Data compression . . . . . . . . . . . . *BKUPCY *DEV, *YES, *NO, *BKUPCY
Data compaction . . . . . . . . . . . . *BKUPCY *DEV, *NO, *BKUPCY
Target release . . . . . . . . . . . . . *BKUPCY *CURRENT, *PRV, *BKUPCY
Clear . . . . . . . . . . . . . . . . . *BKUPCY *NONE, *ALL...
Object pre-check . . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Append to media . . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
End of tape option . . . . . . . . . . . *BKUPCY *UNLOAD, *REWIND...
Journaled objects . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Use optimum block size . . . . . . . . . *BKUPCY *BKUPCY, *DEV, *YES, *NO
Text . . . . . . . . . . . . . . . . . . Backs up all userdata to ITSM without *LINK
Figure 9-79 Attributes for ITSMSAVE1 same for ITSMSAVE2, ITSMSVFRI1, and ITSMSVFRI2 (Part 2)
318 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 9-80 and Figure 9-81 show the details of the backup control group for SAVSYSPLUS.
Group . . . . . . . . . . . . . . . . : SAVSYSPLUS
More...
Group . . . . . . . . . . . . . . . . : SAVSYSPLUS
Automatically backup
media information . . . . . . . . . *OBJ *LIB, *OBJ, *NONE, *BKUPCY
Save access paths . . . . . . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Save contents of save files . . . . . . *BKUPCY *YES, *NO, *BKUPCY
Data compression . . . . . . . . . . . . *BKUPCY *DEV, *YES, *NO, *BKUPCY
Data compaction . . . . . . . . . . . . *BKUPCY *DEV, *NO, *BKUPCY
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 319
Saving backup media information: Run backup control group SAVSYSPLUS after
ITSMSAVE2 and ITSMSVFRI2. This is because, in ITSMSAVE2 and ITSMSVFRI2, the
Automatically backup media information parameter has to be *NONE (for example, as
shown in Figure 9-79). Backup of BRMS media information (its detailed information to
perform a complete iSeries recovery, if necessary) to an IBM Tivoli Storage Manager
server is not allowed. See the “Objects not allowed” note box on page 313 for other objects
that are not allowed when backing up to an IBM Tivoli Storage Manager server.
In the SAVSYSPLUS backup control group, the Automatically backup media information
parameter specifies *OBJ as shown in Figure 9-81. This means “save object level details
necessary for recovery”. Since SAVSYSPLUS saves to tape media on the local system,
BRMS media information (contained within BRMS OS/400 database files) is backed up.
For a total system recovery, you need the latest version of BRMS media information. There
are two options to accomplish this in our example:
SAVSYSPLUS runs after ITSMSAVE2 and ITSMSVFRI2.
Use the Save Media with BRMS (SAVMEDBRM) command after ITSMSAVE2 and
ITSMSVFRI2 are completed. This command saves the latest version of media
information to a local tape, which in our case is to a QIC tape.
The object detail recovery information is stored in BRMS database files in library
QUSRBRM, such as QAO1AOB, QAO1AOD, QAO1AMB, QAO1ADI1, QAO1ADI2, and so
on. See Backup Recovery and Media Services for iSeries, SC41-5345, for more
information.
320 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
In both backup cases, we run BRMS maintenance using the Start Maintenance for BRMS
(STRMNTBRM) command at 1:30 the next day, for each Monday through Thursday
ITSMSAVE1 and ITSMSAVE2, and Friday ITSMSVFRI1 and ITSMSVFRI2 backup. For
example, STRMNTBRM runs at 01:30 on Tuesday, following the Monday ITSMSAVE1 and
ITSMSAVE2 backup, and on Saturday at 01:30 following the Friday ITSMSVFRI1 and
ITSMSVFRI2 backup.
Next
-----Schedule------ Recovery Submit
Opt Job Status Date Time Frequency Action Date
ITSMSAVE1 SCD USER DEF 19:00:00 *WEEKLY *SBMRLS 09/09/03
ITSMSAVE2 SCD USER DEF 19:05:00 *WEEKLY *SBMRLS 09/09/03
SAVMEDIBRM SCD USER DEF 23:00:00 *WEEKLY *SBMRLS 09/09/03
STRMNTBRM SCD USER DEF 01:30:00 *WEEKLY *SBMRLS 09/10/03
ITSMSVFRI1 SCD *FRI 19:00:00 *WEEKLY *SBMRLS 09/12/03
ITSMSVFRI2 SCD *FRI 19:05:00 *WEEKLY *SBMRLS 09/12/03
SAVSYSPLUS SCD *FRI 23:00:00 *WEEKLY *SBMRLS 09/12/03
Bottom
Figure 9-82 Job schedule entries for system AS02 backups using BRMS backup control groups
Figure 9-83 Details for scheduled job ITSMSAVE1, same for ITSMSAVE2 with time 19:05
Figure 9-84 Details for scheduled job ITSMSVFRI1, same for ITSMSVFRI2 with time 19:05
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 321
Job name . . . . . . . . . . . . > SAVSYSPLUS Name
Entry number . . . . . . . . . . > 001732 000001-999999, *ONLY
Command to run . . . . . . . . . STRBKUBRM CTLGRP(SAVSYSPLUS) SBMJOB(*CONSOLE)
For recovery purposes, it is mandatory to print and have accessible BRMS maintenance
reports for system AS02. For example, the QP1ARCY file name report is placed on output
queue (OUTQ) QUSRSYS/BRMS on system AS02. In our network, this spooled output
queue is defined as a remote OUTQ that is directed to system AS27 output queue
QUSRSYS/BRMS. See Figure 9-86 for the definition of the remote output queue.
In our network, we verified that system AS27 is available daily around 2:00 to receive our
spooled files from AS02. On AS02, the output queue QUSRSYS/BRMS is defined as the
default OUTQ for user profile EDELGARDS.
All job scheduler entries were added using the user profile EDELGARDS. Therefore, all
spooled file output, when the associated jobs run, normally goes to output queue
QUSRSYS/BRMS on AS02, which is defined as a remote output queue to AS27.
To direct the spooled files to system AS27 and keep them available on AS02, we change the
printer files attributes to specify SAVE(*YES), as shown in the Change Print File command:
CHGPRTF FILE(QBRM/*ALL) SAVE(*YES)
Important:
You must run this command again after a BRMS release upgrade as the upgrade
resets SAVE to *NO for these and other IBM-supplied print files.
As documented in 2.8, “Full system recovery” on page 30, we recommend that you
have the BRMS recovery reports, such as QP1ARCY, in two separate locations, one
local and one off site, for disaster recovery purposes.
322 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Work with Output Queue Description Page 1
5722SS1 V5R2M0 020719 AS02 09/08/03 11:56:00
Queue: BRMS Library: QUSRSYS
Status:
Writer active . . . . . . . . . . . : Y
Writer name(s) if active . . . . . . : BRMS
Output queue held . . . . . . . . . : N
Maximum spooled file size:
Number of pages . . . . . . . . . . : *NONE
Starting time . . . . . . . . . . . :
Ending time . . . . . . . . . . . . :
Writers to autostart . . . . . . . . . : 1
Display any file . . . . . . . . . . . : *NO
Job separators . . . . . . . . . . . . : 0
Operator controlled . . . . . . . . . : *YES
Order of files on queue . . . . . . . : *FIFO
Data queue . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . :
Authority to check . . . . . . . . . . : *OWNER
Remote system . . . . . . . . . . . . : *INTNETADR
Remote printer queue . . . . . . . . . : QUSRSYS/BRMS
Queue for writer messages . . . . . . : QSYSOPR
Library . . . . . . . . . . . . . . : *LIBL
Connection type . . . . . . . . . . . : *IP
Internet address . . . . . . . . . . . : x.x.x.x
Destination type . . . . . . . . . . . : *OS400
VM/MVS class . . . . . . . . . . . . . :
FCB . . . . . . . . . . . . . . . . . :
Host print transform . . . . . . . . . : *NO
User data transform . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . :
Manufacturer type and model . . . . . :
Workstation customizing object . . . . :
Library . . . . . . . . . . . . . . :
Image configuration . . . . . . . . . : *NONE
Destination options . . . . . . . . . : *NONE
Print separator page . . . . . . . . . : *NO
User defined option . . . . . . . . . : *NONE
User defined object:
Object . . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . :
Object type . . . . . . . . . . . . :
User driver program . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . :
Spooled file ASP . . . . . . . . . . . : *SYSTEM
Text description . . . . . . . . . . . : outq for brms
* * * * * E N D O F L I S T I N G * * * * *
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 323
b. Place the media with active data into a safe place together with recovery report.
Friday on the system console
Start the BRMS console monitor.
Monday through Friday reports and backup process
a. Verify the reports during BRMS maintenance created on AS02 and verify. The reports
are on AS27 as well. Print the recovery report.
b. Look for objects that should be saved but were not. Use the DSPLOGBRM and Display
Job Log (DSPJOBLOG) (for the BRMS jobs) commands to do this.
c. If a backup job ended abnormally or objects were not backed up, take action
immediately to prevent this from continuing to happen. Change your backup strategy or
processes, if necessary.
d. Review the Save While Active message queue QUSRBRM/SAVE for important
messages and take the appropriate action as soon as possible.
In our example backup scenario on Monday morning, this message queue is empty,
because there were no save-while-active backups on the previous Friday or Saturday.
From the BRMS view, this restore is a normal full system recovery just as it would be on other
iSeries with BRMS not running as the BRMS Application Client to an IBM Tivoli Storage
Manager server. You must have the recovery report and medias used from your latest backup
available.
As mentioned previously, for a full system recovery, you need an actual save of BRMS media
information. You did this either using our example backup control group SAVSYSPLUS or by
using the SAVMEDIBRM command. See the “Saving backup media information” box
immediately preceding “Full backup job scheduling considerations” on page 320.
Tip: Your recovery report (for example created during BRMS maintenance as spooled file
QP1ARCY) shows the latest saved media information under “STEP: Recover BRMS related
media information”. Consider these examples:
If you use automatically backup media information from SAVSYSPLUS:
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
QUSRBRM *QBRM *SYSBAS 00001 8/22/03 17:51:50 18 129 SAVSYSPLUS BRM002
For a complete recovery report example for system AS02, see “Full system recovery report
to tape” on page 376.
For a full restore of system AS02, we must have our recovery report and one QIC media
BRM00x or two QIC medias BRM00x from the latest backup.
324 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
We need one QIC media BRM00x, if our restore case is on Saturday. This is because we
have our full system backup from Friday.
We need two QIC media BRM00x and BRM00y, if our restore case is from our Monday
through Thursday backups. For example, we have the backup media for Wednesday, because
then we have our full system backup from the Friday before on one BRM00x and our latest
SAVMEDIBRM data on BRM00y.
Important: For complete system recovery of system AS02, we must follow exactly the
steps in our recovery report. This report is one of the most outstanding aspects of the
BRMS product. This is important regardless of whether BRMS backed up exclusively to
attached tape media or ran as the BRMS Application Client to an IBM Tivoli Storage
Manager server.
When backing up as the BRMS Application Client, before we perform the recover
additional user libraries step, we must ensure that our connection to the backed up to IBM
Tivoli Storage Manager server system AS27 is up and running. This is because, beginning
with this step, our restore process must contact the IBM Tivoli Storage Manager server to
gather data from it.
In summary, because we do not have messages about the end of library synchronization,
the monitoring of these messages provides no additional value.
Although save-while-active *SYNCLIB is not supported, Save While Active without *SYNCLIB
is supported for the BRMS Application Client to an IBM Tivoli Storage Manager server.
Remember that Save While Active for non-library IFS objects in this IBM Tivoli Storage
Manager environment is supported.
Messages about checkpoint processing of the detail backup items are sent to message
queue QUSRBRM/SAVE. Because we want to have only actual messages for the latest
backup in this message queue, we define in item sequence number 10 *EXIT CLRMSGQ
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 325
QUSRBRM/SAVE. This enables our message queue to be cleared before a backup starts
running, so it contains only new messages when viewed. For related information, see 9.5.1,
“Full backup for system AS02” on page 313.
Group . . . . . . . . . . : ITSMSAVE
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Backs up all allowed userdata to ITSM
During backup, or after they have completed, we can use the DSPMSG command for
MSGQ(QUSRBRM/SAVE) to verify checkpoint processing messages. Figure 9-88 shows an
example.
Display Messages
System: AS02
Queue . . . . . : SAVE Program . . . . : *DSPMSG
Library . . . : QUSRBRM Library . . . :
Severity . . . : 00 Delivery . . . : *HOLD
326 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 9-89 and Figure 9-90 show message details for the messages in bold in Figure 9-88.
You can view these details by positioning the 5250 cursor to the message and pressing F1.
This completes our coverage of full system backup (save) and recovery (restore) when using
the BRMS Application Client to an IBM Tivoli Storage Manager server.
In our test environment, we start with the default IBM Tivoli Storage Manager password
expiration value of 90 days on our IBM Tivoli Storage Manager server on system AS27. See
Figure 9-10 on page 259 for the password-related IBM Tivoli Storage Manager server values.
Perform the following actions to enable this function in the BRMS Application Client. These
steps describe an interim solution until the function can be more fully integrated into the
end-user interface.
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 327
1. Create a source physical file named QA1AGENPWD in the QUSRBRM library with a
member named NODENAMES, using the command:
CRTSRCPF FILE(QUSRBRM/QA1AGENPWD) RCDLEN(92) MBR(NODENAMES)
2. Change the owner of file QUSRBRM/QA1AGENPWD to user profile QBRMS using the
command:
CHGOBJOWN OBJ(QUSRBRM/QA1AGENPWD) OBJTYPE(*FILE) NEWOWN(QBRMS)
3. Revoke any current public authorities to file QUSRBRM/QA1AGENPWD using the
command:
RVKOBJAUT OBJ(QUSRBRM/QA1AGENPWD) OBJTYPE(*FILE) USER(*PUBLIC) AUT(*ALL)
4. Grant *USE public authority to file QUSRBRM/QA1AGENPWD using the command:
GRTOBJAUT OBJ(QUSRBRM/QA1AGENPWD) OBJTYPE(*FILE) USER(*PUBLIC) AUT(*USE)
5. Use the OS/400 STRPDM command and edit member NODENAMES. Add an entry for a
node name that you want enabled for PASSWORDACCESS GENERATE. In our example,
this is system AS02. The inserted node name must follow these rules as shown in
Figure 9-91:
– The node name must match the node name used in the media policy. In our case, this
is media policy IBM Tivoli Storage Manager, as shown in Figure 9-19 on page 267.
– Left justify the node name in the record.
– Use uppercase when you enter the node name.
Figure 9-91 QUSRBRM/QA1AGENPWD file with one entry AS02 in member NODENAMES
If the node name is found, BRMS submits the PASSWORDACCESS GENERATE client option
when it starts the session with the IBM Tivoli Storage Manager server. The automatic
password management is under the control of the IBM Tivoli Storage Manager APIs and the
IBM Tivoli Storage Manager server. BRMS does not manage the passwords when the
PASSWORDACCESS GENERATE client option is used.
The IBM Tivoli Storage Manager created passwords are stored in the /etc/adsm/TSM.PWD
file. To simplify recovery, make sure this file is backed up regularly to tape media and not to
IBM Tivoli Storage Manager server. In our example, we back up this file to a QIC tape, which
is an expired BRMS media, in drive TAP02 at system AS02 and not to IBM Tivoli Storage
Manager server AS27.
328 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 9-92 shows what you see if you use OS/400 command Work with Links (WRKLNK)
command and enter option 5 to display file TSM.PWD.
Browse : /etc/adsm/TSM.PWD
Record : 1 of 2 by 18 Column : 1 70 by 131
Control :
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+...
.
************Beginning of data**********************************************************
This file contains an encrypted TSM password, do not change or delete.
Õ NULLDSMSERVAS02AS02ª÷ä6eªÄ
************End of Data****************************************************************
This section documents some OS/400 partition-to-partition test results. However, it does not
address the complete set of possible LAN network topology configuration and various IBM
Tivoli Storage Manager Backup-Archive Clients. It is clear that the topology of an actual LAN
network (bridges, routers, LAN traffic congestion while saving or restoring, and other server
and client activities) greatly affects throughput when saving or restoring. While writing this
redbook, we focused on iSeries LPAR partition-to-partition scenarios using the iSeries virtual
LAN between partitions. We also had discussions with developers who work on BRMS and
the IBM Tivoli Storage Manager server on iSeries.
Based on that experience, consider the following statements. Then see the examples of our
iSeries partition-to-partition virtual LAN scenarios:
Extensive performance testing of IBM Tivoli Storage Manager server V5.2 under OS/400
PASE was underway. Some results were becoming available. In those available test
results, in general, using similar processing power series and iSeries servers, the AIX and
OS/400 PASE IBM Tivoli Storage Manager servers achieved similar throughput.
Test results showing that the iSeries BRMS Application Client to an AIX IBM Tivoli Storage
Manager server is completed are available from the following Web site:
http://www-1.ibm.com/servers/eserver/iseries/service/brms/adsmperf.htm
First we give some general performance-related tips, followed by our test results:
TCP/IP configuration and statements
a. We used the 1 Gbps Virtual Ethernet LAN between the two partitions. This eliminated
any network “noise” or bridge or router limitations. We used very large IP buffers
between partitions. On a physical LAN, if possible, you should use the 1 Gbps capacity
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 329
and the large buffers, assuming you network topology and hardware (switches and
routers) supports these capacities. We discuss the buffer size in a following tip.
b. Determine the maximum network performance.
We used basic file-to-file FTP in both directions between the IBM Tivoli Storage
Manager server partition (AS01) and the BRMS Application Client partition (AS01C) to
determine maximum throughput. Do this in your physical LAN environment with the
actual files you want backed up.
Partition to partition, our FTP test results were between 35 GB/hr and 36 GB/hr
independent of direction.
c. Use the iSeries TCP/IP performance tips as documented in Chapter 5 in the iSeries
Performance Capabilities Reference Guide, available on the Web at:
http://www-1.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm
BRMS Application Client environment
The following tuning was made on both the iSeries IBM Tivoli Storage Manager server and
BRMS Application Client partitions.
– Buffer Size in BRMS Net Device
We recommend that you use 512 (KBPS) for Buffer Size when defining the BRMS Net
Device. Use the WRKDEVBRM command and select option 5 (Display) to verify this for
our device ITSMSERVER, as shown in Figure 9-93.
Net Device Buffer Size: This parameter specifies the buffer size in KB for the
device. This buffer size allows you to control the amount of storage that is allocated
by the IBM Tivoli Storage Manager (ADSM) Application Client APIs for server
communication and data exchange. The maximum value is 512 KB.
Location . . . . . . . . . . . . : ITSMSERVER
330 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
CRTDTAARA DTAARA(QUSRBRM/Q1ATSMSIZE) TYPE(*CHAR) LEN(8)
CHGDTAARA DTAARA(QUSRBRM/Q1ATSMSIZE (1 8)) VALUE('000xxxxx')
The size (VALUE parameter) is in MB. In our test scenario, we created this data area at
system AS01C as shown in Figure 9-94. The VALUE parameter value should be the
size of largest IFS backup. If you are saving your IFS user data with *LINK, then this
value must be the total size of your IFS user data.
The IBM Tivoli Storage Manager server uses this value to estimate space for this
backup, normally in the BACKUPPOOL disk pool. Note that, on the iSeries IBM Tivoli
Storage Manager server side, our backup goes directly to tape using the BACKUPLTO
pool, if our BACKUPPOOL is not large enough.
For more details about these IBM Tivoli Storage Manager definitions, see 6.3, “IBM
Tivoli Storage Manager advanced storage” on page 105.
In our test scenario, we determined the right size for the VALUE parameter in two
steps:
i. Determine the current size of IFS user data to be backed up. In our environment, it
was 12.2 GB. Use the Retrieve Disk Information (RTVDSKINF) command and then
run the Print Disk Information command against the RTVDSKINF collected data:
PRTDSKINF RPTTYPE(*OBJ) OBJ(*ALL) OBJTYPE(*DIR)
ii. Estimate the future total size of IFS user data. In our environment, this is 15 GB.
We used 15360 MB (15 GB) as the value for the Value parameter as shown in
Figure 9-94.
Value
Offset *...+....1....+....2....+....3....+....4....+....5
0 '00015360'
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 331
iSeries IBM Tivoli Storage Manager server for OS/400 PASE performance
Performance for backup and restore operations on each IBM Tivoli Storage Manager client
(including the BRMS Application Client) also depends on IBM Tivoli Storage Manager
server performance capabilities. Because of this, you need must apply PTF MF30245 on
your iSeries IBM Tivoli Storage Manager server and set an associated storage pool
attribute. You can learn more about this PTF and storage pool attribute in 6.3.8, “IBM Tivoli
Storage Manager disk storage pool performance improvements” on page 112.
We implemented all of these performance enhancement tips in our test scenarios.
Tip: We used BRMS logging activity to determine our start and end backup times to
achieve our throughput rates. On the BRMS Application Client partition or system, we
used the WRKLNK command to browse the /tmp/brms/performance file. See the bold
file entries shown in Figure 9-95.
332 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
09/11/03 13:38 017897 E q1aOL Q1ARBK()-Start of processing for control group ITSMIFS
09/11/03 13:38 017897 E q1aOL Q1ARBK()-Start of pre-processing.
09/11/03 13:38 017897 E q1aOL Q1ARBK()-Start save of *LINK *ALLAVL
09/11/03 14:02 017897 E q1aOL QaneSava()-TSM transfer rate : 28.0080 gigabytes/hour
09/11/03 14:02 017897 E q1aOL Q1AXSAV()-Start of output file processing.
09/11/03 14:02 017897 E q1aOL Q1AXSAV()-Processed 0000019997 records.
09/11/03 14:02 017897 E q1aOL Q1AXSAV()-End of output file processing.
09/11/03 14:02 017897 E q1aOL Q1ARBK()-Start of post-processing.
09/11/03 14:02 017897 E q1aOL Q1ARBK()-End of processing for control group ITSMIFS
========================================================================================
09/12/03 17:29 017999 E q1aOL Q1ARBK()-Start of processing for control group LIBS
09/12/03 17:29 017999 E q1aOL Q1ARBK()-Start of pre-processing.
09/12/03 17:29 017999 E q1aOL Q1ARBK()-Start save of DUPAH11 *SYSBAS
09/12/03 17:30 017999 E q1aOL QaneSava()-TSM transfer rate : 30.6753 gigabytes/hour
09/12/03 17:30 017999 E q1aOL Q1ARSTHS()-Start of output file processing.
09/12/03 17:30 017999 E q1aOL Q1ARSTHS()-End of output file processing.
09/12/03 17:30 017999 E q1aOL Q1ARBK()-Start of post-processing.
09/12/03 17:30 017999 E q1aOL Q1ARBK()-End of processing for control group LIBS
========================================================================================
09/12/03 17:43 017975 E q1aOL QaneRsta()-TSM transfer rate : 17.3827 gigabytes/hour
========================================================================================
09/12/03 17:51 018000 E q1aOL QaneRsta()-TSM transfer rate : 17.3827 gigabytes/hour
Watch for more complete performance test results on the Tivoli Storage Manager Web site:
http://www-3.ibm.com/software/tivoli/products/
Chapter 9. Setting up an iSeries server as the Backup Recovery and Media Services Application Client 333
334 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Part 4
This part provides details about the following topics regarding Backup Recovery and Media
Services (BRMS) and IBM Tivoli Storage Manager integration:
Sharing of devices and media resources
Backup Recovery and Media Services troubleshooting and tips
IBM Tivoli Storage Manager troubleshooting and tips
The process is simple. Each day, these OS/400 programs check with the IBM Tivoli Storage
Manager server to see if there are any IBM Tivoli Storage Manager tapes to be moved off site
or on site. If there are any IBM Tivoli Storage Manager tapes to be moved off site, then a
BRMS move policy is assigned to them and the volume location is set to OFFSITE within IBM
Tivoli Storage Manager. Since these tapes now have a BRMS move policy attached to them,
you can eject them from a tape library and move them off site like any normal BRMS save.
If there are IBM Tivoli Storage Manager tapes to be moved on site, then you update and
delete the tapes in IBM Tivoli Storage Manager. BRMS sees all IBM Tivoli Storage Manager
tapes with an expiration date of *PERM. When theses volumes are removed from IBM Tivoli
Storage Manager, this automatically expires the media in BRMS. Now theses tapes are
expired in BRMS, so you use the normal BRMS media movement to recall the tapes and
bring them back on site.
This chapter provides an example of how to control IBM Tivoli Storage Manager movement of
media using a backup BRMS. The movement is based on sample interface programs that are
not supported by IBM. This chapter shows how you can simplify media movement by
integrating the movement of IBM Tivoli Storage Manager media through BRMS when both
products are installed on the same iSeries server. Several customers are using programs
successfully that are similar to the sample programs described here.
Important: The sample interface programs provided in this redbook are not supported by
IBM and are intended only to show how you can simplify media movement when both
BRMS and IBM Tivoli Storage Manager are installed on the same iSeries server. You can
download the sample source code as explained in Appendix D, “Additional material” on
page 411.
338 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
– TSMCPYOFF: Checks for IBM Tivoli Storage Manager Copypool tapes to be sent off
site
– TSMVOLON: Checks for any expired IBM Tivoli Storage Manager tapes to be moved
on site
– MOVMEDTSM: Runs the BRMS MOVMEDBRM command for all IBM Tivoli Storage
Manager tapes
You can find the sample source code of these commands in “Sample code for the
STRMNTTSM command and programs” on page 404. Compile and place these
commands in a user library. In our example, we placed these commands in library
TSMEXITS. This is the same library that was used for the tape library exit programs in
6.2.2, “Creating IBM Tivoli Storage Manager and BRMS exit programs” on page 98.
To compile the source code for these programs, you must create a temporary work
physical file named TSMTAPE. You can delete this file after the programs are compiled. If
you compile the programs interactively, then create the file in QTEMP using the command:
CRTPF FILE(QTEMP/TSMTAPE) RCDLEN(133)
Chapter 10. Backup Recovery and Media Services movement of IBM Tivoli Storage Manager media 339
3. On the Create Move Policy display (Figure 10-3), enter the values for Home location,
Verify moves, Location, and Duration.
The Home location is the location that you want the IBM Tivoli Storage Manager media
returned to when the tape expires. In our example, we specified *ORIGIN which, returns
the media to the same location it was moved from.
The Verify moves parameter is used if you want to check which tapes are to be moved off
site before you actually move them. We left the default value of *YES.
For Location and Duration, enter a sequence number for the location that your media will
move to and the duration (how long the tapes will remain off site). We used BRMS location
TSMOFFSITE for our location entry and *EXP for the duration. Since all IBM Tivoli
Storage Manager media has an expiration date of *PERM, the value *EXP ensures that
our IBM Tivoli Storage Manager tapes remain off site until they are expired. At that point,
BRMS then asks for them to be returned on site.
Leave all other fields with their default values. Press Enter to store the policy values and
then Enter again create the BRMS move policy.
Before you run the STRMNTTSM command, you can check the current status of the IBM
Tivoli Storage Manager media. The following examples shows how to see which IBM Tivoli
Storage Manager volumes are moved when you run the STRMNTTSM command. This
section is intended for informational purposes only since the STRMNTTSM command does
this work for us.
340 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
IBM Tivoli Storage Manager database backups
You can enter the query volhist command in the IBM Tivoli Storage Manager Web
administrative client interface Server Command window to see all IBM Tivoli Storage
Manager database backups. In our example, we entered the following command:
query volhist type=dbb
Figure 10-4 shows the status of two IBM Tivoli Storage Manager database backups.
LB0354 has a Volume Location set to OFFSITE and LB0705 has a blank Volume Location.
From this panel, you can see that volume LB0705 is ready to be moved to the disaster
recovery location.
IBM Tivoli Storage Manager copypool tapes ready to be moved off site
To see the status of all copy storage pool volumes ready to be moved off site, you can use
the query volume command in the IBM Tivoli Storage Manager Web administrative client
interface Server Command window. We entered the following command:
query volume stg=copylto access=READW,READO
Here copylto is the name of our copy storage pool defined in 6.3.7, “Creating a copy
storage pool” on page 111. Figure 10-5 shows copypool volume LB0702. This is the only
copy storage pool volume on site. It is ready to be moved off site.
Chapter 10. Backup Recovery and Media Services movement of IBM Tivoli Storage Manager media 341
Figure 10-5 Web administrative client interface: Querying volume on site
IBM Tivoli Storage Manager expired copypool tapes ready to be moved back on site
To see the status of all copy storage pool volumes ready to be moved back on site, you
can enter the query volume command again in the IBM Tivoli Storage Manager Web
administrative client interface Server Command window. We entered the following
command:
query volume stg=copylto access=OFFSITE status=empty
Again, copylto is the name of our copy storage pool defined in 6.3.7, “Creating a copy
storage pool” on page 111. Figure 10-6 shows copypool volumes LB0379 and LB0714,
which are empty and ready to be returned on site.
Figure 10-6 Web administrative client interface: Querying volume off site
342 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 10-7 shows the Work with Media using BRM (WRKMEDBRM) status of the BRMS
tapes before you run the STRMNTTSM command. Here we can see the two tapes LB0702
(copytape) and LB0705 (database backup) in location TAPMLB05 (these are the tapes to be
moved off site). Notice that the empty tapes, LB0379 and LB0714 (copytapes), are in the
TSMOFFSITE location and are not yet expired in BRMS. These tapes expire when you run
the STRMNTTSM command.
Figure 10-7 Work with Media display before running the STRMNTTSM command
You must run the command in batch. You can schedule it using the OS/400 job scheduler or
submit it manually using the OS/400 Submit Job (SBMJOB) command.
Chapter 10. Backup Recovery and Media Services movement of IBM Tivoli Storage Manager media 343
We use ITSMLTO2 for the IBM Tivoli Storage Manager device class for the database
backups, COPYLTO for our copy storage pool name, and TSMOFFSITE for the BRMS move
policy name. You normally replace these values with your own definitions. We submit the
STRMNTTSM command using the following OS/400 SBMJOB command:
SBMJOB CMD(STRMNTTSM TSMDBBOFF(*YES) TSMCPYOFF(*YES) TSMVOLON(*YES) MEDIACLS(ITSMLTO2)
CPYPOOL(COPYLTO) BRMMOVPCY(TSMOFFSITE) MOVMEDBRM(*YES)) JOB(STRMNTTSM) JOBQ(QBATCH)
If you select to run the BRMS MOVMEDBRM from the STRMNTTSM command, then a
BRMS volume movement report is produced. The report shown in Figure 10-9 was generated
when we submitted the STRMNTTSM command. This report details the media movement
within BRMS. Here you can see the database (LB0705) and copytape (LB0702) volumes
moving from TAPMLB05 to TSMOFFSITE. You can also see the two empty copytape volumes
(LB0379 and LB0714) returning to TAPMLB05 from TSMOFFSITE.
In 10.2, “Configuring BRMS for IBM Tivoli Storage Manager media movement” on page 339,
we defined the BRMS move policy to verify any tape movements before updating the BRMS
media information. To confirm our tape movements, we enter the BRMS VFYMOVBRM
command on an OS/400 command line. Then you see the Verify Media Moves display
(Figure 10-10). In this example, we typed 1 next to the media being moved to the off-site
location TSMOFFSITE. Then we pressed Enter to verify the move.
Attention: Depending on the setting of the BRMS QA1PRM data area, media may be
ejected when you enter either the MOVMEDBRM or VFYMOVBRM commands. See 4.1.5
“Moving media” in Backup Recovery and Media Services for OS/400: A Practical
Approach, SG24-4840, for details about BRMS media movement. Or refer to Informational
Authorized Program Analysis Records (APAR) II09882 by searching for it on the Web at:
http://www-912.ibm.com/n_dir/nas4apar.nsf/$$Search?openform
The two tapes returning to the TAPMLB05 location (as shown in Figure 10-10) must be
physically placed inside the tape library before their move can be verified.
344 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Verify Media Moves AS27
Figure 10-11 shows the final status of the WRKMEDBRM information after we returned the
two off-site volumes (LB0379 and LB0714) to our 3584 tape library and verified the media
movement in BRMS. Here you can see that the returned media is now expired in BRMS and
can be reused by IBM Tivoli Storage Manager.
Chapter 10. Backup Recovery and Media Services movement of IBM Tivoli Storage Manager media 345
If you press F11 three times, you can see the volume text for each media in BRMS.
Figure 10-12 shows the text for the newly moved tapes. Notice that the STRMNTTSM
command updated the volume text to show which tapes are database or copy storage pool
volumes. This information can be useful in a disaster recovery situation.
Volume
Opt Serial Text
LB0375 *NONE
LB0379 *NONE
LB0702 ITSM COPY Tape
LB0705 ITSM Database Backup
LB0714 *NONE
067ACE *NONE
078ACE *NONE
More...
Parameters or command:
===>
F3=Exit F4=Prompt F5=Refresh F11=Volume information F12=Cancel
F17=Top F18=Bottom F23=More options
346 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
11
The job log always starts at the bottom so you need to page up or press F17 (Top) to reach
the top. Figure 11-1 shows the job log of an interactive job.
To see the message identifier, place your cursor on the message and press F1. Then you see
and Additional Message Information display similar to the example in Figure 11-2.
348 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Additional Message Information
Bottom
Press Enter to continue.
Figure 11-2 Additional message information display from the interactive job log
You can search an interactive job log. Simply enter the DSPJOBLOG command with
OUTPUT(*PRINT). This creates a spooled file that you can search if needed as shown in
Figure 11-3.
If the job is a batch job, then look for the job log in your joblog output queue. On many OS/400
systems, this is set up to be output queue QEZJOBLOG.
If you cannot find the correct job log, try to find it using the Work with Submitted Jobs
(WRKSBMJOB) command for the user profile that ran the job.
350 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Display BRM Log Information AS27
8/18/03 16:00:16 Position to . . . . 8/18/03
Bottom
Press Enter to continue.
BRMS flight recorders are stream files inside of a directory in the integrated file system (IFS).
The files are located in directory /tmp/brms as shown in Figure 11-6. There are five different
files into which BRMS places the information:
Performance
Install
Flightrec
Qbrms
Flightrec.bku
Directory: /tmp/brms
Position to : Record : 1 of 5
New File :
2=Edit 4=Delete File 5=Display 6=Path Size 9=Recursive Delete
Bottom
To gather the flight recorders to get them to your support representative, save the BRMS flight
recorders:
This saves all of the BRMS files needed for further problem determination. There are size
limits for these files and they wrap. If you are experiencing problems, save the BRMS flight
recorders immediately after the failure.
Tape flight recorders are more complicated then the BMRS flight recorders and wrap very
quickly. The tape flight recorders are a set of user spaces that contain files that developers
can run tools against to debug the problem.
1. To access the tape flight recorders, enter the following command as soon as the tape drive
fails:
Call QTADMPDV TAPxx
Here TAPxx is the name of your tape drive/tape library.
2. Create a savefile:
CRTSAVF QGPL/TAPEFLIGHT
3. Enter the Work Problem (WRKPRB) command. This takes you to a listing of problems as
shown in Figure 11-7. On the right side, you see a problem description that states
QTADMPDV - TAPxxx. This is the output that development needs.
4. Enter option 8 next to the problem with the description QTADMPDV - TAPxxx.
5. Select option 32 to save the Authorized Program Analysis Records (APAR) library. This
does a Save Library (SAVLIB) of the problem library that was created by the call
QTADMPDV. Save this to the SAVF you created above. Then contact your support
representative.
352 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Work with Problems
System: AS27
Position to . . . . . . . Problem ID
Thread: 00001F63
Program
Rqs or
Lvl Procedure Library Statement Instruction
QCMD QSYS 0488
QUICMENU QSYS 00C2
1 QUIMNDRV QSYS 055F
2 QUIMGFLW QSYS 04BA
3 QUICMD QSYS 048A
Bottom
F3=Exit F10=Update stack F11=Display activation group F12=Cancel
F16=Job menu F17=Top F18=Bottom F22=Display entire name
BRMS also has a trace function located inside of the BRMS system policy. Use this
parameter only if a support center representative requests you to turn it on. If this is left
turned on, it can create a large file, which in turn can fill up your system. To access the BRMS
system policy, issue the following command:
WRKPCYBRM *SYS
This opens the system policy, from which you have eight options. Select option 1 to change
system policy. Figure 11-10 shows the system policy and parameter that turns the trace on
and off.
Figure 11-10 BRMS system policy with the Trace parameter turned on
354 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
11.4 BRMS program temporary fixes needed
BRMS requires a PTF level to work efficiently. Also, with each BRMS PTF, development
enhances the BRMS flight recorder and other debugging tools. We recommend that you have
the most current cumulative PTF package, Hiper, the group PTF, database group PTFs,
backup and recovery group PTF, and BRMS PTF. To find the PTF numbers that are needed,
see the following Web site:
http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes
This Web site is kept current and contains the recommended PTFs for a large set of iSeries
licensed program products (LPP).
For additional information about PTFs, see 7.5, “Using the Internet to order and install fixes”
on page 143.
You can query the IBM Tivoli Storage Manager activity log from the IBM Tivoli Storage
Manager Web administrative client interface tree structure or the IBM Tivoli Storage Manager
Web Server Command window. If you do not specify any parameters with this command, all
messages generated in the last hour are displayed.
Using the IBM Tivoli Storage Manager Web administrative client interface tree structure,
follow these steps:
a. Expand Object view and select Server-> Activity Log.
b. You see the panel in Figure 12-1. To help tailor your search, you can use various fields
on this panel. Enter the following search requirements and click Finish:
• Begin Date: This value specifies the beginning date of the range for messages to
be displayed. You can enter the date in your system’s date format. You can also
enter a value of TODAY for the current date or, for example, -3 to display all message
from three days ago.
• Begin Time: This value specifies the beginning time of the range for messages to
be displayed. You can enter the time in your system’s time format. You can also
enter a value of NOW for the current time or, for example, -02:00 to view all message
from two hours ago.
• End Date: This value specifies the beginning date of the range for messages to be
displayed. You can use the same format as the Begin Date parameter.
• End Time: This value specifies the beginning time of the range for messages to be
displayed. You can use the same format as the Begin Time parameter.
• Message number: If you know the IBM Tivoli Storage Manager message number,
enter the number here without the ANR prefix.
• Search string: This specifies a text string that you want to search for in the activity
log. Enclose the string expression in quotation marks if it contains blanks. You can
use text and a wildcard character to specify this string. For example, to search the
activity log for failures, we can enter the word fail to search all the messages in the
log.
• Originator: You can choose to query displays messages logged by the server
(SERVER), client (CLIENT), or both (ALL). If you specify CLIENT, you can use the
following subparameters to further restrict your query:
- Node Name: This displays messages logged for a particular node. For example,
we could enter AS02 to search for all messages for our test Backup Recovery
and Media Services (BRMS) Application Client.
- Client Owner: Displays messages logged for a particular owner.
- Schedule Name: Displays messages logged by a particular scheduled client
activity.
- Policy Domain Name: This parameter is used to display messages logged for a
particular policy domain to which a named schedule belongs. Again you can
enter BRMS here to display all messages for the test BRMS Application Client.
- Session: This is used to specify messages logged from a particular client
session number.
358 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 12-1 Web administrative client interface: Querying the activity log
Using the IBM Tivoli Storage Manager Web Server Command window, you can enter
either of the following commands to display the IBM Tivoli Storage Manager servers
activity log:
query actlog
q act
For example, to dispay all failed messages from midnight two days ago until now, you can
use the command syntax:
q act begindate=-2 begintime=00:00 search=fail
The following section explains how to use the IBM Tivoli Storage Manager help command
to see all possible parameter available with this command. You can also refer to Chapter 5
“Administrative Commands” in the IBM Tivoli Storage Manager for OS/400 PASE -
Administrator’s Reference Guide, GC23-4695.
Chapter 12. Troubleshooting IBM Tivoli Storage Manager for OS/400 PASE 359
the menu number. For example, to see information about Entering Administrative
Commands, you enter:
help 2
360 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure 12-3 Web administrative client interface help for a message number
Chapter 12. Troubleshooting IBM Tivoli Storage Manager for OS/400 PASE 361
For a complete list of all IBM Tivoli Storage Manager message numbers, refer to IBM Tivoli
Storage Manager Messages, GC32-0767, supplied with the IBM Tivoli Storage Manager
software.
12.4.1 Ending IBM Tivoli Storage Manager from within OS/400 PASE
Use the following steps to end the IBM Tivoli Storage Manager server from within OS/400
Portable Application Solutions Environment (PASE):
1. Start an OS/400 PASE session. Enter the following command from an OS/400 command
line:
call qp2term
2. On the shell command line, enter the AIX command:
ps -ef
This command is like the OS/400 Work with Active Jobs (WRKACTJOB) for OS/400
PASE. Figure 12-4 shows the resulting display from this command. Here you can see the
IBM Tivoli Storage Manager server running with process ID 776.
/QOpenSys/usr/bin/-sh
$
> ps -ef
UID PID PPID C STIME TTY TIME CMD
itsm 776 1 0 16:04:33 - 0:03 /usr/tivoli/tsm/server/bin/dsmserv
itsm 780 779 0 16:05:38 - 0:00 /QOpenSys/usr/bin/-sh -i
itsm 781 780 0 16:05:43 - 0:00 ps -ef
$
3. To end the IBM Tivoli Storage Manager server, use the AIX kill command:
kill -11 776
In this example, 776 is our process number. You should replace this number with your own
process number using the ps -ef command.
The kill command should end your IBM Tivoli Storage Manager server and place a core
dump file (called a core on AIX) in the IBM Tivoli Storage Manager server’s IFS directory.
This file can be useful for IBM Tivoli Storage Manager support personnel in analyzing the
cause of your IBM Tivoli Storage Manager server hang. In our example, the core dump file
/usr/tivoli/tsm/server/bin/core was created.
4. When the IBM Tivoli Storage Manager server is ended, you may have to delete the IBM
Tivoli Storage Manager server lock file from the IFS before you restart the IBM Tivoli
362 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Storage Manager server. If you are sure that the IBM Tivoli Storage Manager server is
ended, you can delete this file from the IBM Tivoli Storage Manager servers directory. In
this example, we delete the lock file by entering the following OS/400 command:
RMVLNK OBJLNK('/usr/tivoli/tsm/server/bin/adsmserv.lock')
12.4.2 Ending the IBM Tivoli Storage Manager server for OS/400 PASE with the
ENDJOB command
To end the IBM Tivoli Storage Manager server using the OS/400 End Job (ENDJOB)
command, follow these steps:
1. Start an OS/400 PASE session. Enter the following command:
call qp2term
2. On the shell command line, enter the following AIX command to find the process ID of the
IBM Tivoli Storage Manager server:
ps -ef
In the example shown in Figure 12-5, you can see that the IBM Tivoli Storage Manager
server is running with process ID 791.
/QOpenSys/usr/bin/-sh
$
> ps -ef
UID PID PPID C STIME TTY TIME CMD
itsm 791 1 0 16:40:45 - 0:03 /usr/tivoli/tsm/server/bin/dsmserv
itsm 801 779 0 16:55:21 - 0:00 /QOpenSys/usr/bin/-sh -i
itsm 802 801 0 16:55:29 - 0:00 ps -ef
$
> system qsh "cmd('getjobid 791')"
Process identifier 791 is 063454/ITSM/TSMPASESRV
QSH0005: Command ended normally with exit status 0.
$
===>
F3=Exit F6=Print F9=Retrieve F11=Truncate/Wrap
F13=Clear F17=Top F18=Bottom F21=CL command entry
3. Entered the following shell command to find the OS/400 job name and number of the
active IBM Tivoli Storage Manager server:
system qsh "cmd('getjobid 791')"
In this example, we used process number 791. You should replace this number with your
own process number using the ps -ef command.
4. End the IBM Tivoli Storage Manager server by using the ENDJOB command from an
OS/400 command line. In this example, we entered the following OS/400 command:
ENDJOB JOB(063454/ITSM/TSMPASESRV) OPTION(*IMMED)
Replace the job name and number of the one you received in the previous step.
Chapter 12. Troubleshooting IBM Tivoli Storage Manager for OS/400 PASE 363
12.4.3 Ending the IBM Tivoli Storage Manager server for OS/400 PASE with the
ENDJOBABN command
You can only use the End Job Abnormal (ENDJOBABN) command 10 minutes after the you
enter the ENDJOB command. Use the following example to end the IBM Tivoli Storage
Manager server using the OS/400 ENDJOBABN command:
1. Retrieve the OS/400 job name and number for the IBM Tivoli Storage Manager server as
in the previous exercise.
2. End the IBM Tivoli Storage Manager server by using the ENDJOBABN command from an
OS/400 command line. In this example, we entered the following OS/400 command:
ENDJOBABN JOB(063454/ITSM/TSMPASESRV)
Replace the job name and number with the one you received with the system qsh
"cmd('getjobid 791')" shell command.
Table 12-1 IBM Tivoli Storage Manager commands combined using the query system command
IBM Tivoli Storage Function
Manager command
QUERY ASSOCIATION Displays the clients associated with one or more schedules
QUERY SESSION Displays information about all active administrative and client
sessions
364 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
12.6 IBM Tivoli Storage Manager support Web page
The IBM Tivoli Storage Manager support Web page provides links to all your support needs.
Here you can find the latest information about releases, Authorized Program Analysis
Records (APARs), supported devices, support flashes, client/server requirements,
documentation, etc. You can find the IBM Tivoli Storage Manager support Web page at:
http://www-3.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html
This redbook discusses related Tivoli Storage Manager fix information in 4.4, “Downloading
IBM Tivoli Storage Manager for OS/400 PASE fixes” on page 48.
Chapter 12. Troubleshooting IBM Tivoli Storage Manager for OS/400 PASE 365
366 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Part 5
Part 5 Appendixes
The appendixes in this part offer additional assistance when backing up and recovering with
the Backup Recovery and Media Services and IBM Tivoli Storage Manager on OS/400
Portable Application Solutions Environment (PASE) products:
Appendix A, “General backup and recovery considerations” on page 369, offers a list of
questions as a starting point to assist you in developing your own iSeries backup and
recovery processes for your environment.
Appendix B, “Backup Recovery and Media Services reports” on page 375, contains
examples of BRMS recovery reports for a:
– Full system backup to tape
– Full system backup to tape and an ITSM server
The BRMS recovery reports are one of the highlights of the product that users consider
invaluable. The content of these reports clearly identifies the steps to perform a recovery,
based on a specific BRMS-initiated backup that is already performed. While a complete
description of the kinds of information that are contained in any such report is beyond the
scope of this redbook, you can review the text within these sample reports for a good
understanding of how BRMS helps you recover, step by step.
Appendix C, “AIX administrative client in OS/400 PASE sample programs” on page 399,
contains a source listing of a set of pSeries (AIX) IBM Tivoli Storage Manager client
programs and explains how to download them. iSeries programs using these AIX IBM
Tivoli Storage Manager client programs can provide additional integration of IBM Tivoli
Storage Manager for OS/400 PASE server functions that are not directly available in
current BRMS and IBM Tivoli Storage Manager products. Examples using these programs
are included in 6.2.2, “Creating IBM Tivoli Storage Manager and BRMS exit programs” on
page 98, and 10.1, “Sample programs for IBM Tivoli Storage Manager, BRMS media
movement” on page 338.
You can download programs using these AIX IBM Tivoli Storage Manager programs as
part of this redbook as described in Appendix D, “Additional material” on page 411.
368 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
A
Before you start implementing your backup and recovery processes, be sure to review this
appendix.
A way to evaluate your backup and recovery plan is to forget about your current plans. Start
over and see how much your current plan actually protects you. The most vital questions are:
What consequences will there be if we lose data?
For how long can we run our business without key data?
These are not easy questions to answer. However, when you can, you will have a pretty good
idea what you have to do.
For everything, there is a cost. For example, is the cost of protecting us up to the last minute
of data change higher than losing the business for a given time period? You must sort out
these types of considerations before you start determining how you save the data itself.
There are other things that you may lose, such as your data systems, your wiring, your site,
your personnel, etc., that can hurt your business. This is outside the scope of this redbook.
But nevertheless, you have to have a plan for such situations.
When you have an idea of understanding the business impact, then you need to sort out the
kind of resources you can afford and the people you have available (or need).
Your personnel plays a key role in securing your data. You have the best person in place
today, but you cannot be sure that you have them tomorrow. Good advice says to keep
everything as simple and straightforward as possible so you are not in the hand of experts,
which can turn out to be costly from several aspects.
You may think all this is too much and say, “OK. I'll take the cost and go for the highest
protection possible for a mirrored system.” This may shield you from many things, but not from
everything. Remember that most data losses are due to human errors and bad application
coding, not by faulty equipment. For example, in a mirrored environment, if a user deletes a
file, within seconds it is deleted in your backup system as well. How do you recover from that
without a backup copy?
For some reason, bad things have a tendency to happen at the worst possible point in time.
Be sure you have good, up-to-date documentation and that the people involved know where
the documentation is and are trained to use it. Recovery time is vital.
Table A-1 lists questions to ask yourself and includes space for you to record your answer and
any action plan for each question.
370 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Table A-1 General backup and recovery questions checklist
Question Answer Action plan
Is Domino installed?
372 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Question Answer Action plan
IBM has availability services that can assist you in setting up and testing backup and recovery
procedures that are sufficient for your production environment.
374 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
B
You can review the text within a report to understand the kinds of things that BRMS does and
what it tells you to do step by step.
Example: B-1 Full system recovery report to tape for system AS27
5722BR1 V5R2M0 020906 Recovering Your Entire System AS27
****************************************************************************************************
Selection Criteria
Option . . . . . . . . . . . . . : *SYSTEM
Start date and time . . . . . . : *BEGIN *AVAIL
Ending date and time . . . . . . : *END *AVAIL
Use save files . . . . . . . . . : *NO
Use TSM . . . . . . . . . . . . : *NO
Auxiliary storage pool . . . . . :
System name . . . . . . . . . . : AS27
Volume location . . . . . . . . : *ALL
Library to omit . . . . . . . . : *DELETE
*********************
***** ATTENTION *****
*********************
This report excludes objects saved to either save files or TSM servers.
Media information is available for either one or both of these media
types. The report may not show the latest level of saved items.
Verify whether you should run the report again including this media.
****************************************************************************************************
The following report is to be used in conjunction with the "Backup and
Recovery" book, SC41-5304, to assist with recovery from failures.
****************************************************************************************************
When recovering your system, refer to the section on "Recovering
after a Complete Loss" under chapter "Selecting the Right Recovery
Strategy" in the "Backup and Recovery" book, and the details shown
below to determine which recovery steps should be taken and the media
needed for each step.
For information about BRMS recoveries using a Media Library Device refer
to the "Backup Recovery and Media Services for OS/400: A Practical Approach",
SG24-4840, and the "Automated Tape Library
Planning and Management" book, SC41-5309.
If you have logical files, and based-on physical and logical files
are in different libraries refer to the section on "Restoring Logical
Files" in the "Backup and Recovery" book for important restore
considerations before proceeding with recovery.
If you use journaling refer to the section on "Restoring Journals and
Journal Receivers" in the "Backup and Recovery" book for important
restore considerations before proceeding with recovery.
restore considerations before proceeding with recovery.
You can use the Start date/time, Stop date/time and Duration fields
to record the time it takes to test or perform your recovery.
A value of *SYSBAS for ASP Name refers to saved items backed up from
the system (1) or basic user (2-32) auxiliary storage pools.
A value of *TSM for Volume Identifier refers to saved items backed
up to Tivoli Storage Manager (TSM) servers.
****************************************************************************************************
STEP: Recover Licensed Internal Code
Start date/time __________________ Stop date/time __________________ Duration _________________
Use media as shown below and the procedure for "Recovering the
376 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Licensed Internal Code" in the "Backup and Recovery" book.
__ Use "Option 2" if you are recovering to a different system or if
you are recovering to a system with user ASP(s) or if you are
recovering to the same system with a different release.
__ Use "Option 3" if you are recovering to the same release and same
system or you are recovering a logical partition to another logical
partition.
--- Attention -------------------------------------------------------
If you are using a media library device, you will need to use either
standalone, automatic or manual mode, or use the device move media
function to load the media volume containing the *SAVSYS saved item.
Refer to the device documentation if you are not familiar with these
device modes or functions.
---------------------------------------------------------------------
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ *SAVSYS *FULL *SYSBAS 00001 8/14/03 16:58:46 0 1 *SYSTEM LB0702
****************************************************************************************************
STEP: Recover operating system
Start date/time __________________ Stop date/time __________________ Duration _________________
Use the media shown below and the procedure for "Restoring the Operating
System using the Complete Restore Method", as detailed in the "Backup
and Recovery" book.
After sign on, display and change the following system values before
continuing with the recovery.
To do so, run the following command:
WRKSYSVAL
__ Use option 5=Display to show the current system value setting.
__ Record the current setting for use after recovery is complete.
__ Use option 2=Change to change the system value to the new setting.
---------------------------------------------------------------------
System value Current setting New setting
QALWOBJRST _______________ *ALL
QFRCCVNRST _______________ 0
QIPLTYPE _______________ 2
QJOBMSGQFL _______________ *PRTWRAP
QJOBMSGQMX _______________ 30 (minimum, 64 recommended)
QPFRADJ _______________ 2
QVFYOBJRST _______________ 1
---------------------------------------------------------------------
After changing the system values, sign off using the following command:
SIGNOFF LOG(*LIST)
Using a newly created password, sign back on as QSECOFR for the new
system values to take effect.
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ *SAVSYS *FULL *SYSBAS 00001 8/14/03 16:58:46 0 1 *SYSTEM LB0702
****************************************************************************************************
STEP: Setting up standalone or media library devices for recovery
Start date/time __________________ Stop date/time __________________ Duration _________________
If you are using a media library device and automatic configuration was
enabled, you can now use the media library device to automate recovery.
--- Attention -------------------------------------------------------
To perform automated recovery using a media library device, you must
have performed the save with the media library device enabled for
library operations.
---------------------------------------------------------------------
--- Attention -------------------------------------------------------
378 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
guide you through the remaining recovery steps.
Run the following command for each of the libraries listed below
specifying the saved-item, the device name of the standalone drive or
media library you are using, and the volume identifiers and sequence
numbers listed.
RSTOBJ OBJ(*ALL) SAVLIB(saved-item) DEV(device-name)
VOL(volume-identifier) SEQNBR(sequence-number)
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ QUSRBRM *QBRM *SYSBAS 00001 8/14/03 18:28:57 12 536 *SYSTEM LB0702
****************************************************************************************************
STEP: Initialize BRMS functional authority information
Start date/time __________________ Stop date/time __________________ Duration _________________
You must perform this step to initialize BRMS functional authorities.
Use the following command to register all BRMS functional authority
resources with the OS/400 functional authority manager.
INZBRM OPTION(*SETAUT)
Use the following command to assure the QSECOFR user profile has
authority to use the managed functional authority resources.
SETUSRBRM USER(QSECOFR) USAGE(*ADMIN)
****************************************************************************************************
STEP: Update system name in BRMS media information
Start date/time __________________ Stop date/time __________________ Duration _________________
You must update the system name in the saved BRMS media information
if you are recovering to a system or logical partition with a system
name that is different from the system name of the save.
To do so, run the following command:
INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(previous-name) NEWSYSNAM(new-name)
****************************************************************************************************
STEP: Initialize BRMS device and media library information
Start date/time __________________ Stop date/time __________________ Duration _________________
You must initialize the BRMS device and media library information.
Use the following command to clear and initialize the BRMS device and
media library information with the tape and media library devices
currently configured on the system:
INZBRM OPTION(*DEVICE)
INZBRM OPTION(*DEVICE) resets some device information to the BRMS
supplied defaults. Review the BRMS device information using the
following command:
WRKDEVBRM
Update the BRMS device information with any changes necessary to
continue with your recovery.
****************************************************************************************************
STEP: Recover user profiles
Start date/time __________________ Stop date/time __________________ Duration _________________
You should restore a current version of your user profiles.
To do so, run the following command:
STRRCYBRM OPTION(*SYSTEM) ACTION(*RESTORE)
--- Attention -------------------------------------------------------
Press F9 (Recovery defaults) on the Select Recovery Items display.
Ensure the tape device name or media library device name that you are
using is correct.
---------------------------------------------------------------------
--- Attention -------------------------------------------------------
If recovering to a different system or recovering a logical partition
to another logical partition, you must specify the following:
__ *ALL on the Allow object differences (ALWOBJDIF) parameter
__ *ALL on the Data base member option (MBROPT) parameter
__ *NONE on the System resource management (SRM) parameter
380 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
STEP: Recover by control group
Start date/time __________________ Stop date/time __________________ Duration _________________
Depending on your recovery strategy, you may choose to restore your
system by control groups.
--- Attention -------------------------------------------------------
Recovery by control group requires knowledge of the data saved by the
control group and of the system resources needed to complete this
type of recovery.
---------------------------------------------------------------------
If you do not want to recover by control group, continue with "Step:
Recover all remaining system and user data".
Otherwise, run the following command to retrieve the list of control
groups, then select and sequence the control groups to be recovered:
STRRCYBRM OPTION(*CTLGRP) ACTION(*RESTORE) CTLGRP(*SELECT)
--- Attention -------------------------------------------------------
Press F9 (Recovery defaults) on the Select Recovery Items display.
Ensure the tape device name or media library device name that you are
using is correct.
---------------------------------------------------------------------
Press F16 to select all recovery items.
Otherwise, select the individual items you need to recover.
Use the media listed on the "Select Recovery Items" display.
After the saved items are recovered, continue with the step following
"STEP: Recover objects in directories".
--- Attention -------------------------------------------------------
If you have logical files whose based-on physical files are in a
different library, you must restore all based-on physical files
before you can restore the logical file.
---------------------------------------------------------------------
--- Attention -------------------------------------------------------
If you use journaling, the libraries containing the journals must be
restored before restoring the journaled files.
---------------------------------------------------------------------
****************************************************************************************************
STEP: Recover all remaining system and user data
Start date/time __________________ Stop date/time __________________ Duration _________________
You may now select to recover all of the data on your system.
To do so, run the following command:
STRRCYBRM OPTION(*RESUME)
--- Attention -------------------------------------------------------
Press F9 (Recovery defaults) on the Select Recovery Items display.
Ensure the tape device name or media library device name that you are
using is correct.
---------------------------------------------------------------------
Press F16 to select all recovery items.
After the saved items are recovered, continue with the step following
"STEP: Recover objects in directories".
Otherwise, continue with the following step.
****************************************************************************************************
STEP: Recover IBM product libraries
Start date/time __________________ Stop date/time __________________ Duration _________________
You should restore the current version of your IBM libraries.
If you are performing a complete system restore, run the following
command to continue:
STRRCYBRM OPTION(*RESUME)
Otherwise, run the following command(s):
STRRCYBRM OPTION(*IBM) ACTION(*RESTORE)
Select and recover the following saved item(s) on the "Select Recovery
Items" display using the specified volume(s).
Saved ----- ASP ------ Save Save Sequence Control Volume
382 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
STRRCYBRM OPTION(*RESUME)
Otherwise, run the following command(s):
STRRCYBRM OPTION(*ALLDLO) ACTION(*RESTORE)
Select and recover the following saved item(s) on the "Select Recovery
Items" display using the specified volume(s).
--- Attention -------------------------------------------------------
When you recovery Document Library Objects (DLOs), the system updates
the search index database information for these DLOs. If the recovery
fails, the error message may instruct you to run reclaim on the DLOs.
To do so, run the following command:
RCLDLO DLO(*ALL)
After the reclaim, try the DLO recovery again.
---------------------------------------------------------------------
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ *ALLDLO *FULL *SYSBAS 00001 8/14/03 17:46:00 29 534 *SYSTEM LB0702
****************************************************************************************************
STEP: Recover objects in directories
Start date/time __________________ Stop date/time __________________ Duration _________________
You should restore the current version of your objects in directories.
If you are performing a complete system restore, run the following
command to continue:
STRRCYBRM OPTION(*RESUME)
Otherwise, run the following command(s):
STRRCYBRM OPTION(*LNKLIST) ACTION(*RESTORE)
Select and recover the following saved item(s) on the "Select Recovery
Items" display using the specified volume(s).
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ *LINK *FULL *SYSBAS 00001 8/14/03 17:46:09 179,468 535 *SYSTEM LB0702
****************************************************************************************************
STEP: Recover spooled files for all ASPs
Start date/time __________________ Stop date/time __________________ Duration _________________
If spooled files were saved, restore your spooled files using the
following command:
WRKSPLFBRM
Press F16 to select all recovery items.
Otherwise, select the individual items you need to recover.
Use the media listed on the "Select Recovery Items" display.
****************************************************************************************************
STEP: Special Recovery Processing
Start date/time __________________ Stop date/time __________________ Duration _________________
IBM iSeries Integration for Windows Server (5722-WSV)
If iSeries Integration for Windows Server was installed when your
system was saved and has been restored to the system, perform the
following steps:
If the Windows servers were VARIED OFF during the save, perform these
recovery steps:
__ a. Add the links for each server description using the following
command:
ADDNWSSTGL NWSSTG(server-storage-name)
NWSD(server-description-name)
__ b. Vary on your Windows servers using the following command:
WRKCFGSTS CFGTYPE(*NWS)
Select option 1 to vary on each server.
****************************************************************************************************
STEP: Special Recovery Processing
Start date/time __________________ Stop date/time __________________ Duration _________________
384 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
STEP: Print joblog
Start date/time __________________ Stop date/time __________________ Duration _________________
You should print the joblog.
To do so, run the following command:
DSPJOBLOG JOB(*) OUTPUT(*PRINT)
Review the job logs or output from your recovery processing
to ensure that all recovery steps completed successfully.
****************************************************************************************************
STEP: Reset system values
Start date/time __________________ Stop date/time __________________ Duration _________________
Use the commands and recorded values in "Step: Recover operating
system" to change the system values to the original setting or to a
new value that meets your desired policy.
****************************************************************************************************
STEP: Perform IPL
Start date/time __________________ Stop date/time __________________ Duration _________________
Return system to normal mode and IPL using the following command:
PWRDWNSYS OPTION(*IMMED) RESTART(*YES)
****************************************************************************************************
STEP: Special Recovery Processing
Start date/time __________________ Stop date/time __________________ Duration _________________
IBM iSeries Integration for Windows Server (5722-WSV)
If iSeries Integration for Windows Server was installed when your
system was saved and has been restored to the system, perform the
following steps:
If the Windows servers were VARIED ON during the save, perform these
recovery steps:
__ a. Vary off any Windows servers that are VARIED ON using the
following command:
WRKCFGSTS CFGTYPE(*NWS)
Select option 2 to vary off each server.
__ b. Create any needed Network Storages using the following command:
CRTNWSSTG NWSSTG(server-storage-name)
__ c. Add the links for each server description using the following
command:
ADDNWSSTGL NWSSTG(server-storage-name)
NWSD(server-description-name)
__ d. Vary on your Windows servers using the following command:
WRKCFGSTS CFGTYPE(*NWS)
Select option 1 to vary on each server.
__ e. Restore the Windows server data using the following command and
the volumes listed in "STEP: Recover objects in directories":
RST OBJ('/QNTC')
* * * * * E N D O F L I S T I N G * * * * *
386 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ *SAVSYS *FULL *SYSBAS 00001 8/25/03 17:50:59 0 1 SAVSYSPLUS BRM001
****************************************************************************************************
STEP: Recover operating system
Start date/time __________________ Stop date/time __________________ Duration _________________
Use the media shown below and the procedure for "Restoring the Operating
System using the Complete Restore Method", as detailed in the "Backup
and Recovery" book.
After sign on, display and change the following system values before
continuing with the recovery.
To do so, run the following command:
WRKSYSVAL
__ Use option 5=Display to show the current system value setting.
__ Record the current setting for use after recovery is complete.
__ Use option 2=Change to change the system value to the new setting.
---------------------------------------------------------------------
System value Current setting New setting
QALWOBJRST _______________ *ALL
QFRCCVNRST _______________ 0
5722BR1 V5R2M0 020906 Recovering Your Entire System AS02
8/26/03 8:55:45 Page 3 of 19
QIPLTYPE _______________ 2
QJOBMSGQFL _______________ *PRTWRAP
QJOBMSGQMX _______________ 30 (minimum, 64 recommended)
QPFRADJ _______________ 2
QVFYOBJRST _______________ 1
---------------------------------------------------------------------
After changing the system values, sign off using the following command:
SIGNOFF LOG(*LIST)
Using a newly created password, sign back on as QSECOFR for the new
system values to take effect.
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ *SAVSYS *FULL *SYSBAS 00001 8/25/03 17:50:59 0 1 SAVSYSPLUS BRM001
****************************************************************************************************
STEP: Setting up standalone or media library devices for recovery
Start date/time __________________ Stop date/time __________________ Duration _________________
If you are using a media library device and automatic configuration was
enabled, you can now use the media library device to automate recovery.
--- Attention -------------------------------------------------------
To perform automated recovery using a media library device, you must
have performed the save with the media library device enabled for
library operations.
---------------------------------------------------------------------
--- Attention -------------------------------------------------------
If you are using a 3494 Media Library for recovery, you will need to
configure and set up the communications necessary to control the
cartridge loader.
---------------------------------------------------------------------
For recovery using the device as a media library (TAPMLBxx):
__ A. Unload the media volume containing the *SAVSYS saved item from
the device.
__ B. Load all the volumes needed for the recovery (including the
*SAVSYS volume) in the media library.
__ C. Set the media library device for library operations. Refer to
the device documentation if you are not familiar with enabling
the device for library operations.
388 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ QUSRBRM *QBRM *SYSBAS 00001 8/25/03 18:53:01 18 129 SAVSYSPLUS BRM001
****************************************************************************************************
STEP: Initialize BRMS functional authority information
Start date/time __________________ Stop date/time __________________ Duration _________________
You must perform this step to initialize BRMS functional authorities.
Use the following command to register all BRMS functional authority
resources with the OS/400 functional authority manager.
INZBRM OPTION(*SETAUT)
Use the following command to assure the QSECOFR user profile has
authority to use the managed functional authority resources.
SETUSRBRM USER(QSECOFR) USAGE(*ADMIN)
****************************************************************************************************
STEP: Update system name in BRMS media information
Start date/time __________________ Stop date/time __________________ Duration _________________
You must update the system name in the saved BRMS media information
5722BR1 V5R2M0 020906 Recovering Your Entire System AS02
8/26/03 8:55:45 Page 6 of 19
if you are recovering to a system or logical partition with a system
name that is different from the system name of the save.
To do so, run the following command:
INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(previous-name) NEWSYSNAM(new-name)
****************************************************************************************************
STEP: Initialize BRMS device and media library information
Start date/time __________________ Stop date/time __________________ Duration _________________
You must initialize the BRMS device and media library information.
Use the following command to clear and initialize the BRMS device and
media library information with the tape and media library devices
currently configured on the system:
INZBRM OPTION(*DEVICE)
INZBRM OPTION(*DEVICE) resets some device information to the BRMS
supplied defaults. Review the BRMS device information using the
following command:
WRKDEVBRM
Update the BRMS device information with any changes necessary to
continue with your recovery.
****************************************************************************************************
STEP: Recover user profiles
Start date/time __________________ Stop date/time __________________ Duration _________________
You should restore a current version of your user profiles.
To do so, run the following command:
STRRCYBRM OPTION(*SYSTEM) ACTION(*RESTORE)
--- Attention -------------------------------------------------------
Press F9 (Recovery defaults) on the Select Recovery Items display.
Ensure the tape device name or media library device name that you are
using is correct.
---------------------------------------------------------------------
--- Attention -------------------------------------------------------
If recovering to a different system or recovering a logical partition
to another logical partition, you must specify the following:
__ *ALL on the Allow object differences (ALWOBJDIF) parameter
__ *ALL on the Data base member option (MBROPT) parameter
__ *NONE on the System resource management (SRM) parameter
5722BR1 V5R2M0 020906 Recovering Your Entire System AS02
8/26/03 8:55:45 Page 7 of 19
---------------------------------------------------------------------
Select and recover the following saved item(s) on the "Select Recovery
Items" display using the specified volume(s).
Saved ----- ASP ------ Save Save Sequence Control Volume
390 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
STEP: Recover IBM product libraries
Start date/time __________________ Stop date/time __________________ Duration _________________
You should restore the current version of your IBM libraries.
If you are performing a complete system restore, run the following
command to continue:
5722BR1 V5R2M0 020906 Recovering Your Entire System AS02
8/26/03 8:55:45 Page 9 of 19
STRRCYBRM OPTION(*RESUME)
Otherwise, run the following command(s):
STRRCYBRM OPTION(*IBM) ACTION(*RESTORE)
Select and recover the following saved item(s) on the "Select Recovery
Items" display using the specified volume(s).
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ #COBLIB *FULL *SYSBAS 00001 8/25/03 18:10:38 82 38 SAVSYSPLUS BRM001
__ #RPGLIB *FULL *SYSBAS 00001 8/25/03 18:10:38 55 39 SAVSYSPLUS BRM001
__ QANSAPI *FULL *SYSBAS 00001 8/25/03 18:10:38 9 40 SAVSYSPLUS BRM001
__ QAPTL *FULL *SYSBAS 00001 8/25/03 18:10:38 94 41 SAVSYSPLUS BRM001
__ QASE5 *FULL *SYSBAS 00001 8/25/03 18:10:38 83 42 SAVSYSPLUS BRM001
__ QBUILDSS1 *FULL *SYSBAS 00001 8/25/03 18:10:38 2 44 SAVSYSPLUS BRM001
__ QCAEXP *FULL *SYSBAS 00001 8/25/03 18:10:38 16 45 SAVSYSPLUS BRM001
__ QCAP3 *FULL *SYSBAS 00001 8/25/03 18:10:38 14 46 SAVSYSPLUS BRM001
__ QCA400W *FULL *SYSBAS 00001 8/25/03 18:10:38 9 47 SAVSYSPLUS BRM001
__ QCBL *FULL *SYSBAS 00001 8/25/03 18:10:38 74 48 SAVSYSPLUS BRM001
__ QCBLLE *FULL *SYSBAS 00001 8/25/03 18:10:38 10 49 SAVSYSPLUS BRM001
__ QCBLLEP *FULL *SYSBAS 00001 8/25/03 18:10:38 9 50 SAVSYSPLUS BRM001
__ QCE3 *FULL *SYSBAS 00001 8/25/03 18:10:38 6 51 SAVSYSPLUS BRM001
__ QCLE *FULL *SYSBAS 00001 8/25/03 18:10:38 13 52 SAVSYSPLUS BRM001
__ QCPPLE *FULL *SYSBAS 00001 8/25/03 18:10:38 27 53 SAVSYSPLUS BRM001
__ QCXXN *FULL *SYSBAS 00001 8/25/03 18:10:38 13 54 SAVSYSPLUS BRM001
__ QDB2MS *FULL *SYSBAS 00001 8/25/03 18:10:38 2 55 SAVSYSPLUS BRM001
__ QDEVTOOLS *FULL *SYSBAS 00001 8/25/03 18:10:38 214 56 SAVSYSPLUS BRM001
__ QDIRSRV2 *FULL *SYSBAS 00001 8/25/03 18:10:38 4 57 SAVSYSPLUS BRM001
__ QEJBAS5 *FULL *SYSBAS 00001 8/25/03 18:10:38 190 58 SAVSYSPLUS BRM001
__ QFNTCPL *FULL *SYSBAS 00001 8/25/03 18:10:38 1,529 59 SAVSYSPLUS BRM001
__ QGPLTEMP *FULL *SYSBAS 00001 8/25/03 18:10:38 1 60 SAVSYSPLUS BRM001
__ QGY *FULL *SYSBAS 00001 8/25/03 18:10:38 109 61 SAVSYSPLUS BRM001
__ QHLPSYS *FULL *SYSBAS 00001 8/25/03 18:10:38 315 62 SAVSYSPLUS BRM001
__ QHTTP *FULL *SYSBAS 00001 8/25/03 18:10:38 3 63 SAVSYSPLUS BRM001
__ QHTTPSVR *FULL *SYSBAS 00001 8/25/03 18:10:38 179 64 SAVSYSPLUS BRM001
__ QICSS *FULL *SYSBAS 00001 8/25/03 18:10:38 44 65 SAVSYSPLUS BRM001
__ QINMEDIA *FULL *SYSBAS 00001 8/25/03 18:10:38 26 66 SAVSYSPLUS BRM001
__ QINPRIOR *FULL *SYSBAS 00001 8/25/03 18:10:38 1 67 SAVSYSPLUS BRM001
__ QINSYS *FULL *SYSBAS 00001 8/25/03 18:10:38 1 68 SAVSYSPLUS BRM001
__ QIWA2 *FULL *SYSBAS 00001 8/25/03 18:10:38 25 69 SAVSYSPLUS BRM001
__ QIWE *FULL *SYSBAS 00001 8/25/03 18:10:38 30 70 SAVSYSPLUS BRM001
__ QIWR *FULL *SYSBAS 00001 8/25/03 18:10:38 7 71 SAVSYSPLUS BRM001
__ QIWS *FULL *SYSBAS 00001 8/25/03 18:10:38 140 72 SAVSYSPLUS BRM001
__ QJAVA *FULL *SYSBAS 00001 8/25/03 18:10:38 43 73 SAVSYSPLUS BRM001
__ QJT400 *FULL *SYSBAS 00001 8/25/03 18:10:38 15 74 SAVSYSPLUS BRM001
__ QLBL *FULL *SYSBAS 00001 8/25/03 18:10:38 79 75 SAVSYSPLUS BRM001
__ QMQM *FULL *SYSBAS 00001 8/25/03 18:10:38 392 76 SAVSYSPLUS BRM001
__ QMQMJAVA *FULL *SYSBAS 00001 8/25/03 18:10:38 10 77 SAVSYSPLUS BRM001
__ QMQMSAMP *FULL *SYSBAS 00001 8/25/03 18:10:38 8 78 SAVSYSPLUS BRM001
__ QMWAS_RCHA *FULL *SYSBAS 00001 8/25/03 18:10:38 17 80 SAVSYSPLUS BRM001
__ QMWAS_RC00 *FULL *SYSBAS 00001 8/25/03 18:10:38 14 81 SAVSYSPLUS BRM001
__ QMWAS_RC01 *FULL *SYSBAS 00001 8/25/03 18:10:38 16 82 SAVSYSPLUS BRM001
5722BR1 V5R2M0 020906 Recovering Your Entire System AS02
8/26/03 8:55:45 Page 10 of 19
392 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
to ensure that all recovery steps completed successfully.
****************************************************************************************************
STEP: Perform IPL
Start date/time __________________ Stop date/time __________________ Duration _________________
Return system to normal mode and IPL using the following command:
PWRDWNSYS OPTION(*IMMED) RESTART(*YES)
****************************************************************************************************
STEP: Recover additional user libraries
Start date/time __________________ Stop date/time __________________ Duration _________________
You should restore the current version of your user libraries saved
from auxiliary storage pool devices or saved to TSM servers.
If you are performing a complete system restore, run the following
command to continue:
STRRCYBRM OPTION(*RESUME)
Otherwise, run the following command(s):
STRRCYBRM OPTION(*ALLUSR) ACTION(*RESTORE) USEADSM(*YES)
STRRCYBRM OPTION(*ASP) ACTION(*RESTORE) ASP(auxiliary-storage-pool-name)
Select and recover the following saved item(s) on the "Select Recovery
Items" display using the specified volume(s).
--- Attention -------------------------------------------------------
5722BR1 V5R2M0 020906 Recovering Your Entire System AS02
8/26/03 8:55:45 Page 12 of 19
If you have logical files whose based-on physical files are in a
different library, you must restore all based-on physical files
before you can restore the logical file.
---------------------------------------------------------------------
--- Attention -------------------------------------------------------
If you use journaling, the libraries containing the journals must be
restored before restoring the journaled files.
---------------------------------------------------------------------
Saved ----- ASP ------ Save Save Sequence Control Volume
Item Type Name Number Date Time Objects Omit Number Group Identifier
---------- ----- ---------- ----- -------- -------- ------- ----- --------- ---------- ----------
__ #LIBRARY *FULL *SYSBAS 00001 8/25/03 12:00:05 2 0 ITSMSAVE *TSM
__ AH *FULL *SYSBAS 00001 8/25/03 12:00:10 44 0 ITSMSAVE *TSM
__ ALEKN *FULL *SYSBAS 00001 8/25/03 12:07:42 5 0 ITSMSAVE *TSM
__ ANZFLTS *FULL *SYSBAS 00001 8/25/03 12:07:50 10 0 ITSMSAVE *TSM
__ APILIB *FULL *SYSBAS 00001 8/25/03 12:07:52 56 0 ITSMSAVE *TSM
__ APILIBSAV *FULL *SYSBAS 00001 8/25/03 12:08:01 51 0 ITSMSAVE *TSM
__ AS0301LIB *FULL *SYSBAS 00001 8/25/03 12:08:09 1 0 ITSMSAVE *TSM
__ AS0302LIB *FULL *SYSBAS 00001 8/25/03 12:08:11 1 0 ITSMSAVE *TSM
__ AS0303LIB *FULL *SYSBAS 00001 8/25/03 12:08:12 1 0 ITSMSAVE *TSM
__ AS0304LIB *FULL *SYSBAS 00001 8/25/03 12:08:14 1 0 ITSMSAVE *TSM
__ AS0305LIB *FULL *SYSBAS 00001 8/25/03 12:08:15 1 0 ITSMSAVE *TSM
__ AS0306LIB *FULL *SYSBAS 00001 8/25/03 12:08:17 1 0 ITSMSAVE *TSM
__ AS0307LIB *FULL *SYSBAS 00001 8/25/03 12:08:18 1 0 ITSMSAVE *TSM
__ AS0308LIB *FULL *SYSBAS 00001 8/25/03 12:08:20 1 0 ITSMSAVE *TSM
__ AS0309LIB *FULL *SYSBAS 00001 8/25/03 12:08:21 1 0 ITSMSAVE *TSM
__ AS0310LIB *FULL *SYSBAS 00001 8/25/03 12:08:23 1 0 ITSMSAVE *TSM
__ AS0311LIB *FULL *SYSBAS 00001 8/25/03 12:08:24 1 0 ITSMSAVE *TSM
__ AS0312LIB *FULL *SYSBAS 00001 8/25/03 12:08:26 1 0 ITSMSAVE *TSM
__ AS0313LIB *FULL *SYSBAS 00001 8/25/03 12:08:28 1 0 ITSMSAVE *TSM
__ AS0314LIB *FULL *SYSBAS 00001 8/25/03 12:08:29 1 0 ITSMSAVE *TSM
__ AS0315LIB *FULL *SYSBAS 00001 8/25/03 12:08:31 1 0 ITSMSAVE *TSM
__ AS0316LIB *FULL *SYSBAS 00001 8/25/03 12:08:32 1 0 ITSMSAVE *TSM
__ AS0317LIB *FULL *SYSBAS 00001 8/25/03 12:08:34 1 0 ITSMSAVE *TSM
__ AS0318LIB *FULL *SYSBAS 00001 8/25/03 12:08:35 1 0 ITSMSAVE *TSM
__ AS0319LIB *FULL *SYSBAS 00001 8/25/03 12:08:37 1 0 ITSMSAVE *TSM
__ AS0320LIB *FULL *SYSBAS 00001 8/25/03 12:08:38 1 0 ITSMSAVE *TSM
__ AS0321LIB *FULL *SYSBAS 00001 8/25/03 12:08:40 1 0 ITSMSAVE *TSM
394 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
__ QUSRINFSKR *FULL *SYSBAS 00001 8/25/03 14:17:13 1 0 ITSMSAVE *TSM
__ RCIBOL *FULL *SYSBAS 00001 8/25/03 14:17:16 51 0 ITSMSAVE *TSM
__ RETAILSTOR *FULL *SYSBAS 00001 8/25/03 14:17:49 28 0 ITSMSAVE *TSM
__ ROSHANT *FULL *SYSBAS 00001 8/25/03 14:17:53 5 0 ITSMSAVE *TSM
__ SAMP6961 *FULL *SYSBAS 00001 8/25/03 14:17:56 65 0 ITSMSAVE *TSM
__ SMOLEY *FULL *SYSBAS 00001 8/25/03 14:18:02 5 0 ITSMSAVE *TSM
__ SMTRACE *FULL *SYSBAS 00001 8/25/03 14:19:07 1,356 0 ITSMSAVE *TSM
__ SQELIB *FULL *SYSBAS 00001 8/25/03 14:19:46 2 0 ITSMSAVE *TSM
__ SURVEY *FULL *SYSBAS 00001 8/25/03 14:19:47 6 0 ITSMSAVE *TSM
__ SYSIBM *FULL *SYSBAS 00001 8/25/03 14:19:50 44 0 ITSMSAVE *TSM
__ TRADEAH *FULL *SYSBAS 00001 8/25/03 14:19:54 33 0 ITSMSAVE *TSM
__ TRADEB *FULL *SYSBAS 00001 8/25/03 14:20:53 33 0 ITSMSAVE *TSM
__ TRADESF *FULL *SYSBAS 00001 8/25/03 14:21:00 33 0 ITSMSAVE *TSM
__ TRADEXX *FULL *SYSBAS 00001 8/25/03 14:21:11 37 0 ITSMSAVE *TSM
5722BR1 V5R2M0 020906 Recovering Your Entire System AS02
8/26/03 8:55:45 Page 14 of 19
__ TRADE40AE *FULL *SYSBAS 00001 8/25/03 14:21:16 35 0 ITSMSAVE *TSM
__ VNCSAVF *FULL *SYSBAS 00001 8/25/03 14:33:30 13 0 ITSMSAVE *TSM
__ WASTOOLS *FULL *SYSBAS 00001 8/25/03 14:34:00 82 0 ITSMSAVE *TSM
__ WA01LIB *FULL *SYSBAS 00001 8/25/03 14:34:28 2 0 ITSMSAVE *TSM
__ WA02LIB *FULL *SYSBAS 00001 8/25/03 14:34:29 1 0 ITSMSAVE *TSM
__ WA03LIB *FULL *SYSBAS 00001 8/25/03 14:34:31 1 0 ITSMSAVE *TSM
__ WA04LIB *FULL *SYSBAS 00001 8/25/03 14:34:32 1 0 ITSMSAVE *TSM
__ WA05LIB *FULL *SYSBAS 00001 8/25/03 14:34:34 1 0 ITSMSAVE *TSM
__ WA06LIB *FULL *SYSBAS 00001 8/25/03 14:34:36 1 0 ITSMSAVE *TSM
__ WA07LIB *FULL *SYSBAS 00001 8/25/03 14:34:37 1 0 ITSMSAVE *TSM
__ WA08LIB *FULL *SYSBAS 00001 8/25/03 14:34:39 1 0 ITSMSAVE *TSM
__ WA09LIB *FULL *SYSBAS 00001 8/25/03 14:34:40 1 0 ITSMSAVE *TSM
__ WA10LIB *FULL *SYSBAS 00001 8/25/03 14:34:42 1 0 ITSMSAVE *TSM
__ WA11LIB *FULL *SYSBAS 00001 8/25/03 14:34:43 1 0 ITSMSAVE *TSM
__ WA12LIB *FULL *SYSBAS 00001 8/25/03 14:34:45 1 0 ITSMSAVE *TSM
__ WA13LIB *FULL *SYSBAS 00001 8/25/03 14:34:46 1 0 ITSMSAVE *TSM
__ WA14LIB *FULL *SYSBAS 00001 8/25/03 14:34:48 1 0 ITSMSAVE *TSM
__ WA15LIB *FULL *SYSBAS 00001 8/25/03 14:34:50 1 0 ITSMSAVE *TSM
__ WA16LIB *FULL *SYSBAS 00001 8/25/03 14:34:51 1 0 ITSMSAVE *TSM
__ WA17LIB *FULL *SYSBAS 00001 8/25/03 14:34:53 1 0 ITSMSAVE *TSM
__ WA18LIB *FULL *SYSBAS 00001 8/25/03 14:34:54 1 0 ITSMSAVE *TSM
__ WA19LIB *FULL *SYSBAS 00001 8/25/03 14:34:56 1 0 ITSMSAVE *TSM
__ WA20LIB *FULL *SYSBAS 00001 8/25/03 14:34:57 1 0 ITSMSAVE *TSM
__ WA21LIB *FULL *SYSBAS 00001 8/25/03 14:34:59 1 0 ITSMSAVE *TSM
__ WA22LIB *FULL *SYSBAS 00001 8/25/03 14:35:00 1 0 ITSMSAVE *TSM
__ WA23LIB *FULL *SYSBAS 00001 8/25/03 14:35:02 1 0 ITSMSAVE *TSM
__ WA24LIB *FULL *SYSBAS 00001 8/25/03 14:35:03 1 0 ITSMSAVE *TSM
__ WA25LIB *FULL *SYSBAS 00001 8/25/03 14:35:05 1 0 ITSMSAVE *TSM
__ WBL *FULL *SYSBAS 00001 8/25/03 14:35:06 6 0 ITSMSAVE *TSM
__ WDSCLAB *FULL *SYSBAS 00001 8/25/03 14:35:10 13 0 ITSMSAVE *TSM
__ WEBLIB *FULL *SYSBAS 00001 8/25/03 14:35:12 3 0 ITSMSAVE *TSM
__ WHOLESALE *FULL *SYSBAS 00001 8/25/03 14:35:15 13 0 ITSMSAVE *TSM
__ YANTZI *FULL *SYSBAS 00001 8/25/03 14:35:17 3 0 ITSMSAVE *TSM
****************************************************************************************************
STEP: Recover additional document library objects
Start date/time __________________ Stop date/time __________________ Duration _________________
You should restore the current version of your documents, folders,
and mail saved to TSM servers
If you are performing a complete system restore, run the following
command to continue:
STRRCYBRM OPTION(*RESUME)
Otherwise, run the following command(s):
STRRCYBRM OPTION(*ALLDLO) ACTION(*RESTORE) USEADSM(*YES)
Select and recover the following saved item(s) on the "Select Recovery
396 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
__ a. Vary off any Windows servers that are VARIED ON using the
following command:
WRKCFGSTS CFGTYPE(*NWS)
Select option 2 to vary off each server.
__ b. Create any needed Network Storages using the following command:
CRTNWSSTG NWSSTG(server-storage-name)
__ c. Add the links for each server description using the following
command:
ADDNWSSTGL NWSSTG(server-storage-name)
NWSD(server-description-name)
__ d. Vary on your Windows servers using the following command:
WRKCFGSTS CFGTYPE(*NWS)
5722BR1 V5R2M0 020906 Recovering Your Entire System AS02
8/26/03 8:55:45 Page 17 of 19
Select option 1 to vary on each server.
__ e. Restore the Windows server data using the following command and
the volumes listed in "STEP: Recover objects in directories":
RST OBJ('/QNTC')
****************************************************************************************************
STEP: Special Recovery Processing
Start date/time __________________ Stop date/time __________________ Duration _________________
Recovering Linux servers in a logical partition.
If Linux servers were running in a logical partition and were VARIED
OFF when the system was saved, perform these recovery steps:
__ a. Add the links for each server description using
the following command:
ADDNWSSTGL NWSSTG(server-storage-name)
NWSD(server-description-name)
__ b. Vary on each Linux server using the following command:
WRKCFGSTS CFGTYPE(*NWS)
Select option 1 to vary on each server.
****************************************************************************************************
STEP: Special Recovery Processing
Start date/time __________________ Stop date/time __________________ Duration _________________
IBM Content Manager OnDemand for iSeries (5722-RD1)
If Content Manager OnDemand for iSeries was installed when your
system was saved and has been restored to the system, use the
following commands to enable journaling:
__ a. CALL QRDARS/QRLCSTRJ PARM('RLC')
__ b. CALL QRDARS/QRLCSTRJ PARM('RLR')
__ c. CALL QRDARS/QRLCSTRJ PARM('RLO')
****************************************************************************************************
STEP: Apply journal changes
Start date/time __________________ Stop date/time __________________ Duration _________________
To determine if you need to apply journal changes, refer to the
5722BR1 V5R2M0 020906 Recovering Your Entire System AS02
8/26/03 8:55:45 Page 18 of 19
section "Determining Whether You Need to Apply Journaled Changes"
under chapter "Restoring Changed Objects and Applying Journaled
Changes" as detailed in the "Backup and Recovery" book.
****************************************************************************************************
STEP: Recover authorization information
Start date/time __________________ Stop date/time __________________ Duration _________________
You should recover authorization information if user profiles
were recovered in an earlier step.
--- Attention -------------------------------------------------------
Each of these operations can be a long running process.
---------------------------------------------------------------------
--- Attention -------------------------------------------------------
Some authorities may not be restored if the system is not running in
398 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
C
Important: The contents of this appendix are not supported by IBM. However, several
customers are using versions of the programs provided here.
This appendix follows the example to install the IBM Eserver pSeries (AIX) IBM Tivoli
Storage Manager client in OS/400 PASE. The iSeries server doesn’t have a native IBM Tivoli
Storage Manager administration client similar to other operating systems. A solution is to port
the AIX IBM Tivoli Storage Manager client code to OS/400 PASE. Although this is not
supported by IBM, it allows us to create interface programs between BRMS and IBM Tivoli
Storage Manager.
Note: At the time of writing this redbook, the IBM Tivoli Storage Manager V5R2 AIX client
code could not be ported to OS/400 PASE. All the examples in this redbook use the IBM
Tivoli Storage Manager AIX V516 client code.
This appendix also provides sample Command Language Program (CLP) code to show how
you can incorporate this function into your own IBM Tivoli Storage Manager server for OS/400
PASE environment.
400 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
This command restores the AIX client code to the IFS directory
/usr/tivoli/tsm/client/ba/bin/.
* This file contains an option you can use to specify the TSM
* server to contact if more than one is defined in your client
* system options file (dsm.sys). Copy dsm.opt.smp to dsm.opt.
* If you enter a server name for the option below, remove the
* leading asterisk (*).
************************************************************************
SErvername A27
************************************************************************
SErvername AS27
COMMmethod TCPip
TCPPort 1500
TCPServeraddress localhost
402 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Important: The program must have an IBM Tivoli Storage Manager administrative user
and password hardcoded in the program. Make sure that the program and command are
adequately secured by OS/400 security to ensure that only the authorized people are
allowed to use this function.
Important: The code in Example C-3 is case sensitive. You must type the directory
references in lowercase as shown in this example.
CHGCURDIR DIR('/usr/tivoli/tsm/client/ba/bin')
/**/
CALL PGM(QP2SHELL) PARM(&SHELL &CMD)
/**/
ENDPGM
You can use the sample command source shown in Example C-4 to create the
RUNTSMCMD command linked to the previously created RUNTSMCMD program.
Ending the IBM Tivoli Storage Manager server from a batch program
You can use the RUNTSMCMD command to end the IBM Tivoli Storage Manager server for
OS/400 PASE. The following example ends the IBM Tivoli Storage Manager server by
passing the IBM Tivoli Storage Manager server command HALT. You can add this command
to a BRMS control group exit to end the IBM Tivoli Storage Manager server before you save
and restart IBM Tivoli Storage Manager:
RUNTSMCMD TSMCMD(HALT)
404 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
/**/
IF COND(&TSMVOLON = '*YES') THEN(DO)
/**/
CALL PGM(TSMVOLON) PARM(&CPYPOOL)
MONMSG MSGID(CPF0000)
/**/
ENDDO
/*----------------------------------------------------------------*/
/**/
IF COND(&MOVMEDTSM = '*YES') THEN(DO)
/*----------------------------------------------------------------*/
/* Delay job 1 mins to allow for TSM to update BRMS files before */
/* running the BRMS MOVMEDBRM command */
/*----------------------------------------------------------------*/
DLYJOB DLY(60)
/**/
CALL PGM(MOVMEDTSM) PARM(&BRMMOVPCY)
MONMSG MSGID(CPF0000)
/**/
ENDDO
/**/
ENDPGM
/*----------------------------------------------------------------*/
/* Remove temp work files from IFS */
/*----------------------------------------------------------------*/
RMVLNK OBJLNK('/tmp/tsmdbboff.txt')
MONMSG MSGID(CPF0000)
/*----------------------------------------------------------------*/
/* Create temp work files */
/*----------------------------------------------------------------*/
/* */
CRTPF FILE(QTEMP/TSMTAPE) RCDLEN(133)
MONMSG MSGID(CPF0000)
/* */
CPYTOSTMF +
FROMMBR('/QSYS.LIB/QTEMP.LIB/TSMTAPE.FILE/T+
SMTAPE.MBR') TOSTMF('/tmp/tsmdbboff.txt') +
STMFOPT(*REPLACE)
MONMSG MSGID(CPF0000)
/* */
/*----------------------------------------------------------------*/
/* Query ITSM for DB backups ready to move offsite */
/*----------------------------------------------------------------*/
/* */
RUNTSMCMD TSMCMD(&CMD1)
MONMSG MSGID(CPF0000)
CPYFRMSTMF FROMSTMF('/tmp/tsmdbboff.txt') +
TOMBR('/QSYS.LIB/QTEMP.LIB/TSMTAPE.FILE/TSM+
TAPE.MBR') MBROPT(*REPLACE) STMFCODPAG(819)
MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL(ENDPGM))
/*----------------------------------------------------------------*/
/* Assign BRMS move policy to ITSM database tapes and update the */
/* the location parameter in ITSM */
/*----------------------------------------------------------------*/
START: RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(ENDPGM))
/**/
CHGVAR VAR(&TAPE) VALUE(%SST(&TSMTAPE 1 6))
CHGVAR VAR(&DEVCLASS) VALUE(%SST(&TSMTAPE 24 10))
CHGVAR VAR(&LOCATION) VALUE(%SST(&TSMTAPE 45 10))
/**/
IF COND((&MEDIACLS *EQ &DEVCLASS) *AND +
(&LOCATION *EQ ' ')) THEN(DO)
/**/
CHGMEDBRM VOL(&TAPE) MEDCLS(*SAME) +
406 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
MOVPCY(&BRMMOVPCY) TEXT('ITSM Database +
Backup')
MONMSG MSGID(CPF0000)
/**/
CHGVAR %SST(&CMD2 11 6) &TAPE
CHGVAR %SST(&CMD2 24 10) &DEVCLASS
/**/
RUNTSMCMD TSMCMD(&CMD2)
MONMSG MSGID(CPF0000)
/**/
ENDDO
GOTO CMDLBL(START)
/* */
ENDPGM: RETURN
/*----------------------------------------------------------------*/
ENDPGM
CHGCURDIR DIR(/)
MONMSG MSGID(CPF0000)
/*----------------------------------------------------------------*/
/* Remove temp work files from IFS */
/*----------------------------------------------------------------*/
RMVLNK OBJLNK('/tmp/tsmvolon.txt')
MONMSG MSGID(CPF0000)
/*----------------------------------------------------------------*/
/* Create temp work files */
/*----------------------------------------------------------------*/
/* */
CRTPF FILE(QTEMP/TSMTAPE) RCDLEN(133)
MONMSG MSGID(CPF0000)
/* */
CPYTOSTMF +
FROMMBR('/QSYS.LIB/QTEMP.LIB/TSMTAPE.FILE/T+
SMTAPE.MBR') TOSTMF('/tmp/tsmvolon.txt') +
STMFOPT(*REPLACE)
CPYFRMSTMF FROMSTMF('/tmp/tsmvolon.txt') +
TOMBR('/QSYS.LIB/QTEMP.LIB/TSMTAPE.FILE/TSM+
TAPE.MBR') MBROPT(*REPLACE) STMFCODPAG(819)
MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL(ENDPGM))
/*----------------------------------------------------------------*/
/* Update any empty offsite copy tapes to readwrite to delete from*/
/* ITSM and expire in BRMS */
/*----------------------------------------------------------------*/
START: RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(ENDPGM))
/**/
CHGVAR VAR(&TAPE) VALUE(%SST(&TSMTAPE 1 6))
CHGVAR VAR(&STGPOOL) VALUE(%SST(&TSMTAPE 24 30))
/**/
IF COND(&CPYPOOL *EQ &STGPOOL) THEN(DO)
/**/
CHGVAR %SST(&CMD2 12 6) &TAPE
/**/
RUNTSMCMD TSMCMD(&CMD2)
MONMSG MSGID(CPF0000)
/**/
ENDDO
/**/
GOTO CMDLBL(START)
/* */
ENDPGM: RETURN
/*----------------------------------------------------------------*/
ENDPGM
/
408 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
xx'' and access <> ''OFFSITE'' > +
/tmp/tsmcpyoff.txt"')
DCL VAR(&CMD2) TYPE(*CHAR) LEN(180) +
VALUE('update vol xxxxxx acc=offsite +
location=''OFFSITE''')
CHGCURDIR DIR(/)
MONMSG MSGID(CPF0000)
/*----------------------------------------------------------------*/
/* Remove temp work files from IFS */
/*----------------------------------------------------------------*/
RMVLNK OBJLNK('/tmp/tsmcpyoff.txt')
MONMSG MSGID(CPF0000)
/*----------------------------------------------------------------*/
/* Create temp work files */
/*----------------------------------------------------------------*/
/* */
CRTPF FILE(QTEMP/TSMTAPE) RCDLEN(133)
MONMSG MSGID(CPF0000)
/* */
CPYTOSTMF +
FROMMBR('/QSYS.LIB/QTEMP.LIB/TSMTAPE.FILE/T+
SMTAPE.MBR') TOSTMF('/tmp/tsmcpyoff.txt') +
STMFOPT(*REPLACE)
MONMSG MSGID(CPF0000)
* */
/*----------------------------------------------------------------*/
/* Query ITSM for Copy tapes to be moved offsite */
/*----------------------------------------------------------------*/
/* */
CHGVAR %SST(&CMD1 74 30) &CPYPOOL
/* */
RUNTSMCMD TSMCMD(&CMD1)
MONMSG MSGID(CPF0000)
CPYFRMSTMF FROMSTMF('/tmp/tsmcpyoff.txt') +
TOMBR('/QSYS.LIB/QTEMP.LIB/TSMTAPE.FILE/TSM+
TAPE.MBR') MBROPT(*REPLACE) STMFCODPAG(819)
MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL(ENDPGM))
/*----------------------------------------------------------------*/
/* Assign move policy to ITSM COPY tapes in BRMS and update the */
/* copy tapes in ITSM */
/*----------------------------------------------------------------*/
START: RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(ENDPGM))
/**/
CHGVAR VAR(&TAPE) VALUE(%SST(&TSMTAPE 1 6))
CHGVAR VAR(&STGPOOL) VALUE(%SST(&TSMTAPE 24 30))
/**/
IF COND(&CPYPOOL *EQ &STGPOOL) THEN(DO)
/**/
CHGMEDBRM VOL(&TAPE) MEDCLS(*SAME) MOVPCY(&BRMMOVPCY) +
TEXT('ITSM COPY Tape')
MONMSG MSGID(CPF0000)
/**/
CHGVAR %SST(&CMD2 12 6) &TAPE
/**/
/*----------------------------------------------------------------*/
RETURN
/*----------------------------------------------------------------*/
ENDPGM
410 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
D
Select the Additional materials and open the directory that corresponds with the redbook
form number, SG247031.
Using Windows FTP to transmit the TSMEXITSC save file to the iSeries
There are several different FTP and DOS command syntaxes to perform the file transfer. This
section uses the example the worked for us. After you have the save file (tsmexitsc.savf) on
the PC, complete these steps:
1. From your iSeries 5250 session, create a save file in a library of your choice (we use
QGPL in this example):
CRTSAVF FILE(QGPL/TSMEXITSC) TEXT('Receive SG247031 save file’)
2. From your PC, open a DOS prompt window and use FTP to transmit the save file to the
iSeries server (AS01, in our example), using the following commands:
ftp <your iSeries server name or IP address>
respond to the prompt with your <OS/400 user profile>
respond to the prompt with your <OS/400 user profile password>
bin
cd /qsys.lib
put tsmexitsc.savf qgpl.lib/tsmexitsc.file (replace
you set status messages until the transfer has completed
quit
412 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Figure D-1, starting at ftp as01, shows a complete successful transfer example.
Figure D-1 FTP example transferring an iSeries save file from a PC to an iSeries server
Remember to use the OS/400 Restore Library (RSTLIB) command for library TSMEXISTS:
RSTLIB SAVLIB(TSMEXITS) DEV(*SAVF) SAVF(QGPL/TSMEXITSC)
The publications listed in this section are considered particularly suitable for a more detailed
discussion of the topics covered in this redbook.
IBM Redbooks
For information about ordering these publications, see “How to get IBM Redbooks” on
page 416. Note that some of the documents referenced here may be available in softcopy
only.
Backup Recovery and Media Services for OS/400: A Practical Approach, SG24-4840
IBM Tivoli Storage Management Concepts, SG24-4877
IBM Tivoli Storage Manager Implementation Guide, SG24-5416
A Practical Guide to Implementing Tivoli Storage Manager on AS/400, SG24-5472
Managing OS/400 with Operations Navigator V5R1 Volume 3: Configuration and Service,
SG24-5951
Managing OS/400 with Operations Navigator V5R1 Volume 1: Overview and More,
SG24-6226
LPAR Configuration and Management: Working with IBM Eserver iSeries Logical
Partitions, SG24-6251
Tivoli Storage Manager Version 5.1 Technical Guide, SG24-6554
Backup Recovery and Media Services for OS/400: More Practical Information, REDP0508
Other publications
These publications are also relevant as further information sources:
IBM Tivoli Storage Manager for OS/400 PASE Administrator’s Guide, GC23-4694
IBM Tivoli Storage Manager for OS/400 PASE - Administrator’s Reference Guide,
GC23-4695
IBM Tivoli Storage Manager for OS/400 PASE Quick Start, GC23-4696
Backup and Recovery, SC41-5304
Job Scheduler for OS/400, SC41-5324
Backup Recovery and Media Services for iSeries, SC41-5345
Hierarchical Storage Management Use, SC41-5351
416 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Index
administrative user and password 403
Symbols ADSM
*IBM 314 name of previous release of ITSM 330
*PERM 337 value 266
*SAVCFG 314 Advanced Job Scheduler 141, 247
*SAVSECDTA 314 AIX 46
*SAVSYS 314, 377 administrative client in OS/400 PASE sample pro-
*SECOFR 38 grams 399
*SYNCLIB 325 core 362
*SYSBAS 278, 377, 380 dsmadmc command 402
*SYSGRP 29 kill command 362
/usr/tivoli/tsm/server/bin/core 362 ANALYST 38
ANR 1404 W TSM message 361
Numerics APAR 166
1 Gbps Virtual Ethernet LAN 329 API (application programming interface) 249
3494 tape 165 APIOPT member of QOPTADSM file 268
3583 tape 165 appending to volume data 172
3584 tape 165 application programming interface (API) 249
3584 tape library 102 apply journal changes 397
5250 interface 300 archive policy 158
for BRMS Application Client 265 Archive Retention 251
5698-ISX 47, 98 ASP (auxiliary storage pool) 10
5722JS1 141 authorization information recovery 397
5733-197 31 automated library 97
Automatically backup media information parameter 278,
280, 291, 320
A automatically select a device 233
access paths, saving 158 auxiliary storage pool (ASP) 10
Activate Policy Set 258 Auxiliary Storage Pool Device 277
activity log 358 availability services 374
help q actlog 360
Originator 358
policy domain 358 B
Policy Domain Name 358 backing up Lotus Domino servers 27
query actlog or q act 359 backup
search criteria 358 adding library TSMEXITS to a policy 194
search string 358 adjustments before saving 207
Session 358 before 207
Add Environment Variable (ADDDENVVAR) command Before, During, After properties 194
94, 265 control group versus backup policy 187
Add Job Scheduler Entries (ADDJOBSCDE) command customize IBM Data 200
173, 320 details 297
Add Media Class display 101 full or changes since last full 191
Add Media to BRM (ADDMEDBRM) command ADDMED- generic libraries 203
BRM command 165 history 296
Add Storage Location display 265 IBM Tivoli Storage Manager server example 187
ADDDENVVAR command 94, 265 strategies 31
adding a new administrator to ITSM 403 user data 200
adding media using a tape library device 181 using BRMS iSeries Navigator client 284
additional material 411 using the Tivoli Storage Manager Windows Client 89
ADDJOBSCDE command 173, 320 Where properties 210
ADDLICKEY command 135 backup activity override 223
admin password 59 Backup and Recovery Log 226, 248
administrative command line interface 37 backup control group 278, 314–315, 318–319
administrative interface 36 Backup Control Group Attribute display 279
418 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
examples 161 database volume wait 68
TAPMLBxx 161 DBSnapshot 124
TSMOFFSITE 340 default admin password 59
VAULT 161 default backup device 157
BRMS Net Device 330 default media class 157
Browse option 284 default media policy 157
byte stream file 105 default recovery log volume, removing 75
define dbvolume 67
define devclass command 103
C delay for copy storage pool 127
C program 98 delete restriction 271
case sensitivity 273, 403 delete TSM server 271
CD-ROM media 147 DELETION 97
Change Print File (CHGPRTF) command 322 dependent ASP 10
checkpoint processing 25 device class 35, 101, 103, 105, 163
in Backup Recovery and Media Services 325 Mount Limit parameter 102
CHGPRTF command 322 Mount Retention 102
client node 83, 260 device configuration 126
collocation 42, 107 Disaster Recover Manager (DRM) 130
command interface 250 disaster recovery 41, 105, 179, 346
common media pool 104 files in wrong order 179
communication protocol 261 QADBFDEP file 179
complete system recovery 325 requirements 122
concurrent backup 331 retrieval time 218
configuration for Tivoli Storage Manager server 127 Disaster Recovery Manager 41
connection 274 disk space 80
Connection Name 271 disk storage pool 78
control file 54 migrate to tape 110
control group performance 112
*BKUGRP 170 disk storage pool threshold 106
*SYSGRP 170 DISMOUNT 97
*SYSTEM 170 Display BRM Log Information (DSPLOGBRM) command
allow IPL 174 283
backup policy, deletion 171 Display Job Log (DSPJOBLOG) command 324
exit 325 Display Log (DSPLOG) command 284, 350
IBM delivered 171 Display Log for BRM (DSPLOGBRM) command 324
policies 169 Display Object Description (DSPOBJD) command 304
searchable text 173 domain 250
TESTSAVE 277 DRM (Disaster Recover Manager) 130
Control Language (CL) 98 dsmadmc command 402
copy group 113, 250, 254 DSMI_LOG 262, 264
copy storage pool 35, 105–106, 111, 341 dsmserv 54
reusing delay 127 dsmserv option
volumes 105 BUFPoolsize 76
volumes for user-written programs 341 DATEformat 76
core (AIX) 362 EXPINTERVAL 76
CPC3703 message 302 EXPQUiet 76
CPI3710 message examples 326 LANGuage 76
cumulative fixes 144 LOGPoolsize 76
customized cumulative PTF packages 144 MOVEBatchsize 76
MOVESizethresh 76
D TXNGroupmax 76
data area 330 dsmserv.opt.smp 75
QUSRBRM/Q1ATSMSIZ 330 DSPJOBLOG command 324
data protection 39 DSPLOG command 284, 350
data space 278 DSPLOGBRM command 283, 324
database and recovery log 35 DSPOBJD command 304
volumes 128 DSPPTF LICPGM(5722BR1) 153
database backup 124
database size 46, 66, 93
Index 419
E Group PTF 136
End Job (ENDJOB) command 363
End Job Abnormal (ENDJOBABN) command 364 H
END_BACKUPLTO_REC 121 help command 359–360
END_COPYLTO_REC 121 hierarchical space management 39
END_MIGR 120 history log 350
ENDJOB command 363 QHST 358
ENDJOBABN command 364 home location 161, 340
environment variable 174 prompt 161
adding for the OS/400 PASE time zone 94 home location for media prompt 161
considerations 265 HYPER fixes 144
DSMI_LOG 264–265
event 122
event record 122 I
exit (*EXIT) special value 325 IASP (independent auxiliary storage pool) 11, 278
exit program 97–98, 411–412 IBM Redbooks 415
registering 98 IBM Tivoli Storage Manager
EXPIRATION 98 copy group 254
expiration date 166 object view 250
expiration flag 166 Policy Domain 250
expire media (EXPMED) parameter 161 policy domain for BRMS 254
expire tape volumes 161 policy set for BRMS 257
expirecl exit program 104 QOPTADSM options file 261
expired copypool tapes for user-written programs 342 register a new node 260
expired volumes 162 Web Server Command 255
extend command 79 IBM Tivoli Storage Manager APIs (5733-197) 250
extending the database 67 IBM Tivoli Storage Manager Extended Edition 41
image catalog 151
add entry (ADDIMGCLGE) 152
F create 151
file archive 40 Include subdirectories option 232
file structure 66 incremental backup 124, 172
files during disaster recovery 179 independent ASP 11
finding restore results 247 independent auxiliary storage pool (IASP) 11, 170, 278
Fix Central 144 Information Center 151
Fix Central terminology 145 Informational APAR II09882 166, 344
flight recorders for BRMS 351 Informational APAR II12462 31–32
FTP 330 Informational APAR II12473 27
additional material 412 Initial ASP Group parameter 11, 278
download 147 Initialize BRMS (INZBRM) command 134, 136, 159
full backup 124, 156 install fixes 143
job scheduling 320 installing no-charge IBM Tivoli Storage Manager APIs
full iSeries backup and restore on BRMS Application Cli- 142
ent 312 installing PTFs using Virtual Media Installation 151
full iSeries system backup considerations 324 integrated file system (IFS) 66
full system backup restore considerations 324 browse option 284
full system recovery 325 OS/400 9
full system recovery report Internet address 267, 269
example 376 Internet port parameter 267
QP1ARCY spooled file 375 INZBRM command 134, 136, 159, 162
to tape 376 *DATA 159
to tape and Tivoli Storage Manager server 385 *DEVICE 159
full system save 28 IP Buffer Size 330
IP port 1580 37
G iPTF terminology 145
general media class 162 iSeries Access for Windows (5722-XE1) 137
GO BRMBKUPCY 313 iSeries Enterprise Editions Installation Assistant 48, 143
GO PTF 153 iSeries Information Center 151
GO PTF menu 151 iSeries Linux partition 41
group fixes 144 iSeries Navigator client 21
420 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
iSeries Navigator Taskpad area 230 maximum network performance 330
iSeries Navigator to set up BRMS Application Client 269 Media and Storage Extension (MSE) interfaces 160
iSeries server requirements 46 Media and Storage Extensions (MSE) 134
iSeries system recovery 312 media class 101, 104, 162, 179
ITSMLIB library 280 for Tivoli Storage Manager volumes 163
ITSMSERVER member name 277 ITSM volumes 163
ITSMSERVER member of QA1AOPT file 268 specific 162
Media class parameter 266
media information 165, 324
J media management by BRMS 337
Java Runtime Environment (JRE) 56 media movement 338
Java Swing-capable Web browser 56 commands and programs 411
job log 349 sample programs 338
job scheduler (OS/400) 320 media policy 158, 266, 280
job scheduler entries 322 default 157
job scheduling 320 name 266
journal changes 397 media pool 162, 179
journaled files 174 media removal 185
JRE (Java Runtime Environment) 56 Media Storage Extensions 137
media, manually adding 185
K message format 361
kill command 362 message queue 288
messages 314
MF30245 112, 332
L Microsoft Internet Explorer 5.0 56
language-specific support 264 migrate data to tape 110
libraries QBRM, QUSRBRM 135 migration policy 158
library recovery 378 model location 161
license 63, 258 Monitor Save While Active (MONSWABRM) command
iSeries Enterprise Edition 63 325
query 65 MONSWABRM command 325
Linux client on iSeries 41 MOUNT 97
LOCALE for ITSM 262 Mount Limit parameter 102
LOCALE tip 263 Move Media Report 167
location for move policy 158, 218, 337, 339, 344
user-written programs 339 attaching to backup policy 221
locations for home location 161
IBM Tivoli Storage Manager 215 Move policy parameter 266
logical partition (LPAR) 41, 240 MOVMEDBRM command 339
lowercase and uppercase 273, 403 MOVMEDTSM program 410
LTO2 tape devices 101 MOVMEDTSM user program 339
MSE (Media and Storage Extensions) 134
M
maintenance N
BRMS database files 178 naming tape volumes 162
reports 322 native data backup example 224
under BRMS 178 Net Device Buffer Size 330
maintenance reports 322 Net Device display 267
Management Central 226, 246, 293 Net device, type ITSMServer 272
assigned backup activity 292 Netscape Navigator 4.7 56
central system 138 Netscape Navigator 6.0 56
server jobs 139 network definition 157
server jobs job logs 139 network performance 330
task activity 247 new administrator 403
management class 113, 253, 255, 267 new volume 172
BRM 258 node environment 260
name 261 node name and password 261
manual drive 97 node registration 258
manual library 97 NODENAME parameter 262
map network drive 137 non-library IFS objects 325
Index 421
non-QSYS.LIB files 284 progressive incremental backup 42
NORMAL 123 PRTDSKINF command 331
ps -ef AIX command 362–363
PTF (program temporary fix) 47, 154
O PTF search 47
objects not allowed PTF SI09241 150
to be saved to a Tivoli Storage Manager server 313 PTFS and Cover Letters 147
when backing up to a Tivoli Storage Manager server public authorities 328
320
objects not backed up 156
OFFSITE 337 Q
omit backup item 314 q ses 294, 303
online resources 416 Tivoli Storage Manager server query session 282
OPERATOR 38 Q1ATSMSIZE data area 330
Option 33 46 QA1AGENPWD 328
option file 75, 127, 262 QA1AOPT file 268
QUSRBRM/QA1AOPT 277 QA1PRM data area 344
order and install fixes 143 QAANRSMP file 98
OS/400 IFS 9 QALWUSRDMN 135
OS/400 job scheduler 141 QANSAPI library 262
OS/400 job scheduling function 246 QAO1AOB BRMS database file 320
OS/400 PASE 7, 34, 42, 46, 332 QAO1AOD BRMS database file 320
ending Tivoli Storage Manager 362 QBRM, QUSRBRM libraries 135
prerequisite software for Tivoli Storage Manager 46 QEZJOBLOG 349
time zone 94, 96 QGPL 380
other publications 415 QGPL library 313
output queue 322 QHST 358
overwriting data 105 QIC media 325
QIC tape drive 313
QLOCALE system value 262–264
P QOPTADSM options file 262, 277
page 25 QP1ARCY report 30, 322, 375
PASE_TZ (time zone) 94 QP1ARCY spooled file 375, 385
PASSWORD GENERATE 327 qp2term 54, 362–363, 400–401
password management 249, 327 QSYS2 380
expiration 327 QSYS2 library 313
how password update works 328 QSYSLIBL 135
password rules 258–259 QSYSWRK subsystem 139
PASSWORDACCESS GENERATE 328 QTSM library 98
performance 249, 329 query command set 364
Performance Capabilities Reference Guide 330, 416 query sessions for save from BRMS Application Client
physical files during disaster recovery 179 282
physical media 23 query system command 364
POLICY 38 query Tivoli Storage Manager licensed information 65
policy 113, 156 query volhist (query volume history) 341
control group 169 query volhistory command 125
domain 113 query volume stg (storage) 341
set 113 QUSRBRM library 268, 288, 313
policy level 156 QUSRBRM/SAVE 324
policy set 252 QUSRSYS 380
Pool 1 10 QUSRSYS library 313, 322
port 1500 262 QUSRSYS/BRMS output queue 322
preparing IBM Tivoli Storage Manager server for produc- QUSRWRK subsystem 247
tion 93 QUTCOFFSET system value 94
primary storage pool 105 QYPSJSVR job 139
Print Disk Information (PRTDSKINF) command 331 QYPSSRV job 139
print recovery reports (PRTRCYRPT) 30 QZRCSRVS job 247
private disk pool 11
problem determination for Tivoli Storage Manager 357
product recovery 378 R
program temporary fix (PTF) 47 reclamation 108
422 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
recover additional user libraries 325 S
recover authorization information 397 sample code
recovery contacts 173 MOVMEDTSM program 410
recovery list 173 STRMNTTSM command 405
recovery log 75, 93 STRMNTTSM program 404
mode 123 TSMCPYOFF program 408
size 72 TSMDBBOFF program 405
volume removal 75 TSMVOLON program 407
recovery policy 158 SAVDOMBRM command 27
recovery report 30, 178, 325 Save DLO using BRM (SAVDLOBRM) command 169
example 324 save file 325, 412
validating 178 save file (SAVF) 22
Redbooks Web site 416 Save Folder List using BRM (SAVFLRLBRM) command
Contact us xiii 169
registration for Fix Central 145 Save Library using BRM (SAVLIBBRM) command 169
remote output queue 322 save message queue 325
removing the Tivoli Storage Manager default recovery log Save Object using BRM (SAVBRM) command 169
volume 75 Save Object using BRM (SAVOBJBRM) command 169
reports example 376 Save Objects by a List using BRM (SAVOBJLBRM) com-
requisite PTFS 147 mand 169
restarting the Tivoli Storage Manager server 95 Save Savefiles using BRM (SAVSAVFBRM) command
restore 169
Advanced Options 244 save scenario examples 187
considerations 32, 324 save scenario using the 5250 interface 277
from a Tivoli Storage Manager server 299 Save Storage (SAVSTG) command 160, 162, 177
library, its objects, or its members 238 Save System using BRM (SAVSYSBRM) command 169
scheduling example 246 Save While Active 278, 288, 331
select objects in the library to restore 241 *SYNCLIB 280
select the Date of the Save 240 checkpoint processing 325
session state 303 message queue 278, 324
specify media 243 save with append 104
tip 302 save-while-active
Restore - Summary window 244 *SYNCLIB 325
Restore directory and all files option 232 function 25
Restore Library (RSTLIB) command 412 implications 249, 325
Restore Licensed Program (RSTLICPGM) 143 message examples 326
Restore Licensed Program (RSTLICPGM) command 47 saving access paths 158
Restore option 300 saving backup media information 320
restore results 247 saving to a Tivoli Storage Manager server example 277
restore to same location 233 SAVMEDIBRM 323
restoring IBM Tivoli Storage Manager server SAVSTG command 160, 162, 177
as a batch job 236 SAVSYSPLUS 323
using iSeries Navigator 230 scratch tape 160
using the 5250 interface 234 search for fixes 144
restoring native OS/400 data 236 Secure media parameter 266
Retain Extra Versions 255 security 38
Retain Object Detail 278, 331 Select Recovery Items display 234, 301
Retain Only Version 255 Selective Setup in iSeries Access for Windows 137
retrieval time 218 Send PTF Order (SNDPTFORD) command 146
Retrieve Disk Information (RTVDSKINF) command 331 separating media between BRMS, Tivoli Storage Manag-
retrieve policy 158 er 163
REUSEDELAY parameter 127 sequential access storage pool 105
ROLLFORWARD 123 collocation 107
RSTLIB command 412 creation 109
RSTLICPGM command 47 sequential storage pool 108
RTVDSKINF command 331 sequential volume reclamation 108
run-time options 77 server address 88
RUNTSMCMD command 338, 403 Server Command window 62, 358
sample CLP code 403 server recovery file 125
Set ASP Group (SETASPGRP) command 11, 278
Index 423
set logmode command 123 synchronize libraries 325
SETASPGRP command 11, 278 SYSTEM 38
setting up BRMS Application Client using iSeries Naviga- system ASP 10, 278
tor 269 system backup outside of BRMS 177
sharing media between BRMS and IBM Tivoli Storage system data 312
Manager 104 system inactivity 158
shut down integrated servers 208 system policy 156–157
SI09241 136 System Policy (*SYSPCY) 161
sign off interactive users 208 system recovery report to tape 376
snapshot database backup 125 system values 134
software directory path 48
source files
exit programs 411 T
media management commands 405 tape 337
media management programs 411 tape flight recorder 351
Special Recovery Processing 396 tape library 97, 105
specific media class 162 automated library 97
spooled file 322 management 97
Start Backup with BRMS (STRBKUBRM) command 281 manual drives 97
Start Maintenance for BRMS (STRMNTBRM) command manual library 97
30, 161, 321 selection 216
Start Program Development Manager (STRPDM) com- sharing 163
mand 55 sharing between BRMS, ITSM 165
Start Recovery Using BRMS (STRRCYBRM) command USRDFN 97
30 tape library device 161
start the IBM Tivoli Storage Manager 236 cartridge names NL, CLN, BLK, IMP, SLT 169
START_BACKLTO_REC 121 tape library sharing 163
START_COPYLTO_REC 121 tape location 160
START_MIGR 120 example 161
started and last changed information 247 tape manager 97
starting, ending Tivoli Storage Manager server the first tape media movement 337
time 54 tape volume
STORAGE 38 Add Media to BRM (ADDMEDBRM) command 165
storage hierarchy 35, 105 layout 160
storage location 265, 269 linked to media class 179
edit 276 storage 162
edit, advanced 276 storage aspects 162
ITSMSERVER 265 target release 158
storage pool 35, 123 Task Activity 226, 247
migration 106 TCP/IP configuration and statements 329
storage pool volume 35, 105, 108 TCPPORT parameter 262
deletion 83 TCPSERVERADDRESS parameter 262
storing tape volumes 162 time value 54, 95
STRBKUBRM command 281 time zone 94
streamed file 105 tip
STREXPBRM command 161 BRMS backup status 293
STRMNTBRM command 30, 178, 321 BRMS logging activity 332
STRMNTTSM command 343, 405 iSeries Enterprise Editions Installation Assistant 48,
STRMNTTSM command and programs 404 143
STRMNTTSM program 404 recovery report 324
STRMNTTSM user command 338, 340 selecting Delay until job end 209
STRMNTTSM user program 338 Start Recovery using BRMS (STRRCYBRM) com-
STRMNTTSM user-written command 343 mand 301
STRPDM command 55 using BRMS iSeries Navigator with Advanced Job
STRRCYBRM 30, 380 Scheduler 141
Support Line contract 145 Tivoli Storage Manager 33
SWA message queue 278 activity log 358
SWA Message Queue parameter 316 additional server recovery files 125
switched disks 11 administrative command line interface 37
synchronization 26 administrative interface 36
administrative user and password 403
424 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
AIX V516 client 399, 412 restore considerations 42
APIs 31, 249–250 restoring the server as a batch job 236
APIs for BRMS 7 security 38
Backup-Archive Client 250 ANALYST 38
backup-archive concepts 40 OPERATOR 38
BACKUPPOOL size 79 POLICY 38
client 38–39, 258 STORAGE 38
API 39 SYSTEM 38
backup-archive 39 server address 88
data protection 39 Server Command window 62
for iSeries Linux partitions 41 server database file 268
hierarchical space management 39 server description 271
client node 83 server exit
collocation 42 DELETION 97
command interface 250 DISMOUNT 97
Command Language Program (CLP) 55 EXPIRATION 98
control file 54 MOUNT 97
copy group 250, 254 software directory path 48
database 278 storage hierarchy 35
database and recovery log 35 storage pool 123
database backup 124 Support Web page 365
database size 66 tape 337
database volume wait 68 tape manager 97
default database volume 74 troubleshooting 357
deleting storage pool volumes 83 USRDFN tape library 99
device class 103 V516 client
disaster recovery 41 code 401
Disaster Recovery Manager 41 configuring 401
domain 250 download code 400
downloading V516 client code 400 installing 400
ending from within OS/400 PASE 362 Version 5.2 clients 39
exit program 98, 412 volume 66
registering 98 volume status for user written programs 340
verification 103 Web administrative client
expired copypool tapes for user-written programs Web browser 56
342 Web administrative client interface 36, 56
help command 359–360 default port 57
installing the Windows client 84 Object view 60
installing V516 client code 400 Server Command window 260
license 63, 258 Show command line 59
query 65 starting 57
management class 253, 255 time out value 63
media management by BRMS 337 Web administrative client interface tree structure 59
media movement 338 Web Server Command window 358
message format 361 Windows client 85
mirroring database and recovery log volumes 128 backup 89
new administrator 403 for backup 89
node environment 260 without BRMS 97
node registration 258 Tivoli Storage Manager administrative client 37
password management 327 Tivoli Storage Manager APIs 142
how password update works 328 Tivoli Storage Manager Backup-Archive Clients 250
PASSWORD GENERATE 327 Tivoli Storage Manager client 250
password management expiration 327 Tivoli Storage Manager for OS/400 PASE Server 45
policy 113 Tivoli Storage Manager server 23, 55
policy set 252 adding a new administrator 403
problem determination 357 backup with Backup Recovery and Media Services
progressive incremental backup 42 128
PTF 47 batch mode 55
recovery log mode 123 components 34
recovery log size 72 configuration 59, 127
Index 425
displaying the configuration 364 Versions Data Deleted 255
ending from a batch job 404 Versions Data Exists 255
ending from a batch program 404 VFYMOVBRM command 344
ending with the ENDJOB command 363 view and edit saved fix orders 144
ending with the ENDJOBABN command 364 View backup history 296
for OS/400 PASE performance 332 virtual device 151
forcing the server to end 362 virtual Ethernet LAN 41
full iSeries system backup considerations 324 Virtual Media Installation (VMI) 143, 151
IFS files structure 66 VMI (Virtual Media Installation) 151
Internet address 267, 269 VMI catalog objects 154
IP port 34, 37 VMI maintenance 153
limitation 56 volume expiration 104
option file 75, 127 volume history 125
password 273 Volume Movement Report 344
password rules 258 volume name 162
port 262 volume status for user-written program 340
preparing for production 93
program 34
query command set 364 W
restarting 95 Web administrative client interface 37, 56, 250
run-time options 77 tree structure 59
setting the time zone 93 weekly activity 156, 278
time value 54, 95 weekly backup scenario 323
verifying that it is working 83 Windows client 85
Tivoli Storage Manager Web Administrative client 56 Work with Active Jobs (WRKACTJOB) command 362
total system recovery 320 Work with BRMS Devices (WRKDEVBRM) command
troubleshooting 267
BRMS (AIX command) ps -ef 362 Work with Control Groups (WRKCTLGBRM) command
ITSM- help set 360 277–278
ITSM messages 361 Work with Environment Variables (WRKENVVAR) com-
system qsh "cmd(’getjobid 791’)" example 363 mand 95
Tivoli Storage Manager for OS/400 PASE 357 Work with Image Catalog Entries (WRKIMGCLGE) 152
Tivoli Storage Manager on iSeries 357 Work with Job Scheduler Entries (WRKJOBSCDE) com-
Tivoli Storage Manager server configuration 364 mand 320
TSM (Tivoli Storage Manager) 270 Work with Links (WRKLNK) command 329
TSM Server Description delete 271 Work with Locations using BRMS (WRKLOCBRM) com-
TSM Server Retention 212 mand 161
TSMAIXCLIENT directory 304 Work with Media Classes (WRKCLSBRM) command
TSMAIXCLIENT path - backup 299 163
TSMCPYOFF program 404, 408 Work with Media Information (WRKMEDIBRM) command
TSMCPYOFF user program 339 300
TSMDBBOFF program 404–405 Work with Media using BRM (WRKMEDBRM) command
TSMDBBOFF user program 338 283
TSMEXITS 98, 187, 235, 411 Work with Policies using BRMS (WRKPCYBRM) com-
TSMTAPE user work file 339 mand 266
TSMVOLON program 404, 407 Work with Submitted Jobs (WRKSBMJOB) command
TSMVOLON user program 339 349
Work with User Jobs (WRKUSRJOB) command 350
WRKACTJOB command 362
U WRKCLSBRM command 101
uppercase and lowercase 273, 403 WRKCTLGBRM command 277–278
USEADSM(*YES) 301 WRKDEVBRM command 267, 330
user ASP 10 WRKENVVAR command 95
user data 200, 312 WRKJOBSCDE command 320
user disk pool 10 WRKLOCBRM command 161
USRDFN library 97 WRKMEDBRM command 283, 343
USRDFN tape library 99 WRKMEDIBRM command 300
WRKPCYBRM TYPE(*MED) 266
WRKSBMJOB command 349
V WRKUSRJOB command 350
V5R2 AIX client 399 WRLPCYBRM command 266
426 Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager
(0.5” spine)
0.475”<->0.873”
250 <-> 459 pages
Back cover ®
Use BRMS and IBM IBM Backup Recovery and Media Services (BRMS) for the IBM
Eserver iSeries server is the strategic solution to manage
INTERNATIONAL
Tivoli Storage Manager
backup, recovery, media, and storage in an iSeries-only TECHNICAL
for the most complete
environment. IBM Tivoli Storage Manager server and client products SUPPORT
iSeries-based
multiplatform are the tools that correspond to backup, recovery, media, and ORGANIZATION
protection storage management functions in a heterogeneous environment.
IBM offers a unique integrated solution by combining the proven
performance of BRMS on iSeries with the multiplatform capabilities
Use IBM Tivoli Storage of IBM Tivoli Storage Manager.
Manager to protect BUILDING TECHNICAL
your multiplatform In a multiplatform environment with iSeries servers, you can use the INFORMATION BASED ON
two products independently of each other. Or you can integrate them PRACTICAL EXPERIENCE
environment
to achieve powerful capabilities to back up and recover
mission-critical data and applications. Based on iSeries V5R2 BRMS IBM Redbooks are developed
Use BRMS to protect and V5.2 of IBM Tivoli Storage Manager, this IBM Redbook presents:
by the IBM International
your iSeries Technical Support
An overview of BRMS and IBM Tivoli Storage Manager Organization. Experts from
environment IBM, Customers and Partners
terminology, constructs, and capabilities
from around the world create
Examples of getting BRMS and IBM Tivoli Storage Manager timely technical information
server up and running on your iSeries server, and setting up your based on realistic scenarios.
iSeries server as the BRMS Application Client to an IBM Tivoli Specific recommendations
are provided to help you
Storage Manager server running on the iSeries server implement IT solutions more
Troubleshooting guidance and tips for integrating BRMS and IBM effectively in your
Tivoli Storage Manager server on the iSeries server environment.
iSeries user programs and OS/400 commands to help an iSeries
system operator to manage integrated BRMS and IBM Tivoli
Storage Manager server functions via a single user interface For more information:
ibm.com/redbooks