0

This question already has an answer here:

Client's SQL Server farm DBs are backed up by third-party tool that does not use VSS. About half of the instances show backups being made by some tool that is using VSS. I can disable SQL Server VSS Writer to stop these errant backups, but how do I track down what is running the VSS backups?

keywords: Volume Shadow Copy Service, volume-shadow-service [I don't have rep to create tags]

marked as duplicate by Brent Ozar, Philᵀᴹ, Paul White sql-server Mar 19 '17 at 9:52

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 1
    Kick off a server side trace. That will tell you who is doing what. Make sure to filter by the stuff that you only need. – Kin Shah Oct 20 '14 at 19:29
  • Kin, do you mean within SQL Server? That trace only shows that "SQL Server VSS Writer" is running the backup. How do I find what's telling VSS to do that? Or do you mean some other kind of trace? I'm experienced with SQL Server but don't know much about the OS. – Oliver Oct 20 '14 at 19:41
  • 1
    Yes I meant server side trace within SQL Server. If you want to track on OS level, I would recommend using sysinternals process explorer. – Kin Shah Oct 20 '14 at 19:45
  • In the SQL logs are you seeing things like (I/O Frozen, I/O Resume) at the time of these full backups? – Lawrage Feb 9 '16 at 6:51
-1

I believe that if you run native SQL Server backups (using T-SQL BACKUP) instead of DPM protection agent-based SQL backups, the SQL Server VSS Writer service must not be used on your SQL Server database folders. (The same problem is true for other third-party backup tools.)

This DPM/VSS service is not used by native SQL backups. If you prevent the DPM protection agent backups from triggering SQL Server VSS snapshots, this will protect your chain of log backups.

If DPM/VSS does continue to backup the SQL Server files, then the log chain is broken, because there are two tools (T-SQL BACKUP and DPM/VSS) backing up the log files.

  • This would be true if VSS were making log backups. Whatever is using VSS is only making full backups, which does not break the chain. – Oliver Oct 21 '14 at 15:06

Not the answer you're looking for? Browse other questions tagged or ask your own question.