Snapshots, Deduplication and QTrees

Having not been on a NetApp course yet, it makes it "fun" trying to understand how these three concepts work together:  Snapshots, Deduplicaiton and QTrees (not to mention Volumes and SnapVault)

So here's my notes and a place to write anything I might figure out.

https://kb.netapp.com/support/index?page=content&id=1010363

https://library.netapp.com/ecm/ecm_get_file/ECMM1278402 (PDF)

OSSV FAQ not as easy to find as I'd expect. It's got some good stuff like Windows System State backup (registry, AD, etc.) and excluding files/paths in OSSV Backups and:

Q: Anytime I restore even a single file, I have to perform a full baseline or
reinitialize of my primary file system?
A: No.  If you run a full D/R restore, you need to re-initialize.  If you drag/drop a file,
then it should behave reasonably. In that case, it's just as if the user
created/modified a file.  


Q: Is OSSV 2.2 able to adress backing up Operating Systems?
A: OSSV 2.2 can backup Windows 2000/2003 but not the Unix platoforms.


Q: How does OSSV actually transfer data from primary to secondary
system?
A: Data is moved via TCP/IP network using TCP port 10566. The communications
protocol is QSM (based on Qtree-SnapMirror). This is not to be confused with NDMP
protocol. NDMP is used by NDMP-based management applications (DFM) for
management and control of the SnapVault primary and secondary systems. The
NDMP TCP port is 10000.

So, how do snapshots keep straight the different hosts' data being SnapVaulted since the snapshots are at the volume level?  I different snapshot must be created for each host/qtree, but how many SnapVault relationships can exist on one volume at a time?

Just posted a question on the NetApp forums as I'm not having any luck creating OSSV relationships like the diagram above.