cancel
Showing results for 
Search instead for 
Did you mean: 

V-79-57344-65245 and V-79-57344-65247

Sander_Jacobs
Level 4
Partner Accredited

hello,

we get the following 2 errors when we perform a exchange full backup to disk:

=========================================================
Media Label: IMG000123
GRT backup set folder: E:\B2D_02\IMG000123
The consistency check of the snapshot for the Microsoft Exchange database Database was successful.
V-79-57344-65247 - A failure occurred reading an object.

WARNING: "\\xxxx.xxxx\Microsoft Information Store\Mailbox Database 0622574621\Database" is a corrupt file. This file cannot verify.
V-79-57344-65245 - A failure occurred accessing the object list.

The item \\xxxx.xxxx\Microsoft Information Store\Mailbox Database 0622574621\Logs in use - skipped.
==========================================================

 

after that we get the following error when we duplicate to tape:

==========================================================
Job ended: zaterdag 30 juli 2011 at 0:07:52 Completed status: Failed Final error: 0xe0000397 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-919
==========================================================

 

information:

Symantec Backup Exec 2010R3 with latest patches untill 01-08-2011
OS backup server: Windows Server 2008 R2 Enterprise x64
Microsoft Exchange Server 2010
OS exchange server: Windows Server 2008 R2 Enterprise x64
 

30 REPLIES 30

Sander_Jacobs
Level 4
Partner Accredited

result:     backup to disk and to tape succesfully

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...that sounds like a problem with either your OS or Exchange itself. You shouldn't have to restart the Information Store service in order to dismount it...

Lesta_G
Level 6

OP - what does what does

vssadmin list providers show

Please post the results.

Sander_Jacobs
Level 4
Partner Accredited

backup to disk and tape succesfull last night.

========================================
vssadmin list providers exchange server:
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

=====================================================

vssadmin list providers on backup server:
Provider name: 'HP P4000 VSS Provider'
   Provider type: Hardware
   Provider Id: {acef7bd9-c49b-435a-bb6c-bc3bab91fda5}
   Version: 9.0.0.1006

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
 

CraigV
Moderator
Moderator
Partner    VIP    Accredited

That's great...give it another run and if it works, then you can close this off.

Sander_Jacobs
Level 4
Partner Accredited

bad luck.. the full backup has the status: Failed

but i discovered something a couple of minutes ago..

i have updates the backup exec software with the latest patches, but i didn't update the agents on de client servers.

so i have updated all the clients and perform a full backup now.

i'll keep you posted!
 

Sander_Jacobs
Level 4
Partner Accredited

backup succesfully to disk and to tape.
but we restarted the exchange server before the backup started

tonight we schedule a full backup again and see the status tomorrow

Lesta_G
Level 6

If you are still having the issue and it is easy to do, I would remove the HP4000 VSS provider

The fact that a backup is sucessfull on reboot and not after, infers the backup makes something go bad.

Sander_Jacobs
Level 4
Partner Accredited

the backup failed again.

we are goint to call symantec for further support.

thanks for support so far here guys!

i will update this case with the solution

Sander_Jacobs
Level 4
Partner Accredited

finally i've got the backup succesfull!

i have rescheduled the starttime of the exchange backup to 23:59 each day, and the backup status is 100% succesfull

dcctech
Level 2

Hey Sander,

Food for thought.

We're having the same issues for the last month. We've got it narrowed down to circular logging running while the backup starts. Perhaps that could have been your issue considering changing the backup time worked.

Cheers