We are just migrating from Legato Networker to Veritas Netbackup.
Most (not all) of our clients have a dedicated network interface for backups. Naming works in the following way:
- client name (nodename): mars
- name in normal network: mars (10.2.x.x)
- name in backup network: mars-b (10.254.x.x)
- server name: tesla
- server in normal network: tesla (10.1.x.x)
- server in backup network: tesla-b (10.254.x.x)
Each client ist configured in Networker by its real name (eg. mars), so the client name in the catalogue database matches the real client name. Data flows through the backup network to tesla-b by setting the "Server Network Interface" in the client config to "tesla-b" where this is needed.
Is there a way to achieve this setup in Netbackup? I really don't want to name my clients "<name>-b" in Netbackup just to get the data going through the correct interface.
Most (not all) of our clients have a dedicated network interface for backups. Naming works in the following way:
- client name (nodename): mars
- name in normal network: mars (10.2.x.x)
- name in backup network: mars-b (10.254.x.x)
- server name: tesla
- server in normal network: tesla (10.1.x.x)
- server in backup network: tesla-b (10.254.x.x)
Each client ist configured in Networker by its real name (eg. mars), so the client name in the catalogue database matches the real client name. Data flows through the backup network to tesla-b by setting the "Server Network Interface" in the client config to "tesla-b" where this is needed.
Is there a way to achieve this setup in Netbackup? I really don't want to name my clients "<name>-b" in Netbackup just to get the data going through the correct interface.