When backing up a set of files that have different ownership/permissions, you naturally run borg as root. No problem with that, except the repo files are all created with 0600 permissions (and 0700 for /data). This makes it impossible to copy the repo as any other use but root.
The problem is this repo cannot be rsync'ed either: rsync sensibly) does not run as root. capabilities(7) won't help either: you'd have to apply them to either the Python interpreter for borg, or to the rsync binary -- compromising system security even more.
Am I missing something here? I don't see any options to force file/group ownership or permissions when running as root, and that's what is needed here.
To summarize: AFAICS there is no way to do a remote copy of a repo that backs up files with restricted permissions.
When backing up a set of files that have different ownership/permissions, you naturally run borg as root. No problem with that, except the repo files are all created with 0600 permissions (and 0700 for /data). This makes it impossible to copy the repo as any other use but root.
The problem is this repo cannot be rsync'ed either: rsync sensibly) does not run as root. capabilities(7) won't help either: you'd have to apply them to either the Python interpreter for borg, or to the rsync binary -- compromising system security even more.
Am I missing something here? I don't see any options to force file/group ownership or permissions when running as root, and that's what is needed here.
To summarize: AFAICS there is no way to do a remote copy of a repo that backs up files with restricted permissions.