RE: remote journal

Jim...

        I have written a remote journaling product here at CMI and am
currently working on the documentation for the product. We offer it for sale
of course and have the ability to modify and enhance it at the will of our
customers. We also can contribute source code to a home-grown solution if
needed.

        I can tell you that the development and analysis time far exceeded
our original expectations as many issues  caused failures until they were
resolved. In the end though it has become a highly useful solution.

Please feel free to contact me off this list even if you are still
interested in developing your own solution.

HTH,

Ken Slaugh (707) 795-1512 x118 
Chouinard & Myhre, Inc. 
http://www.cm-inc.com/ 

DISCLAIMER: The information contained in this e-mail may be confidential and
is intended solely for the use of the addressee.  Access, copying or re-use
of the e-mail or any information contained therein by any other person is
not authorized.  If you are not the intended recipient, please notify us
immediately by returning the e-mail to the originator and destroying all
unauthorized copies.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Wednesday, September 29, 2004 5:55 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: remote journal

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.