Differences

This shows you the differences between two versions of the page.

--- tutorial:adm:server_os_updates [2019/12/17 07:47]
fiserp [Performing the OS update]
+++ tutorial:adm:server_os_updates [2019/12/17 07:50]
fiserp [Solving issues]
@@ Line 83: / Line 83: @@
   * Know how long (at worst) the whole rollback will take (rollback time **RT**).
   * 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, there is simply not enough time. If something goes wrong, you need at most **RT** time to perform the rollback!
+    * You are not able to safely perform the maintenance in shorter window, there is simply not enough time. If something goes wrong, you will need **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 carry on with updates.
+    * When you have no **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 carry on with updates.
-You should have a rollback procedure that can safely restore the deployment. This depends on your environment.
+You should have a rollback procedure that can safely restore the deployment. This depends on your environment and on the way you updated OS packages.
 Fortunately, in most cases it simply means restoring the snapshot of the virtual machine. After restoring the snapshot, you have to perform tests (with test use-cases) to confirm the rollback was performed correctly.