Rob Owens wrote:
> I'm a little confused and need a little clarification.
>
> Suppose my BackupPC server has 2 full backups of identical data (no
> files were changed or added between backups). The pooling mechanism
> means that these 2 full backups take up the space of 1 full backup,
> right? (ignoring the space required for hardlinks, etc).
Yes, that's right.
> When using tar or smb as a transport, will performing a full backup
> transfer the entire contents of the share being backed up? And then
> BackupPC will discard duplicate files and hardlink them?
Yes.
> What exactly
> happens when using tar or smb to perform an incremental backup?
They use the file timestamp to copy files modified since slightly
earlier than your last full run. I think tar on unix/linux will use the
ctime to detect any kind of change (but will still miss old files in
their new location under a renamed directory) while smb will miss new
files created by any method that keeps an existing older timestamp.
> I've read through the documentation, but it was a lot to digest. If the
> documentation contains the answers to my questions, I'd appreciate it if
> someone could point me to the appropriate section.
You may also want to consider rsync as a transport, especially anywhere
bandwidth might be an issue.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
