Data Domain — DD Retention Lock 和 Commvault 备份等待完成，并显示错误“无法设置文件的访问时间”

从 Commvault 日志 

egrep 'Cannot set the access time of the file' *

5912  16e0  03/14 13:14:28 39714925 89335656-66296274 [MEDIAFS    ] RealMagneticFS Created <\\x.x.x.x\xxxxxxxxx_cvlt_hs_win_30days_repl\xxxxxx_Folder1\CV_MAGNETIC\V_24431218\CHUNK_xxxxx7588> file
5912  16e0  03/14 13:14:28 39714925 89335656-66296274 [DSBACKUP   ] Archive File creation succeeded Type: 16 SubType: 131 Status: 0 EventErrorCode: 0
5912  16e0  03/14 13:14:28 39714925 89335656-66296274 [DSBACKUP   ] Archive File creation succeeded Has been Sent
5912  19e8  03/14 13:14:28 39714925 89335656-66296274 [DSBACKUP   ] Job Update Interval seconds   [300]S
5912  c0c   03/14 13:14:28 39714925 89335656-66296274 [MEDIAFS    ] SetFileValidData is not supported on this path. Code [87]. Current Offset [0x0000000000000000], Chunk increment size [134217728]
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DM_RECEIVER] Recieved close for ARCHIVE FILE ID = [224722928]
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DM_BASE    ] Going to close chunk for archive File [224722928] The current size of the chunk is [217752447 ]
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [MEDIAFS    ] RealMagneticFS::FinalizeChunkForBackup: Setting the end of file to offset [0x000000000D000000]
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [MEDIAFS    ] Cannot set the access time of the file [\\x.x.x.x\xxxxxxxxx_cvlt_hs_win_30days_repl\xxxxx_Folder1\CV_MAGNETIC\V_24431218\CHUNK_569777588]. Time [133555148680000000], Error [5].
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [MEDIAFS    ] Cannot mark the file [\\x.x.x.x\dc19900dd0100_cvlt_hs_win_30days_repl\xxxxxx_Folderx\CV_MAGNETIC\V_24431218\CHUNK_569777588] as read only.
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [MEDIAFS    ] CloseSpecific Failed to close the Media Handle - VolId=24431218
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DM_BASE    ] Error handler: Setting JPR for [errorType - 1] [Error-code - 996] [Error-module - 218104071] [Event-ID - 1040187703] [Handler type - 218104061]
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DM_BASE    ] setting job pending reason [job-ID - 39714925] [job type - 1] [Argument count - 3]
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DM_BASE    ] **ERROR** Failed to close the Chunk on Media. ArchiveFile=224722928 ChunkId= 569777588
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DM_RECEIVER] DataReceiver::Close: Error: DataWriter Close Failed. ArchFileId [224722928]
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DSBACKUP   ] Failed to Close Archive File
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DSBACKUP   ] ERROR! Failed to close Archive file Type: 16 SubType: 132 Status: 102 EventErrorCode: 117440531
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DSBACKUP   ] ERROR! Failed to close Archive file Has been Sent
5912  33b4  03/14 13:14:30 39714925 89335656-66296274 [DSBACKUP   ] [error] occured [handled - yes]

从 DD ddfs.info 日志 

First grep for the chunk in DDFS and then get the file handle. 
grep "CHUNK_xxxxx7588" ddfs.info.7
03/13 22:26:36.837110 [7facfe393c50] FM fm_dm1_open:3690 - Create: /data/col1/xxxxxxxx_cvlt_win_30days_repl/xxxx_Folder1/CV_MAGNETIC/V_24429117/CHUNK_xxxxx7588, FH: ---->5700bc:0:xxx:0:xxx:xxxxx:0:<--------:0:(0:99436), tag: 0, cp_uuid = c85bf3507bxxxxxx:67d1086dbxxxxx


Grep for file handle. 
grep "5700bc:xxxxxxxxxxxxxxx" ddfs.info.7
03/13 22:26:36.837110 [7facfe393c50] FM fm_dm1_open:3690 - Create: /data/col1/xxxxxxxx_cvlt_hs_win_30days_repl/xxxxxx_Folder1/CV_MAGNETIC/V_24429117/CHUNK_xxxxx7588, FH: 5700bc:0:xxxxx:0:xxxx:xxx:0:(0:99436), tag: 0, cp_uuid = c85bf3507xxxxx:67d1086dbxxxxx
03/13 22:27:52.381294 [7facfb801050] Attempt to set atime of file 5700bc:0:xx:x:xxxxx:xxxxx:0 to less than minimum retention period of mtree

Commvault 尝试将 atime 设置为小于 （Current time） + （Retention-lock min-retention-period） 的值。
 

要么缩短最短保留期，要么将 Commvault 设置为将 atime 设置为晚于设置的现值。
 

“>

”>

Retention Lock、Compliance Lock、软件 WORM、WORM 拷贝→ 所有这些都是指相同的 CommVault 软件级 WORM 保护。它可防止用户删除作业、客户端、备份集、子客户端...等等，当它们具有有效的作业时，携带数据的实体，并且它也会防止减少保留。
在 11.30 → 之前，您可以使用 Java 控制台通过选择 WORM 拷贝选项在存储策略拷贝级别启用此功能，或使用启用保留锁定工作流在所选存储池的所有拷贝上启用 WORM 拷贝选项。
从 11.30 开始→我们将此选项重命名为“Compliance Lock”，以避免与“WORM 存储”混淆，并在 Command Center 和 Java 控制台的存储池属性下公开它。只需在存储池上选择切换“Compliance Lock”即可启用此功能。
 
WORM 存储→ 指硬件级（存储供应商端）WORM 保护。使用此选项时，数据将在存储端锁定，以防止从存储端直接删除和/或修改数据。
启用 WORM 存储时，我们会自动启用“合规性锁定”，以防止更改保留以保持与存储端锁定保持一致。
在 11.30 之前，→使用“启用 WORM 存储”工作流来启用此功能。
从 11.30 → 开始，我们在 Command Center 和 Java 控制台的存储池属性下公开了此选项。只需在存储池上选择切换“WORM Storage”即可启用此功能。