Skip to main content
NetApp Knowledge Base

What are ONTAP giveback vetos

  1. Last updated
  2. Save as PDF
Views:
2,680
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9

Answer

  • If giveback 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 failover show-giveback command displays the giveback progress and shows which subsystem vetoed the giveback, if any.
    • Soft vetoes can be overridden, while 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*
  • The following is a list of some common vetos reported by ONTAP:

Veto Name

Description

Autosupport (autosupport)

(Root Aggregate only)

This veto protects the AutoSupport collection performed by the surviving node on behalf of the downed node. 

 

Core Dump (coredump)

(Root Aggregate only)
  • When a hardware or software failure casues an ONTAP panic event, a core dump is stored in predetermined locations on disk.
    • The core dump file contains the contents of memory and NVRAM.
    • The Core Dump process saves the data into a single file which can be uploaded for analysis. 
  • This veto means the takeover host is saving a core dump to a file.

Disk Inventory (disk_inventory)

 
  • This veto occurs when one of the nodes in a high-availability (HA) pair reports that multiple disks in the disk inventory do not match what the partner node reported.
    • This only occurs when sufficient mismatches have occurred to throttle the specific disk inventory mismatch message.
  • The veto might be due to one of following reasons:

  1. One node can see disks that the other node cannot.

  2. Ownership of multiple disks has changed.

  3. Multiple disks have been failed or unfailed.

  4. Multiple disks have been inserted or removed.

Dump / Restore (dump)

 
  • This veto occurs if an NDMP backup or restore is in progress on the volume belonging to the aggregate being relocated or sent home.  
  • A third party backup application would initiate backup/restore using NDMP protocol.
    • The backup/restore are NOT checkpoint-restartable - they will neither be restarted automatically nor can they be restarted using any ONTAP commands.
    • The operations will have to be restarted afresh using third party backup applications that initially triggered the operation.

Key Manager (keymanager)

 

This veto occurs because of unavailability of volume encryption keys for the encrypted volumes of the aggregate on the partner node.

 

Lock Manager (lock_manager)

During a giveback, ONTAP will revoke CIFS oplocks, NFSv4 delegations and Flexcache read-only delegations.  this veto indicates the process is ongoing.

 

RAID (raid)

 

This veto indicates there is a RAID operation still in progress such as:

  1. Disk ownership reassign

  2. Disk add operation

  3. Mirror verify

  4. Mirror resync

  5. Pending NVFile

Lock Manager NDO

(SFO)
  • This veto function checks if NDOLITE is performing lock reconstruction or lock sync to the partner node that just came up.
  • The lock-sync process will veto only if the aggregate being givenback has locks that qualify for NDOLITE mirroring.
  • Reconstruction in progress will veto any aggregate giveback, since it will be unknown whether the aggregate has locks that qualify for mirroring until reconstruction completes - in case of ARL, this will be a hard veto - this is just to keep the design simple.
  • Both reconstruction and lock-sync to the partner are supposed to complete quickly (in the order of a few minutes) unless the node is heavily loaded.
  • It is therefore recommended to not override these vetoes since the main use case for persistent SMB3 opens in SN is to keep Microsoft HyperV applicable non-disruptive.

Volume Move
  • The move code will check to see if there are any volumes participating in a volume move that has entered the cutover state.
  • If there are any volume moves in the cutover phase, the move code will veto the giveback.
    • If the veto is overridden, the cutover will be automatically resumed once the Giveback/ARL has completed.

Backup
  • If dump/restore is in progress on the volume belonging to the aggregate being sent home, then the sendhome will be vetoed.
  • If the veto is overridden, the backup/restore operations will be aborted. In C-mode, dump/restore can be invoked only through NDMP protocol.
    • A third party backup application like Symantec NBU or Dell NetVault would initiate backup/restore using NDMP protocol.
    • The backup/restore are NOT checkpoint-restartable - they will neither be restarted automatically nor can they be restarted using any ONTAP commands.
    • The operations will have to be restarted afresh using third party backup applications that initially triggered the operation.

Replication Engine
  • If there are any ongoing transfers that are not interruptible by aggregate migration (for example, volume move transfers in the cutover phase) then the sendhome will be vetoed.
    • If the veto is overridden, all transfers relating to that aggregate will be asynchronously aborted.
    • The interrupted transfers will have to be resumed from a previous checkpoint.
    • Depending on the consumer of the Replication Engine, the resuming of transfers may have to be done manually.

WAFL
  • If there are pending NVSAVE files that need to be replayed before sendhome or WAFLIRON is running.
  • WAFL saves nvlog records to files when the volume is not available at the time of replay on takeover or reboot.
  • Before sendhome, these files needs to be replayed by online'ing the volume.

Additional Information

additionalInformation_text

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.