Edward Speyer wrote:
Hi!
I'm stuck trying to find a nice way to allow rsync / rdiff-backup enough
permissions to keep ownership information intact at the backup-receiving
end.
I /could/ run as root on the backup-reciever, but it'd be nice if there
was a less sledge-hammer approach to the chown
These are all great suggestions!
My current root-use-avoidance plans were to tar up each filesystem
locally into a tarball owned by some special "backup" user, then rsync
the tarball to another machine (rather than rsyncing the filesystem
itself).
The Mike Rubel page that Clive Menzies mentioned
On 2/8/06, Ken Irving <[EMAIL PROTECTED]> wrote:
> I'm using rsnapshot, which uses rsync over ssh, and "pull" backups to
> the backup server running as root, but I connect to the backup machines
> as an ordinary user. I use keychain to help automate ssh-agent for
> authentication, so I need to con
On Wed, Feb 08, 2006 at 09:00:50PM +, Edward Speyer wrote:
> Hi!
>
> I'm stuck trying to find a nice way to allow rsync / rdiff-backup enough
> permissions to keep ownership information intact at the backup-receiving
> end.
>
> I /could/ run as root on the backup-reciever, but it'd be nice if
On (08/02/06 21:00), Edward Speyer wrote:
> I'm stuck trying to find a nice way to allow rsync / rdiff-backup enough
> permissions to keep ownership information intact at the backup-receiving
> end.
>
> I /could/ run as root on the backup-reciever, but it'd be nice if there
> was a less sledge-ham
5 matches
Mail list logo