If it is faster to duplicate the last filled backup and then update it, would it be reasonable for a future version of BackupPC to pre-duplicate the last backup during one of the maintenance operations? Then it would be possible to simply update that when the time comes.
Or am I misunderstanding this? On 04/21 05:15 , Craig Barratt via BackupPC-users wrote: > I haven't done testing to see if having 100% fulls would be faster. On my > ext4 system running on sw raid 10, it is actually quite slow duplicating a > filled backup (which is the required step prior to starting a backup when > you want the prior one to remain filled), since the whole directory tree > has to be traversed. So that part is definitely slower. However, you are > right that, after that, the backup is somewhat simpler since it is only > modifying the current backup tree in place, since there's no need to update > the prior unfilled backup with the reverse deltas. Another minor advantage > of only having filled backups is deleting any one of them is easier, as you > note. Currently BackupPC needs to merge deltas into the immediate prior > backup (if unfilled) when you deleted a backup. > > Craig -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
