Have set 2 rclone sync commands to run daily by OpenMediaVault to back up two local directories to another local debian computer.
When run on the CLI OR using the 'run' button on the scheduled tasks page in OMV, both work properly.
When OMV runs them automatically as scheduled, both commands delete files in the remote share - even when the files are still present on the Source. eg: I have Omada running on a docker container on the OMV computer. It backs up nightly to the local drive and keeps 7 days of backups on the local drive. When Rsync runs it should delete the oldest file from the remote folder and replace it with the most current backup file - this will match the contents on the backup folder on the OMV computer.
Running Rclone sync from the CLI or 'run' button on the scheduled tasks page of OMV does exactly this but if I leave it overnight to run Rclone sync as a scheduled task, it removes all the backup files on the remote folder machine and does not write any new file - it empties the directory.
Run the command 'rclone version' and share the full output of the command.
os/version: debian 11.7 (64 bit)
os/kernel: 6.1.0-0.deb11.7-amd64 (x86_64)
Are you on the latest version of rclone? You can validate by checking the version listed here: Rclone downloads
Which cloud storage system are you using? (eg Google Drive)
SMB share on other (internal networked) debian system
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone sync /docker/omada debianbackup:debian_hdd_backup/omv_backup/docker/omada
type = smb
host = 192.168.0.120
user = xxx
pass = xxxxxxxxxxxxxxxxxxxxxx
#### A log from the command with the `-vv` flag
<!-- You should use 3 backticks to begin and end your paste to make it readable. Or use a service such as https://pastebin.com or https://gist.github.com/ -->
unable to post as run as a scheduled (CRON) task. When run manually does not return error's - see above
Hi, its a bit inconsitent.
Omada: The source directory holds 7 backup files for the last 7 days. Yesterday the 7 files were there, today, the only file remaining is yesterday's backup file. The files in the other Omada directory all look OK and haven't been deleted.
MariaDB: This is a home assistant database. Yesterday, all the files were there. Today they have all been deleted.
I'm running another Scheduled task to backup the OMV backup files to the same remote Debian share. That is running perfectly. The only difference between this and the Omada/MariaDB set up is Omada and MariaDB also backup to a google drive by the same Scheduling service on OMV (The OMV backup is too big for my google drive so I only have a local backup). I can't see how that could be affecting the local backup though.
OK, thanks for taking the time to look at it. doesn't really make sense as there is nothing else running to interfere with that remote directory (it was set up only for rsync). I'll fiddle around a bit more and see if it becomes more stable.