The whole thing works very different from you expecting it to work. In a nutshell:
1) VSS-aware application (already referenced Symantec [Veritas] BackupExec or Microsoft DPM or for example VEEAM Backup or our own homebrewed Hyper-V Backup) requests VSS layer to create a snapshot for some physical or logical volume.
2) VSS layer (provided entirely by Microsoft) scans list of registered software and hardware VSS providers for this volume. If none is found volume is picked up by default Microsoft software VSS provider. With all the drawbacks - redirected I/O for Hyper-V, slowed down I/O b/c of COW used and 4-requests-instead-of-1, wasted reserved disk space for shadow copy etc. That's what we have for "el cheapo" software and hardware targets w/o VSS provider shipped with.
3) If VSS layer finds a software or hardware VSS provider (our case) provider - it becomes responsible for snapshot action taking. In our case it just signals array firmware (StarWind iSCSI SAN core) to turn a snapshot to another one. We really need to ship both software and hardware providers b/c only hardware could be used by Hyper-V and only software could be used by non-server OS (utter architectural nonsense, they should and are nearly 100% identical for us and most of the vendors I know).
So... No "3rd party snapshots" can work with StarWind (or any other on Earth) VSS provider as snapshot engine (like for example StorageCraft ShadowProtect) has to have own matching VSS provider. From the other point of view any properly written VSS-aware application should deal with StarWind snapshots thru StarWind VSS provieder. Just b/c it has no clue about StarWind presence (and any other VSS provider presence) and deals directly with Microsoft VSS asking to prepare and create a snapshot for particular volume.
Is it a little bit more clear now?
edmondegan wrote:Just speaking to support re: this but can we get confirmation if 3rd party snapshots are supported by the starwind hardware vss provider as I thought this was the case with 5.8 i.e. people with dpm or backupexec would benefit from no redirected io in hyper-v using csv.