Hello Dirk,
On Wednesday 17 June 2009 16:55:04 Dirk Bartley wrote:
> Greetings
>
> Zimbra is a mail server suite. Not extemely fond of it, but we use it.
> It has a feature of doing a backup to a filesystem and we have been
> backing that filesystem up to tape. Like just about any imap mail
> store, man can it have alot of files! 1,088,000 files in 70 GB last
> full backup. I know there are probably large out there but that's alot
> for me.
>
> Having a catalog of this file structure is without value because there
> are no directories that are identified as having Bob's email like with a
> cyrus mail store.
>
> I noticed that there is a configuration item in the pool resource which
> may be a new item. Catalog Files = <yes|no>.
No, it is something that exists from the very beginning, but it is not often
used.
> I remembered reading it
> one time so while thinking about this rather large number of files that
> are put in the catalog, I was wondering if this might come in handy for
> me. So I was a little disapointed that I could not apply this option to
> a job as opposed to a pool. So my question here is would it be
> easy/possible to add this as an option to a job?? I would find that
> quite useful for this situation!!
Yes, that is a possibility, but there are already something like 65 directives
associated with a Job so we are trying to avoid adding anything that is not
essential.
Why don't you simply create a Pool for this job and any other where you really
don't want all the files cataloged? Adding Pools is really pretty easy, and
with the Scratch pool capabilities, it is easy for it to obtain volumes when
they are needed.
>
>
>
> The other thing is that I've been trying is to exclude previous sets of
> backups from full backups. I've tried doing incrementals forever but
> I've been getting concerned on how long it is adviseable to keep doing
> incrementals. So I looked at using a fileset like:
>
> FileSet {
> Name = "TestSet"
> Include {
> Options {
> signature = MD5
> aclsupport = yes
> }
> File = /opt/zimbra/backup/sessions
> # Exclude Dir Containing = ".baculaexclude"
> }
> Exclude {
> File = "\\</etc/bacula/exclude.list"
> }
> }
>
> where
> find /opt/zimbra/backup/sessions/* -maxdepth 0
>
> > /etc/bacula/exclude.list
>
> is in cron populating /etc/bacula/exclude.list before each new full
> backup.
I'm not convinced this is going to work the way you want. If you do a Full
with this FileSet, then you will not be able to easily recover the files you
have excluded. In any case, you will need to manually find the right backup
because Bacula will not be able to do it automatically.
If you want to reduce Full backups, there are two ways:
1. Periodically do a Differential backup. That effectively removes the need
for any of the prior Incrementals.
2. Do a VirtualFull to create a new Full. However, I don't recommend this
option unless you are using Accurate backup.
>
>
> I've settled on using the Exclude { File = } because I think I may have
> found a bug in the new feature of
> Exclude Dir Containing = ".baculaexclude"
>
> First when I uncomment the "Exclude Dir Containing" line I get some
> standard error on a config test:
> [r...@centos2 ~]# bacula-dir -t
> Orphaned buffer: bacula-dir 15 bytes buf=30d6388 allocated at
> inc_conf.c:591
>
> Second when I run an estimate on a directory that looks like below and
> the full is the "Oh my word huge directory", .. .. I can get the
> estimate to exclude any of the incrementals of my choosing with "Exclude
> Dir Containing", but not the full!! I've tried more than once and each
> time I do the estimate It takes 10-15 minutes to estimate the over 1
> million files even with the correct .exclude file in the full directory.
> I triple checked and it was spelled right.
>
> drwxr-x--- 6 zimbra zimbra 79 Jun 16 16:26 full-20090612.220006.194
> drwxr-x--- 6 zimbra zimbra 75 Jun 16 16:26 incr-20090613.220008.876
> drwxr-x--- 6 zimbra zimbra 75 Jun 16 16:26 incr-20090614.220005.806
> drwxr-x--- 6 zimbra zimbra 75 Jun 16 16:26 incr-20090615.220012.035
> drwxr-x--- 6 zimbra zimbra 75 Jun 16 18:01 incr-20090616.220011.796
>
> So I've gotten around the issue by doing the exclude using client side
> list. I am however offering to assist with whatever the bug may be. If
> someone wants to give me directions on how I can help solve why the
> Exclude Dir Containing is not working, I would be willing to assist.
I am not 100% sure that "estimate" follows all the same rules particularly
concerning exclusion that are done during a Bacula. It is quite possible
there is a bug. If you want to work on it, I recommend that you start with a
FileSet of about 100 files and then file a bug report and show clearly how it
is failing. If I have some reasonable sized FileSet and the steps to
reproduce it, it will be much easier to look at.
=====
On bat I have two points:
1. You sent me an email while I was on vacation that identified some problem.
Can you remind me of which email or the exact nature of the problem?
2. In bcomm, it appears that you effectively turned off the code that handles
warning messages. It seems to me that is going to be a problem because users
will not be informed when there is a error. Can you explain the reasoning
for the change?
Regards,
Kern
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
