cancel
Showing results for 
Search instead for 
Did you mean: 

Windows Master Server upgrade and hardware refresh - seeking advice/input

DataProtector2
Level 2
Certified

The current master server NB catalog is stored on C drive with over 50% of images stored on D drive using shortcuts.   The NbDbAdmin.exe is reporting catalog corruption errors within the catalog.    So the plan is to NOT migrate the NB catalog over to the new master server.

Since the longest backup retention in this environment is for 90 days, leave current master server up for restores until all images have expired.

ENVIRONMENT:

  • Consists of Window servers:  master and 4 media servers running NB 7.1.0.4
  • Policies:  25 FlashBackup VMware intelligent backup policies backing up virtual environment (900+ VM’s) and a couple of NT-Windows policies backing up 12 physical client.
  • Storage:  using DataDomain OST, no tape

 

 

PLAN:

  1. Build new master running NB7.6 with a new name (do not move media servers over until the day of cut over)
  2. Recreate all flashbackup policies but assign the master server as the  VM BACKUP host (temporarily, until the day of cut over)  and recreate other NT-Windows policy
  3. Configure storage DataDomain OST plugins and add necessary VM credentials on new Master

 

Day of cut over

  1. Deactivate all backup policies on the old master server NB7.1.0.4
  2. run the nbdecommision command on the old master server to assign all backup images to the master server (this is if restores are  needed from the old environment)
  3. upgrade all 4 media servers to NB7.6.0.1 and assign them to new master NetBackup host running 7.6.0.1
  4. add the new master server name to the server list for the 12 physical clients

 

Please feel free to add any suggestions or comments if any steps are missing or overlooked…

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

nbemmcmd -setemmserver  will simply update the EMM server entry on the media servers. Nothing else.

You will have to configure backup storage as before for all the media servers (remember that all config is stored on the master - nothing on the media servers), such as Storage Server, Disk Pool(s), Storage Units.

Same license key as... ? 

NBU 7.1 license key may work, but best to use new 7.6 license keys. 
If you have not received Upgrade Notification, logon to the Licensing Portal:  https://licensing.symantec.com  to register current licenses and request upgrade licenses.

View solution in original post

5 REPLIES 5

SymTerry
Level 6
Employee Accredited

Hello, 

There is a few things you will want to watch out for. One is renaming the master server. TECH31385 talks about this processes:

However there are many other operations that customers may need to perform at some point, including migrating the NetBackup catalog information from one primary platform to another (UNIX to Windows or vice versa), rename a Master Server or Media Server, cluster an existing Master Server, or merge multiple NetBackup domains, that should not be attempted without the assistance of either a Symantec NetBackup consultant or a certified consultant from a Symantec Consulting Partner.

If you can keep the name the same, you could just upgrade the master server to the newest version and then migrate it over to the new hardware following TECH77447

This will eliminate most of the remaining steps, except connecting the DD. That will still need to be done.

Will_Restore
Level 6

Since the longest backup retention in this environment is for 90 days, leave current master server up for restores until all images have expired.

 

I'd just build the new Master however you like and keep the old one around until all the old images expire.  Point the clients to the new Master but keep the old name in Server list just in case.  Easy peasy. 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Your steps look good.

Best to use existing master to add new master as a SERVER on media servers and all clients.

Once you have tested connectivity from new master, you can select the new master in Host Properties of all clients and Media servers and select 'Make Master'.

Use nbemmcmd -setemmserver on new master to change EMM server to itself on all media servers.

One more thing: 
Probably a good idea to create a new Logical Storage Unit (LSU) on the DD for the new environment.

DataProtector2
Level 2
Certified

All- 

my apologizes for such a late response and  very grateful for all the feedback ….   

 

Marianne -

I’ve always enjoyed reading your posts  winkand so glad to have your input….  

Can you please review my questions below?

 

Best to use existing master to add new master as a SERVER on media servers and all clients.

Great ideal…   Definitely will doyes

 

Use nbemmcmd -setemmserver on new master to change EMM server to itself on all media servers

Will the command above begin writing backup images to the NB catalog on the new server then?

 

The NEW server is ready for the NB7.6.0.1 installation, during the install of NB software, Master server will be selected, so can I use the same NB License Key without any conficts?

 

Probably a good idea to create a new Logical Storage Unit (LSU) on the DD for the new environment.

Great ideal and will do….yes

 

Thanks again for all the great feedback

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

nbemmcmd -setemmserver  will simply update the EMM server entry on the media servers. Nothing else.

You will have to configure backup storage as before for all the media servers (remember that all config is stored on the master - nothing on the media servers), such as Storage Server, Disk Pool(s), Storage Units.

Same license key as... ? 

NBU 7.1 license key may work, but best to use new 7.6 license keys. 
If you have not received Upgrade Notification, logon to the Licensing Portal:  https://licensing.symantec.com  to register current licenses and request upgrade licenses.