PowerProtect Data Manager: Backup con modalità Retention Lock abilitata non riuscito a causa di una differenza di orario tra Data Domain e PPDM

Il backup PPDM con Retention Lock Mode abilitata non è riuscito con l'avviso riportato di seguito in vmdm.log. "Errore durante il tentativo di applicare il blocco di retention alla copia rilevata con ID: 2bc30abb-ae95-578d-a63a-1c053970f13e, dettaglio: Il blocco di retention del nome dell'unità di storage: ppdm-stu, Id: 14A3A424-F3DA-4CC6-A592-DA84524B16A1 non è abilitato. Impossibile impostare il retention lock sull'ID copia: 2b5e8f10-7e72-5097-86b3-dce5b8bb66c3., Rimedio: esaminare la connessione di storage o la configurazione dell'unità di storage.

vmdm.log: 2024-12-09T02:22:52.870Z INFO [] [vpe-completion-3] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bf0cde6dc47dc8e0;JOB_ID:851517b98b0b69a4][] [c.e.b.d.d.DDBoostAdapter.connect(386)] -  Connected to PowerProtect DD System, hostname: 10.0.0.1, connDesc: -1383149567, instanceDesc: 816500736 ddosVersion: Data Domain OS 7.10.1.20-1090468  ddsModel: DD6400-MC
vmdm.log: 2024-12-09T02:22:52.874Z INFO [] [vpe-completion-3] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bf0cde6dc47dc8e0;JOB_ID:851517b98b0b69a4][] [c.e.b.d.s.r.DataDomainRetentionLockServiceImpl.setRetentionTime(120)] -  Successfully connecting to PowerProtect DD System with connectionDescription: -1383149567
vmdm.log: 2024-12-09T02:22:52.874Z INFO [] [vpe-completion-3] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bf0cde6dc47dc8e0;JOB_ID:851517b98b0b69a4][] [c.e.b.d.s.r.DataDomainRetentionLockServiceImpl.retentionLockAllFilesInCopiesOnDataDomain(171)] -  Starting to set retention lock copies for copy set on PowerProtect DD System: copySetId 2bc30abb-ae95-578d-a63a-1c053970f13e, retention time 2024-12-12T00:00:00Z
vmdm.log: 2024-12-09T02:22:52.878Z INFO [] [vpe-completion-3] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bf0cde6dc47dc8e0;JOB_ID:851517b98b0b69a4][] [ddboost.log(41)] -  severity:3 msg:[13563] [140001547364096] ddp_disconnect: Attempting to disconnect for connection descriptor:  connd[-1383149567]
......
vmdm.log: 2024-12-09T02:22:52.878Z INFO [] [vpe-completion-3] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bf0cde6dc47dc8e0;JOB_ID:851517b98b0b69a4][] [ddboost.log(41)] -  severity:3 msg:[13563] [140001547364096] clnt_async_destroy: Source IP:port(10.0.0.2:34224)
vmdm.log: 2024-12-09T02:22:52.878Z INFO [] [vpe-completion-3] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bf0cde6dc47dc8e0;JOB_ID:851517b98b0b69a4][] [ddboost.log(41)] -  severity:3 msg:[13563] [140001547364096] clnt_async_destroy: RPC_CANTRECV will fail all the pending jobs and close socket
vmdm.log: 2024-12-09T02:22:52.878Z INFO [] [vpe-completion-3] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bf0cde6dc47dc8e0;JOB_ID:851517b98b0b69a4][] [ddboost.log(41)] -  severity:3 msg:[13563] [140001547364096] ddp_disconnect: ddcl_disconnect succeeded for all physical connections
vmdm.log: 2024-12-09T02:22:52.879Z WARN [] [vpe-completion-3] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bf0cde6dc47dc8e0;JOB_ID:851517b98b0b69a4][] [c.e.b.v.v.a.VPEProtectOp.completeSessionSuccess(858)] -  Failure while trying to apply retention lock to discovered copy with ID: 2bc30abb-ae95-578d-a63a-1c053970f13e, Detail: The retention lock of Storage Unit name: ppdm-stu, Id: 14a3a424-f3da-4cc6-a592-da84524b16a1 is not enabled. Cannot set retention lock on copy Id: 2b5e8f10-7e72-5097-86b3-dce5b8bb66c3., Remedy :Review the storage connection or storage unit configuration.
com.emc.brs.vmdm.error.RetentionLockException: Unable to apply Retention Lock to copy 'PCS-a232105f-9b71-46ac-a4a6-1caf3ce14f19-50246572-b7f4-cc2b-b986-e3234dc5bbc7', because of invalid target source 'ppdm-stu'.

Eseguire 'mtree list' su Data Domain, l'mtree ha infatti Retention-Lock Governance Enabled.

sysadmin@ddxxxx# mtree list
Name                                Pre-Comp (GiB)   Status    Tenant-Unit
---------------------------------   --------------   -------   -----------
...
/data/col1/ppdm-stu                 0.0		     RW/RLGE   -
...
---------------------------------   --------------   -------   -----------
...
 RLGE : Retention-Lock Governance Enabled
 RLGD : Retention-Lock Governance Disabled
 RLCE : Retention-Lock Compliance Enabled

La root cause del problema è che la differenza di orario tra Data Domain e PPDM è troppo grande. In questo caso, l'ora su Data Domain è 15 minuti avanti rispetto all'ora su PPDM.

connectionDescription è impostato su un valore negativo "-1383149567" a causa di questa differenza di orario, causando l'ddp_disconnect.

Configurare NTP su entrambi i server Data Domain e PPDM per sincronizzare l'ora.

Eseguire nuovamente il backup con la modalità Retention Lock abilitata.