Management → Replication → Replication Merge Strategies
You can specify a properties merge strategy for the import procedure. Properties can be merged according to one of the following strategies:
Results for each merge strategy using example data cases are shown in the following table. These assume the import has already been performed once from the source server to the target server.
Initial data before second import | Properties Merge Strategy and import result on Target Server (Slave) | ||||
---|---|---|---|---|---|
on Master (M) | on Slave (S) | Override | Without conflicts | Master priority | Slave priority |
No changes |
No changes |
No changes |
No changes |
No changes |
No changes |
No changes |
Delete |
Data restored from M |
Data deleted |
Data deleted |
Data deleted |
No changes |
Edit |
Data restored from M |
Edited data from S |
Edited data from S |
Edited data from S |
Delete |
No changes |
Data deleted |
Data deleted |
Data deleted |
Data deleted |
Delete |
Delete |
Data deleted |
Data deleted |
Data deleted |
Data deleted |
Delete |
Edit |
Data deleted |
Conflict, stop import |
Data deleted |
Edited data from S |
Edit |
No changes |
Edited data from M |
Edit data from M |
Edit data from M |
Edited data from M |
Edit |
Delete |
Edited data from M |
Conflict, stop import |
Edit data from M |
Data deleted |
Edit |
Edit |
Edited data from M |
Conflict, stop import |
Edit data from M |
Edited data from S |
Add data on M |
Add data on S |
Only added M data |
Added M and S data |
Added M and S data |
Added M and S data |
Copyright © 2011–2019 Micro Focus or one of its affiliates. All rights reserved.