Re: Tape Rotation Schedule ?

["Ed Walraven" <ed_walraven@xxxxxxx>]

My thought is more simple....

Any system save over a week is to go back and save a user issue not a system
issue.

A Mt end to fix a place in time for the company is system function..

I feel that we in the IT can not overcome the User mistakes for weeks and
years to come.

Users have to accept the role of doing their job in a 7 day window.

If that does not cover the issue, then we need better users.

Doing a 30 day back-up for each day, Is Covering the user not the company.

Our job is to back up the information entered by the users.  We have and can
not have a position on the quality of data preserved...  We just back it up.

As far as I can say.... keep a week and do Mt ends (keep them forever) and
let the user explain the rest...

Ed Walraven
----- Original Message ----- 
From: "PaulMmn" <PaulMmn@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, August 22, 2003 9:10 PM
Subject: Re: Tape Rotation Schedule ?


> We had been keeping daily backups for 28 days.  We have upped that to
> 35 days so our daily rotation will include at least 1 month end.
>
> Month end tapes are sent off-site for permanent rotation.
>
> I keep sticking more things in the month end cases:  copies of purged
> files and libraries, SAVSYS, etc.  I hope to make the month end case
> a completely stand-alone rebuild of our systems.  (We currently would
> need to take the month-end case, plus SAVSYS, plus this stray piec,
> and that stray piece...)
>
> We use SAVLIBs for our backups.  SAVCHGOBJ usually ends up saving
> close to a complete library anyway, so SAVLIB is actually more
> efficient!
>
> --Paul E Musselman
> PaulMmn@xxxxxxxxxxxxxxxxxxxx
> _______________________________________________
> 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.
>