Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
tutorial:adm:server_os_updates [2019/12/16 15:06] fiserp [Things to consider] |
tutorial:adm:server_os_updates [2019/12/16 15:17] fiserp [Performing the OS update] |
||
---|---|---|---|
Line 69: | Line 69: | ||
- Update your test cases if necessary. | - Update your test cases if necessary. | ||
- After about a week, check system logs to make sure all components work as expected. | - After about a week, check system logs to make sure all components work as expected. | ||
+ | |||
+ | < | ||
+ | |||
+ | ==== Solving issues ==== | ||
+ | During maintenance actions, it is necessary to know: | ||
+ | * How long each task will take **TT**. | ||
+ | * How long the whole maintenance will take **MT**. | ||
+ | * This is not simply a sum od **TT**s, you should add some extra time **ET** to have a proper cushion. | ||
+ | * How long (at worst) the whole rollback will take **RT**. | ||
+ | * To have a maintenance window that spans at least **MT**+**RT** with some extra time **ET**. | ||
+ | * You are not able to safely perform the maintenance in shorter window - if something goes wrong, you need at most **RT** time to perform the rollback! | ||
+ | * If you do not have any **ET**, if anything goes wrong you have to perform rollback procedure. Therefore, **ET** gives you some time you can spend on solving the issue so you can continue with updates. |