Re: BRMS - full save with least amount of restricted time

I looked at several of the files in /QIBM/UserData/OS/OSGi. They all seem
related to Eclipse. And I did have it open on my PC. Wonder what would
happen if I tried a *LINK SWA backup when not in RDP? I will try that
tomorrow. That's 40 of the 49 missed objects right there.

The other thing about the test on Saturday. I was the ONLY one on the
system. But since this backup normally runs at 3am, that will generally be
the case anyway. The only exceptions would be 1) the night crew manager
hasn't left yet (but he would get signed off at the start of the control
group anyway), or 2) a customer or sales rep transmits an order during this
time. That HAS been attempted during the backup, probably 3 or 4 times in
the last year. I think I can safely risk that as orders get retried
automatically.




On Mon, Jan 21, 2013 at 11:47 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

Jeff,

A couple of those you should just set to not back up as they are not
needed for a recovery:

byteware logs, not needed

Fax documents, you decide, but most folks do not back them up since in a
recovery you have the source document somewhere.

HTTPA admin logs - not needed for a recovery

OSGI, I don't have so I can't see into the directory but if they are log
files or flight recorders, again not needed for a recovery

MGTC - Management Collection objects, never needed for recovery. Only
reason to back them up is if you need archive of your performance data.
If you stop the performance collection prior to starting the save and
then start it again, you'll avoid this.

easypc/logs are all log files not needed for recovery so omit them.

I think that's about 90%+ of your list.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 1/21/2013 10:24 AM, Jeff Crosby wrote:

I tested this BRMS control group on Saturday:

10 *EXIT *DFTACT
20 *EXIT *DFTACT
30 *SAVSYS *DFTACT
40 UPSLIB *SYSBAS *DFTACT *YES *NO
50 QMPGDATA *SYSBAS *DFTACT *YES *NO
60 *EXIT *DFTACT
70 *IBM *DFTACT *YES *LIB
80 *ALLUSR *SYSBAS *DFTACT *YES *LIB
90 *ALLDLO *DFTACT *YES *YES
100 *LINK *ALLAVL *DFTACT *YES *YES
110 ALLSPLF *SPL *DFTACT
120 *EXIT *DFTACT
130 *EXIT *DFTACT

The *EXIT at sequence 60 returns the system to a normal state via CL
program starting the controlling subsystem and waiting on a data queue
entry from the QSTRUP program before proceeding. Everything after that

is

save while active. The entire control group took 90 minutes. The
restricted state portion took about 18 minutes. This is a vast

improvement

over what I'm currently doing, which is everything in restricted state,
which takes about 75 minutes.

*BUT* the *LINK backup had 49 objects not saved because they were in

use.

These were:

/Bytware/StandGuard/AV/logs/avsvr.log (1 object, a log file)
/FAXD01/RCVFAX/00000001.FAX. (1 object)
/QIBM/UserData/HTTPA/admin/logs/error_log.Q113011900 (1 object)
/QIBM/UserData/OS/OSGi (40 objects in this directory or a subdirectory)
/QIBM/UserData/OS400/MGTC (4 objects in this directory or a subdirectory)
/easy400apc/logs/access_log.Q113011900 (1 object)
/easy400apc/logs/basic_error_log.Q113011900 (1 object)

I have a feeling that trying to figure out a way to do these 49 objects
save while active would/will be an exercise in futility.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.