This section discusses upgrade issues that you should be aware of if you are upgrading from a version of Data ONTAP earlier than 7.1:
The following sections discuss new behavior in systems that have been upgraded to the Data ONTAP 7.0 release family:
If you are upgrading Data ONTAP software in systems with DS14 or DS14Mk2 disk shelves, including FAS200 series systems, and you are currently running a version of Data ONTAP that does not include a fix for Bug ID 113823 (Disk flash corrupted during firmware update), do not update disk firmware before upgrading Data ONTAP. Instead, upgrade your Data ONTAP software to a release that contains a fix for Bug ID 113823 first, then update disk firmware.
Attention
If your system is susceptible to Bug ID 113823, failure to upgrade software before updating disk firmware could cause disk drive damage and data loss.
For a list of Data ONTAP versions in which Bug ID 113823 has been fixed, see the following URL:
http://now.netapp.com/NOW/cgi-bin/bugrellist?bugno=113823
Disk firmware is automatically updated on reboot as part of the Data ONTAP upgrade whenever the disk drives are running firmware older than the firmware version that is included with the new Data ONTAP release. As disk firmware is updated, it is possible (though unlikely) that all disk drives on a shelf will receive the update at the same time. This simultaneous update might cause the firmware update process to fail, rendering the disks unusable and causing loss of data if it happens to multiple disks in the same Redundant Array of Independent Disks (RAID) group.
The Data ONTAP 7.0 release family fixes Bug ID 113823 by preventing firmware from being concurrently updated on all disk drives. For more information about this issue, see the description for Bug ID 113823, on the NOW site at the following URL:
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=113823
Note
Bug ID 113823 occurs only when every disk drive on the shelf requires an update.
If you have AutoSupport enabled, you can use the AutoSupport analysis tool, available on the NOW My Installed Products page, to verify your disk firmware version in advance and find out whether your system is vulnerable to Bug ID 113823.
Attention
If the AutoSupport analysis indicates that all disks on a disk shelf need firmware updates, failure to upgrade software before updating disk firmware could cause disk drive damage and data loss.
For instructions about using the AutoSupport analysis tool to detect disk firmware requirements, see Detecting outdated disk firmware.
If you are upgrading a diskette-based storage system from a version of Data ONTAP earlier than 6.2, your are advised to upgrade to Data ONTAP 6.3.3 or the latest release in the 6.3 release family first before upgrading to the Data ONTAP 7.0 release family.
By upgrading in two steps, you reduce the number of RAID and WAFL® (Write Anywhere File Layout) changes. As a result, the upgrade from Data ONTAP 6.3.3 to 7.0 should finish sooner with less risk of problems.
You are advised to upgrade the following storage systems to Data ONTAP 6.3.3 or the latest release in the 6.3 family before upgrading to the Data ONTAP 7.0 release family:
You can download Data ONTAP 6.3.3 from the Download Software page (on the NOW site at http://now.netapp.com/NOW/cgi-bin/software/). Under Data ONTAP, select your platform, then select View & Download under the Data ONTAP 6.3.3 release and follow the instructions.
When you upgrade to Data ONTAP 7.0 or later, you are advised to configure your Fibre Channel-Arbitrated Loop (FC-AL) adapters to run in 1-Gb and 2-Gb mode by changing the jumpers on the adapter. If you have not already done so, you are also advised to upgrade system firmware to Open Firmware (OFW) 4.3 or later in order to be compatible with the new 1-Gb and 2-Gb setting.
Note
Do not apply any configuration changes to FCP target-mode adapters.
FC-AL adapters configured for 1-Gb mode will continue to work in a Data ONTAP 7.1 environment without resetting the jumpers or upgrading firmware. However, 1-Gb and 2-Gb mode is recommended for best performance of these adapters.
Complete this procedure if your FC-AL adapters have the following marketing and spare part numbers:
To reconfigure your FC-AL adapters and upgrade firmware, complete the following steps.
| 1 |
Upgrade the system firmware to OFW 4.3 or later. You can find system firmware on the Service Image page (on the NOW site at http://now.netapp.com/NOW/download/tools/serviceimage/). Follow the instructions given there to download and install system firmware 4.3 or later. For more information on upgrading system firmware, see Chapter 3, Upgrading NetApp Firmware. Note |
| 2 |
Upgrade Data ONTAP to 7.0 or later as described in Chapter 4, Upgrading Data ONTAP Software. |
| 3 |
Remove any FC-AL adapters from your system chassis and verify that jumpers J3 and J4 are set in the 1-2 position as described in "Configuring new and existing FC-AL adapters" (on the NOW site at http://now.netapp.com/NOW/knowledge/docs/hardware/filer/adapter.pdf). Reposition the jumpers if necessary. Note |
FC-AL adapters can be installed on the following storage systems:
When you upgrade to Data ONTAP 7.0 or later, any existing volumes are preserved as traditional volumes. Both traditional and FlexVol volumes are supported in Data ONTAP 7.1; you are not required to use FlexVol volumes.
If you want to take advantage of FlexVol volume technology, you must create new FlexVol volumes and aggregates, then migrate your data from existing traditional volumes to the new FlexVol volumes using the ndmpcopy command.
Note
Snapshot copies on the original volume are unaffected by the migration, but they are not valid for the new volume.
Note
In the Data ONTAP 7.0 release family, the storage system root volume can be either a traditional or a FlexVol volume. However, because you have more control over the size of FlexVol volumes than you do over traditional volumes, changing the traditional root volume to a flexible root volume allows you to organize your storage more efficiently. For information about changing the root volume to a FlexVol volume, see the System Administration Guide.
To provide space reservations for traditional volumes in the Data ONTAP 7.0 release family, you must assign file reservation after each file is created.
If your system includes volumes with default file space reservation enabled (using the create_reserved parameter of the vol options command), default space reservation is no longer available in the corresponding traditional volume after upgrading to the Data ONTAP 7.0 release family. Any files created in the volume after upgrading will not have space reservations enabled unless specified on a per-file basis. However, space reservations will remain enabled for any files created before upgrading.
For more information about space reservation and guarantees, see the Storage Management Guide.
Beginning with the Data ONTAP 6.5 release family, several vol command options cause automatic updates to the /etc/exports file, as described in Automatic editing of the /etc/exports file.
In the Data ONTAP 7.0 release family, the following additional operations cause the exports file to be edited:
When a clone is created from a FlexVol volume, a new clone volume is created in the exports file. The cloned volume has the same export rules as the parent.
If a vFilerTM unit is migrated to a new physical storage system, the exports file is modified to reflect any changes to volume configuration.
The Data ONTAP 7.0 release family supports files with up to 16 TB of data. However, transfers of data to systems running earlier versions of Data ONTAP fail if the file system being transferred contains a file larger than 4 TB. The following features can be affected by this issue.
A qtree replication from a SnapMirror source system running Data ONTAP 7.0 or higher will fail if any mirrored qtree includes a file larger than 4 TB and the qtree SnapMirror destination system is running a version of Data ONTAP earlier than 7.0.
SnapVault transfers from a primary storage system fail if the qtree or directory to be backed up includes a file larger than 4 TB and the SnapVault secondary system is running a version of Data ONTAP earlier than 7.0.
Data restorations from a tape created with the dump command on a storage system running Data ONTAP 7.0 or later fail if the tape archive includes a file larger than 4 TB and the restoration target system is running a version of Data ONTAP earlier than 7.0.
Note
It is not a requirement for qtree SnapMirror destination systems, SnapVault secondary systems, or restoration target systems to run a version of Data ONTAP that is the same or later than the version the source system is running. The requirement to upgrade destination systems before source system applies only to SnapMirror for volume replication. Nonetheless, if you upgrade systems with these configurations to Data ONTAP 7.0 or later before upgrading the corresponding source systems, you will not encounter problems transferring files up to 16 TB.
For more information about SnapMirror and SnapVault, see the Data Protection Online Backup and Recovery Guide.
For more information about the restore command, see the Data Protection Tape Backup and Recovery Guide.
The Data ONTAP 7.0 release family provides enhanced capabilities for access control and administrative account management. When you upgrade to Data ONTAP 7.0 or later, any existing local users who are not root users are granted full privileges. To manage or reduce those privileges, you must create one or more groups with defined roles and capabilities, then place the users in groups.
For more information about user account management, see the System Administration Guide.
In the Data ONTAP 7.0 release family, user names are no longer case-sensitive. For example, in previous releases the names "admin" and "Admin" can stand for two different users, but in Data ONTAP 7.0 and later, the second name is a duplicate of the first.
When you upgrade to Data ONTAP 7.0 or later, account names are scanned, an error message is displayed if such duplicate user names are detected, and the second name is given a suffix; for example, the duplicate "Admin" would become "admin-a".
In this case, any user attempting to log in to the storage system with the Admin account name and password would be denied. To correct this, you must give the user the modified account name or assign a new account name with appropriate privileges.
For more information about user account management, see the System Administration Guide.
The vol status command has been modified in the Data ONTAP 7.0 release family to distinguish between flexible and traditional volumes. If you created scripts in earlier releases, some command output has changed, which might affect the behavior of your script.
Specifically, the Status column of the vol status command output is now a comma-separated list including RAID type and storage container type (flexible or traditional), as shown in the following example.
filer12> vol status
Volume State Status Options
tv online raid4, trad resyncsnaptime=10
mtv online raid4, trad
mirrored
vol0 online raid_dp, flex root
fv1 online raid_dp, flex
fv2 offline raid_dp, flex
For more information about the vol status command and output, see the vol(1) manual page.
Except as noted, the vol commands continue to function as they have in previous releases. However, the Data ONTAP 7.0 release family introduces the aggr command set, which is used to manage the physical layer of storage management presented in aggregates. If you use a vol command to manage physical storage components, such as disks or RAID, you will see an advisory error message recommending that you use the appropriate aggr command.
For example, if you use the vol mirror command to mirror a FlexVol volume, you will see the following screen message:
filer12> vol mirror fv1 -d v0.25 -dv0.26
vol mirror: 'fv1' is a flexible volume.
Consider using the 'vol container fv1' command to find its
containing aggregate, then 'aggr mirror' to mirror it.
For more information about aggregate and volume management commands, see the follow documents:
Note
You are advised to use the aggr command to manage physical storage components.
Quotas are turned off during the upgrade to the Data ONTAP 7.0 release family. This is because the online quota format is changed in this release and the quota database must be rebuilt. As part of the upgrade, quotas are automatically turned back on when the database has been rebuilt and the upgrade is complete.
If you have set quotas, and you want to verify that the quota database has been rebuilt and quotas are back on, enter the quota command without options. For more information about using the command, see the quota(1) man page.
The Data ONTAP 7.0 release family includes built-in SecureAdminTM functionality with SSL (Secure Socket Layer) protocol. It is no longer necessary to install and license it as a separate product.
If you installed and licensed the SecureAdmin product in earlier Data ONTAP releases, your existing SSL certificates are converted on upgrade. However, you must re-enable SSL after the upgrade for the new certificates to take effect. To do so, enter the following command after the upgrade has completed:
secureadmin enable ssl
For more information about SSL and SecureAdmin functionality in the Data ONTAP 7.0 release family, see the System Administration Guide.
Beginning with Data ONTAP 6.4.4, the vscan timeout option had a default setting of 10 seconds. If your storage system has been upgraded at any time from Data ONTAP 6.4.3 or earlier and you have not explicitly reset this option, the original default value of 30 seconds is still in effect.
This option controls the length of the waiting period before the scanning client checks the status of a virus scan request. By setting the option to a lower value, you enable the storage system to determine more quickly if there is a problem with a virus scan request. You are therefore advised tp set this option to 10 seconds or another lower value appropriate to your configuration.
To view the current setting of the vscan timeout option, enter the following command at the storage system console:
vscan options timeout
To set the vscan timeout option to a new value, enter the following command at the storage system console (where nn is the new value in seconds):
vscan options timeout set nn
For more information about virus scanning in the Data ONTAP 7.0 release family, see the Data Protection Online Backup and Recovery Guide and the vscan(1) man page.
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01083_B0
File: 2upgrad8.htm
Last updated: 16-Dec-2005 18:19:09