This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
debian:upgradepathtemplate [2024/04/17 19:38] 51.174.65.41 old revision restored (2022/11/12 13:32) |
debian:upgradepathtemplate [2024/04/30 10:43] (current) 65.108.0.71 old revision restored (2023/02/03 13:27) |
||
---|---|---|---|
Line 16: | Line 16: | ||
==== 1.1. Back up any data or configuration information ==== | ==== 1.1. Back up any data or configuration information ==== | ||
+ | | ||
==== 1.2. Inform users in advance ==== | ==== 1.2. Inform users in advance ==== | ||
+ | === 1.2.1 - Who and How should be informed === | ||
+ | |||
+ | | ||
+ | |||
+ | === 1.2.2 - Notify 1 Day prior to planned upgrade === | ||
+ | |||
+ | === 1.2.3 - Notify 2 Hours prior to beginn of upgrade === | ||
==== 1.3. Prepare for downtime on services ==== | ==== 1.3. Prepare for downtime on services ==== | ||
Line 26: | Line 34: | ||
| | ||
+ | This is the perfect time to assess the Backup solution of the Company, when not previously done, if you are hired to ensure the reliability of the infrastructure. | ||
==== 1.5. Prepare a safe environment for the upgrade ==== | ==== 1.5. Prepare a safe environment for the upgrade ==== | ||
Line 77: | Line 86: | ||
==== 3.2. Upgrade current installation ==== | ==== 3.2. Upgrade current installation ==== | ||
+ | |||
+ | This is where you notify everyone from Section 1.2 above prior to executing the command below. | ||
# sudo apt upgrade | # sudo apt upgrade |