Background disk firmware update and takeover, giveback, and aggregate relocation

Background disk firmware updates affect HA pair takeover, giveback, and aggregate relocation operations differently, depending on how those operations are initiated.

The following list describes how background disk firmware update affects takeover, giveback, and aggregate relocation:

If a background disk firmware update is occurring on a disk on either node, manually initiated takeover operations are delayed until the disk firmware update finishes on that disk.
If the background disk firmware update takes longer than 120 seconds, takeover operations are aborted and must be restarted manually after the disk firmware update finishes. If the takeover was initiated with the -bypass-optimization parameter of the storage failover takeover command set to true, the background disk firmware update occurring on the destination node does not affect the takeover.
If a background disk firmware update is occurring on a disk on the source (or takeover) node and the takeover was initiated manually with the -options parameter of the storage failover takeover command set to immediate, takeover operations start immediately.
If a background disk firmware update is occurring on a disk on a node and it panics, takeover of the panicked node begins immediately.
If a background disk firmware update is occurring on a disk on either node, giveback of data aggregates is delayed until the disk firmware update finishes on that disk.
If the background disk firmware update takes longer than 120 seconds, giveback operations are aborted and must be restarted manually after the disk firmware update completes.
If a background disk firmware update is occurring on a disk on either node, aggregate relocation operations are delayed until the disk firmware update finishes on that disk.
If the background disk firmware update takes longer than 120 seconds, aggregate relocation operations are aborted and must be restarted manually after the disk firmware update finishes. If aggregate relocation was initiated with the -override-destination-checks of the storage aggregate relocation command set to true, background disk firmware update occurring on the destination node does not affect aggregate relocation.