What is aggregate relocation (ARL)? Choose all that apply.
A.
Provides zero copy, non-disruptive relocation of (non-root) online SFO aggregates to a
partner node
B.
Provides zero copy, non-disruptive relocation of (root) online CFO aggregates to a partner
node
C.
Is utilized during planned events such as fast negotiated takeovers, controller hardware
upgrades, and other maintenance operations
D.
Is utilized during unplanned events such as controller failure
A, C
0
0
A C
Aggregate relocation operations take advantage of the HA configuration to move the ownership of storage aggregates within the HA pair. Aggregate relocation occurs automatically during manually initiated takeover to reduce downtime during planned failover events such as nondisruptive software upgrade, and can be initiated manually for load balancing, maintenance, and nondisruptive controller upgrade. Aggregate relocation cannot move ownership of the root aggregate.
The aggregate relocation operation can relocate the ownership of one or more SFO aggregates if the destination node can support the number of volumes in the aggregates. There is only a short interruption of access to each aggregate. Ownership information is changed one by one for the aggregates.
During takeover, aggregate relocation happens automatically when the takeover is initiated manually. Before the target controller is taken over, ownership of the aggregates belonging to that controller are moved one at a time to the partner controller. When giveback is initiated, the ownership is automatically moved back to the original node. The ‑bypass‑optimization parameter can be used with the storage failover takeover command to suppress aggregate relocation during the takeover.
The aggregate relocation requires additional steps if the aggregate is currently used by an Infinite Volume with SnapDiff enabled.
0
0