Sebastian Perkins wrote:
> 
> 
> 
>>> Nils already wrote about the "full" backups with rsync. You need full 
>>> backups to make expiring work. Only full backups are expired, together 
>>> with their incremental backups. So I would suggest doing a weekly full. 
>>> Also note that because of the pooling in BackupPC, unmodified files are 
>>> only stored once. As an extreme example: If you've got an ISO on every 
>>> client, it will be stored only once on the backup server since pooling 
>>> works across all backups. 
> 
> Is there a link to the paper/howto ? We are mainly backuping samba shares off 
> servers so optimising identical files won't be too great. 
> 
> Our total full backup amounts to about 300Gb of compressed data, + the incr 
> (a few Gb per day). If I stick to a full backup every week, and be capable of 
> restoring 2 months of data, our 2,8 To NAS might blow up ? :o) 
> 

It is somewhat difficult to predict since all identical file copies are 
pooled.  That means that fulls don't take much more space to store than 
incrementals and the amount of space you free by deleting old fulls will 
depend on how many of the files no longer exist in subsequent runs.  If 
you have large files with frequent small changes (database dumps, 
growing log files, unix mailbox files, etc.) the modified copies won't 
be the same in the pool.  But the static instances of rotated logfiles 
or messages in maildir format would be pooled.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/