rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] ACLs/EAs (who is the audience?)


From: Ben Escoto
Subject: Re: [rdiff-backup-users] ACLs/EAs (who is the audience?)
Date: Sun, 02 Mar 2003 11:18:21 -0800

>>>>> "KS" == Kevin Spicer <Spicer>
>>>>> wrote the following on Sun, 2 Mar 2003 18:17:49 -0000

  KS> I'm not using ACL's, but if I was I would want rdiff-backup to
  KS> map them all correctly.  The reason being that my rdiff-backup
  KS> to a remote machine exists for two purposes...

  KS> 1) Speedy restore of individual files / directories

  KS> 2) Should the source machine die its users can be immediately
  KS> switched to the destination machine and carry on working on the
  KS> mirror.

As it is now (and has been in the past) #2 is doable, but risky, as
any modifications made to the mirror directory can destroy information
not just about the current mirror, but any previous increments that
depend on the current mirror.  As people may in general be unaware of
the risks, maybe it's better not to encourage this type of use?

    I saw the metadata stuff as moving away from #2 and towards #1.
If you were backing up an entire filesystem as a non-root user,
ownership information would not be set correctly on the destination
(so #2 wouldn't be possible) but because ownership is stored in the
metadata file #1 would be fine.

    But if we would like both #1 and #2 to be possible, then
rdiff-backup needs to do what rsync needs to do plus a bit more.  For
a thoughtful summary of rsync's ACL/EA issues, see this message that
J.W. Schultz just posted to the rsync mailing list:

http://lists.samba.org/pipermail/rsync/2003-March/010031.html


-- 
Ben Escoto

Attachment: pgpI6hEujR1eb.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]