> I've been trying out the new Exchange plugin from 2.5.28-b1. I've been
> trying
> to backup an Exchange 2003 installation running on Windows 2003
Server.
>
> I have followed the instructions here:
> http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html
>
> I made a fileset that looked like this:
> FileSet {
> Name = "Windows Exchange Server data"
> Include {
> File = C:/Program Files/Exchsrvr/mdbdata
> Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"
Don't need the 'File = ' here.
> }
> Exclude {
> File = C:/Program Files/Exchsrvr/mdbdata/E00.chk
> File = C:/Program Files/Exchsrvr/mdbdata/E00.log
> File = C:/Program Files/Exchsrvr/mdbdata/E000000F.log
> File = C:/Program Files/Exchsrvr/mdbdata/E0000010.log
> File = C:/Program Files/Exchsrvr/mdbdata/E0000011.log
> File = C:/Program Files/Exchsrvr/mdbdata/E00tmp.log
> File = C:/Program Files/Exchsrvr/mdbdata/priv1.edb
You do need to exclude everything in the mdbdata directory, but you do
need the mdbdata directory itself. We are hoping to include
functionality in the plugin that tells Bacula to excludes the files that
are backed up via the plugin, which obviously will vary each backup.
> }
> }
>
> When running this job, all that was backed up were some random files
in
> C:/Program Files/Exchsrvr/mdbdata
> It seems to me that the documentation is trying to say that we want to
> backup
> the mdbdata directory, and not the files in it.
> If this is the case, the fileset given in the documentation is
misleading,
> as
> any number of files might turn up in mdbdata, not just those listed
above.
> So I change my fileset to look like this:
>
> FileSet {
> Name = "Windows Exchange Server data"
> Include {
> File = C:/Program Files/Exchsrvr/mdbdata
> Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"
> }
> Exclude {
> File = C:/Program Files/Exchsrvr/mdbdata/*
> }
> }
>
> This had the desired effect on the mdbdata directory, so perhaps the
> documentation can be updated, if this is the right thing to be doing?
If you misinterpreted the documentation then I agree that it could be
clearer. Care to submit a suggestion?
>
> However, it seemed as if it still wasn't working properly, as nothing
else
> was getting backed up.
> I had no idea whether the plugin was getting loaded, as no log message
> made
> any reference at all to it. Or perhaps the file daemon was reporting
> something
> somewhere - I have no idea where though. It would have been good if
the
> director had mentioned something.
>
> *Eventually*, I realised that I needed to add 'Plugin Directory =
> (directory
> containing exchange-fd.dll on the windows machine)' to the file daemon
> config
> file.
> Once I had done that, the restore backed up some files that looked
like
> this:
> /@EXCHANGE/Microsoft Information Store/...
>
> But now, I can't seem to restore it, but I'll leave that problem for
> another day...
I have emailed Kern suggesting that a 'Plugin =' line in a fileset
should result in at least a warning if the plugin can't be found.
Otherwise the user will think that everything has been backed up when in
fact it hasn't. Haven't had a response yet...
James
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
