Data Domain - DD 保留鎖定和 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 設定為小於 （目前時間） + （Retention-lock min-retention-period）。
 

縮短最短保留期間，或設置 Commvault 將 atime 設置為晚於當前值設置的某個值。
 

“>

”>

保留鎖定， 法規遵循鎖定， 軟體 WORM， WORM 複製→ 所有這些都是指相同的 CommVault 軟體層級 WORM 保護。它可以防止使用者刪除工作、用戶端、備份集、子用戶端...等等，當數據承載實體具有有效作業時，它也會阻止減少保留。
在 11.30 →之前，您可以使用 Java 主控台，透過選取 WORM 複製選項，在儲存原則複製層級啟用此功能，或使用啟用保留鎖定工作流程，在所選儲存集區的所有複本上啟用 WORM 複製選項。
11.30 起→，我們將此選項重新命名為「法規遵循鎖定」，以避免與「WORM 儲存裝置」混淆，並在 command Center 和 Java 主控台的儲存集區屬性下公開此選項。只要選取儲存集區上的切換「Compliance Lock」即可啟用
 
WORM 儲存→是指硬體層級 （儲存裝置廠商端） 的 WORM 保護。使用此選項，數據將鎖定在存儲端，以防止存儲端的任何直接刪除和/或修改。
當啟用 WORM 儲存裝置時，我們會自動啟用「法規遵循鎖定」，以防止保留變更與儲存側鎖定一致。
在 11.30 之前，→使用「啟用 WORM 儲存」工作流程來啟用此功能。
從 11：30 →我們在 Command Center 和 Java Console 的儲存集區屬性下公開此選項。只要在儲存集區上選取切換「WORM 儲存裝置」即可啟用此功能。