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
LVL 1
MichaelBalackAsked:
Who is Participating?
 
lciprianionutCommented:
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:
http://exchangeserverpro.com/exchange-2010-mailbox-database-backup-restore-windows-server-backup/ and
http://www.techrepublic.com/blog/the-enterprise-cloud/back-up-exchange-2010-with-this-windows-server-2008-r2-feature/
0
 
MichaelBalackAuthor Commented:
This is using MS Windows 2008 R2 Standard Edition.
0
 
R--RCommented:
Installed Exchange 2010 SP3 with latest update rollup.
Also please check the event viewer for any errors.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
noxchoGlobal Support CoordinatorCommented:
Check in event logs for the events correlating with the time of vpbackup.
0
 
DaveCommented:
Its possible that the disks are so full there wasn't room to keep the snapshot. It might be worth running a

"VSSADMIN LIST SHADOWS"

to check its still not hanging around, and a

"VSSADMIN LIST VOLUMES"

to see what space is available.
0
 
lciprianionutCommented:
Yes this is possible. Also you need to check VSS configuration on which volume is doing the backups.
0
 
DaveCommented:
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.
0
 
MichaelBalackAuthor Commented:
Hi all experts,

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

Please see the 2 attached files for the results.
vssadmin-list-shadows.txt
vssadmin-list-volumes.txt
0
 
DaveCommented:
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:-

https://technet.microsoft.com/en-us/library/cc772172.aspx

and I think all you need to do is

diskshadows
delete shadows all

but I can't test it here...
0
 
MichaelBalackAuthor Commented:
Ok Dave, let me read through the article...
0
 
lciprianionutCommented:
I remember I was using WMI to delete shadow copies like that because from vssadmin.exe delete shadows I couldn't.
0
 
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.