If we perform a CUC upgrade (e.g. 188.8.131.520 to 184.108.40.20600) to the inactive partition but choose not to reboot until a few weeks (even months) down the line. Am i correct in thinking that at the point we switch versions, the current database from the lower version (in the active partition) is migrated to the newer (e.g. 220.127.116.1100) version. All messages will be also be preserved in the common area.
If the inactive partition is at a lower revision this database migration does not occurr if we choose to role back weeks / months down the line.
Would a valid DR scenario therefore be:
Upgrade inactive partition to later relase
Leave later version in inactive patition running
In the event of a failure* to the active partition: simply switch to later version on inactive partition
All current data will be migrated to new version on incative partition
*This failure should not be severe enough to prevent the database migration / switchover.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.