Skip to main content
NetApp Knowledgebase

SCV 4.3/NDB: Unable to find snapshot for SnapVault or SnapMirror update

Last Updated:

Applies to

  • SnapCenter Plug-in for VMware (SCV) 4.3 and later
  • NetApp Data Broker (NDB) 1.0.1


  • SnapMirror or SnapVault operations fails with one the following messages:

The error on source side:
Unable to find Snapshot (RG|Policy_YYYY-MM-dd_HH:mm:ss.0ms) on volume (primary-volume) from storage (primary-SVM-fqdn).
Failed to attach the label to the specified Snapshot copy.(RG|Policy_YYYY-MM-dd_HH:mm:ss.0ms). Invalid response returned by Set-NcSnapshot: 0

The error on destination side:
Error: SnapVault update failed for the relationship [ source-SVM : source-volume ==> destination-SVM : destination-volume]
with error: Snapshot copy 'RG|Policy_YYYY-MM-dd_HH:mm:ss.0ms' not found on the SnapVault destination destination-SVM : destination-volume

  • SCV (and NDB) are unable to complete SnapMirror or SnapVault operations successfully and will not show as having secondary backups for these failures.


  • Snapshot cannot be found on source side if:
    • Snapshot is deleted by ONTAP autodelete on the volume, in which case, the solution below will not help (adjust Volume settings instead).
    • Storage system's volume database is not updated fast enough after taking the snapshot, seen often in MCC environment or with LS Mirror on SVM root.
  • Snapshot cannot be found on destination side if:
    • SnapVault or SnapMirror update transfer failed, in which case, the solution below will not help (check ONTAP's SnapMirror logs on the destination)
    • SnapVault or SnapMirror update takes longer than (by default) two hours to complete, and the snapshot will appear later:
      After triggering the SnapVault or SnapMirror update, the plugin will check and wait repeatedly for the transfer to end and the snapshot to appear on the destination. The check is attempted 120 times with pauses of 1 minute before giving up and displaying the error message.


  1. From vSphere Web Interface, open the Console
  2. Login with maint user
  3. From Main Menu, press  4
  4. From Support and Diagnostic Menu, press 2
  5. Press 'y'  to enter diagnostic shell
  6. Type 'sudo su'
  7. Edit the appsettings-storage.json file by typing  vi /opt/netapp/protectionservice/publish/storage/appsettings-storage.json
  8. Add following keys inside the AppSettings section (timeouts are in milliseconds)

"SnapshotDiscoverRetryIntervalSecond": "10000",
"SnapshotDiscoverMaxRetryExist": "9",

"SnapmirrorRetry": "360",
"SnapmirrorTimeout": "300000"
"MaxRetrySnapmirrorHistory": "300",
"RetryIntervalSecondSnapmirrorHistory": "4",

  1. Shown here are the defaults that are not normally visible. Adjust the values from the shown defaults to match the duration of longest normal SnapVault or SnapMirror transfer. Instead of increasing just the retries, change the timeout to 10 or 15 minutes (600000, 900000 resp.) and adjust the retries accordingly., which saves on the number of checks and logging.
  2. Save the changes and exit the vi editor
  3. Exit the diagnostic shell by typing 'Exit' at the command prompt
  4. Type 'b' to go back to the Main Menu
  5. From Main Menu, press 1
  6. From the Application Configuration Menu, press 3 to stop the Services
  7. From the Application Configuration Menu, press 2 to start the Services

Additional Information

Note: The SNAPSHOT_CHECK_* variables are meant for the destination Snapshot appearance and the SnapshotDiscovery* for primary Snapshots.

When working with NDB 1.0.1(D1), the capitalized SNAPSHOT_CHECK_* variable need to be outside the AppSettings section !



Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support