> > > Why are full backups needed at all with BackupPC? > > > > > > According to documentation, "BackupPC's CGI interface ``fills-in'' > > > incremental backups based on the last full backup, giving every backup > > a > > > ``full'' appearance." > > > > > > So, in theory, it should be enough to make just one full, initial > > > backup, and then only incremental backups. > > > > > > Or do I miss something here? > > > > one reason (there may be others) is that incrementals don't account > > for the removal of files. if a full contains a file that is later > > removed, it will always appear in that "filled" view, even after > > the file is gone from your system. so full backups are necessary > > to reestablish a true image of your current contents. > > > > (this is with tar -- rsync incrementals may actually remove deleted > > files. i don't use rsync.) > > So with rsync it shouldn't be an issue, right? Could anyone comment on that? > > > Anyway, will several full backups use only one hardlinked file in the > pool, or do full backups use separate, non-hardlinked files?
they use only one hardlinked file -- i.e., no extra space. paul =--------------------- paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 44.1 degrees) ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
