Exchange VSS and File back-up failed

[Sander_Jacobs]

Hello,

we have two back-ups failing, and can't get the solution. the version of BU Exec is:
Backup Exec 2010 R3 with SP2 and patched with the latest patches.

situation:
File-backup to disk, is failing with the following error:

Backup- \\xxx\D:
V-79-57344-33928 - Access is denied.
Access denied to directory xxx

None of the files or subdirectories contained within will be backed up.
V-79-57344-65033 - Directory not found. Cannot backup directory xxx and its subdirectories.

We have tried to give the back-up account full control on the D Volume, and tried to back-up by the administrator account but the error stays.
 

Exchange-backup to disk, is failing with the following error:

Backup- \\xxx\Microsoft Information Store\MailboxDatabase-A-F
V-79-57344-65247 - A failure occurred reading an object.

Backup- \\xxx\Microsoft Information Store\MailboxDatabase-A-F
WARNING: "\\xxx\Microsoft Information Store\MailboxDatabase-A-F\Database" is a corrupt file. This fi...
VSS Snapshot warning. File E:\MailboxLogs\MailboxDatabase-A-F\E02*.log is not present on the snapsho...
VSS Snapshot warning. File E:\MailboxLogs\MailboxDatabase-A-F\E02.chk is not present on the snapshot...

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

We have tried to re-register the VSS dll's in microsoft. also we have set the exchange maintenance on 20:30 - 21:00, and let the backup begin at 21:00.
after a reboot of the exchange server, the backup runs fine for 1 time! but the next run the exchange backup failed again.

[Backup_Exec1]

Hi there , I would check if circular logging is not enabled if yes it is ,then I will disable it and then try doing backup again Also ensure if you have not enable shadow copies on the drive if yes please disable them Also check available physical memory on exchange server at time of backup is enough and not in MB,like 200 or 300 MB is left Thanks

[Sander_Jacobs]

thanks for the answer.

all of the exchange (2010) databases have circular logging enabled. i will disable this and check the back-up tomorrow.

on the exchange server drives is shadow copies disabled.

i will update you tomorrow about the status

[CraigV]

Hi,

Try this: split your data job from Exchange. Enable AOFO for the data backup, and disable it for the Exchange backup.

You can follow my article around this:

Thanks!

https://www-secure.symantec.com/connect/articles/backing-databases-and-files-same-tape-separate-jobs-using-backup-exec

[Sander_Jacobs]

We have 4 different jobs, sorry i was not clear enough about that:

we have 4 different jobs:
File-backup1
Exchange-backup2
SQL-backup3
VMware-backup4

on the exchange back-up there is no AOFO enabled

[CraigV]

...any reason why it references the D:\ drive then? Is that where Exchange is backed up?

Also, run: vssadmin list writers --> from a command prompt, and make sure all the VSS writers are stable and running.

If not, you can either restart the server, or reregister the VSS *.dlls as per the TN below:

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

[Sander_Jacobs]

no this are 2 seperate problems.
1 problem with the exchange problem (corrupt file)
1 problem with the file backup (acces denied)

on the exchange server this is the output from vssadmin list 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: {6a54f19f-ac78-46e5-872f-0782025b2ab5}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {e1c486ff-d49e-4a7b-8327-04f3a81e4eec}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {0c899e1c-e38b-419b-b3c2-b2e3eccfc0e1}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {ea4e9e4c-c1bc-43ca-9fc7-484c7138ee92}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {2c923de7-9300-45d3-9cbb-eff5e06eb0a2}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {d8eb9af4-6c3e-439a-b939-be37001ebe41}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {fdacd2b9-d475-4b8e-9245-358e3f46db52}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {e00899da-0f43-42f3-ad38-c939097a3aab}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {ad2de1e7-4366-4520-88e4-81ec46e7e550}
   State: [1] Stable
   Last error: No error
====================================================

this is the output from the vssadmin list providers:

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

we have registred the *.dll's multiple times, but no succes

[CraigV]

...this could be your issue:

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {d8eb9af4-6c3e-439a-b939-be37001ebe41}
State: [5] Waiting for completion
Last error: No error

[Sander_Jacobs]

we will reboot the exchange server tonight before the backup begin.

this will reset the writer to stable. we just have disabled circular logging, so we will check the backup tommorow

[Sander_Jacobs]

exchange back-up: Failed (vss errors are gone now!):
Backup- \\xxx\Microsoft Information Store\MailboxDatabase-A-F
V-79-57344-65247 - A failure occurred reading an object.
 

WARNING: "\\xxx\Microsoft Information Store\MailboxDatabase-A-F\Database" is a corrupt file. This fi...VSS Snapshot warning. File E:\MailboxLogs\MailboxDatabase-A-F\E02*.log is not present on the snapsho...VSS Snapshot warning. File E:\MailboxLogs\MailboxDatabase-A-F\E02.chk is not present on the snapshot...

file back-up: Failed:
Backup- \\xxx\D:
V-79-57344-33928 - Access is denied.
 

edit: on the file back-up, D partition is Shadow Copies enabled. but the Shadow Copies schedule is set to run at 7:00 in the morning, and 12:00 midday. the backup Exec file backup is scheduled to run at 23:59 in the evening.

[CraigV]

...takd Shadow Copies out of that selection list and add it into the data selection list.

You might also need to check and make sure that Exchange is consistent, and that the file the backup is failing on is present.

[Sander_Jacobs]

file back-up:
i have deselected the Shadow Copy selection from our file backup on the server that is failing with the Acces Denied error.

exchange back-up:
the E02.chk and E02.log are both present on the server.
we run a consisency check on the exchange server this weekend

[Sander_Jacobs]

Exchange back-up:
last weekend we did the repair on the exchange database A-F.
after the repair, the back-up completed without errors.
so the exchange back-up failures are gone.

File back-up:
we have noticed that the D volume from our File-server has a very low disk. 5GB free of 1TB.
after we have extended the D volume with 100GB, the file back-up completed without errors.

we will wait tonight back-ups and if they run without errors, the case can be closed

[Sander_Jacobs]

the exchange backup has as succesfull status.

the file backup has the error again :(
 

Backup- \\xxx\D:
Directory \\xxx\D:\Profiles\SBC-Profiles\_Old\xxx\AppData\Roaming\Microsoft\Windows\Start Menu\Progr...
None of the files or subdirectories contained within will be backed up.

V-79-57344-65033 - Directory not found. Cannot backup directory \Profiles\SBC-Profiles\_Old\xxx\AppD...

and so on ...

[CraigV]

OK...so problem 1 solved.

Do you need to back up the Profiles directory? Try deselecting, and then reselecting the folders in the selection list. Some information may have been deleted, and if you select specific folders instead of the root folder for example, you might have this issue if files are moved around, or deleted. BE expects them to be there.

[Sander_Jacobs]

thanks for the quick reply.
last weekend, the file backup was succesfull (this was started at saturday 21/4 at 7:00PM, and ended sunday 22/4 at 7:15AM

the selection list is the same, so deselecting and selecting the pofiles shouldn't be the problem in my opinion

[Sander_Jacobs]

i have checked the application eventlog from the file server. at the time the backup failed, this is the error in the eventlog:

Source: VSS
EventID: 8193
Volume Shadow Copy Service error: Unexpected error calling routine IMultiInterfaceEventControl::GetSubscriptions. hr = 0x80010108, The object invoked has disconnected from its clients.

Source: VSS
EventID: 12291
Volume Shadow Copy Service error: Error on creating/using the COM+ Writers publisher interface: BackupShutdown [0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.

Check the Application event log for more information.

].

====

update: i have re-registered the vss dll's according to this technote:

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

[Sander_Jacobs]

the exchange back-up failed again with the error corrupt mailstore A-F.

the file back-up failed with the same vss errors as before, even after re-registering the dll's

[CraigV]

...might be worthwhile opening a support ticket with Microsoft around this too...

[Sander_Jacobs]

just discovered the following:

our VMware backup runs at the same time as the File back-up.
the File backup failed on the exact time, the Vmware backup begins at the D volume of the file server.

we have changed the selection list - Recource Order, so the file-backup begins with the File server D volume, and the VMware backup ends with the File server.

think this will solve our problem. i will update you tomorrow