**This is now an expired document**
Windows Server 2003 and NetApp Data OnTAP 8.2
Good news for all you out there that have legacy systems that are running Windows Server 2003 and are connected to NetApp filers and are looking at upgrading to NetApp Data OnTAP 8.2.
With the release of NetApp Data OnTAP 8.2, some users face the problem of having legacy systems connected to their filers with iSCSI connections, it is now possible to connect to the NetApp filers that have Data OnTAP 8.2.
I have multiple Windows Server 2003 system (EE and SE) with Service Pack 2 installed.
I am upgrading a NetApp filer to OnTAP version 8.2.
OnTAP version 8.2 has a minimum requirement of SnapDrive version 7.x if you want to be able to do iSCSI connections. According to NetApp’s Interoperability/Compatibility Matrix – SnapDrive 7.x is not supported on Windows server 2003.
Before I started looking at this I had iSCSI initiator 2.08 and SnapDrive 6.4.2 installed on my Windows 2003 servers.
I also had Snap-manager for SQL on some of the systems.
Steps to resolve the problem:
After some reading and a few conversations with NetApp techies it was suggested that I build a test system and install SnapDrive 7.0.2p1 on it and try connecting to the existing filer (OnTAP 8.1.2 7-mode)
I installed SnapDrive 7.0.2P1 on my windows 2003 server. There are some software requirements before you can proceed with this, namely;
- .Net 351 SP1
- .Net 4.0 Framework
- Microsoft patches – Q931300, Q937382 and Q932755.
Once these were all installed, I was able to continue with the install of SnapDrive 7.0.2P1. I then proceeded to create a volume and lun on the NetApp filer I was connected to – SUCCESS !!