Hello Everybody. We have implemented NBU 7.1 for backups. We have 1 master server(standard) and 12 clients(standard). We are going to upgarde the master server to Enterprise and one of the clients to Enterprise. Once this is completed, we have to migrate the master server to another physical server. The physical server has all the hardware same as the exisitng hardware. Only the hostname and IP address will change. The tasks will be : 1.Install Enterprise server on new server. 2. Restore master server using latest catalog backup. Please let me know if the above steps are sufficient for performing the migration. Please let me know what is the time required for performing the migration and do we require the existing physical server to be down during migration? I am new to NBU, it would be really helpful if anyone can share any document available for performing hardware migration. Thanks & Regards Sri

OK, three choices: Keep hostname the same Get consulting services to migrate and change hostame Use Recovery without Import method to transfer images from old master to new master, put all assigned tapes on old master in new, RESTORE pool on new master plus write-protect them, keep Media List report from old master to keep an eye on media expiration dates. Manually move tapes as images expire to Scratch pool and remove write-protect. Only do this with new master still on 7.1. See http://eval.symantec.com/mktginfo/products/White_Papers/Data_Protection/nbu_wp_replicatingbucatalogs_103003.pdf

Only the hostname and IP address will change Hostname cannot change! NBU master hostname is deeply embedded in each part of NBU config and EMM database. Only a trained Consulting Partner can change this hostname for you. See these TNs: http://www.symantec.com/docs/TECH31385 http://www.symantec.com/docs/TECH77447 The last one will tell you how to migrate to new hardware using same hostname. IP address can be different although TN says it must stay the same.

Only the hostname and IP address will change. It won't be that simple:) http://www.symantec.com/docs/TECH31385 please check 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

Oops! Marianne is here I better leave now :)

Thank you Marianne and Sazz for the details. The master server is on Solaris 10. I read the TNs mentioned above. Can you please tell how long this activity might take. We need to plan for downtime and get customer approval. Involving a Symantec consultant incurs additional cost and it is not a feasible option for our project. We are in a position where the internal team(backup admins) should be able to perform the task. Is it not possible to perform this migration without involving a Symantec consultant. It would be very helpful if anyone provide the steps for the above migration activity. Thanks in advance.... Regards Sri

You have to play with netbackup database and only symantec conultants have the right utility to do so. If something happens tech support won't help you at all and you have to get in touch with Symantec conultant. Involving a Symantec consultant incurs additional cost and it is not a feasible option for our project I agree and do see your environment is very small and instead of upgrading/migrating why don't you just create a new environment from scratch. You can have a standalone drive attached to your old environment incase you want to restore anything. This is what I have done for one of my client but it all depends. Just wait for some time may be experts here will give you more tips.

Netbackup Migration

24 Replies

Marianne
Level 6
13 years ago

Only the hostname and IP address will change

Hostname cannot change!

NBU master hostname is deeply embedded in each part of NBU config and EMM database.
Only a trained Consulting Partner can change this hostname for you.

See these TNs:
http://www.symantec.com/docs/TECH31385
http://www.symantec.com/docs/TECH77447

The last one will tell you how to migrate to new hardware using same hostname.
IP address can be different although TN says it must stay the same.
sksujeet
Level 6
13 years ago
Only the hostname and IP address will change. It won't be that simple:)

http://www.symantec.com/docs/TECH31385 please check

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
sksujeet
Level 6
13 years ago
Oops! Marianne is here I better leave now :)
srikanth09
Level 4
13 years ago
Thank you Marianne and Sazz for the details.

The master server is on Solaris 10. I read the TNs mentioned above.

Can you please tell how long this activity might take. We need to plan for downtime and get customer approval.

Involving a Symantec consultant incurs additional cost and it is not a feasible option for our project. We are in a position where the internal team(backup admins) should be able to perform the task. Is it not possible to perform this migration without involving a Symantec consultant. It would be very helpful if anyone provide the steps for the above migration activity.

Thanks in advance....

Regards

Sri
sksujeet
Level 6
13 years ago
You have to play with netbackup database and only symantec conultants have the right utility to do so. If something happens tech support won't help you at all and you have to get in touch with Symantec conultant.

Involving a Symantec consultant incurs additional cost and it is not a feasible option for our project

I agree and do see your environment is very small and instead of upgrading/migrating why don't you just create a new environment from scratch. You can have a standalone drive attached to your old environment incase you want to restore anything. This is what I have done for one of my client but it all depends. Just wait for some time may be experts here will give you more tips.
mph999
Level 6
13 years ago
Hi Sri,

It is not possible to change the hostname of a master server without the exact instructions/ steps .

There is no way around this.

Apart from the hostname issue, your palan is fine, recovery the catalog will work, fine, as documented in the Troubleshooting Guide.

Apart from the hostname change, your colleagues should be able to perform the task.

How long will it take, it depends on how big the catalog is, and if anything goes wrong.

Work out how long a Full catalog backup takes. Take this value and multiply it by 3.

Add a bit more, and there is your estimate. Reason being is that it is generaly accepted that restores can take up to 3 times longer than backups, with any backup software.

Regards,

Martin
Marianne
Level 6
13 years ago
Keep hostname the same on new server, just assign different IP.
Don't update IP address in DNS or /etc/hosts on any other server(s) and/or client(s) until catalog recovery is done and NBU has been started up successfully.

Use steps in this TN for Solaris migration: http://www.symantec.com/docs/TECH77448

I normally put 1 full day aside for such a migration. Anything less is a bonus! Take the rest of the day off!
srikanth09
Level 4
13 years ago
So it is not possible to perform the migration without the assistance from Symantec consultant if the hostname and IP address changes.

If it has to be done, then the hostname should not be changed and only IP could be changed as mentioned by Marianne. You had mentioned 1 full day for migration. The physical server need not be down the whole time right? only the netbackup services should be stopped?

I got an idea, may be stupid but wanted to confirm if it is possible:

1. Bring the existing physical server down, perform the migration to the new server keeping the hostname same as existing server.

2. After the migration, change the hostname and IP of the new server . What are the files where we need to update the hostname and IP for NBU? Once we change the hostname of the server, we can edit all those files with the current hostname?will it not sync?

3. and bring the existing server UP.

Will this work?

Thank you for the ideas.
Andy_Welburn
Level 6
13 years ago

After the migration, change the hostname and IP of the new server

As stated by Marianne:

hostname is deeply embedded in each part of NBU config and EMM database.

& sazz:

only symantec conultants have the right utility
Marianne
Level 6
13 years ago
KEEP the hostname the SAME!

NBU will not startup if Master/EMM server name and hostname do not match! There are more than just 'files' to be updated during hostname change. Migration plus hostname change will change time needed for migration from 1 day to 2 days - at consulting fee rates, of course...

Why do you/customer insist on changing the hostname?