Netbackup Domain Migration - Recovery without import tips?

[Flyinraptr]

Hello,

Getting ready to do a Netbackup migration from v7.1.0.3 to v7.6.0.4. -  with the migration moving from one Netbackup domain with servers running W2K3 joined to Active Directory Domain "X" to a new Netbackup domain with servers running W2K8R2 joined to Active Directory Domain "Y".   The same storage devices (ie. tape libraries, OST devices, etc) are being used.  

Familiar with the limitations of moving a Netbackup catalog to a new master server with a different name.  We have gotten around this in the past - albeit the new Netbackup system had all new storage devices.  Essentially - what we did is built a "net new" Netbackup environment and retired the existing environment (including storage devices) with the exception of the lone Master Server.  The lone Master Server was essentially turned into a read-only catalog look-up for restoring legacy data.  When one of the backup operators get a request to restore data that pre-dates the existing Netbackup system - they would go to what i call the "Legacy Master Catalog Lookup Server" to lookup the tapes needed to restore the requested the data.  Once they had identified and recalled the tapes - they would simply perform an import of the tapes into the new Netbackup environment and restore the data.  This has worked well for several years and allowed us to avoid having to import the old catalog and a few thousand tapes into the new Netbackup system (the legacy NB was using LTO2 drives and the new Netbackup system had new LTO4 drives - hence we didn't want to import all of the LTO2 tapes).  No disk/OST existed on the orginal Netbackup system.  The only caveat was that you have to essentially freeze the lone Netbackup server so no changes would ever be made to the databases/images etc. - we even virtualized the Catalog Lookup server - so we didn't have to maintain the old hardware.

With this upcoming migration - we do not have new storage devices.  Currently, the new 7.6.0.4 Netbackup environment can see all of the storage devices/OST shares, etc. of the existing 7.1.0.3 Netbackup environment.  We - for obviously reasons have not run any jobs on the new system - looking at doing a cut-over on a single weekend.   We were originally planning on doing what we had done with the previous migration - creating a stand-a-lone NB Catalog lookup server but after reading through the Recovery Without Import - Whitepaper - it appears we might be able to leverage it to move the exsiting catalog info into the new system without having to touch the physical media.   At least from what i'm reading - it warrants looking into further.

If anyone has successfully used the Recovery Without Import methodology - would greatly appreciate any insight, tips, gotchas that would help us make a decision on whether or not to use this methodology.

Thx,

Greg

[RiaanBadenhorst · Accepted solution]

Hi Greg,

You need to take note that there were catalog changes between 7.1, 7.5, and 7.6. So you'll not be able to use the procedure without upgrading your old master first. In 7.6 the (some) metadata from the images are kept in the EMM. So just placing the db/images on the new master won't allow you to browse backups.

Contact Symantec Consulting Services or a Symantec Partner (who is certified on catalog manipulation) to assist you.

[Flyinraptr]

Thanks Riaan.   Yes - i noticed when reading up on Recovery w/o Import of the changes.  If we decide to go the stand-alone - read only master route - we would keep it at the same NB version (7.1) and use the copy image method.   Since it would only used for tape lookup purposes - not worried about new functionality.  

But if we want to import the existing NB catalog into the new 7.6 NB environment utilizing Recovery w/o Import - if i understand correctly - we would need to upgrade our existing 7.1 NB environment to 7.6.  That obviously adds another step and complexity- will have to mull that over.     

[RiaanBadenhorst]

Hi Greg,

All depends on the customer and when and how they prefer to have restores done. If there is no regulatory requirement, after the first round of backups on the new system you might not even refer back to the old system. As you would have noticed when you did this previously.

[Flyinraptr]

Hi Riaan,

Good points.  There is a regulatory requirement to keep backups but seldom do restore requests go back more than a few days or the last full backup.  What was nice about the method we utilized - was we didn't have to carry forward all the baggage of the previous system - and yes - to do a restore from the older system requires a few extra steps - (the lookup and import of the tape) but as you move forward on the new system - the occurances for restores on the older system become more and more infrequent.

Thanks for your help,

Greg

[Flyinraptr]

Riaan,

One question - haven't been able to confirm on any of the compatibility lists - for the read-only Catalog Lookup server - we would want to keep at the same NB version (7.1.0.4) but upgrade the OS - will it run on Windows 2012 server - not worried about being able to back anything up - just have as a portal for looking up legacy tape labels?

Thanks,

Greg