12-21-2017 06:35 PM
Hi,
Due to performance constrains we are thinking to seperate the backup traffic between FC and Ethernet. Right now all our backup runs through FC and we have only one vCenter (We are performing VADP)
Now we want to segregate all non-critical server to use Backup LAN and all critical server to use FC as transport medium.
May i know if this is achievable by creating two vmware policies one to use FC and another for Ethernet.
Note:- We have only one vCenter
Master Server :- Windows 2016
Media Server:- NBU Appliance
Thanks,
Nayab
Solved! Go to Solution.
01-02-2018 10:32 PM
@NAYAB wrote:So the LAN/NBD doesn't work with VMDK datastores ? In this case do we need to install the NBU client directly on the clients for NBU master to interact with clients directly ?
It sure does, just not directly from NBU backup host but read by ESXi server and sent over the LAN to the backup host which is your media server.
Installing clients within VMs may or may not be required but it's not required for the VADP (VMware snapshot) process to work, it will work just fine with SAN or LAN options with or without NBU clients in VMs. Where clients might be useful is when you're interested in getting SQL/Exchange/SharePoint app-level backup done as part of the VADP snapshot process or restore granular items back into VMs. For image-level backups clients in VMs are not required.
Does this answer your question?
12-21-2017 08:39 PM
The configuration you need is SAN transport type versus NBD/NBDSSL. They are selected in VMware policy type policy in the last tab.
Effectively, selecting SAN will provide direct backup from VMDK datastores and NBD/NBDSSL will pass data through ESXi hosts and send it to the media server over the LAN
01-02-2018 09:48 PM
So the LAN/NBD doesn't work with VMDK datastores ? In this case do we need to install the NBU client directly on the clients for NBU master to interact with clients directly ?
01-02-2018 10:25 PM
That is NOT what @Mouse said.
As per your opening post, create 2 policies: one to use FC and another for Ethernet.
So, as suggested by @Mouse, select SAN for FC transport in VMware tab for policy 1. Select NBD for Ethernet transport in policy 2.
You may want to spend some time to read through NetBackup for VMware Administrator's Guide for detailed explanation and instructions.
01-02-2018 10:32 PM
@NAYAB wrote:So the LAN/NBD doesn't work with VMDK datastores ? In this case do we need to install the NBU client directly on the clients for NBU master to interact with clients directly ?
It sure does, just not directly from NBU backup host but read by ESXi server and sent over the LAN to the backup host which is your media server.
Installing clients within VMs may or may not be required but it's not required for the VADP (VMware snapshot) process to work, it will work just fine with SAN or LAN options with or without NBU clients in VMs. Where clients might be useful is when you're interested in getting SQL/Exchange/SharePoint app-level backup done as part of the VADP snapshot process or restore granular items back into VMs. For image-level backups clients in VMs are not required.
Does this answer your question?