|
It ain't elegant, but the price is right. http://www.taatool.com/document/L_apyrmtjrn.htm Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Jim Franz" <franz400@xxxxxxx r.com> To Sent by: "Midrange Systems Technical midrange-l-bounce Discussion" s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 09/29/2004 10:09 Subject AM Re: remote journal Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> So what is a good system replication system for the budget impaired? ----- Original Message ----- From: <michael@xxxxxxxxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, September 29, 2004 9:16 AM Subject: RE: remote journal > I'm doing it, but on a pretty limited scale. I'm keeping a functional > business system in sync using jounalling, but it's only 4 files. I only > have to care about adds, changes and deletes. I dunno how scaleable my > solution is, especially when you get system events involved. File > journalling for a few files is one thing, system replication is quite > another. > > > -------- Original Message -------- > > Subject: remote journal > > From: "Jim Franz" <franz400@xxxxxxxxxxxx> > > Date: Wed, September 29, 2004 8:55 am > > To: MIDRANGE-L@xxxxxxxxxxxx > > > > How successful has homegrown remote journalling been in keeping > > multiple systems in sync vs buying a software package? Is anyone > > managing their own software for this? This is > > for a medium size mfgr, now consolidating systems, and thinking > > of using a surplus system as a disaster recovery site (connected > > via T1). > > jim > > -- > > 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. > > -- > 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. > > -- 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 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.