Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NetBackup 7.5.0.5 Master/Media Server Hardware Refresh

Created: 20 Mar 2013 • Updated: 15 Jul 2013 | 16 comments
This issue has been solved. See solution.

Good afternoon,

We are currently running NetBackup 7.5.0.5 on our Master/Media Server, which in running Windows Server 2003 R2, x64. The hardware is EOL and we want to migrate to a new HP Proliant G7 that is running Windows 2008, R2. After reading up on this it seems pretty clear that the IP address and hostname of the new Master/Media Server should remain the same so that is my intention. All installation paths will remain the same. We have a Quantum i500 Physical Tape Library as well as a Quantum Dxi setup with NAS shares.

My plan is as follows:

Build up the new server (install OS, etc.)

Run a Full Catalog Backup on the current NBU Master Server and turn off all NBU services after the Full Backup completes. Assign a new IP address to the current Master Server and rename the server. Shutdown the server.

Join new server to domain and rename it so that it matches the name of the current master server. Set IP so it is identical to the original IP address of the Master Server.

Move all Fibre cards from the old Master Server to the new and ensure that they are visible and usable at the OS level.

Install NetBackup 7.5.0.5 on the new server as that matches the old server.

Run Device Configuration Wizard to re-add devices in NBU.

Verify Storage Units

Perform a Catalog Recovery. I am a little uncertain about the steps here so I have more reading to do.

Test backup jobs

I had read that the best time to perform this task might be before the next Full Backups run as doing it before then would result in the incremental backups running as Full Backups so I guess I am also taking that into consideration.

Does it appear as though I am missing anything? I would appreciate any input or advice from others who have done a hardware refresh of the NBU Master Server or are just familiar with the process.

Thanks in advance.

Martin P.

Operating Systems:

Comments 16 CommentsJump to latest comment

Yasuhisa Ishikawa's picture

If you use tapes for catalog backup, you need to add catalog backup tapes before performing catalog recovery. Or, if you use BasicDisk storage unit for catalog backup, copy image files to new server with same path.

Catalog recovery is not so complicated if you keep Disaster Recovery Information files. Place it on new server and specify when asked.

After catalog recovery, be sure to restart NetBackup and run device configuration wizard again. Devoce configuration may be replaced by that in old master servrr.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

SOLUTION
aktrout's picture

Yasuhisa,

Thank you very much for your prompt reply. We are backing up the Catalog to BasicDisk STU and we do keep the Disaster Recovery Information File on a network share as well as send it via email so I think we are ok in that regard.

In your last sentence you say "Devoce configuration may be replaced by that in old master servrr." and I think you know what you mean when you say that but a little bit uncertain.

I am still reading up but your input was helpful.

Thank you.

Marianne's picture

Yasuhisa is right - catalog recovery will restore the device config of original master server.

So, delete all devices that were restored, and re-run device config.

Also confirm as per Yasuhisa's post that BasicDisk STU is mounted to same drive letter/path on new master.

The 'Incrementals running as full' issue applies to NBU 6.5 only. See http://www.symantec.com/docs/TECH77447

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
Mark_Solutions's picture

Your plan sounds good and you have had some excellent advice from the others on this forum - but I would like to add a few extra points to make things go smoothly.

1. Even though you are going to move the basic disk area across to the new server you would need to import it all into the new system to be able to do the catalog restore - so i would advise that you do that final catalog backup to tape to make life far simpler

2. Make a note of all settings in the Master Servers Host Properties - many of these get written to the registry and will not get migrated across during the catalog restore

3. Make a note of your barcode and media id generation rules and add them in before doing the catalog restore to make sure all media ids are correct on the new system

4. Make a note of your master servers name in NetBackup (the one shown at the top of the Admin Console) as NetBackup has a habit of using the FQDN when being installed on 2008 and the names mastersrv is not the same as mastersrv.domain.com - so make sure when you install NetBackup on the new server it uses the same naming convention as the original when you get to that last installation screen.

5. Make a note of your last job ID (or take a copy of the \Program Files\Veritas\NetBackup\db\jobs\jobid file) so that your system does not start from job 1 again.

6. Do not get tempted to install NetBackup before the new server is renamed as it will write entries into locations that will cause you issues in the future

Hope all this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION
aktrout's picture

Thanks to both Mark and Marianne for your input. Per your notes Mark I have more thoroughly documented the Master Server Host Properties, noted to document the last job ID, ensure that NBU install doesn't use the FQDN, etc.

I am going over the process of recovering the entire NetBackup Catalog now (Page 207 of the 7.5 Disaster Recovery Guide).

Mark - I don't understand your point in item 1 yet. It states:
***
1. Even though you are going to move the basic disk area across to the new server you would need to import it all into the new system to be able to do the catalog restore - so i would advise that you do that final catalog backup to tape to make life far simpler
***

I am unclear about this but perhaps my reading will clear that up.

Mark_Solutions's picture

I had the feeling that you did your catalog backups to disk

If that is the case then a new installation would have no knowledge of them and would need them importing before you could do the catalog restore properly - if they were on tape you would not need that step

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

aktrout's picture

Thanks again to all who have taken the time and effort to contribute. We are waiting on some hardware but hopefully it will arrive this week and I can make a run at the migration this weekend. I will update this thread with my results.

aktrout's picture

So hardware arrived and hopefully going to try the migration soon.

Question - on the NetBackup server that is going to be retired, the Image Catalog was moved to the E volume.at some point so the plan is to setup the new Master Server with an E volume, of course. My question is, at what point in the migration process do I need to modify the NetBackup configuration and instruct NetBackup on the new server to use the E: drive instead of the C drive for the image Catalog?

RLeon's picture

the Image Catalog was moved to the E volume.at some point

There are at least 3 methods that this could have been done; one of them obsolete. Which method did you use?
There was the registry method (obsolete), the ALTPATH touch file method, and the hard links method (not usually done on Windows).

If the registry method was used, since it is no longer supported, so for the new server you would not be able to do the same anyway.
In this case, I would recommend undoing the registry method on the source server (i.e., putting everything back to the default path, probably C:), do a fresh Catalog backup, then migrate to the destination server normally using Catalog Recovery and the rest of the migration procedures.

If undoing the registry method is not possible for some reason - such as not having enough space on the default drive/path - then you may need to call support and quote this post. I don't think anyone on the forum other than Symantec would be able to give you a solid answer about the implications of doing a Catalog Recovery when the image db was moved elsewhere using a no-longer-supported method.

If the ALTPATH method was used, then having the same E: drive on the destination server should do.
http://www.symantec.com/docs/TECH192528

If hard links were used, then just recreate them at the right source and destination paths either before or after the Catalog Recovery.

SOLUTION
Marianne's picture

Catalog recovery will restore the catalogs to the exact same path where it was backed up from.

It may be a good idea to move all of NBU to E-drive before you migrate to new hardware.

See this TN for instructions; http://www.symantec.com/docs/TECH70962

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

aktrout's picture

RLeon / Marianne - thank you very much for your helpful information.

In this case, the ALTPATH method was used.

Marianne, I know you have a world of experience so not second guessing you but wondering why I would move all of NetBackup to the E drive? I am sure you have a reasons for suggesting this but wondering what they might be.

Thank you.

Marianne's picture

I would like to have all of NetBackup on one drive when migrating to new server - not split between C and E like on the current master server. 

But that would be my personal preference. 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

aktrout's picture

ok, I am removing all of NetBackup from the C volume and Re-installing to E per http://www.symantec.com/docs/TECH70962

Thanks. Hpefully this piece of the puzzle goes without too much fuss, muss, or greasy aftertaste.

dwilliam223's picture

I am looking at needing to do a similar migration for my NetBackup master server.  I am wondering how your upgrade went or if you have had a chance to attempt this yet?

Thanks.

Marianne's picture

Probably best to start your own new discussion for your specific situation.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

aktrout's picture

Hardware Refresh Update -

The refresh went fairly well. There were some minor issues. The biggest problem we had was restoring the Catalog from a dedupe disk appliance. It took a very long time and we eventually opted to restore from tape which went much faster.

The tips and suggestions provided by Marianne, Yasuhisa, Mark, RLeon ,etc. were very helpful, indeed.

It is certainly something that needs to be well planned and there are a lot of details to attend to prior to attempting it. I made sure to document the settings for our Master Server in detail before I cutover.

Thank you all!

Martin P.