PowerProtect Data Manager: replmgr service does not start after upgrading to version 19.10

The replmgr service fails to start, and the /var/log/brs/replmgr/replmgr.out shows:

Error creating bean with name 'XXXXXXXXXXXXXXXXX': Unsatisfied dependency expressed through field 'connectionManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'YYYYYYYYYYYYYY': Invocation of init method failed; nested exception is java.lang.NullPointerException
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:161)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:545)

The Error creating bean could mention many bean names. Seeing similar errors in replmgr.out indicates of this error.

When an exclusion policy is enabled, it causes this check to return a null result because exclusion policies have no stages defined. This causes an exception and prevents the replmgr service from starting.

The issue has been resolved in the PowerProtect release 19.11.0-14. Install the latest PowerProtect Data Manager release to resolve the symptom. If required, contact Dell Support for assistance or with additional questions. The newest available releases are available on the PowerProtect Data Manager Drivers & Downloads page.

Workaround

Disable all exclusion policies to allow the replmgr service to start.

Disabling an exclusion policy does NOT have any operational impact. The assets are already assigned to the policy, which serves the purpose of excluding them from selection in other protection policies.

After the replmgr service starts, leave all exclusion policies DISABLED. If creating a new exclusion policy, immediately disable that policy.