|
You can sync bi-directionally or sync deletes
Not both .
Not sure about unison and PASE support.
On reliability side: RSync is widely used and comes standard with most NAS
devices
El mié., 27 de feb. de 2019 07:24, <Franz.Rauscher@xxxxxxxxxxx> escribió:
This is not working bidirectionally and most important it does not sync
the deletes.
No way to use rsync for this case in production environment.
there are some open-source tools (e.g. osync) based on rsync but i doubt
they are as stable as a client would expect an as400 solution.
greetings,
Franz
From: "Diego Kesselman" <diegokesselman@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 27.02.2019 14:11
Subject: Re: DFS-R like behaviour with two IBMi machines
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
Try with RSYNC
El mié., 27 de feb. de 2019 07:01, <Franz.Rauscher@xxxxxxxxxxx> escribió:
Hi!machines
I have a question according the sync of a ifs filesystem folder between
two IBMi machines.
I would like to have a folder like /shares/public on two IBMi server in
two different locations with a slow network between them.
is ist possible to sync the /shares/public folder between the two
bidirectionally so that the users on each of the to locations can worklist
with their local IBMi machine (via netserver share).
The solution should be comparable to Microsoft DFS-R (Distributes File
System - Replication)
I have not found a builtin solution. Remote-journaling does not help in
this case in my opinion because it does not apply the changes from
machine1 to machine2 and the other way around.
Greetings,
Franz
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.