I think this error will be permission related but need more info on the rsync task/setup.
What are the details of type, source and destination and the user account used.
I think this error will be permission related but need more info on the rsync task/setup.
What are the details of type, source and destination and the user account used.
I use Rsync Service
Push
Source - SMB shared folder on OMV server
Destination - remote OMV server rsync://user@server/folder
Merry Christmas.
Similar setup to me. I had this issue but it was years ago. It was permissions related. What I think is happening is that on the remote/destination, rsync is trying to set date/time on "." directories and does not have the permissions to do this.
What I did to fix my setup was to setup a module on the destination (server) using root user and 'use chroot' setting set. I am not sure this is the correct/only way to do it but it works without any errors.
on the source omv server:
add/create rsync task (see pic)
use password authentication
destination server: rsync://<remote server ip or dns name>/<remote server module>/<directory name>/
** note the <remote server module> in this example should be named backup (see below). You can add any sub directory name
on the destination omv server:
create shared folder for destination (e.g. backup)
enable rsync server
add/create rsync server module called backup linked to the shared folder named backup
set user on module as root (not sure if this is needed)
select use chroot
Now you can add any new rysnc task on the client side pointing to backup/<sub directory> and have all your backup data organised as you like...
I think the limitation of this approach is that all files on the destination side are 'owned' by root. This is not an issue for me but might be for you if you have multiple users.
I suggest you do a test to see if how it works and then tweak until you get the setup you need without the permissions error.
Hope this helps a bit (and as stated above - I'm not saying this is the only/correct way but it works for me for my backups
"I think the limitation of this approach is that all files on the destination side are 'owned' by root. This is not an issue for me but might be for you if you have multiple users."
I need my files to be owned by a specific user.
Thx for the details I will try.
Not sure if it is justified as it still kinda "works" 
I use Rsync Service
Push
Source - SMB shared folder on OMV server
Destination - remote OMV server rsync://user@server/folder
It's better to "pull" an rsync job, from a remote source to a destination on the local server. The reason being, with a push job, if the destination becomes unavailable, a butt-load of temp files may be created on the local server. When pulling, if the remote source is not available, the job simply fails. There's no down side.
If you pull, you also do chown at the destination for local users. It's done at the bottom of an Rsync task in extra options.
--chmod=0755 --chown=root:users
It's better to "pull" an rsync job, from a remote source to a destination on the local server. The reason being, with a push job, if the destination becomes unavailable, a butt-load of temp files may be created on the local server. When pulling, if the remote source is not available, the job simply fails. There's no down side.
If you pull, you also do chown at the destination for local users. It's done at the bottom of an Rsync task in extra options.
--chmod=0755 --chown=root:users
That worked nicely and makes sense, thx!
Don’t have an account yet? Register yourself now and be a part of our community!
