Downgrade Guide
If you need to switch back to an older BPC version, you can use the General downgradewhich should work in most cases. If this is not possible due to an error with the model versions of the internal configuration, then Downgrade in case of different versions of the internal configuration will certainly help.
General downgrade
The following is the procedure if the BPC version to be replaced has not migrated the internal configuration. Under Affected versions the BPC versions are listed for which a migration was carried out.
Downgrade in case of different versions of the internal configuration
As described under Versioning of the internal BPC configuration, it happens from time to time that the internal model of the BPC configuration changes.
This is located in the OpenSearch index with the alias bpc-configuration.
When a new version of the BPC Core module is started, the settings from the bpc-configuration index are migrated to the next version of the internal model if necessary.
Once this has been done, it is not possible to restore or roll back to an older BPC version.
In this case, a snapshot/backup of the bpc-configuration index must be restored, which matches the version of the "older" BPC.
Procedure
The steps required for this are shown here.
1karaf must be started
-
Copy the jar/war files of the previous/older BPC version into the
karaf/deploydirectory. This must be done first, otherwise the still installed/updated BPC core will run and migrate the index again. -
Open the Karaf console
-
List the snapshots/backups of the
bpc-configurationindex with the BPC configuration:bpc:backup-list bpc-configurationThe snapshots that can be used from this version are marked and only these can be restored.
5restore the appropriate snapshot
+
bpc:backup-restore <snapshot-name-vom-schritt-davor>+ Snapshots with newer model versions cannot be restored.
|
If the commands If the Always assuming that snapshots of the |
