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



That was my next step down if the dual journals going remote was not possible (or feasible). As you say, better than I have now and a little ticker to manage. Not sure what happens in dual receivers if the remote one is not accessible for some period. Does it just wait and then send them all later or does the transaction fail like if a journal on a second ASP were to fill the ASP.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, July 26, 2011 7:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: Doing remote journals to the cloud

Remote journalling just for that to get up to the moment backups of transactions is an interesting idea.

I know that Jeff Crosby changes his journal receivers on the hour, saves the old ones and ftp's them offsite. Not as up to the moment but beats losing a whole days transactions.


Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Mike Cunningham <mike.cunningham@xxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/25/2011 05:27 PM
Subject: RE: Doing remote journals to the cloud
Sent by: midrange-l-bounces@xxxxxxxxxxxx



My thought was to dual journal local and remote. In the case of a disaster
that destroyed all data - fix the local system, restore last backup, copy
remote journals local and apply them. Not looking for a hot swap site,
just a place to keep journals so as not to lose a day's work if this were
to happen. We backup nightly and take that off-site both database and
journals but journals are on the same system so if the disaster where to
happen at the end of the next work day I would lose that days
transactions.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, July 25, 2011 1:10 PM
To: Midrange Systems Technical Discussion
Subject: Re: Doing remote journals to the cloud

We use Mimix.

I haven't heard if any of the offsite backup places like Vault/400 allow
you to remote journal to their locations.

I know of one person on this list who is offering cloud services for the
i. Maybe that could be done that way. Unless your transactions are
rather small, wouldn't that take a pretty good pipe?

Are your plans to restore on your home server, move the remote journal
changes back and then apply them? Or restore on the backup, Apply the
remote changes on the backup and then save and send the data back to
primary?


Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Mike Cunningham <mike.cunningham@xxxxxxx>
To: "midrange-l@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>
Date: 07/25/2011 12:40 PM
Subject: Doing remote journals to the cloud
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Does anyone on this list know if and 3rd party or IBM is talking about an
offering for iSeries customers to do remote journaling to the cloud? Keep

one copy local and send another to a remote server farm. That would give
is almost up to the second recovery capabilities in case of disaster. We
use the last backup and the journals form the cloud.

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.