Netbackup AIR over FC consuming a lot of network bandwidth
Hello,
NBU version 8.2
Master server Linux
Appliance 5240 version 3.2
We are facing issue with replication jobs. All the instructions in the guidelines for setting AIR using fibre channel are followed. The replication jobs work well, and the speed are quite high, so we thought that the replication over fc is working accordingly.
However, about a week ago, network team found out that netbackup appliance are consuming a lot of bandwidth during replication (not sure since when this actually happened), so they put a cap to limit the consumption of bandwidth for netbackup replication.
The network report show that the port that is going through the LAN network is 10082, which is the spoold port.
Logging the case to veritas support doesn't help at all. They said that data and spoold and data transfer should go through only one way(fc or lan). But clearly that is not the case.
Now, there are a lot of replication jobs running with no progress(0kb), especially the big sized ones. Even the small size image is replicating very slowly. So obviously network capping is taking effect.
Appreciate if someone in here colud help me with this.
Thanks in advance
NBU version 8.2
Master server Linux
Appliance 5240 version 3.2
We are facing issue with replication jobs. All the instructions in the guidelines for setting AIR using fibre channel are followed. The replication jobs work well, and the speed are quite high, so we thought that the replication over fc is working accordingly.
However, about a week ago, network team found out that netbackup appliance are consuming a lot of bandwidth during replication (not sure since when this actually happened), so they put a cap to limit the consumption of bandwidth for netbackup replication.
The network report show that the port that is going through the LAN network is 10082, which is the spoold port.
Logging the case to veritas support doesn't help at all. They said that data and spoold and data transfer should go through only one way(fc or lan). But clearly that is not the case.
Now, there are a lot of replication jobs running with no progress(0kb), especially the big sized ones. Even the small size image is replicating very slowly. So obviously network capping is taking effect.
Appreciate if someone in here colud help me with this.
Thanks in advance
