Midrange News for the IBM i Community


Posted by: Bob Cozzi
Rogue Programmer
Cozzi Productions, Inc.
Chicagoland
Data Mirroring/Replication?
has no ratings.
Published: 17 Apr 2012
Revised: 23 Jan 2013 - 1783 days ago
Last viewed on: 11 Dec 2017 (3244 views) 

Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.

Data Mirroring/Replication? Published by: Bob Cozzi on 17 Apr 2012 view comments(3)

I've looked at Remote Journalling and have a client that just needs very basic data mirroring between two like-configured systems. They don't need programs or users or other things; those can be managed/transferred on-demand.

What they want is a simple: "Keep the data on machine B in sync with machine A" where machine "B" is just sitting there waiting for the day when machine A fails or is destroyed or the power in that building goes out, etc.

I thought IBM released this back when the OS was still called OS/400? I guess not.

So if you don't want to spend the money on, or don't have the budget for one of the iTera, Vision, Mimix products, what do people use for backup/recover besides tape?

Return to midrangenews.com home page.
Sort Ascend | Descend

COMMENTS

(Sign in to Post a Comment)
Posted by: bdietz400
Premium member *
columbus, oh
Comment on: Data Mirroring/Replication?
Posted: 5 years 7 months 25 days 23 hours 1 minutes ago

there is a "how-to" for using remote journalling with very minimal programming.

i believe if you search for "shoestring remote journal" you get a hit to an article by Larry Y.

Posted by: bobcozzi
Site Admin ****
Chicagoland
Comment on: Data Mirroring/Replication?
Posted: 5 years 7 months 25 days 7 hours 34 minutes ago

Thanks found that article's link here.

Posted by: TFisher
Premium member *
Comment on: Data Mirroring/Replication?
Posted: 5 years 7 months 24 days 7 hours 21 minutes ago

If the data will only be updated from one machine at a time then you could also create a trigger program to capture changes and send to a DDM data queue and a batch process for the remote machine to apply those changes to the remote file.

 

I wrote a process that does this about 16 years ago and it worked really well with less overhead than journalling.