Nice One !! So you think if we are movind from a Windows Mater/Media
Server to Unix Master/Media Server. The process will be the same?
Assuming you have the images saved as text. Are we going to face the
problem of extra characters in the text? How do we handle that.

Thanks.

-----Original Message-----
From: Aleksandar Pantelic [mailto:v-alexpa AT corp.webtv DOT net]
Sent: Tuesday, February 18, 2003 11:12 AM
To: Fabbro, Andrew P
Cc: 'Michael E. Willard'; Veritas NBU List
Subject: Re: [Veritas-bu] Merging Catalog Databases


or you can pay me ;)
it is not that hard, 
copy all clients you want to merge from
A:/usr/openv/netbackup/db/images/<client> to
B, copy A:/usr/openv/netbackup/db/class/<classes you need> 
(i assume that the client names and classes are unique on A and B, and
that media id are
unique on A and B (if not you need to duplicate to the unique id and
merger classed by hand))
see if you need anything from A:/usr/openv/netbackup/db/config (probably
append storage_units) and bp.conf

then if you plan to move all tape drives you have on A (and A's media
servers) to B:
find all tapes on A that are in use and migrate them from A 
and all media servers that had A as a master with
bpmedia -movedb -ev <tape> -newserver B (this will migrate
/usr/openv/netbackup/db/media/mediaDB)
it is important to add B as a master on A and A's media servers anb A as
a slave (media)
server and all A's media servers on B (and restart netbackup
everywhere).
this will migrate mediaDB and also update
/usr/openv/netbackup/db/image/<client>/<images>/<image> 
(not .f file) on B; or you could use FORCE_RESTORE_MEDIA_SERVER but i
never did that.
Also new drives need to be added on B (and robots if A or its slaves
controlled robots)

If you plan to use A as a media (slave) just change bp.conf and put B as
the first(master)
server (and on all A's media servers). 

this assumes that the volume database manager is on C and that A, B and
all A's and B's
media servers point to it. if A was the volume database manager for one
or few robots
and B was the volume database manager for the other robots you can keep
A as the 
volume database manager or migrate the volDB to B. 


ap

> 
> The only process is to engage Veritas Consulting and pay for it.
> 
> Seriously - this is not supported.  In fact, you're not supposed to be
ever
> able to do it, but if you pay Veritas Consulting (and pay at VC
rates), they
> can come out and do it.
> 
> I've heard rumors of people grafting directories with images, etc. but
how
> that syncs up with what's the media, I don't know...and again, not
something
> Veritas will document so you can do it yourself.  
> 
> I just discussed this with them over the last couple weeks and that
was the
> response.  If anyone knows different, I'd love to hear about it.
> 
> 
> 
> -----Original Message-----
> From: Michael E. Willard [mailto:mwillard AT soccour DOT com] 
> Sent: Tuesday, February 18, 2003 9:29 AM
> To: Veritas NBU List
> Subject: [Veritas-bu] Merging Catalog Databases
> 
> 
> Can anyone please describe or point me to documentation regarding the
> process of merging a catalog database from <Master Server A> to
<Master
> Server B> via Master Server A's catalog backup?  How difficult is this
and
> what is the length of time to complete the process?
> 
> TIA!
> 
> Mike Willard
> Systems Engineer
> Soccour Solutions
> 972.960.0400 x422 office
> 972.960.0444      fax
> 214.680.5688      mobile
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu