PowerProtect Data Manager 19.16 Deployment Guide

vCenter registration and VM Direct Engine deployment fails when the PowerProtect Data Manager server is deployed to the same private network as the internal Docker network

PowerProtect Data Manager uses an internal private Docker network. If the PowerProtect Data Manager server is deployed to the same private network as the internal Docker network, or if some data sources have already been deployed to the private network, PowerProtect Data Manager fails to protect the data sources.

To resolve this issue, deploy the PowerProtect Data Manager server and other data sources in a different network. If you cannot modify the deployed network, run a script tool within PowerProtect Data Manager to switch the private Docker network to a different network.

To switch the private Docker network to a different network:

1. Connect to the PowerProtect Data Manager console and change to the root user.
2. Modify the Docker network by running the following command:

   /usr/local/brs/puppet/scripts/docker_network_switch.sh subnet gateway

   Where:

   • subnet describes the new network in the format 172.25.0.0/24
   • gateway is the gateway for the private network. For example: 172.25.0.1

     Ensure that you specify a subnet and gateway that is not in use.
       

Backups fail with an Unable to POST session error

Backups might fail with an error similar to the following in the backup log:

2021-08-08T22:28:52Z TRACE: "status": {
2021-08-08T22:28:52Z TRACE: "state": "Failure",
2021-08-08T22:28:52Z TRACE: "description": "BackupJob 'xxx-11' completed with errors.",
2021-08-08T22:28:52Z TRACE: "progress": 100,
2021-08-08T22:28:52Z TRACE: "error": "Unable to backup PersistentVolumeClaims. Unable to backup PVC 'xxx-0'. BackupPvSessions completed with errors. Unable to Post. Unable to POST session: Post \"https://IP:9090/api/v1/BackupPvSessions\": dial tcp IP:9090: connect: connection timed out (proxy: IP)".

This error indicates that a network policy is preventing PowerProtect Data Manager from connecting to pods outside of the namespace.

To resolve the issue, create a network policy to accept traffic from the PowerProtect namespace. For more information, see Configuring network policy with OpenShift SDN at the OpenShift website.