We have a job on the basic job scheduler that starts at 3:00 am, kills
the subsystems we want to shutdown for backup, then we do a SAVE command
for *ALLUSR which includes some IBM libraries including QUSRSYS. We also
do a SAVCFG, SAVSECDTA, then a SAV of the IFS as shown below (we skip
our image files in the IFS on this save)
SAV DEV('/QSYS.LIB/TAP01.DEVD') OBJ(('/*') +
('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT) +
('/QNTC' *OMIT) ('/QFPNWSSTG' *OMIT) +
('/QIBM/UserData/OS' *OMIT) +
('/RJSIMAGEDOC' *OMIT)) ENDOPT(*LEAVE) +
After this IFS save we start subsystems back up and then a SAV of the
IFS image files)
SAV DEV('/QSYS.LIB/TAP01.DEVD') +
OBJ(('/RJSIMAGEDOC*')) ENDOPT(*LEAVE) +
USEOPTBLK(*YES) UPDHST(*YES)
Been wanting to switch this over to the newer SWA technique to reduce
the time we are offline at night but other projects have gotten in the
way
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of as400
Sent: Thursday, June 07, 2007 12:52 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Backup strategy
We're currently reviewing our backup strategy.
What I would be interested to hear is how other shops handle the QUSRSYS
library.
- Do you back it up as part of your nightly saves?
- If not, how often do you back it up?
- How do you back it up?
(e.g. SAVE21 only, SWA, or shutting down everything holding locks
within it, then SAVLIB)?
Somewhat related: Job Q1PSCH (PM/400 scheduler) is holding a lock
within QUSRSYS. Is there an easy way to stop/start this job for backup
purposes?
Thanks,
Moe
midrange.com
