10-17-2016 01:26 AM
Hello community,
we have a Netbackup-configuration that comprises of a separate master- and media server and a library.
Our backup-scope comprises:
-NDMP (from our NAS)
-VM's (from our NAS) that are controlled by EsXi-servers and managed with VCenter.
-Physical Windows Servers
All servers run on Windows, by the way.
We need to migrate with everything (servers/PC's/user-accounts) to another domain, so the old domain can be switched off in a few months.
Several servers have already been migrated and now we face the task of migrating our Netbackup-servers.
Can we just go ahead with it or are there specific measures to be taken ?
I have already seen similar posts in which was advised to look at:
http://www.symantec.com/docs/TECH58218 and http://www.symantec.com/docs/TECH38988 , but they are dead-end streets, and I cannot find anything of the kind here at Veritas.
Please advise,
Kind regards,
Jaap
10-17-2016 01:36 AM
Would advise against moving the Netbackup servers to a new domain/subnet as it is not a trivial exercise.
It is better to use the supported solutions like AIR if you using depulication or/and import of tapes.
If you really need to move the Netbackup servers from one domain/subnet to another, get Veritas to help you so you have a supported system after the move.
10-17-2016 01:57 AM
Will the migration involve hostname change?
Or can the same hostname be kept?
Was NBU installed as shortname (e.g. Master) or as FQDN (e.g. Master.dom1)?
If hostname cannot stay exactly the same, you will need consulting services to assist with the migration.
See :
DOCUMENTATION: How to migrate the NetBackup catalog information from one platform to another (UNIX to Windows or vice versa), rename a Master Server, cluster an existing Master Server, or merge multiple NetBackup domains.
http://www.veritas.com/docs/000026956
10-17-2016 02:04 AM
the last installation of the master- and media server has been done for us by a consultant, so I do not
know whether NBU was installed as a shortname or FQDN.
How can I see which method has been used ?
The hostname will remain the same (of course will the FQDN change because of the domain-transition)
Jaap
10-17-2016 02:08 AM
Run these commands on the master:
nbemmcmd -listhosts -verbose
nbemmcmd -getemmserver
10-17-2016 02:31 AM
For obvious reasons I changed the accountname and servernames:
Output:
C:\Users\nbu-admin>nbemmcmd -listhosts -verbose
NBEMMCMD, Version: 7.5.0.7
The following hosts were found:
masterserver
MachineName = "masterserver"
FQName = "masterserver.old.domain.net"
MachineDescription = ""
MachineNbuType = server (6)
masterserver
ClusterName = ""
MachineName = "masterserver"
FQName = "masterserver.old.domain.net"
GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"
LocalDriveSeed = ""
MachineDescription = ""
MachineFlags = 0x7
MachineNbuType = master (3)
MachineState = active for disk jobs (12)
NetBackupVersion = 7.5.0.7 (750700)
OperatingSystem = windows (11)
ScanAbility = 5
NAS
MachineName = "NAS"
FQName = "NAS"
MachineDescription = ""
MachineFlags = 0
MachineNbuType = ndmp (2)
mediaserver
ClusterName = ""
MachineName = "mediaserver"
FQName = "mediaserver.old.domain.net"
LocalDriveSeed = ""
MachineDescription = ""
MachineFlags = 0x4
MachineNbuType = media (1)
MachineState = active for tape and disk jobs (14)
MasterServerName = "masterserver"
NetBackupVersion = 7.5.0.7 (750700)
OperatingSystem = windows (11)
ScanAbility = 5
And:
C:\Users\nbu-admin>nbemmcmd -getemmserver
NBEMMCMD, Version: 7.5.0.7
These hosts were found in this domain: masterserver, mediaserver
Checking with the host "masterserver"...
Checking with the host "mediaserver"...
Server Type Host Version Host Name EMM Server
MASTER 7.5 masterserver masterserver
MEDIA 7.5 mediaserver masterserver
Command completed successfully.
10-17-2016 02:50 AM
It seems you are good to go as Master and EMM name is shortname.
The FQName field can be updated with nbemmcmd command.
10-17-2016 03:10 AM
I just got told by a colleague that:
we need to upgrade from Windows Server 2008 R2 to Windows Server 2012 R2 as well.
And because our server hardware is too old, we will need to upgrade that as well (which coincides with the OS-upgrade). We better do that all before the domain-transition in order to prevent doing things twice.
This inevitably causes the master- and media server name to change, so I guess we need to call in consultancy after all ?
Jaap