Moving VSS shadow storage to alternate location: supported?

[jdpal_ccs]

Hi All,

If we were to move the VSS shadow storage location from the C: to the D: on a VM, and back up that VM (all drives) with Veeam, would this be a supported configuration?

The process to move the shadow storage location is below. Would the new shadow copy storage location specified via this method be respected by Veeam?

VSS Storage Space Availability

We have done an initial test and the backup itself completes just fine but we want to make sure there is no reason why we should not be doing this.

Thanks!

[Gostev]

Basically, Veeam interacts with VSS on a much higher level. For example, we do not choose shadow copy storage location. There is an API that abstracts these sort of VSS internals from backup applications. We just tell VSS framework to create a VSS snapshot, etc. - everything else happens under the hood for us.

So sure, you can do anything as long as it does not brake VSS framework. And, if you do something that brakes VSS, this will affect not just Veeam, but any other VSS-aware backup application, or even regular system protection (which also uses VSS).

Thanks.

[jdpal_ccs]

Thank you for your quick response!