Graham Keeling wrote:
> On Tue, Sep 29, 2009 at 02:46:40PM +0200, Torsten Maus wrote:
>
>> I configured the client and job in backup, than I specified the fileset which
>> looks like this:
>>
>>
>> FileSet {
>> Name = "exchange"
>> Enable VSS = no
>> Include {
>> File = C:/Program Files/Microsoft/Exchange Server/Mailbox
>> Plugin = "exchange:@EXCHANGE/Microsoft Information Store"
>>
>> }
>>
>>
>> Exclude {
>>
>>
>> File = C:/Program Files/Microsoft/Exchange Server/Mailbox/First Storage
>> Group/Mailbox/E00.chk
>>
>>
>> File = C:/Program Files/Microsoft/Exchange Server/Mailbox/First Storage
>> Group/Mailbox/E00.log
>>
>>
>> File = C:/Program Files/Microsoft/Exchange Server/Mailbox/First Storage
>> Group/Mailbox/E000000F.log
>>
>>
>> File = C:/Program Files/Microsoft/Exchange Server/Mailbox/First Storage
>> Group/Mailbox/E0000010.log
>>
>>
>> File = C:/Program Files/Microsoft/Exchange Server/Mailbox/First Storage
>> Group/Mailbox/E0000011.log
>>
>>
>> File = C:/Program Files/Microsoft/Exchange Server/Mailbox/First Storage
>> Group/Mailbox/E00tmp.log
>>
>>
>> File = C:/Program Files/Microsoft/Exchange Server/Mailbox/First Storage
>> Group/Mailbox/priv1.edb
>>
>>
>> }
>>
>>
>> }
>>
>>
>>
>>
>> I swichted off VSS because I red in an other mail comment on the list, that
>> VSS
>> should be disabled, or at least it makes it easier to identify whether the
>> exchange plugin is working or not.
>>
>> So but if I run the job the plugin does nothing, because in the report
>> E-Mails I
>> red:
>>
>> 29-Sep 13:45 exchange-fd JobId 19648: Cannot open "C:/Program
>> Files/Microsoft/Exchange Server/Mailbox/First Storage Group/Mailbox
>> Database.edb": ERR=The process cannot access the file because it is being
>> used
>> by another process.
>>
>> I do not know what I did wrong, or where is my mistake, helpfully you can
>> help
>> me because I am quite frustrated.
>>
>
> This is what the fileset that I've been using looks like:
>
> FileSet {
> Name = "Windows Exchange Server data"
> Ignore FileSet Changes = yes
> Include {
> Options {
> signature = MD5
> compression = GZIP9
> IgnoreCase = yes
> }
> Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"
> }
> Exclude {
> }
> }
>
> I have also left VSS turned on.
> I don't think that you need all the random excludes that you listed.
>
Not only that, these random excludes are actually harmful.
The reason the original poster was having problems is that he was trying
to back up FILES. Exchange, by design, runs 24/7, and therefore keeps
the database locked. Thus the error. Enabling VSS would probably work
around that and let you back up the files, but that is still not the
proper way of backing up Exchange.
By excluding the log files, the original poster did two things. First,
he excluded an important part of the database. Second, he failed to
exclude all log files. Exchange will regularly create new ones, so this
Exclude will only leave out a few random ones out of the middle of the
database.
Exchange, like most databases, writes changes first to the log files
before it updates the actual database. The log files stay around until
the next backup of the database.
Doing a file-level backup of Exchange really doesn't do all that much
good. First, even if you can take a snapshot of the files, it still has
not been cleanly shut down. Second, Exchange never finds out about this
type of backup, and therefore never cleans up the log files. So the
number of log files (and the amount of disk space they take up) keeps
growing. I believe this will also slow down Exchange.
--
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About
Office: 866-642-7116
http://www.4nettech.com
This e-mail and attachments, if any, may contain confidential and/or
proprietary information. Please be advised that the unauthorized use or
disclosure of the information is strictly prohibited. The information herein is
intended only for use by the intended recipient(s) named above. If you have
received this transmission in error, please notify the sender immediately and
permanently delete the e-mail and any copies, printouts or attachments thereof.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
