Table of ContentsView in Frames

Veto and destination checks during aggregate relocation

In aggregate relocation operations, Data ONTAP determines whether aggregate relocation can be completed safely. If aggregate relocation is vetoed, you must check the EMS messages to determine the cause. Depending on the reason or reasons, you can decide whether you can safely override the vetoes.

The storage aggregate relocation show command displays the aggregate relocation progress and shows which subsystem, if any, vetoed the relocation. Soft vetoes can be overridden, but hard vetoes cannot be, even if forced.

You can review the EMS details for any giveback vetoes by using the following command:event log show -node * -event gb*

You can review the EMS details for aggregate relocation by using the following command:event log show -node * -event arl*

The following tables summarize the soft and hard vetoes, along with recommended workarounds:

Veto checks during aggregate relocation

Vetoing subsystem module Workaround
Vol Move

Relocation of an aggregate is vetoed if any volumes hosted by the aggregate are participating in a volume move that has entered the cutover state.

Wait for the volume move to complete.

If this veto is overridden, cutover resumes automatically once the aggregate relocation completes. If aggregate relocation causes the move operation to exceed the number of retries (the default is 3), then the user needs to manually initiate cutover using the volume move trigger-cutover command.

Backup

Relocation of an aggregate is vetoed if a dump or restore job is in progress on a volume hosted by the aggregate.

Wait until the dump or restore operation in progress is complete.

If this veto is overridden, the backup or restore operation is aborted and must be restarted by the backup application.

Lock manager

To resolve the issue, gracefully shut down the CIFS applications that have open files, or move those volumes to a different aggregate.

Overriding this veto results in loss of CIFS lock state, causing disruption and data loss.

Lock Manager NDO

Wait until the locks are mirrored.

This veto cannot be overridden; doing so disrupts Microsoft Hyper-V virtual machines.

RAID Check the EMS messages to determine the cause of the veto:

If disk add or disk ownership reassignment operations are in progress, wait until they complete.

If the veto is due to a mirror resync, a mirror verify, or offline disks, the veto can be overridden and the operation restarts after giveback.

Destination checks during aggregate relocation

Vetoing subsystem module Workaround
Disk Inventory

Relocation of an aggregate fails if the destination node is unable to see one or more disks belonging to the aggregate.

Check storage for loose cables and verify that the destination can access disks belonging to the aggregate being relocated.

This check cannot be overridden.

WAFL

Relocation of an aggregate fails if the relocation would cause the destination to exceed its limits for maximum volume count or maximum volume size.

This check cannot be overridden.

Lock Manager NDO

Relocation of an aggregate fails if:

  • The destination does not have sufficient lock manager resources to reconstruct locks for the relocating aggregate.
  • The destination node is reconstructing locks.

Retry aggregate relocation after a few minutes.

This check cannot be overridden.

Lock Manager

Permanent relocation of an aggregate fails if the destination does not have sufficient lock manager resources to reconstruct locks for the relocating aggregate.

Retry aggregate relocation after a few minutes.

This check cannot be overridden.

RAID

Check the EMS messages to determine the cause of the failure:

  • If the failure is due to an aggregate name or UUID conflict, troubleshoot and resolve the issue. This check cannot be overridden.

Relocating an aggregate fails if the relocation would cause the destination to exceed its limits for maximum aggregate count, system capacity, or aggregate capacity. You should avoid overriding this check.