Loading...
Loading...
PowerMax backup 19.22.0-16 using bare mental installed proxy on Red Hat Enterprise Linux 9.6 failed with: sdmng.log: 2026-01-29T01:37:31.503Z ERROR [] [monitorActorSystem-pekko.actor.default-dispatcher-18] [00000000-0000-4000-a000-000000000000][][TASK_ID:89fcd440a98add0a][TRACE_ID:b783b132c0e68658;JOB_ID:913e9f419c176d71;EXEC_ID:9dc0a4f49b149b04][] [c.e.d.e.s.c.h.BvProxySessionResponseHandler.handleFailure(727)] - Backup operation failed for the asset: 01A00 due to the error: Unable to run BVDM container. Unable to get container host. IP address in container is not available. The proxy log /opt/emc/vmdirect/runtime/logs/proxyLogBundles/opt/emc/vproxy/runtime/logs/vbvdmd/vbvdmd-engine.log says it tried to create a Block Volume Data Manager (BVDM) container with image 'dpd/vproxy/bvdm-agent: bundled' . But the subsequent rest call returns the No such container error: 2026-01-29T01:32:00.235Z DEBUG: Update Summary: 693dfadb-978a-4aec-b671-f6fe0b62b28d:Running:0%:2:del=false:up=false:Creating BVDM container with image 'dpd/vproxy/bvdm-agent:bundled'.. ...... 2026-01-29T01:32:05.543Z ERROR: [TRACE_ID:b783b132c0e68658;JOB_ID:913e9f419c176d71;TASK_ID:89fcd440a98add0a;EXEC_ID:9dc0a4f49b149b04] 21bbb82b-ed2f-4aa4-90cb-457118dd3cef-21bbb82b-ed2f-4aa4-90cb-457118dd3cef:000420000704:60000970000420000704533031413030: Docker service responds 'message: No such container: BVDM_21bbb82b-ed2f-4aa4-90cb-457118dd3cef'. 2026-01-29T01:32:05.543Z ERROR: [TRACE_ID:b783b132c0e68658;JOB_ID:913e9f419c176d71;TASK_ID:89fcd440a98add0a;EXEC_ID:9dc0a4f49b149b04] 21bbb82b-ed2f-4aa4-90cb-457118dd3cef-21bbb82b-ed2f-4aa4-90cb-457118dd3cef:000420000704:60000970000420000704533031413030: A 'GET' method to docker service at 'http://v1.40/containers/BVDM_21bbb82b-ed2f-4aa4-90cb-457118dd3cef/json' responded with status code 404. Manually run ‘docker container run’ of dpd/vproxy/bvdm-agent: bundled . The container can be created successfully.
Docker Engine API version incompatibility The environment is running Docker 29.1.4, which enforces a minimum supported API version of 1.44. PowerProtect Data Manager relies on API version 1.40 for the rest call, resulting in the failure.
The workaround is to reinstall Docker with version 26.1.5 up to 28.x on the Block Volume Protection Engine. These versions support API 1.40 and are fully compatible with the PowerProtect Data Manager client. The PowerProtect Data Manager guide has been updated to indicate the compatibility with Docker 26.1.5 to 28.x only. The support for Docker 28.x and later versions will be in a future PowerProtect Data Manager release.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.