RE: backup scenario

Hi Simon

Ignoring *IBM, if you can save *ALLUSR every day, why wouldn't you ?

Not using SAVCHGOBJ reduces the complexity of the recovery - if the window
permits a full save then it doesn't make sense to only do a partial save
unless there's some other constraining factor (e.g. tape).

I'd rather use SWA than SAVCHGOBJ if I had a constrained backup window. I
might consider SAVCHGOBJ if I was constrained by tape space.

SAVCHGOBJ also introduces a relationship between the backup that uses it and
the last full backup it depends on. MY experience is that many sites don't
understand these relationships which makes their backup regime much more
error prone and likely to be broken.

Regards
Evan Harris



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Thursday, 25 September 2008 10:36 a.m.
To: Midrange Systems Technical Discussion
Subject: Re: backup scenario


On 25/09/2008, at 8:02 AM, JDHorn@xxxxxxxxxxxxxx wrote:

is the savsysinf/savsecdta/savcfg/sav *ibm every day overkill?

Depends on how often you change system information, profiles and
authority, or device configuration. If you can afford the time then
it's better to run them than not.

Why savlib *IBM every day? These generally don't change at all.

Why savlib *ALLUSR every day instead of savchgobj *ALLUSR?

Why savdlo every day instead of savdlo REFCHGDATE(*SAVDLOALL)?

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------