× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Backup Policy
  • From: "alan shore" <SHOREA@xxxxxxxx>
  • Date: Wed, 25 Apr 2001 09:55:00 -0400

You ask if a 21 save is enough? The answer is - probably NOT. How often do you 
do a 21 save? Every day, once a week, once a month, once ETC. What about Save 
any changed objects SINCE the LAST 21 save. Saving the security, etc. All I'm 
saying is , a backup policy needs to be investigated. Each sites policy will be 
pertinent for that site. 
Our policy is a FULL sytem save every weekend, and month-end. The month-end 
system save tapes are duplicated,  a copy sent off-site for disaster recovery 
purposes. Every night we back up the production data library prior to starting 
the day-end cycle. Once the day-end cycle is finished, we SAVE CHANGED OBJECTS, 
as well as saving the security data. 

>>> Jim Cannon <JimC@Arizonabiltmore.com> 04/24/01 02:55PM >>>
These are useful sites for general knowledge of the subject....but I think
most of us are interested in AS/400 shops. Is a '21' save enough? If not,
why not? 

Maybe there is some proud department head out that that would share his with
us via direct email????



Jim Cannon
Systems Specialist
Arizona Biltmore Resort and Spa

 -----Original Message-----
From:   MacWheel99@aol.com [mailto:MacWheel99@aol.com] 
Sent:   Tuesday, April 24, 2001 9:03 AM
To:     MIDRANGE-L@midrange.com 
Subject:        Re: Backup Policy

Another useful URL when crafting / reviewing a backup policy might be

http://www.TechRepublic.com/forumdiscuss/thread_detail.jhtml?thread_id=17159 

Disaster Recovery Policy & Procedures

What all needs to be protected & does your policy in fact protect all that?

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com 
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com 
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.