Solved! Go to Solution.
We have couple of similar projects in our pipeline and Symantec sales rep has assured that they will be able to hire consultant that has been trained at the "NetBackup Catalog Manipulation" training and eligible to run the "mergeutil". However, as I understand this is really depends upon region. I know personally couple of guys in UK who are eligible, but I'm not sure that they're able to merge 7.x domain. Merge util definitely works with NBU 6.5.x (we've done several migrations with it).
We are trying to migrate onto a new os, hardware, hostname, ip address and unfortunately the reseller awarded the contract was no help with this migration.
I need the procedures and tools to bring up the databases on the new master, but so far have found nothing helpful. They should have sent me to NetBackup forum, which is going on this week. At least then, I could have gotten all the information needed to complete this migration.
As it stands now, I don't see this happening for at least two, three weeks.
mergeRSA is the successor to mergeutil -- it does an export of the EMM database and then you can do the import at the new Master. It does not require both servers to be up and connected like mergeutil... however neither mergeRSA nor mergeutil will handle advance disk. importing OST images can take days and weeks depending on number of images...
the most time consuming problems I have found during my times doing domain consolidations is cleaning up the domains from conflicts and incosistencies prior to the merge (e.g. non unique media ID, names, catalog issues, etc...).
Not sure if there is anyone left that knows how to use the mergeRSA tool and to my knowledge mergeutil has been retired...
OS, HW and IP address migrations is simple to solve really, fully supported by a catalog recovery. Cross-platform is a bit different, but same OS type to newer version is not a problem.
The problem is more the hostname of the master and media servers, both fairly simple to solve. You can change names with nbemmcmd, you can change ownership of backups with bpimage (or not use ownership at all at backup time). If media is owned by a media server you would need to change that (bpimage). master server name is simple, but you need to re-point all media servers and clients to the new hostname.
Essentially problems really occur when you consolidate one or more NBU domains. This require additional tools in order to update the EMM. OST disk pools is a completely different scenario, and you wouldn't want to go there. 2 phase import is the simplest...