Best Practices for
upgrading to Data
ONTAP 8.0.1 7-Mode
NetApp Partner Services
Enablement Team
28 Mar 2011
Limited Distribution
© 2008 NetApp. All rights reserved.
Partner Services Enablement Team
Develop and enable PS Certified partner’s ability to deliver NetApp related services
Technical enablement and development– Customize partner training, PS-related bootcamps
Installation and implementation advice and know-how– Via the Solution Center (877-NETAPP-0)
– Via email [email protected]
– Implementation planning “peer review” and guidance
Not a technical support group– Call us for the 411 on a service, tool or process
– Call the Global Support Center for a 911 when something does not work.
2Limited Distribution
© 2008 NetApp. All rights reserved. 3
Purpose
1. To discuss best practices for performing Data
ONTAP upgrades.
2. To notify you of currently known upgrade and
reversion issues.
Limited Distribution
© 2008 NetApp. All rights reserved. 4
Assumptions
1. Familiarity with new features in Data ONTAP 8
7-Mode.
2. Familiarity with upgrade process.
3. Customer is running a version of Data ONTAP 7.3
4. Understand that ONTAP 8 is still “new” and best
practices may change as new versions are
released.
Limited Distribution
© 2008 NetApp. All rights reserved.
Data ONTAP 8.0.1 Supported Hardware
Supported Systems
– FAS/V6200
– FAS/V6000
– FAS/V3200
– FAS/V3100
– FAS/V3070 and 3040
– FAS2040
Supported Shelves
– DS2246
– DS4243
– DS4243 with SSD
– DS14mk2 and mk4 FC
– DS14mk2 AT
Supported Cache Cards
– Flash Cache (PAM II)
– PAM I
New
New
New
7-Mode and Cluster-Mode
Non-Supported Systems
– FAS2020 and 2050
– FAS/V3050 and 3020
– FAS900 Series
– NearStore R Series
Non-Supported Shelves
– DS14 (aka DS14mk1)
5Limited Distribution
© 2008 NetApp. All rights reserved.
Data ONTAP 8.0.1 7-Mode Features
Features also in 7.3.4 SAN and NAS support
– FC, FCoE, iSCSI
– CIFS SMB 2.0; NFSv2, v3, v4
Storage efficiency
– Deduplication, FlexClone®, thin
provisioning, Snapshot™
Data protection
– SnapVault® and SnapMirror®
(including network compression)
Storage & data management
– Systems Manager; Operations
Manager and plug-ins
– MultiStore®; zAPIs
Server/application integration– SnapDrive® and SnapManager®
New 8.0.x Features 64-bit aggregates (new aggrs)
– 64-bit root volume aggregate
Data compression
Unified Connect
NetApp DataMotion for
Volumes
16TB vols with deduplication
– FAS2040, FAS/V 3140 & 3040
VMWare vSphere 4.1 VAAI
support
20-drive SATA RAID-DP®
groups
* Features new in 8.0.1 in blue
6Limited Distribution
© 2008 NetApp. All rights reserved.
Data ONTAP 8.0.1 7-Mode
Key Data ONTAP 7.3.x functionality not supported with
Data ONTAP 8.0.1 7-Mode
NetApp Data Motion for MultiStore vFiler
– NetApp Data Motion functionality introduced with
Data ONTAP 7.3.3
– Note: vFilers can be moved between HA systems with
SnapMirror, but not guaranteed to be non-disruptive
IPv6
SnapLock Compliance and Enterprise
IPsec
Data ONTAP 7.3.x Functionality NOT in 8.0.1
7Limited Distribution
© 2008 NetApp. All rights reserved.
Data ONTAP 8.0.1 Cluster-Mode Features
NAS support– CIFS SMB 1.0
– NFSv2 and v3
Storage efficiency– 64-bit aggregates, Snapshot
Data protection– Within cluster SnapMirror, SMTape
Storage and data management– Cluster-wide namespace and single-system management
– Vservers and non-disruptive data movement
– Scale-out controller and capacity growth
– Dynamic lP load-balancing and load-balancing mirrors
– Qtrees
Server virtualization and application integration– not available yet
8Limited Distribution
© 2008 NetApp. All rights reserved.
Data ONTAP 8.0.1 7-Mode Use Cases
Systems with large datastores will typically use high
capacity SATA drives
– Large SATA drives should be used in 64-bit aggregates
for best storage efficiency and volume-level performance
– 20-drive RAID-DP groups adds to storage efficiency
– Flash Cache support improves performance for repeat
random reads
#1 – Large Datastores
#2 – New FAS or V-Series Systems
Customers buying or upgrading to FAS or V 6200 and
3200 systems
– FAS/V 6200 are only supported on Data ONTAP 8.0.1
– FAS/V 3200 are introduced first on Data ONTAP 8.0.1
9Limited Distribution
© 2008 NetApp. All rights reserved.
Data ONTAP 8.0.1 7-Mode Use Cases
Performance-insensitive primary and secondary
storage where data compression can improve storage
efficiency – Data Compression
#3 – Compressible Datasets
#4 – FC and iSCSI SAN Storage
SAN deployments where non-disruptive data
movement is important – NetApp DataMotion
FCoE or Unified Target Adapter
#5 – New Datacenter Deployments
Customers planning new datacenter deployments may
want to consider an unified 10GbE network - UTA
10Limited Distribution
© 2008 NetApp. All rights reserved. 11
Preparing for an upgrade
1111Limited Distribution
© 2008 NetApp. All rights reserved. 12
Choosing the version of Data ONTAP
Does the customer have a preference?
Some customers are only authorized to install
releases they have already validated.
What hardware components are installed?
New components, like Flash Cache or UTA cards,
often function better with the latest RC or P releases.
What functionality does the customer want?
New functionality may only be available in new
releases.
12Limited Distribution
© 2008 NetApp. All rights reserved. 13
Choosing an RC or P release
1. RC releases have been tested internally but have not
reached the minimum number of installs on production
systems to be granted GA status. They are production
ready and supported by NetApp Global Services (NGS).
2. P releases contain patches added to RC or GA releases.
They may not have been as rigorously tested. NetApp
recommends P releases if a system has already
experienced a bug. These upgrades are free for
Premium Support customers. Troubleshooting P
releases can be more time-intensive for NGS.
When installing a P release, we suggest offering a free
upgrade to the next GA release. Make the offer time-limited
(e.g., within 2 weeks of GA availability).
13Limited Distribution
© 2008 NetApp. All rights reserved. 14
Determine Feasibility and Potential
Issues
Compare current version with new version by reading the
Release Notes
Read the Upgrade Guide – it contains caveats for Non-
Disruptive Upgrades.
Verify free space in aggregates (<=96% full)
Verify free space in volumes with LUNs (>= 1MiB)
Run the HA Configuration Checker
(aka Cluster Configuration Checker)
14Limited Distribution
© 2008 NetApp. All rights reserved. 15
Determine Feasibility and Potential
Issues
Identify SnapMirror/SnapVault source and destination
systems and record relationship information
Run the Upgrade Advisor tool – check for firmware
upgrades and include back out plans
SAN environments – verify components are still compatible
using the Interoperability Matrix Tool (IMT)
- verify all hosts are multipathed and the multipath
connections are working
Use the Knowledge Base, Communities, and TechNet
websites to search for tribal knowledge
15Limited Distribution
© 2008 NetApp. All rights reserved. 16
Create a checklist
Checklists reduce errors and gives the customer confidence
in the process. Add these steps to your checklist:
- use the config dump command to backup the current
configuration
- Take Snapshots of the root volume and all
SnapMirror/SnapVault volumes
(create a „source‟ script to automate the work)
- Use the logger command to insert comments into the
system log
- Capture the options settings to a text file before and
after the upgrade
16Limited Distribution
© 2008 NetApp. All rights reserved. 17
Verifying storage controller options using WinMerge to
compare text files
17Limited Distribution
© 2008 NetApp. All rights reserved. 18
Prepare for the worst
- establish checkpoints and hard stop conditions
Set Customer Expectations
- NDU or disruptive upgrade?
Major release upgrades should always be disruptive
- Time required to perform upgrade and reversion
Plan for 20 – 60 minutes just for the download process
- Impact of reversion
18Limited Distribution
© 2008 NetApp. All rights reserved.
13
Check to see if the card has been properly updated.
filer01> version -b
The primary kernel should be 6.4.5.
13.5
If step 13 fails, perform the following steps and repeat step 12:
filer01> priv set advanced
ljcds-filer*> bootfs help info
ljcds-filer*> bootfs fdisk <name> 1
14Terminate CIFS.
filer01> cifs terminate
15Disable the cluster.
filer01> cf disable
16Stop the iSCSI service:
iler01> iscsi stop
17Halt the filer.
filer01> halt
GO/NO-GO CHECKPOINT
18Restart the filer
CFE>bye
19Interrupt the reboot process. While POST is running, press CTRL-
BACKSPACE to abort the autoboot.
20Update the MB firmware
CFE>update_flash
21Reset the firmware.
CFE>set-defaults
19Limited Distribution
© 2008 NetApp. All rights reserved. 20
Performing the upgrade
20© 2008 NetApp. All rights reserved. Limited Distribution
© 2008 NetApp. All rights reserved. 21
Performing the Upgrade
Perform intermediate upgrades from 7.2 and earlier to
7.3 first.
Download the correct install package
- one for upgrading from 7.3.x
- one for upgrading from 8.x
Resize root volume (250 GiB minimum)
Halt or abort SnapMirror, SnapVault and Dedupe
processes
Verify system configuration and cf functionality by
rebooting or performing a takeover/giveback
21Limited Distribution
© 2008 NetApp. All rights reserved. 22
Performing the Upgrade
Upgrade using the software update command
- CIFS and NFS installs not supported (file copy still
acceptable)
Use HTTP server to transfer install package and
firmware
- easy to install a free standalone server on laptop
- eliminates need to connect to customer network
Install firmware packages that were released after the
latest GA version of Data ONTAP
22Limited Distribution
© 2008 NetApp. All rights reserved. 23
Known Upgrade Issues
23© 2008 NetApp. All rights reserved. 23Limited Distribution
© 2008 NetApp. All rights reserved. 24
Upgrade Issues
New console messages to become familiar with
SnapLock remains unsupported until Data ONTAP 8.1
32-bit to 64-bit aggregate conversion still requires data
migration
- root volume can now be moved to 64-bit aggregate
SnapMirror/SnapVault restart checkpoints deleted during
upgrade
- The replication sessions will restart at the beginning
24Limited Distribution
© 2008 NetApp. All rights reserved. 25
Upgrade Issues
NTP only supported time protocol
- rtc and rdate no longer supported
Dedupe volume limitations
- 100 or fewer dedupe volumes for NDU
(you must „rehydrate‟ excess volumes)
- DOT 8.0.1 will support 300 volumes for future NDUs
Manual editing of /etc/rc required
- process does not change „vif‟ to „ifgrp‟
25Limited Distribution
© 2008 NetApp. All rights reserved. 26
Upgrade Issues
System firmware updates will add 5 – 10 minutes and
trigger a reboot
NVRAM firmware updates add 10 minutes to process
Flash Cache (PAM II) firmware upgrades
- During NDU, a node may reboot several times as the
firmware is updated prior to booting ONTAP
FAS/V3200 series may start flashing Fault LEDs
- see TSB 1101-02: Fault LED Flashing on FAS/V3200
for remediation process
26Limited Distribution
© 2008 NetApp. All rights reserved. 27
Reversion Process
27© 2008 NetApp. All rights reserved. 27Limited Distribution
© 2008 NetApp. All rights reserved. 28
The Reversion Rules
Contact NetApp Technical Support first
- reversions have unique requirements
- the process is purposely not well-documented for yours
and the customer‟s protection
- newly installed systems without data and test systems are
only exceptions
Scenarios requiring NGS assistance:
- ONTAP upgrade process failed and did not finish
- ONTAP upgrade finished, but system is unusable
- System performance or behavior is noticeably worse
28Limited Distribution
© 2008 NetApp. All rights reserved. 29
Reversion Concerns
Inode-to-Path (I2P) must complete before revertingfas> priv set advanced
fas> wafl scan status
Cannot revert with 64-bit aggregates
- must migrate data to 32-bit aggregates
Cannot revert to release prior to DOT 7.3
Delete all 8.x snapshots to revert to 7.3 or earlier
- this is why you took Snapshots of root vol and
SnapMirror/SnapVault volumes prior to the upgrade
29Limited Distribution
© 2008 NetApp. All rights reserved. 30
Reversion Concerns
NFS volumes may need to be remounted
- File System Identifiers (FSIDs) are rewritten during the
reversion
Disable quotas or allow the quota upgrade process to
complete
- use quota status command to check
Edit /etc/rc to change ifgrp back to vif
Solid State Disk shelves must be removed
- only supported in DOT 8.0.1
- must migrate data, destroy aggregates, and remove shelf
30Limited Distribution
© 2008 NetApp. All rights reserved. 31
Reversion Concerns
MultiStore vfilers must be online but all services turned
off
- The vfilers also get reverted. Turning them off can corrupt
them and make them unusable.
Deduplicated volumes must first have their metafiles
reverted.
- You will be instructed on how to use the sis revert_tocommand
31Limited Distribution
© 2008 NetApp. All rights reserved. 32
Post Upgrade Steps
32© 2008 NetApp. All rights reserved. 32Limited Distribution
© 2008 NetApp. All rights reserved. 33
Post Upgrade
Test client access for every licensed protocol
– failure is often due to changes in ONTAP options
– Make the customer perform the testing
Test cluster failover functionality
- be certain you can prove failover worked when you left
If you experience something not documented then add
what you have learned to the tribal knowledge
33Limited Distribution
© 2008 NetApp. All rights reserved. 34
Additional Information
Data ONTAP 8.0.1 Upgrade Guide
NetApp University courses:
- Data ONTAP 8.0 7-Mode: New Features
- Data ONTAP 8.0 7-Mode Fundamentals
- Data ONTAP 8.0 7-Mode Administration
- Data ONTAP 8.0 7-Mode Troubleshooting: New
Features
- High Availability on Data ONTAP 8 7-Mode
- Data ONTAP 8.0.1 New Features
34Limited Distribution
© 2008 NetApp. All rights reserved. 35
As a follow up to our popular Hands-on Installation
Workshop:
Advanced Hands-On Workshop:
Data ONTAP Upgrades
Advanced Hands-On Workshop:
Storage Controller Upgrades
Contact your TPM for updates and schedules
35Limited Distribution
Coming Soon
to a city near you
© 2008 NetApp. All rights reserved.
QUESTIONS?
36Limited Distribution
Top Related