Traditionally, our strategy overview for backup has been this.
Backup LAN for backup traffic, all physical hosts have a separate NIC for connection to backup LAN. If the physical server requires more bandwidth we throw in a HBA card and configure it as a SAN client or media server(to backup itself via FC).
With the consolidation of physical servers into blades, LAN and FC physical ports are limited.
On top of this, Netbackup has issues supporting FC based backups for HyperV clusters, i.e. When i configure the backup policy with the HyperV cluster name, the backup proceeds via LAN. The temp workaround symantec engineers have suggested is to configure the node name into the backup policies instead of cluster name, but this poses issues such as having multiple policies for multiple nodes as well as if the VM moves to another node, the backup will fail.
So, my original plan to reserve a FC port on the blade solely for backups and configure all VMs in the same blade to backup via FC doesnt seem very hopeful.
So, What would be the typical recommended strategy for this scenario?
By the way, im running NBU 7.5 on windows 2012 R2 as of now.
