-
1. Re: What is the status of replication and automatic synchronization of a backup server?
clebert.suconic Jan 13, 2012 5:46 PM (in response to skidvd)1 of 1 people found this helpfulWe are working towards it...
It will be on hornetQ 2.3... I'm not promising when it will be ready as it's hard to predict.. last time I promised something on forums took us 4 times more to finish it.. so I don't want that curse again
-
2. Re: What is the status of replication and automatic synchronization of a backup server?
skidvd Jan 13, 2012 7:40 PM (in response to clebert.suconic)Clebert,
Thank you for your reply and I can certainly understand where you are coming from.
Based upon the discprencies between the two user guides, I'm still left wondering though about what exactly is (or is not) in 2.1 and 2.2.5? Is there any replication, even with the manual restart synchronixzation as described in the 2.1 user guide, or is there really none at all? How about 2.2.5? Is is there really no replication at all and only shared disk options exists for failovers concerns in either of these releases?
Thanks again.
-
3. Re: What is the status of replication and automatic synchronization of a backup server?
gaohoward Jan 16, 2012 1:14 AM (in response to skidvd)Replication hasn't been ready in any of the releases (2.1 or 2.2.5).
Howard
-
4. Re: What is the status of replication and automatic synchronization of a backup server?
skidvd Jan 17, 2012 2:45 PM (in response to gaohoward)Thanks for the insight! FYI to others, the docs (especially the 2.1 version) can give you the wrong impression that replciation is there quickly.
-
5. Re: What is the status of replication and automatic synchronization of a backup server?
clebert.suconic Jan 18, 2012 10:43 AM (in response to skidvd)1 of 1 people found this helpfulIt was actually available in 2.1... However, there were issues with you having to sync the servers manually, and you would have issues also with split brain on 2.1..
Those issues were fixed on 2.2, but we couldn't finish replication as we would need some engineering to finish it... What's happening now.
So, in short it was availble on 2.1 but it wasn't acceptable by some of our users hence we are refactoring it now.