Problem witch scheduled backup

[paros]

Need som help with scheduled backup.
I want to backup to a computer in the network. I have created a remote share as Samba.
I can backup successfully using the "direct funktion", but if I want to schedule the backup, nothing happens in the log or destination folder.

This is an example:
24 22 25 10 4 sudo /usr/sbin/rsync --stats --force --ignore-errors --modify-window=2 -HltDvr --delete '/share/1000/tf-downloads' '/share/1000/192.168.0.100-smb-Backup' >> '/share/1000/cronjobs/tf-downloads.log' 2>&1

[fvdw]

this the field of expertise of Jocko as he designed and implemented it.
This could happen if the time you have set has already passed or is not reached yet. You could check if time is correct by comparing it in the web interface. Please note that the system doesn't take daylight saving into account so if you are in europe and have chosen your time zone then it will be one hour earlier on the NAS as the real time. This will not be tcase anymore next sunday when daylight saving ends

ps you selected as well month and date en day in the week maybe you should leave day of week on * when you have set day and month

[Jocko]

Hi paros,

I see no error in rsync command line and if rsync can't write to 192.168.0.100, the log would be at least created. So I think the problem is in the planning job.

To check this, you only need to add a job like:

Code: Select all

date > /share/1000/cronjobs/date.log;chmod o+w /share/1000/cronjobs/date.log

(chmod only to delete easily the file)
If nothing happens is that your choice is wrong.

As Fvdw said, it is possible that the time selected is already passed (I planned to display the current date in the menu) or the event is not yet happen.

I also note that your selection in your sample may cause problems :
24 22 25 10 4 means all 25/10 at 22:24 when the day of the week is Thursday. So for example, next year it will not work.

For example a weekly schedule, the line will be:
24 22 */7 * * (<=> any day of the week, any month, any day but by step of 7 days at 22:24)

[paros]

If i look in the log file for a backup, I find this line:
sending incremental file list
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: ERROR: cannot stat destination "/share/1000/192.168.0.10-smb-nas_backup": Permission denied (13)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(565) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
sending incremental file

I dont know why the log say: "192.168.0.10" ?

The job is:

sudo /usr/sbin/rsync --stats --force --ignore-errors --modify-window=2 -HltDvr --delete '/share/1000/Music' '/share/1000/192.168.0.100-smb-Backup' >> '/share/1000/cronjobs/Music.log' 2>&1

[paros]

Any ideas?

[Jocko]

Sorry Paros, I didn't see your post :?

Yes, it's very strange and I don't have yet idea about it :scratch .
So some checks or asks.
1- See your crontab to ensure that the command line is right :
edit the file "active_jobs.cron" in the share cronjobs and ckeck if the cmd line use the right remote share.
2- Do you mount another remote share with an IP 192.168.0.10 ?
3- What is the output of the command mount ?(just run mount in a putty window)
4- run this cmd line (without the log file) in a putty window

Code: Select all

/usr/sbin/rsync --stats --force --ignore-errors --modify-window=2 -HltDvr --delete '/share/1000/Music' '/share/1000/192.168.0.100-smb-Backup'

5-previously with version 12.0, do you have this issue ?
6-check if you set write permission with your window share but I assume you do it because backup runs well without cronjob