What is a rolling upgrade in ONTAP and why would you use it?

What is a rolling upgrade in ONTAP and why would you use it?

• A. Rolling upgrade updates all nodes simultaneously.
• B. Rolling upgrade updates nodes one at a time to maintain service availability while upgrading ONTAP software.
• C. Rolling upgrade replaces the cluster hardware automatically.
• D. Rolling upgrade is used to roll back to a previous version.

Answer: (B)

Rolling upgrade updates ONTAP software on each cluster node one at a time, so the cluster stays online and serving clients during the process. In a NetApp clustered environment, multiple controllers work together, sharing data and client connections. Upgrading nodes sequentially means you bring one node up with the new software, verify it’s healthy, then proceed to the next node, ensuring the remaining nodes handle I/O and failover in the meantime. This approach minimizes downtime and reduces risk because services aren’t interrupted across the entire cluster at once. It’s used when you want to upgrade ONTAP software without taking the whole system offline. Upgrading all nodes simultaneously would cause downtime, hardware replacement isn’t part of the software upgrade itself, and rolling back to a previous version is a separate recovery action, not the upgrade process.

Rolling upgrade updates ONTAP software on each cluster node one at a time, so the cluster stays online and serving clients during the process. In a NetApp clustered environment, multiple controllers work together, sharing data and client connections. Upgrading nodes sequentially means you bring one node up with the new software, verify it’s healthy, then proceed to the next node, ensuring the remaining nodes handle I/O and failover in the meantime. This approach minimizes downtime and reduces risk because services aren’t interrupted across the entire cluster at once. It’s used when you want to upgrade ONTAP software without taking the whole system offline. Upgrading all nodes simultaneously would cause downtime, hardware replacement isn’t part of the software upgrade itself, and rolling back to a previous version is a separate recovery action, not the upgrade process.