October 13, 2015 at 12:55 pm
Hello. We've been trying to track down the source of backups generated by NT AUTHORITy/SYSTEM with odd names like {3A7FFDE2-95E4-4976-A3BC-33A0943C150A}3. (backups occur about every 15 mins) We can't seem to find any other sources that might be generating this backup. We have trans log shipping going, but those are clearly other backups.
Is there a way to determine what is calling SQL VSS at those times? Event logs are not giving us clues at this point.
Thanks,
Steve
October 13, 2015 at 1:19 pm
FYI, we did find the source of the VSS Backups by disabling 3rd party services one at a time until they stopped occurring.
-Steve
October 13, 2015 at 2:19 pm
Steve1014 (10/13/2015)
FYI, we did find the source of the VSS Backups by disabling 3rd party services one at a time until they stopped occurring.-Steve
And the guilty service was???
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
October 13, 2015 at 2:42 pm
When I see these virtual disk file names it is our Veritas NetBackup running, the client/agent is configured to run a backup, but I only see this about once per week when the Windows Admin/Backup team take full backups.
October 13, 2015 at 4:24 pm
It is actually our DR replication client (InMage). The DRaaS vendor is claiming the InMage client is not supposed to be taking SQL VSS backups - it's supposed to be doing block-level disk replication. We kept seeing disk spikes and found it was these mysterious VSS backups.
Working with the vendor to make sure we're covered for DR without having these SQL VSS backups, which they claim are not necessary.
Thanks for checking back!
-Steve
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply