Ensuring sufficient iSeries system backup for data protection
Ken Graap explains how an option 21 save (full system save) once a month is not sufficient to protect system disk information if only a daily data backup is conducted.
SAVSYS
SAVLIB LIB(*NONSYS) ACCPTH(*YES)
SAVDLO DLO(*ALL) FLR(*ANY)
SAV OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT) +
('/QIBM/ProdData' *OMIT) +
('/QOpenSys/QIBM/ProdData' *OMIT))
UPDHST(*YES)
After you run these commands you will have a complete backup of your system. If you then just backup data files once a day, you won't be backing up the contents of the DLO or IFS file systems. This leaves a big hole in your backup strategy.
At a bare minimum I'd suggest that you do an Option 21 after any upgrade or any PTF maintenance followed by an Option 23 save on a daily basis. It executes the following save commands:
SAVSECDTA
SAVCFG
SAVLIB LIB(*ALLUSR) ACCPTH(*YES)
SAVDLO DLO(*ALL) FLR(*ANY)
SAV OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT) +
('/QIBM/ProdData' *OMIT) +
('/QOpenSys/QIBM/ProdData' *OMIT))
UPDHST(*YES)
You will need all of this data in order to recover your system. If you don't have time to run these save options, then you will need to come up with a more complicated save strategy that includes backing up changed objects, doing save while active saves, and possibly journaling objects.
Good Luck...
Dig Deeper on Data backup, storage and retrieval on iSeries
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.
Meet all of our AS/400 experts
View all AS/400 questions and answers
Start the conversation
0 comments