#1422 Bacula Include Audit
Closed: Fixed None Opened 14 years ago by ricky.

Currently, we have
{{{
File = /
File = /var
File = /var/log
File = /netapp/app
File = /srv
File = /backups
}}}

in our Include list for Full Set. Unless each of these paths are on separate partitions, they will get backed up twice, which can add up, especially for the log files. We need to go through and create different FileSets for each different partitioning scheme/server type that we have.


Boxes using Full Set are db05, db01, db04, fas01, releng03, releng04, relepel01 and log02. I only have login access to log02 so here is what I got.[[BR]]

log02 partition scheme is:[[BR]]
/dev/mapper/GuestVolGroup00-root /[[BR]]
/dev/vda1 /boot[[BR]]
/dev/vdb1 /var/log[[BR]]

log02 Include list maybe streamlined as:[[BR]]
File = /[[BR]]
File = /var/log[[BR]]

Not exactly sure if I'm on the right track here so let me know what you think.

Sigh. I just typed in a big long comment, then my browser crashed and I lost it. ;(

Will attempt to re-create.

The file here to look at in puppet is: modules/bacula5/templates/bacula-dir.conf.erb

Any machine we backup should use the full set once a week to do a full backup.

On the above list (db05,db04,fas01,releng03,releng04,relepel01), all of them just have / and /boot (and various nfs mounts which we do not want to backup)

So, I think here we could break "Full Set" into two:

One thats just / and /boot and one thats / and /var/log and /boot for log02 ("Log set" ?)

Can you produce a patch for that?

Also, we should look at the other sets and see if there are things we should include/exclude.

Kevin, you did not mention db01 on your list so I left it as it is. Oh, and I apologize for not using "Log set" as the name... I just realized it after posting the patch;)

ok. I commited a version of this. ;)

Just kept the "Full Set" name for most and made a seperate log one. ;)

I think this should be all set now. Thanks very much for looking into it.

Login to comment on this ticket.

Metadata