May 30, 201610 yr I tried setting a backup cron job, but it's not working. I'm using two files: a cron file (backup.cron), to run everyday, at 10:45 AM and a script (backup.sh) file to compress everything into a Dropbox monitored folder, this script file works every time I run it manually /boot/config/plugins/dynamix/backup.cron 45 10 * * * /bin/bash /boot/config/plugins/dynamix/backup.sh /boot/config/plugins/dynamix/backup.sh #!/bin/bash #Purpose = Backup of Important Data #Created on 14-5-2016 #Author = Marcio Matielo #Version 1.0 #START # Data do Backup TIME=`date +%Y-%m-%d--%H-%M` # Nome do arquivo FILENAME=backup-$TIME.tar.gz # Arquivos a serem salvos SRCDIR=/boot # Onde será salvo o backup DESDIR=/mnt/user/Cloud/Dropbox/unRAID/boot tar -cpzf $DESDIR/$FILENAME $SRCDIR #END This is what unRAID is sending me, at 09:11 AM, via e-mail /bin/sh: /boot/config/plugins/dynamix: Is a directory
May 30, 201610 yr Community Expert Probably a typo, but you say the script is /boot/config/plugins/backup.sh ... but the cron is /boot/config/plugins/dynamix/backup.cron 45 10 * * * /bin/bash /boot/config/plugins/dynamix/backup.sh If so then the cron has the wrong path to the script.
May 30, 201610 yr Author Probably a typo... Yes, it was a typo, sorry... both files are at the same directory: /boot/config/plugins/dynamix/ root@Savannah:/boot/config/plugins/dynamix# ls backup.cron* dynamix.cfg* parity-check.cron* users/ backup.sh* monitor.cron* plugin-check.cron* docker-update.cron* monitor.ini* ssd-trim.cron* dynamix-2016.04.02.tar.gz* mover.cron* status-check.cron* root@Savannah:/boot/config/plugins/dynamix# If so then the cron has the wrong path to the script. Considering it's a typo, is the path really wrong?
Archived
This topic is now archived and is closed to further replies.