Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

AUTO-ARCHIVED: CommVault Simpana or SnapProtect pruning issues with snapshots vaulted to desination volumes with storage efficiency enabled

Views:
537
Visibility:
Internal
Votes:
1
Category:
snapprotect
Specialty:
legacy
Last Updated:

Applies to

  • SnapProtect/CommVault Simpana - All Versions up to and including Version 11 SP8
  • OnTap/Clustered Data OnTap - All Versions
  • Veeam Backups and Replication
  • Troubleshooting

Issue

The "Rotation Phase" of a SnapVault (XDP) transfer to destination where deduplication is enabled, CommVault Simpana/SnapProtect may incorrectly catalog the data with temporary "SnapMirrorSE*" names. As a resolt SImpana/SnapProtect is unable to locate these snapshots to perform operations including tape backups, restores, cascaded replication, scheduled indexing, and pruning.

SnapProtect/Simpana fails to prune, backup to tape, further replicate (cascade) snapshots on Vault (XDP) destinations where deduplication is enabled.
CommVault Media Agent Logs (CVMA.*) reveal an attempt to delete snapshot  with long names beginning with the string "snapmirrorSE":

17160 380c  10/18 12:02:20 ------ GetDFMInfoFromSnap_II SM_MDT_COPY_UUID : [myvserver|CC_myserver_SP_6_Copy_14_mydestination|snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_1474136996|/myvserver/CC_myserver_SP_6_Copy_14_mydestination/myvolume/myvolume.lun]
17160 380c  10/18 12:02:20 ------ Snapshot UniqueID is
[myvserver.demhm.corpintra.net|CC_myserver_SP_6_Copy_14_mydestination|snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_1474136996|/myvserver/CC_myserver_SP_6_Copy_14_mydestination/myvolume/myvolume.lun]
17160 380c  10/18 12:02:20 ------ CVSnapEngineNetApp::cvso_deleteSnaps DFM SnapShot on secondary copy. Secondary volume name [CC_myserver_SP_6_Copy_14_mydestination] Secondary snap name [snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_1474136996] Secondary filer name [mydestination]
17160 380c  10/18 12:02:44 ###### ManageONTAPDFMCMode::DFMGetResourceKeyForObject() - Failed to get resource key for object:[myvserver:/CC_myserver_SP_6_Copy_14_mydestination:snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_1474136996]. OnCommand Server:[myocumserver]. Error returned:[22255][No resource 'snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_1474136996' of type 'snapshot' was found in volume 'myvserver:/CC_myserver_SP_6_Copy_14_mydestination'.]
17160 380c  10/18 12:02:44 ###### ManageONTAPDFMCMode::DFMGetResourceKeyForObject() - Failed to get resource key for object:[myvserver:/CC_myserver_SP_6_Copy_14_mydestination:snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_1474136996]. OnCommand Server:[myocumserver]. Error returned:[22255][No resource 'snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_1474136996' of type 'snapshot' was found in volume 'myvserver:/CC_myserver_SP_6_Copy_14_mydestination'.]
17160 380c  10/18 12:02:44 ------ ManageONTAPDFMCMode::DFMDeleteSnapshot2 Snapshot[myvserver:/CC_myserver_SP_6_Copy_14_mydestination:snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_1474136996] not found by OnCommand server.
17160 380c  10/18 12:02:49 ------ DeleteDFMSnaps +++++++++ Successfully marked snap:[snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_1474136996] for deletion+++++++++​

On the Filer Side, the failed snapshot deletion attempt is observed in the MGWD logs on the Vault destination:

00000011.00167535 10d6d1d0 Tue Oct 18 2016 14:01:34 +00:00 [kern_mgwd:info:1010] 0x83294e340: 8103e9000007cf5d: ERR: tables:snapshot: dblade_get_single_snapshot:: Getting info for a snapshot "snapmirrorSE.xxxxxxxx-xx-xxxx-xxxx-xxxxxxxxxxxx.SP_2_230959_33446_14200654240174136996" failed on volume "CC_myserver_SP_6_Copy_14_mydestination" error: 13021:"The snapshot name does not exist"

Same issue can be found with Veeam backup:

Wed Jul 24 2019 14:21:14 +02:00 [kern_audit:info:1944] 8503e80000f648e6 :: D2-S-CSTOR1:ontapi :: 10.10.10.10:56943 :: D2-DR-NFS:d2-veeam :: snapmirrorPreSE.VeeamSourceSnapshot_D1_NFS_PA01.2019-07-24_1420VeeamSnapVault_D1_NFS_PA01.2019-07-24_1420D1_SVM_NFS_D1_NFS_PA01_mirror_vault^M :: Pending

Wed Jul 24 2019 14:21:14 +02:00 [kern_audit:info:1944] 8503e80000f648e6 :: D2-S-CSTOR1:ontapi :: 10.10.10.10:56943 :: D2-DR-NFS:d2-veeam :: entry doesn't exist :: ONTAPI :: Error

 

Scan to view the article on your device
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