× 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.



Except from out Backup Documentation:

***********************************************************

Backups are performed on the System i5 for the purpose of Disaster
Recovery. The entire system is backed up to tape on a regular basis in
order to restore the system in the event of a catastrophic loss of the
system.

We use an IBM software package called BRMS/400 to organize our backup
procedures. These procedures are executed via jobs defined in our job
scheduling software (IJS/400) and/or via custom designed command
language programs (CLP).

Every Sunday evening all production and development data, along with
system security and configuration data, is fully backed up to tape. This
backup is sent offsite Monday morning along with BRMS recovery reports,
for 14 days and retained for 35 days.

If a Sunday is the last Sunday of the month, a system IMPL is done and
Program Temporary Fixes (PTF) are applied. Then the entire system,
including all system data, production data, development data, security
data and configuration data, is fully backed up to tape. This backup is
sent offsite Monday morning along with BRMS recovery reports, for 14
days and retained for 365 days.

Tuesday - Friday mornings, all changes made to production and
development data since the last full backup along with production
application journal receivers, security data, and configuration data are
backed up to tape. This backup is sent offsite for 8 days and retained
for 14 days, except for the Journal Receiver backup, which is sent
offsite along with BRMS recovery reports, for 14 days and retained for
16 days.

Saturday morning, the system isn't quiesced and only production Journal
Receivers and BRMS/400 data are backed up to tape. This backup is sent
offsite Monday morning along with BRMS recovery reports, for 14 days and
retained for 16 days.

***********************************************************

Note:

Downtime for a M/E backup is approximately 3 hours...

Downtime for a weekly backup is approximately 45 minutes...

Downtime for a daily backup is approximately 20 minutes...

Kenneth

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Willie J. Moore
Sent: Monday, April 23, 2007 2:51 PM
To: Midrange-System (E-mail)
Subject: SAVSYS & SAVLIB(NONSYS) during week

Well management has changed their minds again. At first the decided that
if month end fell during the week, the month end procedures would stay
the same. Now they do not want the lengthy down time that it would
require.
Among other Net Work saves, we also stop the Sub-Systems and do a SAVSYS
and SAVLIB(NONSYS). They do not want to give up the convenience and
security that this kind of backup gives.
I would like to here from others on how they handle these two save if
done during the week, or how they handle a month end backup during the
week.
I am begging to see Dilbert's point of view...
Thanks,
William Moore


--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.