If disaster recovery is configured and an upgrade from NetBackup Flex Scale 2.1 to 3.0, the upgrade operation hangs

If you perform an upgrade from NetBackup Flex Scale 2.1 to 3.0 and disaster recovery is configured on the cluster, the upgrade hangs. This happens because the vxnetd start daemon hangs on the secondary cluster. (IA-39899)

Workaround:

Restart the node on which vxnetd start daemon hangs. But this will cause the upgrade to fail and rollback. Once rollback is completed successfully, you can restart the upgrade process.