I have been troubleshooting an issue with Veritas for approximately 2 1/2 
months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange backups are 
failing with the following error:

Error, Unable to open \ because it is currently being backed up by another 
process.
WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage 
Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
This file cannot verify.
Database or database element is corrupt

Veritas has exclaimed that it is a Microsoft issue and that the information 
store is corrupted.  So, I began researching my log files on my Exchange 
server.  I noticed there is an Event Source titled ESE.  Please keep in mind 
that I am a novice when it comes to the Exchange server.  It appears as 
though Windows defragments the "Exchsrv" directory.  Once complete, it backs 
up the information.  When the backup is complete, it reports Event ID 213.  I 
am troubled because it hasn't reported Event ID 213 since 3/4/06.  The defrag 
is being interrupted and Event ID 704 is reported.  Once that happens, the 
backup halts.

The "Exchsrv" directories have been de-selected in Veritas as to avoid this 
conflict.  Can anyone shed some light on this matter.  I really want to get a 
successful backup.

Thanks in advance.

Excluding the exchsrvr folder is right - don't back it up at that level.
Back it up using ntbackup. This will flush your logs and give you a good 
backup.
Then stop all BE services and restart them and see if that cures your woes.

"teenzbutler"  wrote in message 
news:60ECB3BD-693A-4A62-B741-CA415E186933@microsoft.com...
>I have been troubleshooting an issue with Veritas for approximately 2 1/2
> months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange backups 
> are
> failing with the following error:
>
> Error, Unable to open \ because it is currently being backed up by another
> process.
> WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage
> Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
> This file cannot verify.
> Database or database element is corrupt
>
> Veritas has exclaimed that it is a Microsoft issue and that the 
> information
> store is corrupted.  So, I began researching my log files on my Exchange
> server.  I noticed there is an Event Source titled ESE.  Please keep in 
> mind
> that I am a novice when it comes to the Exchange server.  It appears as
> though Windows defragments the "Exchsrv" directory.  Once complete, it 
> backs
> up the information.  When the backup is complete, it reports Event ID 213. 
> I
> am troubled because it hasn't reported Event ID 213 since 3/4/06.  The 
> defrag
> is being interrupted and Event ID 704 is reported.  Once that happens, the
> backup halts.
>
> The "Exchsrv" directories have been de-selected in Veritas as to avoid 
> this
> conflict.  Can anyone shed some light on this matter.  I really want to 
> get a
> successful backup.
>
> Thanks in advance.

Thanks for your reply.  I will give it a go.  I know this is going to sound 
strange, but I have never used NTbackup.  I have always used Veritas.  Is the 
NTbackup found under Accessories>System Tools>Backup?

Thanks again.

"Nick Gillott [MVP]" wrote:

> Excluding the exchsrvr folder is right - don't back it up at that level.
> Back it up using ntbackup. This will flush your logs and give you a good 
> backup.
> Then stop all BE services and restart them and see if that cures your woes.
> 
> "teenzbutler"  wrote in message 
> news:60ECB3BD-693A-4A62-B741-CA415E186933@microsoft.com...
> >I have been troubleshooting an issue with Veritas for approximately 2 1/2
> > months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange backups 
> > are
> > failing with the following error:
> >
> > Error, Unable to open \ because it is currently being backed up by another
> > process.
> > WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage
> > Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
> > This file cannot verify.
> > Database or database element is corrupt
> >
> > Veritas has exclaimed that it is a Microsoft issue and that the 
> > information
> > store is corrupted.  So, I began researching my log files on my Exchange
> > server.  I noticed there is an Event Source titled ESE.  Please keep in 
> > mind
> > that I am a novice when it comes to the Exchange server.  It appears as
> > though Windows defragments the "Exchsrv" directory.  Once complete, it 
> > backs
> > up the information.  When the backup is complete, it reports Event ID 213. 
> > I
> > am troubled because it hasn't reported Event ID 213 since 3/4/06.  The 
> > defrag
> > is being interrupted and Event ID 704 is reported.  Once that happens, the
> > backup halts.
> >
> > The "Exchsrv" directories have been de-selected in Veritas as to avoid 
> > this
> > conflict.  Can anyone shed some light on this matter.  I really want to 
> > get a
> > successful backup.
> >
> > Thanks in advance. 
> 
> 
>

I have a general question.  What is the most important information to backup 
on the Exchange server.  Is it the System State and Information Store?  If 
so, couldn't I back those up using NTbackup then remove those directories 
within Veritas?

Thanks.

"teenzbutler" wrote:

> Thanks for your reply.  I will give it a go.  I know this is going to sound 
> strange, but I have never used NTbackup.  I have always used Veritas.  Is the 
> NTbackup found under Accessories>System Tools>Backup?
> 
> Thanks again.
> 
> "Nick Gillott [MVP]" wrote:
> 
> > Excluding the exchsrvr folder is right - don't back it up at that level.
> > Back it up using ntbackup. This will flush your logs and give you a good 
> > backup.
> > Then stop all BE services and restart them and see if that cures your woes.
> > 
> > "teenzbutler"  wrote in message 
> > news:60ECB3BD-693A-4A62-B741-CA415E186933@microsoft.com...
> > >I have been troubleshooting an issue with Veritas for approximately 2 1/2
> > > months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange backups 
> > > are
> > > failing with the following error:
> > >
> > > Error, Unable to open \ because it is currently being backed up by another
> > > process.
> > > WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage
> > > Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
> > > This file cannot verify.
> > > Database or database element is corrupt
> > >
> > > Veritas has exclaimed that it is a Microsoft issue and that the 
> > > information
> > > store is corrupted.  So, I began researching my log files on my Exchange
> > > server.  I noticed there is an Event Source titled ESE.  Please keep in 
> > > mind
> > > that I am a novice when it comes to the Exchange server.  It appears as
> > > though Windows defragments the "Exchsrv" directory.  Once complete, it 
> > > backs
> > > up the information.  When the backup is complete, it reports Event ID 213. 
> > > I
> > > am troubled because it hasn't reported Event ID 213 since 3/4/06.  The 
> > > defrag
> > > is being interrupted and Event ID 704 is reported.  Once that happens, the
> > > backup halts.
> > >
> > > The "Exchsrv" directories have been de-selected in Veritas as to avoid 
> > > this
> > > conflict.  Can anyone shed some light on this matter.  I really want to 
> > > get a
> > > successful backup.
> > >
> > > Thanks in advance. 
> > 
> > 
> >

Yes sir.

"teenzbutler"  wrote in message 
news:E717F995-4A79-4C04-90F3-B1350692AAAE@microsoft.com...
> Thanks for your reply.  I will give it a go.  I know this is going to 
> sound
> strange, but I have never used NTbackup.  I have always used Veritas.  Is 
> the
> NTbackup found under Accessories>System Tools>Backup?
>
> Thanks again.
>
> "Nick Gillott [MVP]" wrote:
>
>> Excluding the exchsrvr folder is right - don't back it up at that level.
>> Back it up using ntbackup. This will flush your logs and give you a good
>> backup.
>> Then stop all BE services and restart them and see if that cures your 
>> woes.
>>
>> "teenzbutler"  wrote in message
>> news:60ECB3BD-693A-4A62-B741-CA415E186933@microsoft.com...
>> >I have been troubleshooting an issue with Veritas for approximately 2 
>> >1/2
>> > months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange 
>> > backups
>> > are
>> > failing with the following error:
>> >
>> > Error, Unable to open \ because it is currently being backed up by 
>> > another
>> > process.
>> > WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage
>> > Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
>> > This file cannot verify.
>> > Database or database element is corrupt
>> >
>> > Veritas has exclaimed that it is a Microsoft issue and that the
>> > information
>> > store is corrupted.  So, I began researching my log files on my 
>> > Exchange
>> > server.  I noticed there is an Event Source titled ESE.  Please keep in
>> > mind
>> > that I am a novice when it comes to the Exchange server.  It appears as
>> > though Windows defragments the "Exchsrv" directory.  Once complete, it
>> > backs
>> > up the information.  When the backup is complete, it reports Event ID 
>> > 213.
>> > I
>> > am troubled because it hasn't reported Event ID 213 since 3/4/06.  The
>> > defrag
>> > is being interrupted and Event ID 704 is reported.  Once that happens, 
>> > the
>> > backup halts.
>> >
>> > The "Exchsrv" directories have been de-selected in Veritas as to avoid
>> > this
>> > conflict.  Can anyone shed some light on this matter.  I really want to
>> > get a
>> > successful backup.
>> >
>> > Thanks in advance.
>>
>>
>>

Listen to what it says. You have a corrupt database.

Best option is to create another database and start moving users to it as 
quick as possible. It is expected that one or more users are going to have 
problems being moved, that's because they have messages in the corrupt area.

What you are seeing is a safety check. If Exchange sees database corruption, 
it will not allow a backup to occur. This way you don't backup corrupt data.

FIX THE PROBLEM NOW!



"teenzbutler"  wrote in message 
news:60ECB3BD-693A-4A62-B741-CA415E186933@microsoft.com...
>I have been troubleshooting an issue with Veritas for approximately 2 1/2
> months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange backups 
> are
> failing with the following error:
>
> Error, Unable to open \ because it is currently being backed up by another
> process.
> WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage
> Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
> This file cannot verify.
> Database or database element is corrupt
>
> Veritas has exclaimed that it is a Microsoft issue and that the 
> information
> store is corrupted.  So, I began researching my log files on my Exchange
> server.  I noticed there is an Event Source titled ESE.  Please keep in 
> mind
> that I am a novice when it comes to the Exchange server.  It appears as
> though Windows defragments the "Exchsrv" directory.  Once complete, it 
> backs
> up the information.  When the backup is complete, it reports Event ID 213. 
> I
> am troubled because it hasn't reported Event ID 213 since 3/4/06.  The 
> defrag
> is being interrupted and Event ID 704 is reported.  Once that happens, the
> backup halts.
>
> The "Exchsrv" directories have been de-selected in Veritas as to avoid 
> this
> conflict.  Can anyone shed some light on this matter.  I really want to 
> get a
> successful backup.
>
> Thanks in advance.

Just open a command prompt and enter

NTBACKUP

That will launch the GUI....

Regards,
Hank Arnold

teenzbutler wrote:
> Thanks for your reply.  I will give it a go.  I know this is going to sound 
> strange, but I have never used NTbackup.  I have always used Veritas.  Is the 
> NTbackup found under Accessories>System Tools>Backup?
> 
> Thanks again.
> 
> "Nick Gillott [MVP]" wrote:
> 
>> Excluding the exchsrvr folder is right - don't back it up at that level.
>> Back it up using ntbackup. This will flush your logs and give you a good 
>> backup.
>> Then stop all BE services and restart them and see if that cures your woes.
>>
>> "teenzbutler"  wrote in message 
>> news:60ECB3BD-693A-4A62-B741-CA415E186933@microsoft.com...
>>> I have been troubleshooting an issue with Veritas for approximately 2 1/2
>>> months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange backups 
>>> are
>>> failing with the following error:
>>>
>>> Error, Unable to open \ because it is currently being backed up by another
>>> process.
>>> WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage
>>> Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
>>> This file cannot verify.
>>> Database or database element is corrupt
>>>
>>> Veritas has exclaimed that it is a Microsoft issue and that the 
>>> information
>>> store is corrupted.  So, I began researching my log files on my Exchange
>>> server.  I noticed there is an Event Source titled ESE.  Please keep in 
>>> mind
>>> that I am a novice when it comes to the Exchange server.  It appears as
>>> though Windows defragments the "Exchsrv" directory.  Once complete, it 
>>> backs
>>> up the information.  When the backup is complete, it reports Event ID 213. 
>>> I
>>> am troubled because it hasn't reported Event ID 213 since 3/4/06.  The 
>>> defrag
>>> is being interrupted and Event ID 704 is reported.  Once that happens, the
>>> backup halts.
>>>
>>> The "Exchsrv" directories have been de-selected in Veritas as to avoid 
>>> this
>>> conflict.  Can anyone shed some light on this matter.  I really want to 
>>> get a
>>> successful backup.
>>>
>>> Thanks in advance. 
>>
>>

What do you feel is the best way to repair this?
John

"Ed"  wrote in message 
news:ucQ0hHdWGHA.3800@TK2MSFTNGP03.phx.gbl...
> Listen to what it says. You have a corrupt database.
>
> Best option is to create another database and start moving users to it as 
> quick as possible. It is expected that one or more users are going to have 
> problems being moved, that's because they have messages in the corrupt 
> area.
>
> What you are seeing is a safety check. If Exchange sees database 
> corruption, it will not allow a backup to occur. This way you don't backup 
> corrupt data.
>
> FIX THE PROBLEM NOW!
>
>
>
> "teenzbutler"  wrote in message 
> news:60ECB3BD-693A-4A62-B741-CA415E186933@microsoft.com...
>>I have been troubleshooting an issue with Veritas for approximately 2 1/2
>> months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange backups 
>> are
>> failing with the following error:
>>
>> Error, Unable to open \ because it is currently being backed up by 
>> another
>> process.
>> WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage
>> Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
>> This file cannot verify.
>> Database or database element is corrupt
>>
>> Veritas has exclaimed that it is a Microsoft issue and that the 
>> information
>> store is corrupted.  So, I began researching my log files on my Exchange
>> server.  I noticed there is an Event Source titled ESE.  Please keep in 
>> mind
>> that I am a novice when it comes to the Exchange server.  It appears as
>> though Windows defragments the "Exchsrv" directory.  Once complete, it 
>> backs
>> up the information.  When the backup is complete, it reports Event ID 
>> 213. I
>> am troubled because it hasn't reported Event ID 213 since 3/4/06.  The 
>> defrag
>> is being interrupted and Event ID 704 is reported.  Once that happens, 
>> the
>> backup halts.
>>
>> The "Exchsrv" directories have been de-selected in Veritas as to avoid 
>> this
>> conflict.  Can anyone shed some light on this matter.  I really want to 
>> get a
>> successful backup.
>>
>> Thanks in advance.
>
>

Hold on for a sec. Are you using the Exchange agent woth BE? You say that 
you have removed the exchsvr folder from the backup job. This sounds like 
you were trying to do a file backup as opposed to a store backup. That's 
a no-no. In addition, do you have a non-Exchange aware anti-irus running 
on that server?

"John ICS"  wrote in
news:uRYZBVfdGHA.564@TK2MSFTNGP02.phx.gbl: 

> What do you feel is the best way to repair this?
> John
> 
> "Ed"  wrote in message 
> news:ucQ0hHdWGHA.3800@TK2MSFTNGP03.phx.gbl...
>> Listen to what it says. You have a corrupt database.
>>
>> Best option is to create another database and start moving users to
>> it as quick as possible. It is expected that one or more users are
>> going to have problems being moved, that's because they have messages
>> in the corrupt area.
>>
>> What you are seeing is a safety check. If Exchange sees database 
>> corruption, it will not allow a backup to occur. This way you don't
>> backup corrupt data.
>>
>> FIX THE PROBLEM NOW!
>>
>>
>>
>> "teenzbutler"  wrote in
>> message news:60ECB3BD-693A-4A62-B741-CA415E186933@microsoft.com...
>>>I have been troubleshooting an issue with Veritas for approximately 2
>>>1/2 
>>> months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange
>>> backups are
>>> failing with the following error:
>>>
>>> Error, Unable to open \ because it is currently being backed up by 
>>> another
>>> process.
>>> WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage
>>> Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
>>> This file cannot verify.
>>> Database or database element is corrupt
>>>
>>> Veritas has exclaimed that it is a Microsoft issue and that the 
>>> information
>>> store is corrupted.  So, I began researching my log files on my
>>> Exchange server.  I noticed there is an Event Source titled ESE. 
>>> Please keep in mind
>>> that I am a novice when it comes to the Exchange server.  It appears
>>> as though Windows defragments the "Exchsrv" directory.  Once
>>> complete, it backs
>>> up the information.  When the backup is complete, it reports Event
>>> ID 213. I
>>> am troubled because it hasn't reported Event ID 213 since 3/4/06. 
>>> The defrag
>>> is being interrupted and Event ID 704 is reported.  Once that
>>> happens, the
>>> backup halts.
>>>
>>> The "Exchsrv" directories have been de-selected in Veritas as to
>>> avoid this
>>> conflict.  Can anyone shed some light on this matter.  I really want
>>> to get a
>>> successful backup.
>>>
>>> Thanks in advance.
>>
>> 
> 
> 
>

Hold on!!! Before you consider that the database is corrupt, be advised 
that Veritas Backup Exec will report a file as being corrupt if you have 
verify turned on and it can't backup a file due to it's being opened.

 From your description, it sounds like you are trying to do a file level 
backup of the Exchange server. If so, this message is to be expected and 
does not indicate a problem (other than the fact you are not backing up 
your Exchange databases...

If you want to backup the Exchange databases, you need to do one of the 
following:

   - Buy and install the Exchange agent from Veritas. This will allow 
real time backup of the databases.
or
   - Exclude the Exchange databases from the backup. Then schedule an 
NTBACKUP job prior to the Veritas backup job.



Regards,
Hank Arnold

John ICS wrote:
> What do you feel is the best way to repair this?
> John
> 
> "Ed"  wrote in message 
> news:ucQ0hHdWGHA.3800@TK2MSFTNGP03.phx.gbl...
>> Listen to what it says. You have a corrupt database.
>>
>> Best option is to create another database and start moving users to it as 
>> quick as possible. It is expected that one or more users are going to have 
>> problems being moved, that's because they have messages in the corrupt 
>> area.
>>
>> What you are seeing is a safety check. If Exchange sees database 
>> corruption, it will not allow a backup to occur. This way you don't backup 
>> corrupt data.
>>
>> FIX THE PROBLEM NOW!
>>
>>
>>
>> "teenzbutler"  wrote in message 
>> news:60ECB3BD-693A-4A62-B741-CA415E186933@microsoft.com...
>>> I have been troubleshooting an issue with Veritas for approximately 2 1/2
>>> months.  I use Veritas Backup Exec 9.1.  The issue is my Exchange backups 
>>> are
>>> failing with the following error:
>>>
>>> Error, Unable to open \ because it is currently being backed up by 
>>> another
>>> process.
>>> WARNING: "\\EXCHANGESERVER\Microsoft Information Store\First Storage
>>> Group\Private Information Store (EXCHANGESERVER)" is a corrupt file.
>>> This file cannot verify.
>>> Database or database element is corrupt
>>>
>>> Veritas has exclaimed that it is a Microsoft issue and that the 
>>> information
>>> store is corrupted.  So, I began researching my log files on my Exchange
>>> server.  I noticed there is an Event Source titled ESE.  Please keep in 
>>> mind
>>> that I am a novice when it comes to the Exchange server.  It appears as
>>> though Windows defragments the "Exchsrv" directory.  Once complete, it 
>>> backs
>>> up the information.  When the backup is complete, it reports Event ID 
>>> 213. I
>>> am troubled because it hasn't reported Event ID 213 since 3/4/06.  The 
>>> defrag
>>> is being interrupted and Event ID 704 is reported.  Once that happens, 
>>> the
>>> backup halts.
>>>
>>> The "Exchsrv" directories have been de-selected in Veritas as to avoid 
>>> this
>>> conflict.  Can anyone shed some light on this matter.  I really want to 
>>> get a
>>> successful backup.
>>>
>>> Thanks in advance.
>>
> 
>