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

[Sander_Jacobs]

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
 

[CraigV]

Hi,

I suspect your second error is related to the first.

Couple of things to do:

1. Turn off AOFO if you're already using it. It's not recommended when backing up Exchange.

2. Run: vssadmin list writers on the Exchange and backup servers and make sure your writers are all stable and running. If not, a reboot normally sorts it out.

Thanks!

[Sander_Jacobs]

Hi,

we don't use the Advanced Open File Option on our Exchange Backup. When we restart the exchange server, the error is gone. But on the next full back-up, the error is back. we have got this error only at the full backup. The incremental backup is going fine.

vssadmin list writers output:

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

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {f3831104-13f6-41aa-a641-22775f6f6fd2}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {94687fcb-da71-4a1f-86c0-358a30095fdf}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {5afc56be-d904-4d63-996b-6b2e58d7b8e1}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {bd27f63f-f7ca-499f-8719-48b7ba3087bf}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {7e52fa32-697a-4529-b535-263b42dfff98}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {1f375265-e67e-4887-835d-890c4e995c23}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {44ee8b47-d539-4928-832b-a72a2b46aba0}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {805f5e83-4217-43e8-aa34-b8bdc43eb100}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {03e86f0d-a1a5-4088-94cc-24b4b9145af0}
   State: [1] Stable
   Last error: No error

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

[CraigV]

There is a TN on that error but it talks about running the VSS rollup patch for Server 2003 which you're not using.

I'd suggest you follow the TN below in order to reregister the VSS *.dlls on Server 2008. Once done, try the backup again and report back here...

http://www.symantec.com/business/support/index?page=content&id=TECH70486

[Sander_Jacobs]

i have followed the TN and i will schedule a full backup tonight.
i'll update you tomorrow for the results

[Lesta_G]

what does vssadmin list providers show?

[CraigV]

...it shows which VSS provider is being used by the system. This should correllate with what is in BE where you can manually select the VSS provider if need be...

[Sander_Jacobs]

here are the results of the exchange backup:

to disk (run for 49 seconds):
=============================================
Job ended: maandag 1 augustus 2011 at 21:00:53
Completed status: Failed
Final error: 0xe0008516 - Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed.
Final error category: System Errors

For additional information regarding this error refer to link V-79-57344-34070
=============================================

to tape (didnt run because the backup to disk didnt run):
=============================================
Job ended: maandag 1 augustus 2011 at 23:14:26
Completed status: Failed
Final error: 0xe00081d2 - The script associated with this job contained no valid selections.
Final error category: Job Errors

For additional information regarding this error refer to link V-79-57344-33234
=============================================

[CraigV]

OK then...check the TN below which addresses this error you're getting:

http://www.symantec.com/business/support/index?page=content&id=TECH139703

[Sander_Jacobs]

when i run the command: "vssadmin list writers" on the exchange server, i'll get this output (there are less writers shown as when i performed the same command yesterday):

==========================================================
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {7fbe40bc-c685-4a10-9295-f4a93beff95f}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {f30ab13e-661e-47da-90c1-74469b959a6e}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {bd898404-9f7a-4762-99f1-6b7d60525110}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {c509131f-f7a2-443d-94f2-46b893bd6cb6}
   State: [1] Stable
   Last error: No error
==========================================================

regarding the TO:
we allready have the option enabled: "Backup exchange from the active copy"

[Sander_Jacobs]

i have just restarted the exchange server. when i run the command "vssadmin list writers" now i see more writers:

==========================================================
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {944c9c80-fb23-4efb-a860-5a2ac71489ed}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {fce1cae1-69da-4fd0-9167-99b0adfb84fd}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {9d7c8a12-98c9-4dc2-a0d7-fccebb853b0b}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {a34cf0ce-c233-426b-a35d-bbf49af2b944}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {8a77e038-5cc2-440a-bfd5-a61c5e702e15}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {e0a92517-5937-4b12-b2ea-047329dd2d7a}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {3734597d-23a5-44ad-ad68-9f153aabb077}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {2b329517-b580-4aee-992b-b16f6e46ffdf}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {91bfcca4-a9ae-429d-b025-2c62de0e5906}
   State: [1] Stable
   Last error: No error
==========================================================

I have started the full backup, and i will post here the result.
the backup is running now (3GB done at this moment)

[CraigV]

...sounds like this might be an OS issue...

[Sander_Jacobs]

results of the exchange backup:

backup to disk: Completed status: Successful
backup to tape: Completed status: Successful

i will schedule an incremental backup tonight, and tomorrownight i will schedule a full backup.
then we can see if the errors are gone

[Sander_Jacobs]

results of the exchange backup from last night:

backup to disk: Completed status: Successful
backup to tape: Completed status: Successful

i will schedule a weekly backup tonight and post the results here tomorrow

[Sander_Jacobs]

the full backup failed last night:

Backup- \\xxxx\Microsoft Information Store\Mailbox Database 0622574621
WARNING: "\\xxxx\Microsoft Information Store\Mailbox Database 0622574621\Database" is a corrupt file... The item \\xxxx\Microsoft Information Store\Mailbox Database 0622574621\Logs in use - skipped.

Backup
V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all ...

we have created a policy for the exchange backup
every day we perform a full backup. I have compared the daily jobs, and the weekly job but i cant find any difference.
the daily jobs complete succesfully, but when i schedule the friday job.. its going wrong

[Sander_Jacobs]

if i start the backup now, i'll get this error:

Backup- xxx
V-79-57344-6404 - AOFO: Initialization failure on: "\\xxxx\Microsoft Information Store\Mailbox Datab... Snapshot provider error (0xE0001904): A failure occurred querying the Writer status. Writer Name: Ex... Check the Windows Event Viewer for details.

but in the properties of the job/policy, we have disabled the AOFO option

[CraigV]

...and you're not using AOFO with this are you? If you are, turn it off and try again...

[Sander_Jacobs]

the AOFO option is not checked.

i think this is a OS problem, and not a symantec problem.

on the exchange server i can find the following events:

9840
9814
2007
9606
8229

so i have found the following TO:
http://www.symantec.com/business/support/index?page=content&id=TECH125176

[CraigV]

...if you don't come right I will hit the support flag. Alternatively, if you have support, why not log a call around this. Post back with the solution if you do log the call and they help you!

[Sander_Jacobs]

we have stopped the information store service and started the service.then we ware able to dismount the store, and mount it.

now the backup is running. i'll keep you up to date for the result of the backup