Forum Discussion

X2's avatar
X2
Moderator
10 years ago

VIP policy and multiple IP addresses

Hi,

We do our backups for VMs using NetBackup VIP policy. The last few days I have noticed that the Windows admins added a network interfaces to cluster nodes. The additional IP addresses are private IP addresses used only to communicate between the cluster nodes.

The backup was working fine with public IP and FQDN before the new network interfaces. Backups still work but now they are being done as backup for the private IPs of the VMs rather than the public/FQDN.

Is there a way to configure which IP gets used for backups (in VIP) by NetBackup? in NetBackup or VMware or even in Windows (node run Windows)?

Thanks.

NB: This is also an issue with VMs having unassigned NICs and hence reporting the 169.254.xxx.xxx APIPA address

PS: NetBackup is 7.6.1.2 on master/media

7.6
Agent for VMware Virtual Infrastructure
Backup and Recovery
Configuring
NetBackup
Not Applicable
Virtualization
  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    10 years ago

    Its probably getting the IP from Vcenter. Can look at the summary of the VM guest and see what it reflects in terms of IP/Hostname vs non clustered VM?

  • areznik's avatar
    areznik
    10 years ago

    When you use VM Hostname, you are essentially telling netbackup to take whatever is the main IP reported by vCenter and look it up in DNS and use the result of that lookup as the client name for the backup. All sorts of weird things can happen when the IP reported to Netbackup is not the one you expect.

    Is switching to DisplayName an option? If its not have a look at this article, bullet point number 2. Netbackup relies on a VMWare utility called vcbVmName.exe to return the IP. You would need to get your VMWare admins to make sure this returns the "correct" IP address. (This might be just for VCB backups, not sure if vADP method uses a different method for querying the IP)

     

     

8 Replies

Sort By
  • X2's avatar
    X2
    Moderator
    10 years ago
    NOT Annotation Contains "NBU=N" AND Template Equal FALSE AND Cluster Equal "Cluster-Dev01" AND VMHasRDM Equal FALSE

    This is the selection query form one of the policies. It backs up all VMs on a cluster without that annotation/templates/VMs with RDM.
     

     

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    Can you add additional selection criteria to exclude these IP's?
  • X2's avatar
    X2
    Moderator
    10 years ago

    I really don't want to go into the game of adding IP addresses for exclusion. Too much hassel to manage it and it is prone to human error.

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    10 years ago

    Its probably getting the IP from Vcenter. Can look at the summary of the VM guest and see what it reflects in terms of IP/Hostname vs non clustered VM?

  • areznik's avatar
    areznik
    Level 5
    10 years ago

    When you use VM Hostname, you are essentially telling netbackup to take whatever is the main IP reported by vCenter and look it up in DNS and use the result of that lookup as the client name for the backup. All sorts of weird things can happen when the IP reported to Netbackup is not the one you expect.

    Is switching to DisplayName an option? If its not have a look at this article, bullet point number 2. Netbackup relies on a VMWare utility called vcbVmName.exe to return the IP. You would need to get your VMWare admins to make sure this returns the "correct" IP address. (This might be just for VCB backups, not sure if vADP method uses a different method for querying the IP)