NetWorker:在启用 DD Retention Lock 时,nsrclone 无法克隆以前无法通过脚本自动克隆的存储集
Summary: 在启用 DD Retention Lock 时,nsrclone 无法克隆以前无法使用脚本自动克隆的存储集。
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
- 一些以前无法使用脚本或自动克隆的存储集。
- 如果没有包含 mminfo 的卷名称,则可能会显示“ghost”存储集(请参见下文)。
- 检查目标文件系统是否显示存储集文件,但不显示“备注”文件。
- saveset 的 scanner 命令失败(请参见下文)。
- 克隆存储集的进一步尝试失败,并显示错误:Err: 5004-nfs lookup failed (nfs: 无此类文件或目录)
# mminfo -q ssid=928093938 -r ssid,cloneid,ssretent,clretent,ssflags,clflags,copies
ssid clone id retent clretent ssflags clflg copies
928093938 1532073714 08/24/2018 08/20/2018 vrF 2
928093938 1532252170 08/24/2018 08/24/2018 vrF E <--- This is the incomplete clone.
但是,添加“volume”交换机后,仅报告 1 行:
# mminfo -q ssid=928093938 -r ssid,cloneid,ssretent,clretent,ssflags,clflags,copies,volume
ssid clone id retent clretent ssflags clflg copies volume
928093938 1532073714 08/24/2018 08/20/2018 vrF 2 source-volume-name
^ ---2 copies yet only 1 shows in the output.
扫描仪 CLI 输出:
8909:scanner: using 'DD-name_destination-device-path' as the device name
8936:scanner: scanning Data Domain disk destination-volume-name on DD-name_destination-device-path
8939:scanner: Data Domain disk destination-volume-name already exists in the media index
107505:scanner: Opening the file '/nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd' failed [5004] ([57525] [140043448723232] Wed Aug 1 13:18:50 2018
ddp_open_file() failed for File: //nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd, Err: 5004-nfs lookup failed (nfs: No such file or directory)
).
107505:scanner: Opening the file '/nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd' failed [5004] ([57525] [140043448723232] Wed Aug 1 13:18:50 2018
ddp_open_file() failed for File: //nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd, Err: 5004-nfs lookup failed (nfs: No such file or directory)
).
8761:scanner: done with Data Domain disk destination-volume-name
80470:nsrclone: Following volumes are needed for cloning
80471:nsrclone: source-volume-name (DD)
100303:nsrclone: Cloning savesets from storage node 'nw-server-name'
142165:nsrclone: Number of clone threads per client is set to 256. Max number of savesets per thread is set to 0. Max client threads is set to 0.
104860:nsrclone: Concurrent proxy clone started for service type DD.
Cloning save sets from the volume source-volume-name
Total client count in a volume source-volume-name is 1
77426:nsrclone: Cloning save sets from the volume source-volume-name
104861:nsrclone: Total client count in a volume source-volume-name is 1
104864:nsrclone: Number of clone threads per client set to 1. Max number of savesets per thread is set to 0. Max client threads is set to 30 for volume source-volume-name
174908:nsrclone: Saving the backup data in the pool 'destination-pool'.
175019:nsrclone: Received the media management binding information on the host 'nw-server-name'.
174910:nsrclone: Connected to the nsrmmd process on the host 'nw-server-name'.
32379:nsrclone: Cloning save set index:705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd (ssid/cloneid 928093938/1532073714)
75360:nsrclone: Cloning of size 1 KB is in progress...
72985:nsrclone: Source volume 'source-volume-name' ready for cloning
75675:nsrclone: Failed to initiate the save nsrmmd to create a clone instance.
Direct File Save failed for /nw-server-name/destination-device-path/active/df304e8e-00000006-375196f2-5b5196f2-23ce16ac-34ae8c2d on volume destination-volume-name
75267:nsrclone: Failed to initiate mmd session for ssid 928093938.
75712:nsrclone: Cloning failed for save set : index:705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd (ssid 928093938)
77276:nsrclone: Total size cloned so far: 0 KB.
141764:nsrclone: Unable to perform clone of client saveset. Error: proxy_clone_rs failed.
104863:nsrclone: Concurrent proxy clone completed for sevice type DD.
67790:nsrclone: Total size cloned: 0 KB.
77275:nsrclone: DD cloning failed
Proxy clone failed to clone all or few savesetsSome of the clones failed
Some of the clones failed
Cause
DD 已启用 Retention Lock。这可防止删除不完整的原始存储集,并防止下一次克隆尝试在目标路径中过度写入数据。
Resolution
解决办法:
从上面的扫描仪尝试中,查找目标上存储集的路径://nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd
我们需要存储集本身的路径,该路径将高于“注释”的一个级别,例如:
//nw-server-name/destination-device-path/08/04/
然后添加始终启动 /data/col1/mtree-name 的 DD mtree 路径。DD CLI 上的“mtree list”显示已配置的 Mtree。通常,Mtree 名称与主机 NetWorker 服务器名称匹配。然后将长存储集名称添加到末尾。
在此示例中,完整路径变为:
/data/col1/nw-server-name/destination-device-path/08/04//705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd
我们必须使用此路径在目标 Data Domain 系统上禁用保留锁定:
- 在目标 DD CLI 上,运行: mtree retention-lock revert [path] (从上面的路径)这 要求 sysadmin 密码。
- 再次克隆存储集 — 这现在应该可以正常工作,而不会出错,因为它现在可以写入目标路径。
- 克隆的存储集的 mminfo 查询现在应正常工作。
- 对任何其他受影响的存储集重复此操作。
Affected Products
NetWorkerProducts
NetWorkerArticle Properties
Article Number: 000052916
Article Type: Solution
Last Modified: 27 Sep 2023
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.