RE: Save While Active

["Graap, Ken" <keg@xxxxxxxxxxxxx>]

>This would be a more dependable backup then the save while active.
>Saving files while in use can be a problem when it comes to a restore.  In
a
>properly set up database each table is not an entity onto itself.  Hence
the
>restore may create "Orphaned" records.  To prevent this the save while
>active requires a lot of monitoring and can't be used as your sole recovery
>method.  With good journaling and perhaps a main backup once per week you
>may be able to get it to work for you though.

As Al stated, simply quiecesing the system prior to running a SWA BU
prevents any problem.

I have a terabyte system and use BRMS with SWA to save it daily. I do a
SAVSYS once a month, full saves weekly and incremental saves during the
week. I also journal my production databases, data areas, data queues and
parts of the IFS. Down time to the user is just 1.5 hours when I take the
system down for a SAVSYS, and 15-20 minutes for all other backups. This
strategy has made it possible to provide over 98% up time to my users when
measured over a year. This includes time required to upgrade the OS yearly
and add hardware too!

We test our restore procedures regularly and have had only very minor
problems recovering our entire system at a hot site.

Save while active is a proven and safe way to save your system. I hardily
recommend using it to reduce your backup window!

Kenneth

****************************************
Kenneth E. Graap
IBM Certified Specialist
AS/400e Professional System Administrator
NW Natural (Gas Services)
keg@nwnatural.com
Phone: 503-226-4211 x5537
FAX:    603-849-0591
****************************************


-----Original Message-----
From: Eric Graeb [mailto:eric_graeb@kingoptical.com]
Sent: Wednesday, June 19, 2002 7:23 AM
To: midrange-l@midrange.com
Subject: Re: Save While Active