Hmmm... I created those scripts and had them run overnight. It successfully uploaded the files to the FTP server, but the files are empty (size 0 bytes).
When I run the script, rsync seems to 'upload' the files way too quickly - reporting 50Mbps etc. I think rsync thinks it's uploading the files properly, so it's probably a problem with curlftpfs. I've managed to create individual files and folders within the curlftpfs directory and it's worked fine - I've been able to access the files and their contents on the FTP using FileZilla. The problem seems to be when loads of files are being transferred at once.
I thought this might be a buffering issue, so I set rsync's temp directory to use /var/tmp/rsync and not a folder within the curlftpfs directory. Doesn't seem to have worked though.
Does anyone have any ideas as to what is going on?
Here are my two cron jobs:
mkdir -p /home/sean/.livedrive
mkdir -p /var/tmp/rsync
curlftpfs ftp://ftp.livedrive.com/ /home/sean/.livedrive
rsync --progress --no-perms --no-owner --no-group --recursive --temp-dir=/var/tmp/rsync /home/sean/Backup/* /home/sean/.livedrive/Backup/
remotebackupstart.sh is scheduled to run at 00:05 daily, and remotebackupstop.sh is scheduled to run at 07:55 daily.
fusermount -u /home/sean/.livedrive
I get a warning "fusermount: failed to open /etc/fuse.conf: Permission denied" when I run the cron first cron job - but /etc/fuse.conf is empty anyway so I don't think this matters. Nonetheless it seems to successfully mount the FTP directory in the correct place.
EDIT: Ok I've found what I think is the problem: after rsync 'transfers' the complete list of files, it then prints a load of errors afterwards, like this: rsync: open "/home/sean/.livedrive/Backup/some/file": No such file or directory (2). Any ideas?