Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:14
From version 14.1
edited by Erik Bakker
on 2024/06/24 14:16
Change comment: There is no comment for this version
To version 16.1
edited by Erik Bakker
on 2024/06/24 14:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -45,12 +45,16 @@
45 45  
46 46  === 3.3 Disaster recovery runtimes ===
47 47  
48 -In particular cases, a runtime may not function properly after a specific release is done. That means the flows in that runtime are not 100% compatible with the runtime image used to create the container images. One example of this can happen is when there hasn't been a deployment for many months, and the new runtime images will contain significant changes. Effectively, that means that the Runtime Image delivered by eMagiz is incompatible with the flows in that runtime. As a result, action is needed at eMagiz to update the runtime image or assist you as a client in resolving the issue within the constraints of the new runtime image. This situation is expected to be very exceptional. We at eMagiz need to be informed if you encounter such a situation. As part of our regular process and agreements with our partners and clients, we need a registered ticket from our Support department to act upon this.
48 +In particular cases, a runtime may not function properly after a specific release is done. That means the flows in that runtime are not 100% compatible with the runtime image used to create the container images. One example of this can happen is when there hasn't been a deployment for many months, and the new runtime images will contain significant changes. Effectively, that means that the runtime image delivered by eMagiz is incompatible with the flows in that runtime. As a result, action is needed at eMagiz to update the runtime image or assist you as a client in resolving the issue within the constraints of the new runtime image. This situation is expected to be very exceptional. We at eMagiz need to be informed if you encounter such a situation. As part of our regular process and agreements with our partners and clients, we need a registered ticket from our Support department to act upon this.
49 49  
50 -Should this situation occur, you can navigate to your model's Deploy architecture. The details of the specific runtime (right-click option) can be opened, and on the "Basic" tab, you can select an older release. 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 the machine level. This will force that specific runtime to load the previous docker image.
50 +In this situation, we can navigate to your model's Deploy architecture. The details of the specific runtime (right-click option) can be opened, and on the "Basic" tab, you can select an older release. 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 the machine level. This will force that specific runtime to load the previous docker image.
51 51  
52 52  [[image:Main.Images.Microlearning.WebHome@assessing_impact_runtime_images_disaster_recovery.png]]
53 53  
54 +{{warning}}Note that the following applies to disaster recovery.
55 +* Although you can select the old and correct release yourself, you need us to execute the deployment.
56 +* Once a new release is deployed on the environment, the manual disaster recovery is **overwritten**.{{/warning}}
57 +
54 54  == 4. Key takeaways ==
55 55  
56 56  * A runtime image is the foundational layer of a container image.
... ... @@ -59,4 +59,4 @@
59 59  
60 60  == 5. Suggested Additional Readings ==
61 61  
62 -If you are interested in this topic and want more information on it, please read the [[release notes>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] provided by eMagiz.)))((({{toc/}}))){{/container}}{{/container}}A three-layered pyramid with a Spring framework and Java framework icon on the side of the bottom layer of the pyramid. Moving up on the pyramid, we find a flow icon, an eMagiz icon, and some non-descriptive text in technical style.
66 +If you are interested in this topic and want more information on it, please read the [[release notes>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] provided by eMagiz.)))((({{toc/}}))){{/container}}{{/container}}