Upgrading to Data ONTAP 7.1 or later

Issues you must resolve before upgrading

The following sections discuss upgrade issues that you must resolve before upgrading to the Data ONTAP 7.1 release family:

SnapVault relationships to WORM volumes cannot be updated after upgrading

Data ONTAP 7.1 includes new SnapVault functionality that provides better support for SnapVault relationships to WORM volumes. If you created SnapVault relationships to WORM volumes in previous Data ONTAP releases, the relationships continue to exist after the upgrade. However, because of changes in SnapVault technology, they cannot be updated.

You are advised to identify existing SnapVault relationships to WORM volumes, destroy them before upgrading, then reconfigure these SnapVault relationships after the upgrade has completed. For more information about establishing SnapVault relationships to SnapLock^TM volumes, see the Data Protection Online Backup and Recovery Guide.

iSCSI targets unavailable after upgrading to Data ONTAP 7.1

In Data ONTAP 7.1, the iSCSI target portal group tags have changed from the values used in previous releases. You must reconfigure any iSCSI hosts that use these tags or they will not be able identify the iSCSI target provided by the NetApp storage system.

Attention
HP-UX and Linux hosts must be reconfigured before upgrading to Data ONTAP 7.1.

For information about reconfiguring iSCSI hosts to identify Data ONTAP 7.1 iSCSI targets, see Upgrading iSCSI hosts.

DAFS services no longer supported

Beginning with Data ONTAP 7.1, Direct Access File System (DAFS) services are no longer supported.

To ensure that data previously exported with DAFS services remains available after upgrading to Data ONTAP 7.1, you are advised to transition critical data services from DAFS to other protocols before upgrading. To do so, complete the following steps.

Step	Action
1	Identify volumes and qtrees exported with DAFS by entering the following command: `dafs export list`
2	For each entity identified with the `dafs export` command, reassign the export to another service (such as CIFS or NFS). For current information about data access services, see the File Access and Protocol Management Guide.
3	Identify VI NIC interfaces that use the DAFS service by entering the following command: `dafs status -n`
4	Halt the DAFS service by entering the following command: `dafs stop`
5	For each VI NIC interface identified with the `dafs status` command, detach the interface from the DAFS service by entering the following command: `dafs detach` interface_name
6	Make appropriate changes on DAFS client systems to ensure continuity of data access.

For more information about configuring and managing DAFS, see the File Access Management Guide and dafs man pages for the Data ONTAP release on which you originally configured DAFS services.

SnapLock Compliance license update

If you have a SnapLock^TM Compliance license and you are upgrading to Data ONTAP 7.1 from a Data ONTAP version earlier than 7.0.0.1, you must obtain a unique, updated SnapLock Compliance license code from the Protocol Licenses page, located on the NOW site at the following URL:

https://now.netapp.com/eservice/agree.do?moduleName=PROTOCOL

Previous SnapLock Compliance license codes have been replaced with updated license codes on the Protocol Licenses page.

Note
There are two types of SnapLock licenses: SnapLock Compliance and SnapLock Enterprise. When you display licenses for your storage system, the Snaplock Compliance license is listed as "snaplock" and the Snaplock Enterprise license as "snaplock_enterprise". This update concerns SnapLock Compliance licenses only.

If a storage system is upgraded to Data ONTAP 7.0.0.1 or later without changing the license code, the attributes and SnapLock protection on existing SnapLock files (and SnapLock volumes) are not affected in any way. However, since the old license is no longer functional, you cannot commit any new files to SnapLock protected status (WORM--Write-Once-Read-Many) until the license code is updated. Also, you cannot create new WORM volumes until the license code is updated.

For more information about displaying and managing licenses, see the System Administration Guide.

FlexClone license update

If you created FlexClone^TM volumes (clones of FlexVol volumes) in a Data ONTAP 7.0.x release and you are upgrading to Data ONTAP 7.1, you must obtain a unique FlexClone license code from the Protocol Licenses page, located on the NOW site at the following URL:

https://now.netapp.com/eservice/agree.do?moduleName=PROTOCOL

The FlexClone license was not enforced in Data ONTAP 7.0.0x releases (you could create FlexClone volumes without a license). However, the license is enforced in Data ONTAP 7.0.1 and later releases. When you upgrade to Data ONTAP 7.1, you do not need a license to access FlexClone volumes created in previous releases, but you cannot create new FlexClone volumes without a license.

For more information about FlexClone volumes, see the Storage Management Guide.

Space guarantees now enabled on FlexClone volumes

If you created FlexClone volumes in releases of Data ONTAP earlier than 7.1 and you specified space guarantees in the parent volumes, these guarantees were inherited but not enabled in the FlexClone volumes. FlexClone volumes in earlier releases therefore were not subject to aggregate overcommitment requirements.

Beginning with Data ONTAP 7.1, space guarantees are enabled in FlexClone volumes, including FlexClone volumes that were created in earlier releases. To ensure that existing FlexClone volumes can obtain guaranteed space when mounted after upgrading, your are advised to review the volume guarantees of any existing FlexClone volumes before upgrading to Data ONTAP 7.1.

You can change space guarantees to enable or disable aggregate overcommitment using the vol options guarantee command. For more information about FlexClone volumes and space guarantees, see the Storage Management Guide.

SnapDrive for Windows upgrade to version 3.1.1

Versions of SnapDrive^TM for Windows earlier than 3.1.1 are incompatible with Data ONTAP 7.0.0.1 and higher. If you are upgrading to Data ONTAP 7.1 and you are using an earlier SnapDrive version, you must upgrade SnapDrive for Windows to version 3.1.1 or higher.

You are advised to upgrade SnapDrive on your Windows host before upgrading your storage system to Data ONTAP 7.1.

To download SnapDrive for Windows software from the NOW site to your Windows host, complete the following steps.

Step	Action
1	Use a Web browser to go to http://now.netapp.com/.
2	Click Service & Support.
3	Click Download Software.
4	In the Select Platform list box in the SnapDrive product row, select Windows and click Go. Result You see a list of the versions of SnapDrive for Windows. Click the 3.1.1 version link to see more information and to download software.

Change in CIFS SMB signing default behavior

By default, SMB signing is disabled in Data ONTAP 7.0.2 and later releases; it was enabled by default in Data ONTAP 7.0.1. If you are upgrading to Data ONTAP 7.1 from 7.0.1 and if you have configured CIFS clients in your environment to require SMB signing, you must enable SMB signing by setting the cifs.signing.enable option to on.

For more information, see the NetApp options(1) man page and the File Access and Protocols Management Guide.

Note
Enabling SMB signing in a Windows environment can affect the performance of both Windows clients and storage systems running Data ONTAP. For more information, see the File Access and Protocols Management Guide.

Data ONTAP 7.1 upgrades could take longer than usual

When you upgrade to Data ONTAP 7.1, Inode To Pathname (i2p) information is written to each existing volume. Depending on the number of volumes on your system, this could cause the upgrade to take more time than previous Data ONTAP upgrades to complete.

Recommendations for all storage systems upgrading to Data ONTAP 7.1

Keep the following tips in mind before upgrading to Data ONTAP 7.1:

Upgrade during non-peak hours.
Avoid performing a quota initialization prior to upgrading. If a quota initialization is begun prior to upgrading, wait for the initialization to complete.
Note
Beginning in Data ONTAP 7.0, quota initialization is terminated when you halt, reboot, or upgrade your storage system. For more information, see the Storage Management Guide.