Differences

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

--- omv7:utilities_maint_backup [2024/07/30 15:57] – [Full Disk Mirroring / Backup with Rsync] crashtest
+++ omv7:utilities_maint_backup [2024/08/05 21:04] (current) – [The Benefits of Maintaining Operating System Backup] crashtest
@@ Line 262: / Line 262: @@
 ----
 \\
-<html><center>To find the appropriate UUID entries for the user’s drives for the Rsync command line; at the user's server under <b>Storage</b>, <b>File Systems</b>, on the far right, click on the <b>table</b> icon. In the pop down menu, check the <b>Mount Point</b> box.</center></html>
+<html><center>To find the appropriate UUID entries for the user’s drives for the Rsync command line; at the user's server under <b>Storage</b>, <b>File Systems</b>, on the far right, click on the <b>table</b> icon.</center></html>
 \\
 {{ ::omv6-maint-08.jpg?800 |}}
@@ Line 268: / Line 268: @@
 ----
 \\
-<html><center>In the popup menu, check the <b>Mount Point</b> Box</center></html>
+<html><center>In the popup menu, check the <b>Mount Point</b> box.</center></html>
 \\
 {{ ::omv6-maint-09.jpg?200 |}}
@@ Line 526: / Line 526: @@
 **The practical issues of maintaining boot drive clones – when to update and rotate?**\\
 \\
-. Linux Operating System package and security updates are unlikely to have a direct impact on the operation of the server.  While updating the boot drive is not strictly required after a package or security update, it would make sense to wait a week or two (more?) to insure that all is working.  Remember, the cloned drive is "the fall back".  Insure that there are no ill effects with an OS update, before updating the clone. \\
+. Linux Operating System package and security updates are unlikely to have a direct impact on the operation of the server.  Updating the boot drive is not strictly required after a package or security update. After updating, it would make sense to wait a week or two (more?) to insure that all is working well and that there are no issues between existing packages and updates.  Remember, the cloned drive is "the fall back".  Insure that there are no ill effects with an OS update, before updating the clone. \\
 \\
 . Add-on packages that are direct installed on the boot drive, Dockers (Plex, Urbackup, Pi-Hole, etc.), are another matter.  If add-ons are updated, where the update may change the way server add-on's interact with the data they generate, updating the cloned boot drive may be a good idea.\\
 \\
-. If a network share is added, deleted, or any aspect of the NAS is reconfigured that changes the operation of the NAS, the backup would need to be updated. Otherwise,  if needed for recovery, the configuration of the cloned boot drive would not mesh with the configuration and contents of data storage drives.\\
+. If a network share is added, deleted, or any aspect of the NAS is reconfigured that changes the operation of the NAS, the backup would need to be updated. Otherwise, when used for recovery, the older configuration of the cloned boot drive would not mesh with the new configuration and contents of data storage drives.\\
 \\
 . If a cloning mistake is made (let’s respect Murphy’s Law), a 3rd clone could become a “fallback of last resort”. Given that Linux package upgrades and openmediavault sub-version upgrades have little to no effect on network shares or the high level configuration of the NAS, a 3rd clone can be maintained that is updated //only// when the NAS configuration is changed.\\