How to prevent Microsoft's NTBackup from using the VSS Provider from Symantec System Recovery
By default, any software that uses Microsoft's Volume Shadow Copy Services (VSS) and does not specify a VSS Provider to use will be assigned a VSS Provider by the operating system in the following order:
1. Registered 3rd party hardware VSS providers
2. Registered 3rd paty software VSS providers
3. Microsoft Software Shadow Copy Provider (the VSS provider built in to the operating system)
By default, Microsoft's NTBackup utility does not specify which VSS provider to use when it generates a bakcup. Because of this, the operating system may assign the Symantec VSS Provider to process snapshot requests from NTBackup since the Symantec VSS Provider is a 3rd party software VSS provider which takes precedence over the built-in Microsoft VSS Provider. As the Symantec VSS Provider was only designed to interact with Symantec System Recovery 2011 (SSR) and Backup Exec System Recovery (BESR), this may either cause snapshot related errors within NTBackup or within the SSR or BESR backups.
The following Microsoft article contains instructions for forcing NTBackup to use the Microsoft VSS Provider:
The registry value listed in the "Resolution" section of that article being set to 1 will force NTBackup to use the Microsoft VSS Provider instead of using the Symantec VSS Provider. This will help eliminate VSS problems caused by NTBackup utilizing the Symantec VSS Provider.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried -out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.