FIrst, some background: we are migrating from SnapDrive/SMSQL to SnapCenter, however SC has numerous bugs <related to failover clusters and mount points> that requires us to keep SnapDrive (but not SMSQL) on a few servers until the bugs are patched. We are running OnTAP 9.3 because SnapDrive isn't supported in OnTAP 9.4 and above. I am aware there are special bundled versions of SnapDrive with certain SnapManager products (such as Hyper-V) that are supported in OnTAP 9.4 and above, but SMSQL isn't one of them.
Now my question: what if I installed one of the special SnapManager/SnapDrive bundled products on the SQL Servers where I need SnapDrive, and just didn't use the SnapManager component? Would that be a legitimate way to get a supported version of SnapDrive on those servers so we can upgrade to OnTAP 9.5? It would be even simpler, of course, if installing the latest SnapDrive patch as a standalone would be compatible (see below), but everything I've seen so far indicates it is not.
Would love to hear anyone's insight! Thanks in advance.
When a SnapDrive version is not supported on a certain Ontap version, it becomes pretty much useless as it doesn't let you do anything. My question is, why use SnapDrive at all? What's the hypervisor? VMware or Hyper-V? You should just be able to mount the LUN to an iGroup and connect to the physical hosts.
Thanks @mrahul . The only thing we have to continue using SnapDrive for is LUN creation on Windows Failover Clusters. All other activities would be done in SnapCenter. Once the bug is resolved we would eliminate SnapDrive. I'm not using PowerShell to run SnapDrive or SnapCenter commands so that shouldn't be an issue for us. Thank you for the tips!