Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| omv7:utilities_maint_backup [2024/04/22 04:05] – crashtest | omv7:utilities_maint_backup [2025/06/05 13:09] (current) – [Full Disk Mirroring / Backup with Rsync] crashtest | ||
|---|---|---|---|
| Line 236: | Line 236: | ||
| ===== Full Disk Mirroring / Backup with Rsync ===== | ===== Full Disk Mirroring / Backup with Rsync ===== | ||
| - | While individual shared folders can be replicated using Services, Rsync, a more efficient approach is using an Rsync Command line, in a scheduled job, under System, Scheduled Jobs to mirror a drive. This method allows for replicating the file and folder contents of an entire data drive, to an external drive or a second internal drive of adequate size. | + | While individual shared folders can be replicated using **Services**, **Rsync**, a more efficient approach is using an Rsync Command line, in a scheduled job, under **System**, **Scheduled Jobs** to mirror a drive. This method allows for replicating the file and folder contents of an entire data drive, to an external drive or a second internal drive of adequate size. |
| - | * To implement something similar to the following example; it’s necessary to add and mount a destination drive, in accordance with the section labeled A Basic Data Drive. | + | * To implement something similar to the following example; it’s necessary to add and mount a destination drive, in accordance with the New User Guide section labeled |
| * When formatted, the hard drives used in this example were labeled to indicate their function. This is a good practice that will help new users to easily identify drives and avoid admin mistakes. | * When formatted, the hard drives used in this example were labeled to indicate their function. This is a good practice that will help new users to easily identify drives and avoid admin mistakes. | ||
| * Dissimilar sized drives can be used, provided that the destination drive is large enough to hold the source drive’s data. | * Dissimilar sized drives can be used, provided that the destination drive is large enough to hold the source drive’s data. | ||
| Line 262: | Line 262: | ||
| ---- | ---- | ||
| \\ | \\ | ||
| - | < | + | < |
| \\ | \\ | ||
| {{ :: | {{ :: | ||
| Line 268: | Line 268: | ||
| ---- | ---- | ||
| \\ | \\ | ||
| - | < | + | < |
| \\ | \\ | ||
| {{ :: | {{ :: | ||
| Line 280: | Line 280: | ||
| ---- | ---- | ||
| \\ | \\ | ||
| - | To organize the construction of the Rsync command line, users should consider using a text editor like Windows Note Pad. Copy the source drive on the left and the destination on the right. | + | To organize the construction of the Rsync command line, users should consider using a text editor like Windows Note Pad. Copy the source drive on the left and the destination on the right. |
| The following is an example of a completed command line that will copy the entire contents of the source drive (**/ | The following is an example of a completed command line that will copy the entire contents of the source drive (**/ | ||
| Line 314: | Line 314: | ||
| As shown in this example: | As shown in this example: | ||
| - | This Scheduled Task will run the Rsync command | + | This Scheduled Task will run the Rsync command every Sunday at 0110AM. |
| Line 526: | Line 526: | ||
| **The practical issues of maintaining boot drive clones – when to update and rotate?**\\ | **The practical issues of maintaining boot drive clones – when to update and rotate?**\\ | ||
| \\ | \\ | ||
| - | 1. Linux Operating System package and security updates are unlikely to have a direct impact on the operation of the server. | + | 1. Linux Operating System package and security updates are unlikely to have a direct impact on the operation of the server. |
| \\ | \\ | ||
| 2. Add-on packages that are direct installed on the boot drive, Dockers (Plex, Urbackup, Pi-Hole, etc.), are another matter. | 2. Add-on packages that are direct installed on the boot drive, Dockers (Plex, Urbackup, Pi-Hole, etc.), are another matter. | ||
| \\ | \\ | ||
| - | 3. 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, | + | 3. 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, |
| \\ | \\ | ||
| 4. 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.\\ | 4. 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.\\ | ||
| Line 591: | Line 591: | ||
| If USBImager.exe is opened on the Desktop, the image file will be deposited on the Desktop. | If USBImager.exe is opened on the Desktop, the image file will be deposited on the Desktop. | ||
| This format provides the year, month, date and time that the image is taken.\\ | This format provides the year, month, date and time that the image is taken.\\ | ||
| - | If storing the image for future use, renaming it to something like **OMV6-Server1-2022-1209.dd.zst** may be helpful.\\ | + | If storing the image for future use, renaming it to something like **OMV7-Server1-03-15-2025.dd.zst** may be helpful.\\ |
| \\ | \\ | ||
| < | < | ||
| Line 696: | Line 696: | ||
| **Third: | **Third: | ||
| \\ | \\ | ||
| - | In the vast majority of cases, Dockers that fail to work won’t have anything to do with openmediavault or Portainer. Their issues tend to originate from selecting the wrong architecture, | + | In the vast majority of cases, Dockers that fail to work won’t have anything to do with openmediavault or the Compose plugin. Docker |
| \\ | \\ | ||
| Since most Dockers share Network ports with the host (openmediavault), | Since most Dockers share Network ports with the host (openmediavault), | ||