Skip to main content
NetApp Knowledge Base

Application consistent backups with SMHV fail to rename snapshot

  1. Last updated
    Jan 12, 2022
  2. Save as PDF
Views:
439
Visibility:
Public
Votes:
4
Category:
snapmanager-for-hyper-v
Specialty:
legacy
Last Updated:
1/12/2022, 7:25:50 AM

Applies to

  • SnapManager for Hyper-V (SMHV)
  • Windows Server 2016
  • Windows Server 2019

Issue

When running an application consistent backup with SnapManager for Hyper-V the below errors may be generated

SnapDrive debug log

01/02-00:00:00.000    PID:9560    TID:7964    filer.cpp@479        An attempt to rename Snapshot copy from '{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}_backup' to '<snapshot name_backup' on volume '<volume>' failed on the storage system '<storage system name>'. Error code: 15661. Error description: entry doesn't exist.
 HRESULT 0xc004032d.

SnapManager for Hyper-V Backup Report

[1/2/2020 00:00:00 PM, (55)] Renaming snapshot {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}_backup to 
<snapshot name>_backup  for volume C:\ClusterStorage\CSV#\
[1/2/2020 00:00:00 PM, (55)] An error occured while renaming snapshots after backup operation.

 

 

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.