Hello everyone,

I'm currently designing a backup solution based on Dell EMC NetWorker 19.14, NMDA for Oracle, Data Domain with DD Boost Client Direct, and Veritas InfoScale Enterprise.

The environment is as follows:

Oracle 19c running on a 2-node Veritas InfoScale Enterprise geocluster.
One physical Oracle node in each Data Center (DC1 and DC2).
Oracle runs active/passive, with a single Virtual IP (VIP) managed by InfoScale.
Each Data Center has:
- One local Storage Node.
- One local Data Domain.
There is a strict design requirement that backup traffic must always remain local to the active Data Center. Cross-DC backup traffic is only acceptable during exceptional disaster scenarios.
The two Data Domains replicate their MTrees between sites.

The expected behavior is:

If Oracle is active on Node A (DC1), RMAN/NMDA should write to Storage Node A and Data Domain A.
After a Veritas failover, when the VIP moves to Node B (DC2), the backup should automatically use Storage Node B and Data Domain B, without requiring manual reconfiguration.

My questions are:

What is the recommended Dell/NetWorker design for this scenario?
Should the Storage Node Affinity be configured on:
- the physical Oracle clients,
- the virtual cluster client (VIP),
- or both?
When a backup is launched against the virtual Oracle client (VIP), does NetWorker resolve the preferred Storage Node based on:
- the virtual client configuration,
- or the physical node where NMDA is actually running?
Is Storage Node Affinity sufficient for this design, or is it recommended to implement:
- Backup Target Devices,
- separate workflows,
- pre/post scripts,
- or another supported mechanism?
Has anyone implemented this architecture successfully in production?

Any Dell documentation, best practices or real-world experience would be greatly appreciated.

Thank you!

Cloud

Dell Support Resources

Latest Solutions

NetWorker 19.14 + Oracle NMDA + Veritas InfoScale Geocluster + Data Domain local affinity

REST API returns error 500 - (Internal Server Error) after Avamar 19.12 upgrade

Security Advisory: Unclear recommended version: 19.12, 19.13, or 19.14?

NetWorker server vm Hardware Compatibility version

Data Protection Advisor SWID only showing