Skip to main content
NetApp Knowledgebase

VSC/SMVI backup fails with "Failed to rename snapshot"

Views:
256
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

  •   Clustered Data ONTAP 8    
  •   FlexPod    
  •   SnapManager for Virtual Infrastructure 
  •   Virtual Storage Console (VSC) 4.x, 5.x, 6.x.

Issue

When running Virtual Storage Console Backup and Recovery, the job will fail when attempting to rename an existing VSC snapshot. The backup will not complete. Typically, this will occur when you have one or more backup jobs, which are set to retain only an 'X' number of snapshots before a delete or rename.

The following output is reported in the SMVI logs located in /smvi/server/log/server.log
2010-01-06 15:20:52,344 [backup:fd3853c6dfe6cab18b0f69ecc1d4aa70:] DEBUG - ZEPHYR-10003: ZAPI call "snapshot-rename" to "192.168.0.1" returned error: The new snapshot already exists (13020)
2010-01-06 15:20:52,344 [backup:fd3853c6dfe6cab18b0f69ecc1d4aa70:] ERROR - Failed to rename snapshot smvi__vmname_20100106152002 to smvi__vmname_recent on volume 192.168.0.1:/vol/vmware

2010-01-06 15:20:52,359 [backup:fd3853c6dfe6cab18b0f69ecc1d4aa70:] ERROR - FLOW-11019: Failure in NaSnapshotCreateActionWrapper: Failed to rename snapshot smvi__vmname_20100106152002 to smvi__vmname_recent on volume 192.168.0.1:/vol/vmware

 

CUSTOMER EXCLUSIVE CONTENT

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