I've been having some interesting discussions regarding the different versions of SnapManager for SharePoint (SMSP) and how they work with the different versions of SnapDrive for Windows (SDW). One of the major investments in the latest release of SMSP 8.0 was support for Clustered ONTAP 8.2, this also included upgrades to SnapManager 7.0 for SQL Server and SDW 7.0. As always refer to the NetApp Interoperability Technology & Matrix site for all compatibility details, in this post I'm just trying to explain a few technical details that are not covered in IMT. Here are a few of the facts:
SMSP 8.0 is the version that fully supports SDW 7.0 and SMSQL 7.0 with all of the new features introduced. For example, SnapVault integration with SMSQL 7.0 without the need for using Protection Manager; SMSP leverages the new features in SMSQL 7.0 to offer this capability.
SMSP 7.1.1 does support SDW 7.0, but it does not support SnapMirror or SnapVault updates on Clustered ONTAP 8.2. This is because SMSP 7.1.1 does not provide an interface to handle this processing. In Clustered ONTAP 8.2 we use the Invoke-SdSnapMirrorUpdate cmdlet to update the SnapMirror and SnapVault destinations and because SMSP 7.1.1 was developed prior to SDW 7.0s release we don't support that specific feature cmdlet call. SMSP 7.1.1 and SDW 7.0 can be used together but some functionality will not work as noted previously.
SMSP 6.x, 7.0 and 7.1 do not support SMSQL 7.0 because it requires the Microsoft .NET Framework 4.x, which also means that SDW 7.0 will not work well with these versions either.