VMware Tools is responsible for invoking the VSS writers during VMware snapshots. There's a VMware KB that covers how to exclude specific VSS writers from being invoked:
For physical systems, as far as I know there's no official way to exclude specific VSS writers.
After searching around a bit, I found some hints on Technet that disabling the SQL VSS Writer Service will prevent the SQL writer from being invoked. If you're using Avamar for the physical server backups, you could probably write a prescript that calls "net stop" to stop the SQL VSS Writer Service and a postscript that calls "net start" to start it back up again. It's hacky but it might do what you need.
ionthegeek
2 Intern
•
2K Posts
0
September 19th, 2013 06:00
VMware Tools is responsible for invoking the VSS writers during VMware snapshots. There's a VMware KB that covers how to exclude specific VSS writers from being invoked:
VMware KB: Disabling specific VSS writers with VMware Tools
admingineerchitact
1 Rookie
•
30 Posts
0
September 19th, 2013 18:00
Wow! I've been looking for that for 10 years! You don't happen to know if a similar exclusion concept is available for physical servers, do you?
ionthegeek
2 Intern
•
2K Posts
0
September 20th, 2013 06:00
For physical systems, as far as I know there's no official way to exclude specific VSS writers.
After searching around a bit, I found some hints on Technet that disabling the SQL VSS Writer Service will prevent the SQL writer from being invoked. If you're using Avamar for the physical server backups, you could probably write a prescript that calls "net stop" to stop the SQL VSS Writer Service and a postscript that calls "net start" to start it back up again. It's hacky but it might do what you need.
Edit: Clarity