Re: Modernizing applications (was: Explaining single level store to non ipeople) -- MIDRANGE-L

Subject: Re: Modernizing applications (was: Explaining single level store to non ipeople)
From: ALopez@xxxxxxxxxx
Date: Thu, 20 Aug 2009 13:24:20 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

A random scattering of files. There's no commitment control on anything,
so these are after images only. The sad part is that the files in
question would not be enough to fix anything, we'd be better off calling
the day a loss and having everyone key in the whole day again.

The problem is that they were setup in the early 90's when they didn't have
much spare DASD and no software that could make use of journaling. The
thought seemed to be that with journal receivers in another ASP and daily
backups, we could recreate the main ERP ASP if it suffered a complete
crash.

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.