[Bacula-users] getting the exchange plugin to work with 2007
I've got the 64 bit client installed (3.0.1) and it is loading the exchange
plugin (as verified by looking at the loaded dll's with Process Monitor),
but I think the syntax for the FileSet's Plugin line must be different for
Exchange 2007 than for Exchange 2003 (I've only seen an example for 2003).
Here's my FileSet definition:
FileSet {
Name = Exchange
Include {
File = C:/Program Files/Microsoft/Exchange Server/Mailbox
Plugin = exchange:/@EXCHANGE/Microsoft Information Store
}
Exclude {
File = C:/Program Files/Microsoft/Exchange Server/Mailbox/*
}
}
When I run with this, I get all the other VSS stuff (which I don't want!!!),
but not a backup of the Exchange information store. In fact, the job only
took 3 minutes, so obviously it's not backing up the store. Here's a snippet
of what I see in the report:
09-Jun 22:57 mcp-fd JobId 8: Truncated database logs for Storage Group First
Storage Group 09-Jun 22:57 mcp-fd JobId 8: Truncated database logs for
Storage Group Second Storage Group 09-Jun 22:57 mcp-fd JobId 8: VSS Writer
(BackupComplete): System Writer, State: 0x1 (VSS_WS_STABLE) 09-Jun 22:57
mcp-fd JobId 8: VSS Writer (BackupComplete): SqlServerWriter, State: 0x1
(VSS_WS_STABLE) 09-Jun 22:57 mcp-fd JobId 8: VSS Writer (BackupComplete):
MSDEWriter, State: 0x1 (VSS_WS_STABLE) 09-Jun 22:57 mcp-fd JobId 8: VSS
Writer (BackupComplete): Event Log Writer, State: 0x1 (VSS_WS_STABLE)
09-Jun 22:57 mcp-fd JobId 8: VSS Writer (BackupComplete): Registry Writer,
State: 0x1 (VSS_WS_STABLE) 09-Jun 22:57 mcp-fd JobId 8: VSS Writer
(BackupComplete): COM+ REGDB Writer, State: 0x1 (VSS_WS_STABLE) 09-Jun
22:57 mcp-fd JobId 8: VSS Writer (BackupComplete): Microsoft Exchange
Writer, State: 0x1 (VSS_WS_STABLE) 09-Jun 22:57 mcp-fd JobId 8: VSS Writer
(BackupComplete): Dhcp Jet Writer, State: 0x1 (VSS_WS_STABLE) 09-Jun 22:57
mcp-fd JobId 8: VSS Writer (BackupComplete): FRS Writer, State: 0x1
(VSS_WS_STABLE) 09-Jun 22:57 mcp-fd JobId 8: VSS Writer (BackupComplete):
WMI Writer, State: 0x1 (VSS_WS_STABLE) 09-Jun 22:57 mcp-fd JobId 8: VSS
Writer (BackupComplete): NTDS, State: 0x1 (VSS_WS_STABLE) 09-Jun 22:57
mcp-fd JobId 8: VSS Writer (BackupComplete): IIS Metabase Writer, State:
0x1 (VSS_WS_STABLE) 09-Jun 22:57 mcp-sd JobId 8: Job write elapsed time =
00:02:45, Transfer rate = 4.728 M bytes/second 09-Jun 22:57 mcp-dir JobId 8:
Bacula mcp-dir 3.0.1 (28Apr09): 09-Jun-2009 22:57:38
Any idea what's wrong?
--
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
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. Thanks! | C:/Program Files/Microsoft/Exchange Server/Mailbox/ | | /@EXCHANGE/Microsoft Information Store/First Storage Group/Mailbox Database/DatabaseBackupInfo | | /@EXCHANGE/Microsoft Information Store/First Storage Group/Mailbox Database/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb | | /@EXCHANGE/Microsoft Information Store/First Storage Group/Mailbox Database/ | | /@EXCHANGE/Microsoft Information Store/First Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000836.log | | /@EXCHANGE/Microsoft Information Store/First Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000837.log | | /@EXCHANGE/Microsoft Information Store/First Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000838.log | | /@EXCHANGE/Microsoft Information Store/First Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000839.log | | /@EXCHANGE/Microsoft Information Store/First Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E00083A.log | | /@EXCHANGE/Microsoft Information Store/First Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E00083B.log | | /@EXCHANGE/Microsoft Information Store/First Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E00083C.log | | /@EXCHANGE/Microsoft Information Store/First Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E00083D.log | | /@EXCHANGE/Microsoft Information Store/First Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E00083E.log | | /@EXCHANGE/Microsoft Information Store/First Storage Group/ | | /@EXCHANGE/Microsoft Information Store/Second Storage Group/Public Folder Database/DatabaseBackupInfo | | /@EXCHANGE/Microsoft Information Store/Second Storage Group/Public Folder Database/C:\Program Files\Microsoft\Exchange Server\Mailbox\Second Storage Group\Public Folder Database.edb | | /@EXCHANGE/Microsoft Information Store/Second Storage Group/Public Folder Database/ | | /@EXCHANGE/Microsoft Information Store/Second Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\Second Storage Group\E01014D.log | | /@EXCHANGE/Microsoft Information Store/Second Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\Second Storage Group\E01014E.log | | /@EXCHANGE/Microsoft Information Store/Second Storage Group/C:\Program Files\Microsoft\Exchange Server\Mailbox\Second Storage Group\E01014F.log | | /@EXCHANGE/Microsoft Information Store/Second Storage Group/ | | /@EXCHANGE/Microsoft Information Store/ | | /@EXCHANGE/ | -Original Message- From: James Harper [mailto:james.har...@bendigoit.com.au] Sent: Wednesday, June 10, 2009 4:29 AM To: Jeff Shanholtz; bacula-users@lists.sourceforge.net Subject: RE: [Bacula-users] getting the exchange plugin to work with 2007 I've got the 64 bit client installed (3.0.1) and it is loading the exchange plugin (as verified by looking at the loaded dll's with Process Monitor), but I think the syntax for the FileSet's Plugin line must be different for Exchange 2007 than for Exchange 2003 (I've only seen an example for 2003). Your fileset looks okay wrt the plugin line. I'm not aware of any changes in 2007 that would prevent it working like that. Why are you including and excluding the same C:\... path? (it shouldn't be a problem, I'm just curious) When I run with this, I get all the other VSS stuff (which I don't want!!!), but not a backup of the Exchange information store. I think you use vss=0 or something like that to turn off vss. It's documented. In fact, the job only took 3 minutes, so obviously it's not backing up the store. Here's a snippet of what I see in the report: 09-Jun 22:57 mcp-fd JobId 8: Truncated database logs for
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] getting the exchange plugin to work with 2007
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.har...@bendigoit.com.au] Sent: Wednesday, June 10, 2009 4:08 PM To: Jeff Shanholtz; bacula-users@lists.sourceforge.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
