ofcourse yes..
you have 3 ways to achive this..
1) it will only work if you have good communication form the Master/media A to client C
a) check the communication of client C from Master/media A
b) add client C in one of the test policy in the Master server A
c) add the measter and media server of A entiers in client C
d) trigger the alternate clietnt restore where source client is B and destination client is C
2) using Import
ship the tapes into the Master/media B controled libraty if the images are in tape, it not in tape duplicate them into tape and shit
using import to create the catalog and do the restore
http://www.symantec.com/business/support/index?page=content&id=TECH43584
3) Recovery with out import
folllow the below T/N
http://www.symantec.com/business/support/index?page=content&id=TECH28722
taken from (https://www-secure.symantec.com/connect/forums/how-restore-data-another-master-server#comment-9221901)
if you have to run the two in parallel then i guess you have little choice but to do the following:
1. Install a new Master at the new site and use that for clients being migrated
2. Upgrade the existing Master to be the same version as the new Master
3. When you are ready to retire the old Master get the specialists in to do the catalog merge for you so that the new Master has all of your backup data.
A few things to be careful of as you go along:
1. Make sure any tape library at the new site sees tape barcodes the same as the current site (i.e. all 8 didgits or just 6 digits)
2. Make sure the barcode rules are the same
3. Do not use any new media on the new site that has the same mediaid as used on the current site
4. When you move clients across keep their names in policies the same (so if it is server.domian.com on the old site dont have it as just server on the new site)
Just the stuff that makes the catalog merge a little easier / possible without running up against any conflicts that make life difficult
Hope this helps
taken from (https://www-secure.symantec.com/connect/forums/catalog-migration-one-nbu-domain-another#comment-10050431)