Holger Parplies wrote:
>>>> Also I see the --ignore-times option in rsync args for full backups. Why
>>>> is this necessary exactly?
>>> If you don't, you are trusting that every file that has the same name,
>>> timestamp and length on the previous backup still matches the contents
>>> on the target. It probably, mostly, usually, does...
>
> actually, if you don't, you are trusting that nobody/nothing wrote to a file,
> keeping its size the same, and then reset the modification time to the
> previous value. Technically, that's simple to do and does happen.
Actually, tar should be using ctime, not modification time. Ctime is the
time of the last inode change, which will include the action of
modifying mtime - or changing owner/permissions, etc. The only thing it
will miss is a file which was itself unchanged but is under a directory
that has been renamed since the full run. You will have a copy of these
files in the full, just not in the right place. On the other hand, if
the system time gets reset incorrectly so new files are getting
timestamps earlier than the last full, they would all be skipped in the
incrementals. And I think smb only sees mtime.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
