Table of Contents
Advertisement
22.2.1 Server quiesce
Before upgrading the server, the server instance should be as idle as possible.
Consider the following:
1. Perform the scheduled upgrade during a period of little of no activity if
possible.
2. Change the migration thresholds on the disk pools so as to move all the data
to the tape pools before starting the upgrade.
3. Make a copy or your server options file, dsmserv.opt.
4. Disable the central scheduler (add DISABLESCHEDS YES to dsmserv.opt)
5. Cancel all remaining processes and sessions (issue the disable sessions
command).
6. Add to the dsmserv.opt file EXPINTERVAL 0, which keeps expiration from
running at startup.
7. Add to the dsmserv.opt file the NOMIGRRECL option, which keeps both
migration and reclamation from running on the server at startup. Note that this
is an undocumented command.
8. After you complete the upgrade, you can merge the original server options file
to the current version, since some default options may have changed.
22.2.2 Backing up important components
Now, when the server is idle, you may proceed with the preparation steps, as
follows:
1. Back up your primary disk and sequential storage pools.
2. Back up your server database.
3. Back up device configuration file (devconfig).
4. Back up volume history (volhist).
5. Make a copy of the dsmserv.dsk files and keep it in a safe place, since it
contains database and recovery log volumes' file names and locations.
6. Make a copy of the dsmserv.opt files and keep in safe place, as it contains all
of your server instance options. Note that if you already made the
recommended changes to the server options file as described in the previous
section, you should already have saved a copy of the file.
7. Halt your server instance.
698
IBM Tivoli Storage Manager Implementation Guide
Advertisement
Table of Contents
