Loading...
Loading...
The PowerProtect appliance is used to protect the vSphere environment with the Transparent Snapshot Data Mover (TSDM) solution. The VM backups have been intermittently performing a full level backup instead of the scheduled synthetic incremental full. The VM incremental backups take ~6 minutes to complete, while the unexpected full backup is taking ~12 hours to complete. The backup session log shows the Snapshot Data Mover (SDM) Full sync was requested for the backup session: YYYY-MM-DD HH:MM:SS INFO: [944fbb66c50e5f64;ab0948490ff0d754] SDM Data Mover: SDM Full Sync: SDM Full Sync required by client. YYYY-MM-DD HH:MM:SS TRACE: [944fbb66c50e5f64;ab0948490ff0d754] SDM Data Mover: SDM Full Sync: Created TSDM progress dir 'MY_STORAGE_UNIT/MY_PLC-17062183-88d6-434e-afd3-91e382a5c066/Stagings/86c027d3-5cfb-483b-a081-a5b664de34d7/50168553-e634-31eb-2159-82ed1327680b/progress-dir'. YYYY-MM-DD HH:MM:SS TRACE: [944fbb66c50e5f64;ab0948490ff0d754] SDM Data Mover: SDM Full Sync: Created temporary directory 'MY_STORAGE_UNIT/MY_PLC-17062183-88d6-434e-afd3-91e382a5c066/Stagings/86c027d3-5cfb-483b-a081-a5b664de34d7/50168553-e634-31eb-2159-82ed1327680b/1680134428680401976/fullSyncTmp' for SDM full sync. YYYY-MM-DD HH:MM:SS INFO: [944fbb66c50e5f64;ab0948490ff0d754] SDM Data Mover: SDM Full Sync: Performing SDM Full Sync on Hard disk 2, Hard disk 4, Hard disk 3, Hard disk 1. YYYY-MM-DD HH:MM:SS TRACE: [944fbb66c50e5f64;ab0948490ff0d754] SDM Data Mover: SDM Full Sync: vCenter SOAP call 'DpSync' was accepted The vmdm log shows that there were no copies found for the affected asset: YYYY-MM-DD HH:MM:SS INFO [https-jsse-nio-0.0.0.0-8447-exec-75] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:944fbb66c50e5f64;JOB_ID:ab0948490ff0d754][] [c.e.b.v.v.a.VPEProtectOp.getBackupCopies(1217)] - Copies size : 10 YYYY-MM-DD HH:MM:SS INFO [https-jsse-nio-0.0.0.0-8447-exec-75] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:944fbb66c50e5f64;JOB_ID:ab0948490ff0d754][] [c.e.b.v.v.a.VPEProtectOp.getBackupCopies(1244)] - No copies found for asset MY-VM-NAME on MY-VCENTER-NAME.MY-DOMAIN.COM
This is a known issue in PowerProtect 19.13 and prior versions. The backup logic checks the last 10 copies of the virtual machine. These 10 copies are sorted by creation time and the most recent dataTargetId . The dataTargetId is compared against the running Protection Policy stage dataTargetId. If the first retrieved dataTargetIds are not the same during the comparison, the copies are not considered (no copies found). In some instances, the first copy returned is a valid replication copy ( Replica dataTargetId ) which was different than the current copy target ( Target dataTargetId ).
The issue has been resolved in PowerProtect 19.14 (PPDM-231108). If required, contact Dell Technical Support for more details.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.