Home Dashboard Directory Help

Protect Us From Veeam by Randy in Marin



Sign in
to vote
Type: Suggestion
ID: 910349
Opened: 6/30/2014 5:21:23 PM
Access Restriction: Public


A broken backup chain is a serious event. There should be both an alert for this event and a means to prevent it from happening. I would like to have control of the validity of my SQL backups.
Sign in to post a comment.
Posted by Martin Suchanek on 10/21/2014 at 4:10 AM
Veeam says it is fully compatible with Microsoft Hyper-V. But this error is very dangerous. Will there be a hotfix for this situation? As Randy wrote, when you try to restore and find you can't is very disappointing. Customer doesn't care it is caused by Veeam. It is caused by fully compatible products???
Posted by Randy in Marin on 8/24/2014 at 9:08 AM
We needed to restore a production database to a point in time, but could not with either diff or log backups. The Veeam backup was enabled by mistake on this server. (This server was a converted physical server. It was to use the original backup methods.) I had no warning until the restore failed even though I was aware of the issue. I think I might have to create the alert myself. There was a day when we could trust our backups. Not anymore.    
Posted by Randy in Marin on 7/8/2014 at 9:01 AM
Thanks for the link. I did not know about this option. Unfortunately, this is not an option at this time. Also, I'm not sure how this would protect me from a broken log chain or the inability to do a diff backup after a Veeam or similar backup.
Posted by Sethu Srinivasan on 7/7/2014 at 11:44 PM
Have you looked at Managed SQL Server backup in SQL 2014? - http://sqlcommunity.com/Article-Library/Post/820/Let-there-be-Backups-Automated-Backup-Management-Using-SQL-Server-2014

You can quickly create a SQL 2014 Virtual machine on Windows Azure to check this new SQL 2014 feature - http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-provision-sql-server/

Sethu Srinivasan [MSFT]
SQL Server
Sign in to post a workaround.