Re: remote journal

[pnelson@xxxxxxxxxx]

My clients with a "backup system" are saving the important stuff to a save 
file, FTP it to the other box, and have the FTP program fire off a restore 
of the data. This happens each evening, so that in the AM, both systems 
have the same data. If the primary box fails during the day, the data that 
was entered onto it gets re-entered, and processes are re-run. It's a KISS 
principle solution.


Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx





"Jim Franz" <franz400@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/29/2004 09:09 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        Re: remote journal


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.