Support for multiple VLAN when disaster recovery is configured
When disaster recovery is configured between two sites using catalog replication between two NetBackup Flex Scale clusters, the primary service is active on only one cluster at any given time. However, the primary service manages the media services, storage servers, and storage units across both clusters.
Each cluster requires independent configuration and management of additional data networks, with the number of data networks varying depending on network needs.
Before setting up catalog replication, only the primary cluster can have additional data networks configured. The secondary cluster cannot have any additional data networks.
If disaster recovery is configured to use a single virtual IP for the NetBackup primary service FQDN, all additional data networks must share the same virtual IP configuration for the primary service FQDN.
You cannot add data networks on both the primary and secondary clusters simultaneously.
When performing a replication role change (moving the primary service between clusters), ensure that the DNS server (if configured) is updated with the correct virtual IP for the NetBackup primary service on all data networks of the target cluster.
If an additional data network introduces a new primary service FQDN, you must configure it first on the cluster where the primary service is active. Only then can the same FQDN be used when configuring the additional data network on the secondary cluster.
The option in the page relies on DNS resolution to map the virtual IP to the correct FQDN. If the primary service uses different virtual IPs on each cluster, the DNS server might not resolve the FQDN correctly when adding it to the secondary cluster, as it may already be resolving to the primary cluster's virtual IP. To avoid this, either use the option or update the DNS to correctly resolve the FQDN before adding the data network.