Data ONTAP 7.3 Upgrade Guide

Copyright information
Trademark information
About this guide
Audience
Accessing Data ONTAP man pages
Terminology
FilerView as an alternative to the command-line interface
Command, keyboard, and typographic conventions
Special messages
Overview of the upgrade process
Decisions to make before you upgrade
Using the Upgrade Advisor to plan your upgrade
System requirements
- Making sure your system supports the current Data ONTAP release
- Making sure there is adequate free space in every volume containing LUNs
- Checking for the latest versions of system firmware for your system
- Determining the required firmware for your disks
- Determining the required firmware for your disk shelves
Upgrade host requirements
- Requirements when upgrading from a Windows or UNIX client using the CIFS or NFS protocols
- Requirements when upgrading from a Windows or UNIX client using the Upgrade Utility
- Requirements when upgrading from an HTTP server
Decisions to make about release family upgrades
- Differentiating among types of upgrades
- Upgrading within a release family
- Upgrading between release families
Decisions to make about the upgrade method for active/active configurations
- Overview of standard active/active upgrades
  - When to use standard active/active upgrades
- Overview of nondisruptive active/active upgrades
- Cluster Configuration Checker
Upgrade requirements for SnapMirror
- Why you must plan for SnapMirror upgrades
- Identifying SnapMirror destination volumes
- Upgrading SnapMirror for volume replication
- SnapMirror synchronous and asynchronous mode during upgrade
- Upgrade requirements for systems mirroring each other
Decisions to make about upgrade issues
- Required intermediate upgrades
- Decisions to make to upgrade to the Data ONTAP 7.3 release family
- Decisions to make to upgrade from releases earlier than Data ONTAP 7.2
  - Issues to resolve before upgrading from releases earlier than Data ONTAP 7.2
    - Solaris iSCSI targets need to be reconfigured before upgrading to Data ONTAP 7.2 or later
    - If you use a vif that is named "vip"
  - Behavior changes when upgrading from a release earlier than Data ONTAP 7.2
- Decisions to make to upgrade from releases earlier than Data ONTAP 7.1
  - Issues to resolve before upgrading from releases earlier than Data ONTAP 7.1
  - Behavior changes when upgrading from a release earlier than Data ONTAP 7.1
- Decisions to make to upgrade from releases earlier than Data ONTAP 7.0
  - Issue to resolve before upgrading from releases earlier than Data ONTAP 7.0
    - Upgrading storage systems with FC-AL adapters
  - Behavior changes when upgrading from a release earlier than Data ONTAP 7.0
Considerations for upgrading iSCSI hosts
- Changes to target portal group tags in Data ONTAP 7.1 and later
- Required steps before upgrading an iSCSI host
Firmware updates
Firmware upgrade requirements
- How to obtain system firmware updates
- Determining whether you need a system firmware update
- Firmware updates on single systems
- Firmware updates on systems in an active/active configuration
  - Updating firmware nondisruptively
  - Updating firmware using the standard method
Updating disk firmware
- About disk firmware updates
- Service availability during disk firmware updates
- Detecting outdated disk firmware
- When to update disk firmware manually
- Command for updating disk firmware
Updating disk shelf firmware
- About disk shelf firmware updates
- Service availability during disk shelf firmware updates
- Detecting outdated disk shelf firmware
- Updating disk shelf firmware manually
About RLM firmware updates
- Using the Data ONTAP CLI to update the RLM firmware
- Using the RLM CLI to update the RLM firmware
About BMC firmware updates
- Obtaining and installing the BMC service image
- Updating BMC firmware nondisruptively
- Updating BMC firmware using the standard method
How to upgrade Data ONTAP software
Prerequisites to software upgrade
- What you need for the upgrade
- Preparing for the upgrade
  - Enabling DNS with Windows 2000 name server addresses
  - Verifying that you have a domain account
How to obtain Data ONTAP upgrade .exe images
- HTTP server steps
  - Copying the upgrade .exe image
  - Copying upgrade .exe images without installing
- UNIX client steps
  - Mounting the storage system on your client
  - Obtaining upgrade .exe images
    - Getting the upgrade .exe image using a Web browser
    - Copying the upgrade .exe image from the CD-ROM
- Windows client steps
  - Mapping the storage system to a drive
  - Obtaining upgrade .exe images
    - Getting the upgrade .exe image using a Web browser
    - Copying upgrade .exe images from the CD-ROM
- Managing files in the /etc/software directory
- The Upgrade Utility
How to install Data ONTAP system files
- Using the software update command
- Using the software install command
How to download Data ONTAP to single systems
- Upgrading single systems
- Upgrading Data ONTAP on a single FAS900 series or NearStore system
How to download Data ONTAP to systems in an active/active configuration
- Decisions to make about your active/active configuration upgrade procedure
- Upgrading your active/active configuration from an earlier release family nondisruptively
- Upgrading your active/active configuration within a release family nondisruptively
- Upgrading your active/active configuration using the standard method
- Upgrading your FAS900 series storage system in an active/active configuration using the standard method
Guidelines for reverting to a previous release
Why there might be issues
General guidelines for reverting from the Data ONTAP 7.3 release family
Decisions to make before reverting from Data ONTAP 7.3.1
- Downgrading deduplicated volumes with increased maximum size to Data ONTAP 7.3
- Reverting deduplicated volumes with increased maximum size
- Reverting a SnapMirror destination system with volumes that use deduplication or clone operations
- Reverting when IPv6 is enabled
  - Downgrading to Data ONTAP 7.3 when IPv6 is enabled
  - Reverting to an earlier release family when IPv6 is enabled
- Reverting when SnapLock is enabled
- Reverting archival Snapshot copies
- Reverting systems with cloning enabled
- Reverting when Kerberos multi-realm support is enabled
  - Downgrading to Data ONTAP 7.3 when Kerberos Multi Realm support is enabled
  - Reverting to an earlier release family when Kerberos Multi Realm support is enabled
Decisions to make before reverting to Data ONTAP 7.2
- Flexcache reversion limitations
- Deduplication requires additional free space in volumes after reverting
- SnapMirror and SnapVault restart checkpoints deleted during reversion
- SnapVault licenses might need to be removed before reverting
- SnapVault restore processes must be complete before reverting
- Large NFSv4 ACLs removed when reverting from Data ONTAP 7.3
- FPolicy file extension length limits on revert
Decisions to make before reverting to Data ONTAP 7.1
- Volumes in excess of 200 must be destroyed before reverting to Data ONTAP 7.1.x or earlier
- SnapLock autocommit option must be disabled before reverting
Decisions to make before reverting to Data ONTAP 7.0
- SnapVault relationships to SnapLock volumes must be removed before reverting
- Reverting to releases earlier than Data ONTAP 7.1 not permitted with WORM appendable files on SnapLock volumes
- Reversion cannot take place during I2P initialization
- Reversion to Data ONTAP 7.0.x removes root from administrator group
Decisions to make before reverting to Data ONTAP 6.5
- Flexible root volumes cannot be reverted
- FlexVol volumes and data cannot be reverted
- FlexCache volumes cannot be reverted
- Full administrative access privileges after reversion
- Changes to vol status and aggr status command output after reversion
- SSL must be reenabled after reversion
- Connections requiring SMB signing not available after reversion
- Connections requiring LDAP signing not available after reversion
- Storage system domain accounts must be recreated after reverting to releases earlier than Data ONTAP 6.5.3
Optimizing service availability during upgrades
How upgrades impact service availability
Service and protocol considerations
- Considerations for stateless protocols
- Considerations for session-oriented protocols