Forum Discussion

H_Sharma's avatar
H_Sharma
Level 6
10 years ago

Backup Hostname

Hello Experts,

I need to know the client name via command. When we install netbackup we put the different name of the client at the time of installation that is not the actual hostname. So pls let me know the command which can be executed from master to a client or client itself to know the intallation name of the client.

Thanks,

 

7.6
Backing Up
Backup and Recovery
Basics
NetBackup
Windows Server (2003-2008)
  • Marianne's avatar
    Marianne
    10 years ago

    For a backup network you need a total different setup in DNS or in local hosts files.

    So, the IP address for hostname abcdefg should only ever resolve to that name and IP address for abcdefg-backup not be aliased to abcdefg hostname.

    Something like this:

    192.168.10.1  abcdefg
    10.10.10.1  abcdefg-backup

    Hostnames and IP address range should be unique on public and backup network.
    Anything other than totally separating hostnames and IP will cause all sorts of comms issues which will impact on backups.

    In my example above, 'bpclntcmd -hn abcdefg' should ONLY return IP address 192.168.10.1.
    'bpclntcmd -ip 10.10.10.1' should ONLY return hostname abcdefg.

    Same applies to abcdefg-backup.
    'bpclntcmd -hn abcdefg-backup' should ONLY return 10.10.10.1.
    'bpclntcmd -ip 10.10.10.1' should ONLY return hostname abcdefg-backup.

    The only aliases for each of these hostnames can be the FQDN for the relevant hostname.
    So, the alias for abcdefg will be abcdefg.fqdn.
    Alias for abcdefg-backup will be abcdefg-backup.fqdn.

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    When we install netbackup we put the different name of the client at the time of installation that is not the actual hostname. 

    Why on earth would you want to do that?

    If you are doing a push-install from the master, how would you know where to connect to if you do not have correct client hostname?

    If you don't know the name, best to do local installation on the client.

    Use 'hostname' command in cmd window on the client to know the client name.
    This command works on Unix/Linux and Windows.

  • H_Sharma's avatar
    H_Sharma
    Level 6
    10 years ago

    Hi Marianne,

    I think i could not make you understand. Let me try. Currently we install netbackup locally on clients not using push install.

    Supose host name is of client is  abcdefg

    1:-When we intall netbackup on client we change the netbackup software name abc-backup and Computer hostname remains the same only software name is getting changed.

    2:- we make host name entry of client as abc-backup on master and client correcponding to IP address.

    It works fine. 

    So i need to know the client netbackup name that was given at the time of installation of netbackup client? Hostname is fine.

    We have some netbackup software installation same as hostname some have been changed as abc-backup

  • Jaime_Vazquez's avatar
    Jaime_Vazquez
    Level 6
    10 years ago

    If this is a Unix/Linux client, look at the file /usr/openv/netbackup/bp.conf. Look at the "CLIENT_NAME =" entry.

    For Windows, look at the registry key "HKLM\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\Client_name"

  • Jaime_Vazquez's avatar
    Jaime_Vazquez
    Level 6
    10 years ago

    From The Administration Console, click on:

    NetBackup Administration -> Host Properties -> Clients

    That will be the full list of "known" NBU clients.

  • INT_RND's avatar
    INT_RND
    Level 6
    10 years ago

    Marianne is correct. You should never do this. You have added many extra steps but no benefit. Only more problems. I would recommend trying to go back and fix this. It will help you in the long run.

    What was the reason it was set up this way?

    Is there something stopping you from fixing it?

  • Will_Restore's avatar
    Will_Restore
    Level 6
    10 years ago

    George Foreman named all of his sons George. 

    But he never tried to install NetBackup Client this way!  :D

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    The only reason why you should ever have hostnames abcdefg and abcdefg-backup for the same client is when the client are connect to 2 networks:
    abcdefg connected to public/production network
    abcdefg-backup connected to a separate network/VLAN for backups.

    Is this what you have?

  • H_Sharma's avatar
    H_Sharma
    Level 6
    10 years ago

    Yes Marianny you are right....

    We have dedicated LAN for prodiction and Backup.

  • H_Sharma's avatar
    H_Sharma
    Level 6
    10 years ago

    i beleive i have found the command to know the name

    bpclntcmd -hn clientname it will return the alias name also

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    For a backup network you need a total different setup in DNS or in local hosts files.

    So, the IP address for hostname abcdefg should only ever resolve to that name and IP address for abcdefg-backup not be aliased to abcdefg hostname.

    Something like this:

    192.168.10.1  abcdefg
    10.10.10.1  abcdefg-backup

    Hostnames and IP address range should be unique on public and backup network.
    Anything other than totally separating hostnames and IP will cause all sorts of comms issues which will impact on backups.

    In my example above, 'bpclntcmd -hn abcdefg' should ONLY return IP address 192.168.10.1.
    'bpclntcmd -ip 10.10.10.1' should ONLY return hostname abcdefg.

    Same applies to abcdefg-backup.
    'bpclntcmd -hn abcdefg-backup' should ONLY return 10.10.10.1.
    'bpclntcmd -ip 10.10.10.1' should ONLY return hostname abcdefg-backup.

    The only aliases for each of these hostnames can be the FQDN for the relevant hostname.
    So, the alias for abcdefg will be abcdefg.fqdn.
    Alias for abcdefg-backup will be abcdefg-backup.fqdn.