Differences

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

--- publications:synology_trigger_hyper_backup_on_usb_connect [2020/01/08 19:43] – [Overview - general workflow] Maik Wodarz
+++ publications:synology_trigger_hyper_backup_on_usb_connect [2020/01/08 19:47] – [Script startDatenBackup.sh] Maik Wodarz
@@ Line 38: / Line 38: @@
 ====== USB-Copy ======
-Originaly the USB-Copy app from Synology is intendet to do simple jobs like “copy file from USB drive to NAS” or “copy files from NAS to USB drive” when the copy button is pressed or a specific backup medium is detected. (UUID) It has to be installed by Synology package center.
+Originaly the //USB-Copy// app from Synology is intendet to do simple jobs like “copy file from USB drive to NAS” or “copy files from NAS to USB drive” when the copy button is pressed or a specific backup medium is detected. (UUID) It has to be installed by Synology package center.
 Actions caused by copy button are affecting only the fron USB port while USB detecting actions are working for the back site USB ports as well.
@@ Line 56: / Line 56: @@
   /volume1/Shared/USB_AUTO_BACKUP/TRIGGERS/MEDIA/autobackup
-The USB-Copy program lets beep the NAS after connecting twice.
+The //USB-Copy// program lets beep the NAS after connecting twice.
 After finishing the trigger file it beebs again twice.
@@ Line 78: / Line 78: @@
 So it is possible to connect the second backup drive a bit later or even in the same moment. The backups are handled serial.
-What happens when a trigger counter is bigger than Zero?:
+What happens when a trigger counter is bigger than zero?:
   * Create activity file (using touch command)
   * Remove all entries in trigger folders:
@@ Line 144: / Line 144: @@
 ====== Synousbcopy ======
-''/usr/syno/bin/synousbcopy'' was a script until DSM5. So it was easier to manipulate it respective to replace it inside file system. Further, this script was containing the whole copy button handling. Since DSM6 the copy button acting was moved into an app called “USB-Copy”. Nowadays the script is still there but contains some helper functions probably used by the “USB-Copy” app.
+''/usr/syno/bin/synousbcopy'' was a script until DSM5. So it was easier to manipulate it respective to replace it inside file system. Further, this script was containing the whole copy button handling. Since DSM6 the copy button handlich was moved into an app called //USB-Copy//. Nowadays the script is still there but contains some helper functions probably used by the //USB-Copy// app.
-What can synousbcopy do for us?
+What can ''synousbcopy'' do for us?
   /usr/syno/bin/synousbcopy –h
 Shows the help.
@@ Line 160: / Line 160: @@
 ====== Script startDatenBackup.sh ======
-This script or the corresponding counterpart startMediaBackup.sh is the heart of the trigger process.
+This script or the corresponding counterpart ''startMediaBackup.sh'' is the heart of the trigger process.
 It does the following:
   * activate copy LED blinking
-  * triggers hyper backup task
+  * triggers //hyper backup// task
   * waits until the hyper backup task finishes.
   * Deactivates the copy LED