We have DR situation on one of production system and currently working on to activate the DR but overall process is very slow if we use the import phase 1 & 2 methodology as both system have different node configuration and BAR configuration.
We are looking if anyone has done the recovery without running the import phase 1&2 on Netbackup.
Below link has the details :
We did try above approach but the catalog restore is not working. It fails with error 48: client hostname could not be found.
I have done research on this issue and it seems that catalog restore to a different system requires both the source and destination master servers to have the same name. Otherwise the restore requires support from Veritas/ Symantec.
Any ideas on this will be appreciated.
Whenever I do a catalog recovery to a master of a different name, I add the original master name to the DR master's hosts file as an alias to the system hostname. Usually I've got a few media servers in prod but only a single master/media at DR, so all the media servers added as well.
On unix in /etc/hosts; on windows in c:\windows\system32\drivers\etc\hosts; something like this.
127.0.0.1 localhost 184.108.40.206 drmaster drmaster.localdomain prodmaster prodmaster.company.com prodmedia1 prodmedia1.company.com prodmedia2 prodmedia2.company.com
Then, when installing NetBackup, use the original master name at the prompts, add storage devices, catalog recovery wizard, ...
It's been a while since I've done one of these, it might help if you also add the orginal master and media as aliases to the DR master in nbemm before runing the catalog recovery wizard.
I found that the catalog restore to a differnet system, you have to check the HOT CAT file, and edit it to update the host name, I think it is the fragment lines.