Hello,
We tested bmr for a client in a different subnet than the master server is in. We had an issue because the restoring client (booting from NB bootable CD) could not contact the master server . The client is in a different network than master and boot server. I thought I could workaround this, booting with the NB SRT bootable cd and setting gateway Ip address, netmask, etc. This client has four network devices (eth0, eth1, eth2, eth3), each two in bonding (eth0+eth1=bond0.vlanX and eth2+eth3=bond0.vlanY) with a tagged vlan. During the CD based BMR boot, I set the client IP address known by the master server, netmask, gateway and ip of master server....but the client tried to contact the master via eth1...eth2...eth2...eth4...without success.
We suppose that the problem could be that the network we use from/to the switch is a tagged vlan and booting from NB SRT bootable CD need an untagged vlan network ...
Is tagging vlan on network devices supported by Netbackup bare metal restore process.....?
Other times I tested BMR, the clients had always been in same network of master server, so this issue did not arise.
Was I clear enough in explaining? Any helps....?
Thanks in advance
Andrea
------
Master NB 6.5.4 (Linux x86 RhEL AS4.8)
Media Server NB 6.5.4(Linux x86_64 RhEl 4 and RhEL 5.5)
Client: NB 6.5.4 (RHEL 5.5 x86_64)
Boot Server: NB 6.5.4 (RhEL 5.5 x86-64)