omv7:utilities_maint_backup

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
omv7:utilities_maint_backup [2025/05/01 02:18] – [Cloning Flash Media] crashtestomv7: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 New User Guide section labeled [[A Basic Data Drive|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 [[A Basic Data Drive|A Basic Data Drive]].
Line 314: Line 314:
  
 As shown in this example: As shown in this example:
-This Scheduled Task will run the Rsync command will run every Sunday at 0110AM.+This Scheduled Task will run the Rsync command every Sunday at 0110AM.
  
  
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, selecting the wrong network mode (host, bridged, macvlan) for the application, other configuration issues (such as port 80 OMV/Docker conflicts), permissions problems or the Dockers themselves.\\+In the vast majority of cases, Dockers that fail to work won’t have anything to do with openmediavault or the Compose plugin. Docker issues tend to originate from selecting the wrong architecture, selecting the wrong network mode (host, bridged, macvlan) for the application, other configuration issues (such as port 80 OMV/Docker conflicts), permissions problems or the Dockers themselves.\\
 \\ \\
 Since most Dockers share Network ports with the host (openmediavault), it’s important to use ports that are __not__ currently in use. To get a better understanding of network ports and for commands that will reveal ports that are in use, refer to this forum post for more information:\\ Since most Dockers share Network ports with the host (openmediavault), it’s important to use ports that are __not__ currently in use. To get a better understanding of network ports and for commands that will reveal ports that are in use, refer to this forum post for more information:\\
  • omv7/utilities_maint_backup.1746065925.txt.gz
  • Last modified: 2025/05/01 02:18
  • by crashtest