跳转到主内容

VSS 备份失败,并显示 " 缓存最大卷影数 " 每个 SVM 的复制操作数

Views:
3
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

适用场景

  • SnapManager for Hyper-V (SMHV) 2.1.4
  • ONTAP 9
  • 卷影复制服务( VSS )
  • CIFS 副本( SMB3 )
  • Microsoft Hyper-V
  • EMC 网络员工

问题描述

  1. 驻留在特定 SVM 的任何 SMB3 共享上的任何 VM 的 SMHV 备份失败。
  • 将 VM 移动到同一 SVM 上的其他共享时出现相同错误。
  • SnapMgrServiceHostDbg.log 显示以下错误:
03/25 14:28:05.133: ProcessID= 2680 ThreadID= 24 AddToSnapshotSet failed. Error 0x8004230f
03/25 14:28:05.165: ProcessID= 2680 ThreadID= 24 Aborted backup.
03/25 14:28:05.170: ProcessID= 2680 ThreadID= 24 FormatMessage failed for code 0x8004230f with error 15100.
 
  • SnapDriveDebug.log 显示:
Backup of the Dataset Name: test
Backup id: f26d8349-53c5-4578-ba6d-c000000a00a1 failed to execute
Error :Error: Vss Requestor - Backup Components failed.Failed to add volume \\SVM1\SHARE1\ to snapshot set. The shadow copy provider had an unexpected error while trying to process the specified operation.
 
  1. 第三方备份软件请求的 VSS 备份 在 SMB3 CIFS 共享上托管的 Hyper-V VM 失败

在客户端软件日志中:CVssSnapshotSetObject::AddToSnapshotSet() Unexpected error calling a provider routine: BeginPrepareSnapshot({12345678-1234-1234-1234-1234567890ab},{123456789-1234-1234-1234-1234567890ab},\\Server1\Share1\) [hr = 0x800106be] Provider ID = {12345678-1234-1234-1234-1234567890ab}.

在 ONTAP MGWD 日志中:00000018.0041f6b7 071ebc54 Thu Mar 25 2021 14:28:47 +00:00 [kern_mgwd:info:2177] 0x83d4ddb00: 0: ERR: tables::cifs_shadowcopy: sc_startSCS:src/tables/cifs/cifs_shadowcopy.cc:1853 sc_startSCS(vserverId=6, autorecover=false, clientScsetId=7af6ffa5-a735-48ae-87da-41f0ac6fa90d) failed: StartShadowCopySet: reached the maximum number of shadow copy operations per vserver
00000018.0041f6b8 071ebc54 Thu Mar 25 2021 14:28:47 +00:00 [user_mgwd:error] processOp:src/mgmtgwd/vss_handler.cc:299 Error 7702
00000018.0041f6b9 071ebc54 Thu Mar 25 2021 14:28:47 +00:00 [kern_mgwd:info:2177] 0x83d4ddb00: 0: ERR: tables::cifs_shadowcopy: sc_startSCS:src/tables/cifs/cifs_shadowcopy.cc:1879 sc_startSCS() failed

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device