On Thursday, 23 April 2015 02:27:49 UTC+9:30, Jarno Elonen wrote: > Hi, > > I've got a disk with 5TB of files that have been moved one directory level > deeper since last backup. > > Is there any way to get Bareos to NOT store all this data again, but instead > only record the new paths based on checksums or such? > > Accurate set doesn't seem to help; at least not according to the "estimate" > command. Even some sort of manual solution would be better than wasting > several terabytes of tape space. > > -Jarno
This might be a bit late, but I'm playing around with base jobs to do deduplicaton of my backups. It might be worth a look. From what I gather, it works like this: 1) You manually run a job to backup your files. The job should contain something like this: Name = "Base_Job" Level = base 2) You modify your regular backup job to include the "Base" parameter. Something like: Name = "Backup_OS_1" Base = "Backup_OS_1", "Base_Job" Accurate = yes Now when Backup_OS_1 job runs, it's will compare files with those already in the Base_Job and won't back them up again if it finds a match. I think the way a "match" is defined is by using "Accurate" in the "Backup_OS_1" job and modifying "Accurate" in the fileset definition to change the default behaviour of how matches are performed. This links to the relevant section of the bareos docs: http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-24600022 -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
