Summary
If the cluster ownership node changes when a DPX 4.4.1 software update occurs on a CDOT cluster where a Base backup had been done, the next Incremental backup can fail. This is because the Incremental backup and Base backup are incongruous. This change of cluster ownership node might occur, for example, if the nodes are rebooted, go down, or if a patch update is done and a failover happens.
Symptoms
In a failover Clustered Data OPTAP environment, an incremental backup fails with a message similar to the following:
Message: Task 2 NDMP_LOG: id(2,136), type(NDMP_LOG_ERROR), text(CRelation::open_rw(C:\Program Files\DPX/RELATIONSHIPS/[SSclstBKP]DPXvirtualnode@APPS_/.RELATIONSHIP) failed. File not existing
Resolution
After applying DPX 4.4.1 patch updates, at least one incremental must be run with the original owner node having ownership. To change ownership node, in the Failover Cluster Manager, the resources can be failed over to the original node.
Once the first incremental is run with the original owner node, then subsequent failovers should not cause this issue.
Additionally, if a new Base backup is run in the DPX 4.4.1environment, the user should not experience problems for later incrementals, even if a failover happens.