Changes for page Failover - Deploy Possibilities
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.74
edited by Danniar Firdausy
on 2024/09/25 17:12
on 2024/09/25 17:12
Change comment:
There is no comment for this version
To version 28.69
edited by Danniar Firdausy
on 2024/09/25 16:55
on 2024/09/25 16:55
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -22,16 +22,7 @@ 22 22 23 23 [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-router-containers.png]] 24 24 25 -Once you have applied the changes, if you go to the "Details" of each of those machines via right-cliking them, then you can find and set, for each failover runtime, the preferred machine to be the leader. As an example shown in the screenshot below, there are two runtimes that are enabled for failover and you can select whether that runtime running in that "External 01" machine is the preferred leader or the backup, or if you want to reset it back to "None". 26 26 27 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-failover-preference.png]] 28 - 29 -When you have made your decision, and assuming that your machines are already deployed and running, then you can move to the other page discussed in the next section. 30 - 31 -== 3.2 Deployment Plan == 32 - 33 -== 3.3 Deploy Release == 34 - 35 35 == 4. Key takeaways == 36 36 37 37 * Grouping is beneficial when external systems go through maintenance or downtime.