Univention Bugzilla – Bug 50038
backup2master: describe risks about potential newer defaults
Last modified: 2019-08-21 17:10:32 CEST
Scenario: * DC Master has been installed a few years ago * DC Backup has been installed yesterday * DC Backup is promoted to DC Master using "backup2master" As we change some UCR settings and other defaults only for newly installed machines, the configuration and therefore behavior of the new DC Master might be different from the DC Backup. We should describe the risk in the documentation and give some hints how to mitigate them (i.e. compare "ucr dump"). One Example: newer installations of univention-s4-connector add attributes to the mapping.
Additional note about the example: For package based Apps the App Center will install e.g. schema extension packages on DC Backups during app installation. They will be missing if the DC Backup was 'just' added.