I would like to know the process to rename Netbackup Master Server 7.5.0.6. Please Advice NEERAJ MEHTA

You need to locate a Symantec Consulting Partner - not a DIY job. See http://www.symantec.com/docs/TECH31385 Symantec has developed comprehensive methodologies to handle a variety of reconfiguration requirements including the following scenarios: Migration from an existing master server to a NetBackup appliance master server Merging of two or more domains Splitting of a domain into two or more domains Clustering of a non-clustered Master Server Renaming of a Master Server or Media Server Moving a Master Server to a new machine involving a host name change Moving a Master Server to a different platform/operating system (Windows to Linux/Unix or Linux/Unix to Windows) Un-clustering a clustered Master Server A number of Symantec consultants and Consulting Partners worldwide have been trained on these procedures and certified to deliver them in accordance with standards required by the Symantec technical support organization. Symantec consultants and Consulting Partners will assist customers by determining the correct approach to take, planning the activity and executing the plan successfully with minimum disruption to the operational environment.

Master server is on Windows 2008 R2 64 Bit....

Thanks Marianne, The same information i got from symatec support , i just wanna know if ther is any supporting documents available so no need to spend money for Symantec Consulting Partner. As I already have experiance on Netbackup , so some documents can help me to rename master server. Thanks,

Short answer is if you don't already know how, do not do it! Too easy to break your environment!

There is no documentation available. Consulting partners are not allowed to share documentation.

Absolutely no documentation at all. You need to engage Consulting OR you keep the name the same.

Renaming of a Master Server

14 Replies

NEERAJ_MEHTA
Level 4
12 years ago
Master server is on Windows 2008 R2 64 Bit....
Marianne
Level 6
12 years ago
You need to locate a Symantec Consulting Partner - not a DIY job.

See http://www.symantec.com/docs/TECH31385

Symantec has developed comprehensive methodologies to handle a variety of reconfiguration requirements including the following scenarios:

Migration from an existing master server to a NetBackup appliance master server

Merging of two or more domains

Splitting of a domain into two or more domains

Clustering of a non-clustered Master Server

Renaming of a Master Server or Media Server

Moving a Master Server to a new machine involving a host name change

Moving a Master Server to a different platform/operating system (Windows to Linux/Unix or Linux/Unix to Windows)

Un-clustering a clustered Master Server

A number of Symantec consultants and Consulting Partners worldwide have been trained on these procedures and certified to deliver them in accordance with standards required by the Symantec technical support organization.

Symantec consultants and Consulting Partners will assist customers by determining the correct approach to take, planning the activity and executing the plan successfully with minimum disruption to the operational environment.
NEERAJ_MEHTA
Level 4
12 years ago
Thanks Marianne,

The same information i got from symatec support , i just wanna know if ther is any supporting documents available so no need to spend money for Symantec Consulting Partner.

As I already have experiance on Netbackup , so some documents can help me to rename master server.

Thanks,
Will_Restore
Level 6
12 years ago
Short answer is if you don't already know how, do not do it! Too easy to break your environment!
Marianne
Level 6
12 years ago
There is no documentation available. Consulting partners are not allowed to share documentation.
revarooo
Level 6
12 years ago
Absolutely no documentation at all. You need to engage Consulting OR you keep the name the same.
C-Ray
Level 3
11 years ago
You can always build a new master, then migrate over. You would have to get a new server (hardware), and you would have to keep the old master around till all the images have expired. That's one way of getting what you want acomplished.

Unless you really have a need to change the name of the master server, I would just leave it the way it is. I do not know how big your environment is, but if you change the name of the master, then you will have to change it on all your clients.
NEERAJ_MEHTA
Level 4
11 years ago
My master server have images for more than 200 servers with infinity Retention !!!!!!

Actually we moved from one domain to another domain , I can use same name but with different domain name ...

So FQDN will change .....

Please advice ....
Marianne
Level 6
11 years ago
It all depends on how NBU was installed in the first place.

Was master server installed with shortname or FQDN?

Check output of 'nbemmcmd -listhosts -verbose'.

If shortname, all is good - you can use nbemmcmd to add and alias for new FQDN.

If FQDN, there is no easy way - it is seen as a hostname change for which consulting is needed.
NEERAJ_MEHTA
Level 4
11 years ago
Hi .

Please find the output of 'nbemmcmd -listhosts -verbose'

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listhosts -verbose
NBEMMCMD, Version: 7.5.0.5
The following hosts were found:
msh-sv-sdo-drfs
        MachineName = "msh-sv-sdo-drfs"
        FQName = "msh-sv-sdo-drfs.minustah-sosd.dpko.un.org"
        MachineDescription = ""
        MachineNbuType = server (6)
msh-sv-sdo-drfs.minustah-sosd.dpko.un.org
        ClusterName = ""
        MachineName = "msh-sv-sdo-drfs.minustah-sosd.dpko.un.org"
        FQName = "MSH-SV-SDO-DRFS.minustah-sosd.dpko.un.org"
        GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x5
        MachineNbuType = master (3)
        MachineState = active for tape and disk jobs (14)
        NetBackupVersion = 7.5.0.5 (750500)
        OperatingSystem = windows (11)
        ScanAbility = 5
msh-sv-ssd-vc1
        MachineName = "msh-sv-ssd-vc1"
        FQName = "msh-sv-ssd-vc1.minustah-sosd.dpko.un.org"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
msh-sv-sdo-vc1.minustah.dpko.un.org
        MachineName = "msh-sv-sdo-vc1.minustah.dpko.un.org"
        FQName = "msh-sv-sdo-vc1.minustah.dpko.un.org"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
msh-sv-sdo-drfs.minustah-sosd.dpko.un.org
        MachineName = "msh-sv-sdo-drfs.minustah-sosd.dpko.un.org"
        FQName = "MSH-SV-SDO-DRFS.minustah-sosd.dpko.un.org"
        MachineDescription = "PureDisk"
        MachineFlags = 0x2
        MachineNbuType = ndmp (2) (storage_server)
nbmeds7.minustah.dpko.un.org
        MachineName = "nbmeds7.minustah.dpko.un.org"
        FQName = "nbmeds7.minustah.dpko.un.org"
        MachineDescription = ""
        MachineFlags = 0x2
        MachineNbuType = ndmp (2) (storage_server)
msh-sv-lgb-lib.minustah.dpko.un.org
        MachineName = "msh-sv-lgb-lib.minustah.dpko.un.org"
        FQName = "msh-sv-lgb-lib.minustah.dpko.un.org"
        MachineDescription = ""
        MachineFlags = 0x2
        MachineNbuType = ndmp (2) (storage_server)
nbmeds8.minustah.dpko.un.org
        MachineName = "nbmeds8.minustah.dpko.un.org"
        FQName = "nbmeds8.minustah.dpko.un.org"
        MachineDescription = ""
        MachineFlags = 0x2
        MachineNbuType = ndmp (2) (storage_server)
Command completed successfully.

As my Master server name msh-sv-sdo-drfs.minustah-sosd.dpko.un.org