Hi A simple question... is there any way to "roll back" a multimaster database setup? Assuming you only take backup of one of the masters and then roll that master back, it will receive updates from the other masters because it is an older version.
You could stop all replication agreements and then initialize all consumers again, any other ideas thoughts?
Regards
________________________________________________________________________ In order to protect our email recipients, Betfair Group use SkyScan from MessageLabs to scan all Incoming and Outgoing mail for viruses.
________________________________________________________________________
Gerrard Geldenhuis wrote:
Hi
A simple question... is there any way to “roll back” a multimaster database setup? Assuming you only take backup of one of the masters and then roll that master back, it will receive updates from the other masters because it is an older version.
Not sure. If they still have the same replication generation, the other masters may be able to bring it back up to date. If not, then the only option is reinit.
You could stop all replication agreements and then initialize all consumers again, any other ideas thoughts?
Regards
In order to protect our email recipients, Betfair Group use SkyScan from MessageLabs to scan all Incoming and Outgoing mail for viruses.
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
389-users@lists.fedoraproject.org