Interesting. I was thinking in terms of restoring the entirety of exchange
in a disaster scenario such as hard drive failure. But it sounds like you're
talking about handling a more localized problem with exchange itself. So
then would you suggest letting my normal system backup handle all but the
edb's and log's, and having a job for *only* the exchange information store
(i.e. no file specs whatsoever)? I do think I like that idea.
On a related note, when I did a test run of backing up the entirety of
exchange, I realized I would need VSS for the "in use" files. That got me to
wondering if there is a way to limit the VSS usage to a single VSS writer,
or is it all or none when turning on VSS?
-----Original Message-----
From: James Harper [mailto:james.harper AT bendigoit.com DOT au]
Sent: Wednesday, June 10, 2009 4:08 PM
To: Jeff Shanholtz; bacula-users AT lists.sourceforge DOT net
Subject: RE: [Bacula-users] getting the exchange plugin to work with 2007
>
> Looks like I was getting thrown off by all the VSS stuff (I figured
that
> would be off by default - guess not), and didn't realize Outlook was
> removing the line breaks, making it hard to read.
>
> It does appear to be working, and the Exchange Best Practices Analyzer
is no
> longer complaining about the store never having been backed up! :D
>
> Those file specifications came from my research on setting this up. It
was
> in a thread I found on the subject (which I think you were a part of
IIRC),
> and the purpose was to get the directory itself without the files.
2007 has
> a significantly different directory structure than 2003 and it was
unclear
> to me what I should/shouldn't back up. But now that I can see what the
> plugin is backing up it appears that I should just exclude the edb and
log
> files from the normal FileSet file specs. In fact, I think I should
> configure it to back up the whole Exchange Server directory (rather
than
> letting my normal backup job do that), minus the edb's and log's.
>
I think all the files in the exchange data directory (or directories)
should be excluded from the backup. When doing a restore of the exchange
databases, having leftover files there can cause problems. At some point
in the future (when the bacula plugin infrastructure supports it), the
exchange plugin should be able to hand bacula a list of files to exclude
from the backup, eg all the files it backed up (or is going to back up)
itself.
Thanks for the feedback.
James
------------------------------------------------------------------------------
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-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
