Someone else shared with me offline a tested method for converting the
server from unix to windows or windows to unix. I'd like to drop my
idea (the unix2dos version) and start discussing this idea. This one
has actually been used successfully, but the person in question request
anonymity.
So, ASSUMING THE MASTER SERVER NAME DOESN'T CHANGE...
It goes roughly like this:
A. Copy the binary files that are OS & Endian independent. Use binary
mode ftp to copy the files from the following directories:
/usr/openv/netbackup/db/images
5.1:/usr/openv/volmgr/database/volDB
6.0:/usr/openv/db/data
B. Copy the text files that are endian independent, but need to have
proper line termination for the OS they'll be on. Use ascii mode ftp to
copy the files from the following directories:
/usr/openv/netbackup/db/class
5.1:/usr/openv/volmgr/database/poolDB
C. In 5.1, fix a file that can't be copied over.
5:1 Use tpautoconf -a to re-populate globDB
D. Do not transfer /usr/openv/netbackup/db/jobs. It is binary, but is
endian dependent, and therefore cannot make the journey from unix to
windows.
---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies
-----Original Message-----
From: Ed Wilts [mailto:ewilts AT ewilts DOT org]
Sent: Thursday, July 12, 2007 6:01 PM
To: Curtis Preston
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Converting catalog form Solaris to Windows
2003
Nice try, but I hope nobody follows the template below. Having been
heavily
involved in a Windows to Solaris migration back in 3.4, I can tell you
it's
a lot more complicated than this. If you have to ask for how to do this
migration, honestly, you don't have the skills to complete it.
The short answer is to get professional help. If you don't know what
you're
doing, you'll corrupt the works, lose backups as you revert, and
generally
create a huge mess for yourself. You've got both the image catalog and
the
volume database to deal with. You can't do one without the other.
Along with the fun stuff that Curtis documented below, you'll run into
files
that are over 2GB that unix2dos won't handle, and internal references to
the
master server name. It's non-trivial and you'll watch NBU break in
weird
and wonderful ways when you try.
When we did a *media server* rename with a Level 3 person on site (and
this
was on 6.0MP4), it still took us several hours and a call to engineering
before we gave up and left it the old name.
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:ewilts AT ewilts DOT org
I GoodSearch for Bundles Of Love:
http://www.goodsearch.com/?charityid=821118
> -----Original Message-----
> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-
> bounces AT mailman.eng.auburn DOT edu] On Behalf Of Curtis Preston
> Sent: Thursday, July 12, 2007 1:47 PM
> To: Akker Henk van den; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Converting catalog form Solaris to Windows
> 2003
>
> Back to the original question. I think the databases (Sybase/emm, etc)
> would restore just fine, but the text files would have a problem. So
> what if you just fixed the text files?
>
> Although it's unsupported, I'm thinking that it's like the scenario
> below. (Test and try at your own risk. I'm typing from memory/ideas,
> not testing.)
>
> 1. Load NBU software on the new master
> 2. Load Unix utilities on the Windows server (you're going to want
them
> anyway)
> 3. Recover the database (don't start the daemons yet)
> 4. Run a script like the following
>
> cd <openv>
> find . -print |xargs file |grep text |awk -F: '{print $1}'|while read
i
> do
> unix2dos $i >$$.$i
> mv $$.$i $i
> done
>
> Again, try at your own risk.
>
> ---
> W. Curtis Preston
> Backup Blog @ www.backupcentral.com
> VP Data Protection, GlassHouse Technologies
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
