I am in a similar situation. My master server (4.5) is very slow. I have
3 media servers. I am planning on building a 5.1 master in the Dev
forest and try to migrate my Prod settings over. I think it will require
me to reinstall Veritas on my 3 media servers and all 199 clients. All
are Windows servers.

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Eric
Ljungblad
Sent: Wednesday, March 09, 2005 3:12 AM
To: 'Ed Wilts '; 'Daniel Lupton '
Cc: 'brounb AT adi-limited DOT com '; 'veritas-bu AT mailman.eng.auburn DOT edu 
'
Subject: RE: [Veritas-bu] Master migration to new server. 2 masters to
consolidate to one.

Basically VMGLOB should work with trial and error - 
VMGLOB does work but it's tuff - set global database host and volume
data
base host does work,  set gdb and vdb to the new name, setgdb_host
vdb_host
make sure to take off-line all other existing master/media servers and
remove them from the domain, put them in a work group  boot the old
systems,
Veritas sees these old systems and starts acting wierd,  Not sure if the
names match but it is set global database host and set volume database
host,
then run a database backup, catalog backup and check the status, reboot
the
master sever vmglob does eventually work with rough and tuff trials.

-----Original Message-----
From: Ed Wilts
To: Daniel Lupton
Cc: brounb AT adi-limited DOT com; veritas-bu AT mailman.eng.auburn DOT edu
Sent: 3/8/2005 5:07 PM
Subject: Re: [Veritas-bu] Master migration to new server. 2 masters to
consolidate to one.

On Wed, Mar 09, 2005 at 11:55:27AM +1100, Daniel Lupton wrote:
> I am not sure about the name change but migrating the catalogue from
UNIX
> to Windows is not easy if  possible at all. I have attempted this the
other
> way round (Windows to Linux). We tried to import the catalogue from
the
> catalogue backup (we knew it would not work but thought we would give
it a
> shot). We tried to convert the binary image and media catalogue to
ASCII,
> ftp them to the new server and then import them into the new server.
This
> failed because apparently the media database does not convert from
binary
> to ASCII. The only solution for us is to import each tape manually.

We successfully migrated our master from Windows to Solaris back on 3.4.
The catalog was all ASCII but it was still a very complex problem that
took us a couple of attempts before we got it right.  It's not for the
faint of heart and I can see why Veritas doesn't support it.  It's not
just the catalog that is fun to migrate - it's also the policies, the
media database, etc.

> As for changing the name, we will be addressing this in the next week
or so
> in our test environment as we change the new name of our NetBackup
server
> due to a new naming convention. If you find any tips/info please let
us all
> know!

I don't think is easy either...  The easiest thing to do is tell whoever
you were sharing the name with before that you have to keep it and make
them take a new name.  Yes, I know that doesn't always work...

-- 
Ed Wilts, Mounds View, MN, USA
mailto:ewilts AT ewilts DOT org
_______________________________________________
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