自动归档：Commvault Simpana或SnapProtect 在启用存储效率的情况下将快照存储到目标卷时发生的修剪问题

适用场景

• SnapProtect/Commvault Simpana—11 SP8及之前的所有版本
• ontap/Clustered Data ONTAP —所有版本
• Veeam备份和复制
• 故障排除

问题描述

在将SnapVault (XDP)传输到启用了重复数据删除的目标的"轮换阶段"中、Commvault Simpana/SnapProtect可能会错误地使用临时的"SnapMirrorSE*"名称对数据进行目录编制。由于resolvt Simpana/SnapProtect无法找到这些快照来执行磁带备份、还原、级联复制、计划索引编制和修剪等操作。

SnapProtect/Simpana无法在启用了重复数据删除的存储(XDP)目标上对快照进行修剪、备份到磁带、进一步复制(级联)。
Commvault Media Agent Logs (CVMA.*)显示尝试删除名称较长且以字符串 "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+++++++++​

在存储器端、在存储目标上的MGWD日志中观察到Snapshot删除尝试失败：

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"

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