|
Cyndi, Lets pretend that today is Wednesday and a disaster occurs at your building. The building is in a state that you are denied permission to enter by emergency services (fire, police, FEMA). How would you reconstruct the data from last week up to today? You could be denied permission to enter the building and retrieve your daily tapes due to (1.) an earthquake results in structural damage, (2.) a chemical spill prohibits anyone in the area for the next 3 days., (3.) a fire rages for longer than the safety rating of your safe and the back up media is useless, (4.) a tornado results in structural damage. A true disaster recovery plan has consideration of restoring at another site by using data, supplies, etc. that are secured away from the normal business location. I realize that the odds of these types of events are quite low. However, it is my understanding that nearly 80% of business that experience a disaster and are not able to recover their critical applications and data are out of business within six months. HTH Richard Shealy DCS Software and Services 800/999-2495 ----- Original Message ----- From: "Cyndi Bradberry" <CyndiB@IHFA.ORG> To: <MIDRANGE-L@midrange.com> Sent: Wednesday, April 25, 2001 11:50 AM Subject: RE: Backup Policy > We created our own procedure that does the equivalent of a Go SAVE 23 Save > User Data. We submit everything to a JOBQ that is on hold and a separate job > checks the time to release the JOBQ. Whenever there is a change to the > system, PTF's etc, someone comes in on the weekend and does a Go SAVE 22 > Save System Data Only. Once a week on Thursday, the tapes are sent to an > off-site storage facility. Daily tapes are kept in a Fire Vault in another > room. All tapes are rotated every three weeks. > At this time, this appears to be working for us. We just moved from one box > to another, using the tapes produced as above. Everything works fine. > If you can poke holes in this, please let me know. > > Cyndi B. > Boise, ID > +--- > | 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 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.