Skip to main content
NetApp Knowledge Base

Snapvault update to Cloud Volume ONTAP failing to trigger

Last Updated:

Applies to

  • SnapCenter Server (SC) 4.3.1P2
  • Cloud Volume ONTAP (CVO)
  • Microsoft Azure


  • SC fails to trigger the SnapVault update to a CVO destination on a single node in Azure
  • SC does not show the relationship in the Job logs and no error is shown
  • PowerShell command Get-SDSnapmirror does not show the relationship
  • SVM is configured with Cluster management LIF in SC Storage Systems
  • Manual updates via ONTAP are successful


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.