Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:14
From version 4.1
edited by eMagiz
on 2022/11/22 12:42
Change comment: There is no comment for this version
To version 5.1
edited by eMagiz
on 2022/11/22 12:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -30,7 +30,8 @@
30 30  
31 31  Whenever this situation occurs, a user can navigate to the Deploy architecture of the model. The details of the specific runtime (right-click option) can be opened and a release can be selected. That release should be the previous release where the runtime was operating normally. Once selected, press Save and choose the Deploy Runtime option (right-click option) on machine level. This will force that specific runtime to load the previous docker image.
32 32  
33 -
33 +[[image:Main.Images.Microlearning.WebHome@assessing_impact_runtime_images_disaster_recovery.png]]
34 +
34 34  === 3.4 Approach ===
35 35  
36 36  It is usually best to update the test and acceptance environment first and leave that running for a certain grace period. So that in case potential issues can be fixed still.