MS Server backup failed on MS EXchange 2010 server mailbox database

This is using a single MS Exchange 2010 server in Windows 2008 AD domain. There wasn't any regular backup software, and I found that about 350 GB exchange logs were accumulated. Anyway, the database is about 80 Gb. So, I need to truncate the log and then purge them. There wasn't any backup software install, so I decided to use MS Server backup.

I open server backup, and on the list, choosing the above mailbox database for backing up. I also chosen "full" backup option. After that, start the backup. Process seems working fine until the end and it ended 100%. However, the backup status is "completed with some warning" with yellow asterisk. In the application event, there were a few events as follows:

Exchange VSS Writer (instance b422aee7-b023-4f38-878d-6180d7d59bf5:3) has completed the backup of database 'Mailbox  Database 0408027073' with errors. The backup did not complete successfully, and no log files were truncated for this database.

Very much appreciate any help and guidance
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MichaelBalackAuthor Commented:
This is using MS Windows 2008 R2 Standard Edition.
Installed Exchange 2010 SP3 with latest update rollup.
Also please check the event viewer for any errors.
noxchoGlobal Support CoordinatorCommented:
Check in event logs for the events correlating with the time of vpbackup.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

If you just want to get rid of the transaction logs you can enable circular logging for the database, let it run to do the work and then disable it again. And then after this do a full backup. Check next resources for this: and

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Its possible that the disks are so full there wasn't room to keep the snapshot. It might be worth running a


to check its still not hanging around, and a


to see what space is available.
Yes this is possible. Also you need to check VSS configuration on which volume is doing the backups.
Actually changing to circular logging may free space for the shadow storage.

However if the logs and database are correctly configured on separate physical drives (not separate partitions of the same drive) and the database drive is also full you may need to use the

vssadmin resize shadowstorage

command to change the snapshot location for the database drive to else where.  Just type it without any arguments and all should be clear.

If the database and logs are on the same drive, then it is probably a good idea to move them so they are on separate physical drives, not just separate partitions. You can use mount points to keep them on the same drive letter.

While the logs and database are on the same drive, and can leave circular logging enabled.  I don't think disabling it adds resilience in this config.
MichaelBalackAuthor Commented:
Hi all experts,

Sorry for the Delay. Give me sometimes to read through the suggestions.
MichaelBalackAuthor Commented:
Hi Dave,

Please see the 2 attached files for the results.
That's a lot of shadow files. Looks like they are not getting cleared when the backup fails. You can check how much space they are using by :-

vssadmin list shadow storage

If its a lot, I suspect its OK to delete them once you are ready to do the next backup..
However from what I remember when I got in this mess vssadmin won't delete shadows created by backups but the new "diskshadow" command will. Its documented here:-

and I think all you need to do is

delete shadows all

but I can't test it here...
MichaelBalackAuthor Commented:
Ok Dave, let me read through the article...
I remember I was using WMI to delete shadow copies like that because from vssadmin.exe delete shadows I couldn't.
MichaelBalackAuthor Commented:
The intention is to get rid of the log files, and using circular logging proven that log  files are purged away without affecting the database integrity. Thanks for Iciprianionut pointing out this "shortcut" but effective approach.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.