If you happy just to get things working then I guess you 'might' not be too concerned about this cause.
Persoanlly, I would want to check this new server can do a cat recov. off and inct backup, as you may have to do this for real in the future.
If, the issue really is with the DR file off the old system, then providing the catalog backups on the new server work, it doesn't matter, you're getting rid of the system after all - however, your thoughts may differ.
You can recover from the 2nd copy of the tapes ...
We can't merge the EMM DBs / or the image DB for that matter ...
Persoanlly I get nervous when people talk about syncing /usr/openv/etc ...
Why you ask, after all, you have done this in the past etc ... other people do this etc ...
As you've worked out, I work for Sym - I do this all day/ every day and I have lost count of situations where people have called up one week after a 'migration' bacuase something is broken ...
So then I ask, when you ran the Catalog recovery ...
Oh no, we copied across ....
Really I say ... as tears begin to fill my eyes, and I consider a new career ...
You get the idea - sure, coping across /usr/openv is probably ok ... IF you install the correct (equal) version of NBU first, to set up things like /etc/services etc ..
Persoanlly, and you did ask, if possible my preference would be to run a proper cat recov. , as documented in the manuals. That way, if it goes wrong, you can turn round to Symantec and say ..." I did as described in the manuals, using a supported method".
I apologise in advance for my views, I see from your very reasonable comments that you are not looking to take short cuts, and are slightly backed into a corner. But speaking, 'on average' from the systems I see that are often very onwell, it is no surprise when we find a short cut has been taken at some point.
Martin