I have read through the responses to this problem in other threads but none of them seem to address the fundemental issue: Windows Server 2008 R2 does not know how to manage the space on the hard drive being used to store backups.
We should not have to go into an obscure (barely documented) utility to remove shadow copies. When the space gets low, the system should either delete old backups or send a message to the operator to inform him/her that there is an issue.
It might be acceptable to manage old backups as you can in Windows 7, where one can remove old backups using the GUI in the Backup/Recovery program.
As it is, when the space is exhausted on the backup drive, the backup fails. While I was able to use DiskShadow to delete old shadow copies (repeatedly) but this did not solve the problem. DiskShadow gives you the option of deleteing the oldest shadows but does not say how much space was released (if any). The backups still failed after having done a Diskshadow delete shadows all.
Microsoft can do better than this--especially for server-class products.
Do you really want to force your customers to go to other third-party tools?
__________________________________________________________________
William Vaughn
Author, Mentor, Trainer, MVP
Beta V Corporation
William Vaughn's blog
“Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)”
“The Owl Wrangler” a fantasy fiction novel
Please click the Mark as Answer button if a post solves your problem!
