Which practice is recommended when upgrading ONTAP firmware on SPs and shelves?

Which practice is recommended when upgrading ONTAP firmware on SPs and shelves?

• A. Upgrade all shelves in a cluster in a single downtime window
• B. Back up current configuration before upgrading
• C. Skip verification after upgrade
• D. Do not plan for failover

Answer: (B)

Starting with a safe rollback point is essential when performing firmware upgrades on SPs and shelves. Upgrading can introduce unexpected issues or misconfigurations, and having a current configuration backup lets you quickly restore the system to its previous working state if something goes wrong. In NetApp ONTAP, the configuration defines how the cluster and hardware are set up, so safeguarding it means you can reapply settings or recover without rebuilding from scratch. This approach minimizes downtime and speeds recovery, making it the most reliable precaution among the options. While planning for failover and verifying the upgrade are important practices, they don’t provide the same immediate safety net as having a backed-up configuration. Skipping verification or attempting a large-scale upgrade in one downtime window increases risk, whereas a pre-upgrade backup directly supports a safe, resalable path if issues arise.

Starting with a safe rollback point is essential when performing firmware upgrades on SPs and shelves. Upgrading can introduce unexpected issues or misconfigurations, and having a current configuration backup lets you quickly restore the system to its previous working state if something goes wrong. In NetApp ONTAP, the configuration defines how the cluster and hardware are set up, so safeguarding it means you can reapply settings or recover without rebuilding from scratch. This approach minimizes downtime and speeds recovery, making it the most reliable precaution among the options. While planning for failover and verifying the upgrade are important practices, they don’t provide the same immediate safety net as having a backed-up configuration. Skipping verification or attempting a large-scale upgrade in one downtime window increases risk, whereas a pre-upgrade backup directly supports a safe, resalable path if issues arise.