On Tue, Sep 21, 2010 at 02:11:06PM +0100, Graham Keeling wrote:
> On Tue, Sep 21, 2010 at 10:12:26AM +0100, Graham Keeling wrote:
> > On Tue, Sep 21, 2010 at 10:10:08AM +0100, Graham Keeling wrote:
> > > OK, that sounds easy enough.
> > >
> > > Attached is my patch to bacula-5.0.3 (completely untested at the moment).
> > >
> > > I've made two new options:
> > > truncondiff
> > > trunconincr
> > > I will report on whether it works in a while.
> >
> > Sorry, here is the patch...
>
> It turns out that it didn't work, because the decision on what to set
> context->truncate_logs to was being made before the plugin options were
> parsed.
>
> This also means that 'notrunconfull' has been broken up until now.
>
> I have fixed it in the new patch attached to this email.
In attempting to test this, I believe that I have found a bigger problem,
unrelated to my patch.
Take bacula-5.0.3 (without my patch).
Use this fileset:
FileSet {
Name = "Windows Exchange Server data"
Ignore FileSet Changes = yes
Include {
Options {
signature = MD5
compression = GZIP9
IgnoreCase = yes
}
Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"
}
}
Have 'Accurate' turned off.
Run a full backup of Exchange 2003.
Run an incremental.
Run an incremental.
Now, in the bconsole restore browsing mechanism, you will have something
similar to the following in
"/@EXCHANGE/Microsoft Information Store/First Storage Group":
C:\Program Files\Exchsrvr\mdbdata\E0000012.log
C:\Program Files\Exchsrvr\mdbdata\E0000013.log
C:\Program Files\Exchsrvr\mdbdata\E0000014.log
Mailbox Store (2K3-PT2)
Public Folder Store (2K3-PT2)
Follow the procedure of restoring to a 'Recovery Storage Group', where you
mark all the log files and the 'Mailbox Store'. I am running Exchange on
VirtualBox, so after each attempt, I use VirtualBox to send Exchange back to
the snapshot of the time immediately before the first install. This ensures
no confusion with needing to clear out rubble and restart things on Windows.
If you restore from the full backup - i.e, choose the right jobid to restore
from and mark all the log files:
C:\Program Files\Exchsrvr\mdbdata\E0000012.log
Mailbox Store (2K3-PT2)
...it is fine.
If you restore from the first incremental backup:
C:\Program Files\Exchsrvr\mdbdata\E0000012.log
C:\Program Files\Exchsrvr\mdbdata\E0000013.log
Mailbox Store (2K3-PT2)
...it is fine.
If you restore from the second incremental backup:
C:\Program Files\Exchsrvr\mdbdata\E0000012.log
C:\Program Files\Exchsrvr\mdbdata\E0000013.log
C:\Program Files\Exchsrvr\mdbdata\E0000014.log
Mailbox Store (2K3-PT2)
...it is not fine.
I am given the message:
Fatal error: HrESERestoreComplete failed with error 0xc7ff1004 - Error returned
from ESE function call. Check the Windows Event Logs for more information.
So, I look on Windows, and the Event Log tells me:
Information Store (3048) Callback function call ErrESECBRestore Complete ended w
ith error 0xC8000713 Unable to find the file.
In "C:\Program Files\Exchsrvr\Recovery Storage Group", I have these files:
restore\E0000012.log
restore\E0000014.log
restore\restore.env
Mailbox Store (2K3-PT2).edb
Mailbox Store (2K3-PT2).stm
There is no restore\E0000013.log.
My instinct was that bacula tried to give back the log files not in the order
that Exchange was expecting.
But, having added some extra debug to the plugin, this appears not to be the
case.
So what is going on? Shall I enter a bug report?
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
