NetApp
ONTAP Storage Failover and Giveback Runbook
Scope
This article covers planned storage failover testing or maintenance where one node in an HA pair is taken over and later given back. NetApp documents the key commands as storage failover takeover and storage failover giveback: storage failover takeover and storage failover giveback.
Prechecks
storage failover show-giveback
event log show -severity ERROR
system health alert show
Confirm:
| Check | Requirement |
|---|---|
| SFO state | Enabled and possible |
| Partner health | Partner node healthy enough to serve storage |
| Data LIFs | Failover targets valid |
| Workloads | Owners aware of possible pause |
| SnapMirror | No critical unexpected lag or unhealthy state |
CLI Takeover Process
Use normal takeover for planned maintenance unless support directs otherwise:
storage failover show-giveback
event log show -severity ERROR
system health alert show
Monitor:
storage failover show-giveback
event log show -severity ERROR
system health alert show
Complete maintenance. Then check giveback readiness:
storage failover show-giveback
event log show -severity ERROR
system health alert show
Give back:
storage failover show-giveback
event log show -severity ERROR
system health alert show
Monitor until complete:
storage failover show-giveback
event log show -severity ERROR
system health alert show
REST API Validation Process
Use REST to collect pre and post evidence:
storage failover show-giveback
event log show -severity ERROR
system health alert show
For takeover and giveback execution, use the documented CLI or System Manager workflow unless your automation standard has validated the matching REST operations for your ONTAP release and platform.
Best Practices
- Avoid
-forceand veto overrides unless support or a documented emergency procedure requires them. - Do not start giveback until the partner is ready and EMS reasons for vetoes are understood.
- Watch client-facing protocols, not just aggregate ownership.
- Capture the exact start and end time for both takeover and giveback.
- Keep node management access available during the whole change.
Backout
If giveback fails, do not repeatedly force it. Capture:
storage failover show-giveback
event log show -severity ERROR
system health alert show
Resolve the veto or health issue, then retry giveback. Use override options only when the operational risk is understood and approved.
Comments