|
midrange.com
I'm not challenging you on this AL but adding to this thread, I never hear
of anyone using GO ASSIST for doing saves on this list. It's a great menu
system for saving data. If your doing an ENTIRE SYSTEM save, it will put the
system in the restricted state and restart the system after it completes the
save. For somebody like Sue, she could suggest to this company she is
dealing with to use GO ASSIST.
Art
-----Original Message-----
From: Al Barsa, Jr. [mailto:barsa2@ibm.net]
Sent: Monday, April 03, 2000 11:27 AM
To: MIDRANGE-L@midrange.com
Subject: Re: DR Plan - Got one? Will it work?
At 11:02 AM 04/03/2000 -0400, you wrote:
Hi,
Our save strategy is to do a save option 21 periodically,
and then to do a
save of changed objects every day from every library,
referencing the
date/time of the save option 21. We happen to use the
SAVALLCHG command in
TAA Tool, which predates SAVCHGOBJ's ability to specify
LIB(*ALLUSR). It
addition we do a SAVSECDTA and a SAVCFG every day, both of
which do not
require a restricted state.
IMHO, this is sufficient. I welcome anyone who would like
to challenge this.
Al
>Friends,
>
>Myself and others have spent the past 10 days or so
assisting a company in
>recovering lost data from a failed AS/400. Trust me, it
wasn't fun. Now
>the point is not that the 400 failed. (We all know that
doesn't happen very
>often). What's important is that the backup and recovery
plan of this
>organization didn't work. Some critical files could be
recovered from the
>previous night's backup, but others had to be recovered
from a SAVSYS that
>was almost 2 weeks old at the time of the crash.
>
>I don't wish to bore any of you with the details of the
recovery, I just
>want you to think about your company and your plan. Do you
have a plan?
> Have you tested it? Have you tried a 'hot site'
recovery? Are there
>manual procedures for the users while the system is
unavailable? The
>information tucked away in that pretty, black box is a
company asset. Are
>you doing all you can to protect it?
>
>Food for thought,
>Sue
>
>
>+---
>| 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
>+---
+--------------------------------------------------+
| Please do not send private mail to this address. |
| Private mail should go to barsa@ibm.net. |
+--------------------------------------------------+
Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.
400 > 390
Phone: 914-251-1234
Fax: 914-251-9406
http://www.barsaconsulting.com
http://www.taatool.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 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.
