cancel
Showing results for 
Search instead for 
Did you mean: 

NetBackup 7.1 & 5.1 change domain

brat
Level 2

Hi, I know there have already been several questions regarding this, but I'm still a little unclear on the solution.

We are planning to perform a windows domain migration for our Netbackup servers (7.1 which performs the current backups and 5.1 which is kept for legacy restores)

From what I've already read, if our NBU install was performed using shortnames instead of FQDNs, then I should be able to change the domain of the servers and all should be good. However I'm still a little unclear as to how they were installed. I've got the following from running "nbemmcmd -listhosts -verbose" on our NBU 7.1 master server:

 

BEMMCMD, Version:7.1.0.4
The following hosts were found:
backup1
        MachineName = "backup1"
        FQName = "backup1.domain.com"
        MachineDescription = ""
        MachineNbuType = server (6)
backup1
        ClusterName = ""
        MachineName = "backup1"
        FQName = "backup1.domain.com"
        GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x5
        MachineNbuType = master (3)
        MachineState = active for tape and disk jobs (14)
        NetBackupVersion = 7.1.0.4 (710400)
        OperatingSystem = windows (11)
        ScanAbility = 5
backup2
        ClusterName = ""
        MachineName = "backup2"
        FQName = "backup2.live.co.uk"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x5
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "backup1"
        NetBackupVersion = 7.1.0.4 (710400)
        OperatingSystem = windows (11)
        ScanAbility = 5
restore1.contoso.net
        ClusterName = ""
        MachineName = "restore1.contoso.net"
        FQName = "restore1.contoso.net"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x4
        MachineNbuType = media (1)
        MachineState = active for disk jobs (12)
        MasterServerName = "backup1"
        NetBackupVersion = 7.1.0.4 (710400)
        OperatingSystem = windows (11)
        ScanAbility = 5
Command completed successfully.
 
I'm guessing that because the FQName is a FQDN rather than a simple hostname, it was installed with FQDNs instead of hostnames? Which means that we need to go for a completely new install?
 
The above command does not seem to work on out 5.1 environment, is there a way of finding out how this was installed?
 
Many thanks in advance
 
 
2 REPLIES 2

Marianne
Level 6
Partner    VIP    Accredited Certified
backup1
        MachineName = "backup1"
        FQName = "backup1.domain.com"
 
backup1 was installed with shortname.
 
backup2
         MachineName = "backup2"
        FQName = "backup2.live.co.uk"
backup2 was installed with shortname.
 
restore1.contoso.net
        MachineName = "restore1.contoso.net"
        FQName = "restore1.contoso.net"
 
restore1 was installed with FQDN.
 
You simply add new domain as alias to master server backup1:
nbemmcmd -machinealias -machinename backup1 -machinetype master -addalias -alias backup1.domain
 
NBU 5.1 is whole different ball game - there is no EMM database, but a number of individual databases per server. 
Check the SERVER entries in the GUI and vmglob command:
<installpath>\volmgr\bin\vmglob -get_gdbhost
 

brat
Level 2

Thank you very much Marianne for the reply.

Just to clarify, on 7.1 I add a new domain as an alias to master server backup1. Then I can change the domain membership of both backup1 and backup2, is that correct? The NBU services are all running as Local System so there's no service accounts to change?

I have run the specified command on our 5.1 servers and it responds with just a hostname and not a FQDN, can I therefore presume that all is good and I can just change the domain membership of our 5.1 NBU servers?

Thanks