Data Domain – DD-fastholdelseslås forårsager fejl i CommVault-sikkerhedskopieringer kan ikke indstille filadgangstiden
Summary: Commvault-sikkerhedskopier går i stå med fejlene "Kan ikke indstille filadgangstid" og "Kan ikke markere fil", når låsen til opbevaring af Data Domain er aktiveret.
Symptoms
Fra Commvault-logfiler
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]
Fra DD ddfs.info logfiler
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
Cause
Commvault forsøger at indstille en tid til en værdi mindre end (Aktuelt tidspunkt) + (Retention-lock min-retention-period).
Resolution
Sænk enten min opbevaringsperiode, eller indstil Commvault til at indstille tiden til noget senere end nutidsværdisættet.
Additional Information
https://community.commvault.com/self-hosted-q-a-2/difference-between-retention-lock-enabling-worm-compliance-lock-6540 [community.commvault.com] ">
https://documentation.commvault.com/2023e/expert/configuring_worm_storage_lock_and_compliance_lock.html [documentation.commvault.com] ">
Fastholdelseslås, Overholdelseslås, Software-WORM, WORM-kopi → Alle disse refererer til samme CommVault-softwareniveau WORM-beskyttelse. Det forhindrer sletning af job, klienter, backupsæt eller underklienter med gyldige job og forhindrer også reduktion af opbevaringsperioder.
Før version 11.30 skal du bruge Java Console til at aktivere WORM på kopieringsniveauet for lagerpolitikken. Du kan også bruge arbejdsprocessen Fastholdelseslås til alle kopier i en lagerpulje.
Fra version 11.30 og fremefter blev indstillingen omdøbt til 'Compliance Lock' for at undgå forveksling med WORM-lager og er tilgængelig i Command Center og Java Console under egenskaber for lagerpulje. Vælg til/fra-knappen "Compliance Lock" på lagerpuljen for at aktivere dette.
WORM-storage→ Henviser til WORM-beskyttelse på hardwareniveau (storageleverandørsiden). Med denne indstilling låses data på storagesiden for at forhindre direkte sletninger og modifikationer fra storagesiden.
Vi aktiverer automatisk "Compliance Lock" når WORM Storage er aktiveret for at forhindre fastholdelsesændringer, så de passer med låsen på storagesiden.
Før 11.30 → brug "Enable WORM Storage" arbejdsgang for at aktivere dette.
Fra kl. 11.30 → vi eksponerede denne mulighed i både Command Center og Java Console under egenskaber for lagerpulje. Vælg at klikke på "WORM Storage" i lagerpuljen for at aktivere dette.