Readynas rsync failing on .ssh folder

Show the config of the backup job (screenshots).

If the intention is to backup all home folders the user must (of course....) have at least read access to all users home folders on the remote (source) system.

The rsync process on that remote system does run under that user the UID and GID and probably secondary groups. When I look on the masks andthe ACLs on files and folders in the users folder, I get this:

root@RN516:~# getfacl /data/home/myusername/*

# file: data/home/myusername/VDO_1269.avi
# owner: myusername
# group: users
user::rwx
user:myusername:rwx
group::r-x
group:users:r-x
mask::rwx
other::r-x

....so not even ACLs in place...

root@RN516:~# ls -als /data/home/myusername/VDO_1269.avi
167964 -rwxrwxr-x+ 1 myusername users 171994108 Aug 05 2020 /data/home/myusername/VDO_1269.avi

So you see - a process run by a normal user created by the ReayNAS Web UI defaults to the user group users - and it has access to all, well, almost all files.

When looking into a typical .ssh - I show the /root/.ssh as an example (similar for other users in thier home folder) - you find that the .ssh and it's content has special protection masks in place, e.g. to "protect" the private key:

root@RN516:~# ls -als /root/
total 28
0 drwx------ 1 root root 88 Mar 3 22:22 .
4 drwxr-xr-x 1 root root 296 Mar 3 22:28 ..
12 -rw------- 1 root root 9305 Jul 17 20:57 .bash_history
4 -rw-r--r-- 1 root root 570 Jan 31 2010 .bashrc
0 drwxr-xr-x 1 root root 38 Sep 26 2015 .forever
4 -rw-r--r-- 1 root root 140 Nov 19 2007 .profile
4 -rw------- 1 root root 1024 May 9 2019 .rnd
0 drwx------ 1 root root 32 Jun 15 2013 .ssh
root@RN516:~# ls -als /root/.ssh
total 8
0 drwx------ 1 root root 32 Jun 15 2013 .
0 drwx------ 1 root root 88 Mar 3 22:22 ..
4 -rw------- 1 root root 1679 Jun 15 2013 id_rsa
4 -rw-r--r-- 1 root root 399 Jun 15 2013 id_rsa.pub