Today I was asked how we provide VSS application support (eg. Exchange, SQL, SharePoint, Hyper-V) for Windows Server Backup.
It’s standard practice to add in the GUIDs of each VSS writer to the following registry key:
However, when our user went to this key, he discovered that it was “missing”, and wondered how BackupAssist could provide VSS application support without the keys.
The answer is:
- BackupAssist creates the key before the backup, and deletes it afterwards, so it will not interfere with any other settings that may exist on your system. If the key already exists, then we won’t touch it (or delete it). You can see an example of the key that BackupAssist creates, and subsequently deletes, in the screenshot below.
- If you try to do a restore, you’ll be able to see your VSS applications listed if you try to restore the application, as shown below.
- Looking at the backup report, in the Backed Up Items section, you’ll see the VSS applications listed as being backed up.
I hope that explains the situation, and gives everyone an understanding of how we achieve VSS application backup support in Windows Server Backup – and how to verify that it’s working!