Separate Backup network

Question

Have an installation of Networker 7.3.2 Windows with currently one storage node of the same. After the install of the master, customer decided to have a separate backup network which is configured and now in place with host file entries of all servers to backed up on the backup network on the backup server and storage node. When the master server was installed it installed with the short name which is associated with the production network. The storage node and all other clients have been installed with the long name of the backup network.

So now the master server and storage node are communication through the production network and I need them to talk to each other through the backup network.

Is there an easy way change the installation of the master server so that it is installed with the long name for the backup network? I hope it is as simple as disabling the production network and re-installing the software so all the current config can be saved.

ble1 · Answer

Metadata communication is small and as such can go over the production. Data communication is another thing. For each client set backup server interface to point to bck name of server and apply same rule for storage node fields.

If you want to have everything (including metadata communication) over backup interface there is a way, but it is more complicates then reinstalling software and it does require changes to server and SN box configuration itself.

If possible I would leave metadata to go over the production as impact is minimal. KB used to have article about such setups so you may wish to check it out (hopefully that document is part of Powerlink now).

Richie5 · Answer

So am I incorrect in assuming that If I had only had the backup network nic(production nic disabled so that short name is not resolved by DNS for the production network) enabled and installed the master server using the long backup network name, wouldn't networker be using only the backup network for data and metadata? If I dissable the production nic and re-install the master server software using the long backup network name, would this fix the issue?

I believe the customer customer is wanting have the production and backup network completely separate where one cannot see the other. But I will confirm. It seems this may not be possible if the customer has some clients that will not have a backup network nic and will need to backup through the production network.

What is the procedure to do this and if all communication is done over the backup network, will the customer be able to backup clients that are not on the backup network? Meaning they could be backed up through the production network.

ble1 · Answer

Richie, to put it simple, you will need both networks (as you imply customer has clients not on backup LAN). Those on backup LAN have backed up via backup VLAN and leave their metadata go over production - metadata is small and does not present any threat to customer's network. Data on the other side should go over backup LAN if customer needs that.

NetWorker

Separate Backup network

Was this post helpful?