I carefully checked the log to see how long the SAVSYS took. It was only 45 minutes, but I did notice a message indicating interactive users are allowed to stay active.
The save *IBM took one hour. The rest of the time was for the save *ALLUSR.
I have two questions:
1. Doesn't a SAVSYS require the system to be in a restricted state? So how does this work based on the message that says "Interactive users are allowed to stay active."
2. Is there a way to cut this time? This is a 24/7 warehouse operation, so I don't understand how they got away with this for so long! I most likely will have to cut up the backup process. I tested SAVWHILEACTIVE with two libraries (4009 objects -- it took 4.5 hours). There are 30759 objects with just the save *ALLUSR.
IBM has published whitepaper that will walk you through how to shrink your backup window. You can view it a here.
IBMer Debbie Saugen presented a great session on shrinking backups, at several technical conferences. You can view her presentation slides here.
Dig Deeper on Data backup, storage and retrieval on iSeries
Related Q&A from Ken Graap
The BRMS Network feature allows a BRMS system to connect to other BRMS systems via a network, and enables a user to consolidate media such as backup ... Continue Reading
The only option to correct damage preventing file journaling is to use the RCLSTG command. Continue Reading
IBM's iSeries Backup and Recovery manual answers many questions related to system backup and disaster recovery. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.