Hi Wanda,

It could be caused by a premature termination of a prior backup.
You could check the DP/Exchange log and Windows Event Log to see
if there are any signs of a premature failure just prior
to the backups starting to fail. Look for a missing backup
or incomplete console captures of the backups just prior
to this problem.

You might be able to clear the condition by changing the
passive to active and then back again. You could also
try dismounting and mounting the database.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 04/10/2013
02:01:04 AM:

> From: "Prather, Wanda" <Wanda.Prather AT ICFI DOT COM>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 04/10/2013 02:01 AM
> Subject: Exchange 2010 backup fails with ACN6076, ACN6068
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> TSM 6.3.3 on Win2K8-64
> Exchange 2010
>
> Two Exchange nodes in a DAG, each with multiple active mailbox DB's,
> running TDP for Exchange 6.4.0.0, TSM client 6.4.0.0.
> (The passive DBs live at a DR site across a WAN, which is why I'm
> backing up the active ones.)
>
> TDP Scheduled backup ran for a couple of weeks on both nodes with no
problem.
> Full backups only so far, as the DB's are still in circular logging
mode.
>
> 2 nights ago the backups started failing on one mailbox on node A,
> and one mailbox on node B with:
> ACN6076I < databaseName > cannot be backed up because its
> 'BackupInProgress' flag is set to 'True'. Check whether the database
> is being backed...
>
> But there is no other TSM backup in progress.  The Exchange utility
> getmailbox shows the "backup in progress" flag is indeed set to "True".
> Diskshadow shows no leftover shadows.
> I found this hit that says we are essentially toast and will
> probably have to reboot.
>
> http://www-01.ibm.com/support/docview.wss?uid=swg21626354
>
> So my question is, what causes this situation and how do I prevent
> it happening again?