Netapp ONTAP 8.2 and SnapManager compatibility
Summary: Running SnapDrive or SnapManager on Windows 2003? You might have some decisions to make….
Netapp recently announced that ONTAP 8.2 will bring with it a new licencing model which impacts the SnapDrive and SnapManager suites. Unfortunately this could have significant impact on companies currently using those products so you need to be familiar with the changes. In KB7010074 (NOW access required) it clearly states that current versions (when running on Windows) don’t work with ONTAP 8.2;
Because of changes in the licensing infrastructure in Data ONTAP 8.2, the license-list-info ZAPI call used by the current versions of SnapDrive for Windows and the SnapManager products is no longer supported in Data ONTAP 8.2. As a result, the current releases of these products will not work with Data ONTAP 8.2.
The SnapManager products mentioned below do not support ONTAP 8.2.
- SnapDrive for Windows 6.X and below
- SnapManager® for Exchange 6.X and below
- Single Mailbox Recovery® 6.X and below
- SnapManager for SQL® 6.X and below
- SnapManager for SharePoint® 7.x and below
- SnapManager for Hyper-V 1®.x
Unfortunately there is no workaround and we need to wait for future versions of SnapManager and SnapDrive to be released sometime in 2013 (according to the KB article) before we get ONTAP 8.2 compatibility. I’ve no major issue with this situation as ONTAP 8.2 was only released a few days ago for Cluster mode and isn’t even released yet for 7 mode customers.
If you’re using Windows 2003 with any of the above products however this could be a big deal. SnapDrive 6.5 (the latest as of June 2013) only supports Windows 2008 and newer so it’s a reasonably assumption that the newer releases will have similar requirements. Until now you could still use SnapDrive 6.4 if you needed backwards compatibility with older versions of Windows – I suspect Windows 2003 is still plentiful in many enterprises (as well as my own). Now though you have a hard choice – either upgrade the relevant Windows 2003 servers, stop using the Snap products, or accept that you can’t upgrade ONTAP to the 8.2 release.
Personally I have a bunch of physical clusters all running Windows 2003 and hosting mission critical SQL databases and if these dependencies don’t change I’ll have to accelerate a project to upgrade them all in the next year or so, something that currently has no budget. Software dependencies aren’t unique to Netapp nor are Netapp really at fault – upgrading software is part of infrastructure sustainability and Windows 2003 is ten years old.
Lesson for the day: Running old software brings with it a risk.