RE: BRMS and bare bones System Save

["Mike" <mshaw2456@xxxxxxxxxxx>]

Rick,

Bring up the backup policy via the BRMS add in for iSeries Navigator.  Right
click on the policy select Properites, click on After Backup.  There is a
tab at the top called Subsystems, click on this.  This will allow you to
start the subsystems back once the backup is done.

It's as easy as that!  :-)

Regards,

Mike Shaw
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rick.baird@xxxxxxxxxxxxxxx
Sent: Thursday, July 15, 2004 2:05 PM
To: midrange-l@xxxxxxxxxxxx
Subject: BRMS and bare bones System Save

Hey all,

I'm trying to setup a bare bones system save via BRMS.

We have several IXAs running and using iseries disk, and we want to
minimize the impact of bringing down those servers while saving restricted.

I have a BRMS backup control group that does most the following using exit
programs and save lists.

1.  end the IXA servers, in order using VRYCFG (this is important, because
2 of them are failovers to the others and have to be shut down in order).
2.  wait for these servers to shut down.
3  ENDSBS *ALL *IMMED
4.  save *SAVSYS
5.  save *ALLIBM
6. save '/QFPNWSSTG/*' (the IXA server data blob)
7.  STRSBS QSERVER and QSYSWRK
8.  STRTCP
9.  bring up the IXA servers.
10.  save 3 domino servers, and several other things
11.  bring the system back up to it's original state.

all unattended.

My question is this - how do I do step 11?

I see a lot of places where it shows how to bring the system into a
restricted state, but no place where it tells you how to bring it all back
up again.  Does an IPL simply run the QSTRUP procedure when bringing the
system back up?  or does it do other stuff?

Thanks,

Rick




--
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.