Backup and Recovery
IBM's Knowledge Center should be where you get a bulk of your information regarding backup and recovery. What we hope to cover here are items which may be lacking on their site.
It is considered a 'best practice' to keep track of IBM objects you may have changed in a CL program that you can run after an OS upgrade or after a complete system restore. While one would hope that a complete system restore would get these back, experience has shown that IBM is sorely lacking in a few places. Items you may contain in this CL program may include:
- CHGCMDDFT operations to change commands to default to your preferences.
- GRTOBJAUT operations that change IBM object authority. For example changing RSTOBJ to *PUBLIC *USE.
If you are backing up in preparation for a system migration or DR test this might be a good time to review a few things.
- If you have a program that you run after any OS upgrade or system restoration you might want to ensure that it is current.
- If you have save files that you use to restore shell files for batch processing you may want to record what these are for after the restoration.
- It's a good idea to get a copy of your network attributes (DSPNETA).
- It's a good idea to get a copy of your system values (WRKSYSVAL). The system recovery process has you change several for the restore process. You may wish to change them back to your desired values after the restore.
- You may also wish to consider getting a copy of your PTF listing (DSPPTF).
- If you generally do not save spool files you may wish to consider doing so.
- Use the option to save access paths. It could take days to rebuild otherwise. IBM changed the commands to default to saving access paths. Some shops changed them back hoping to reduce their save times and to use less tape space.
- People should be aware that any history from STRSQL is not saved. If history is important they should look at "run sql scripts" from System i Navigator or some other solution.
- Keep track of all vendor software on your system and how to get keys to run their software on your new machine.
- If you are using a High Availability package discuss your plans with your vendor. Some have detailed operations which must be performed in an exacting manner to get journal receivers in a usable state.
- If you are using a High Availability package follow that vendors instructions carefully.
- Make sure you run your program to change certain IBM supplied objects. This program was mentioned in Backup. See also http://www-01.ibm.com/support/docview.wss?uid=nas8N1017745
- Apply software keys
- Repackage any shell save files to avoid lack of coding ALWOBJDIF(*ALL) potentials.
Pages in category "Systems Management"
This category contains only the following page.