A little planning, and the right hardware go a long way.
I had SSA disks looped thru both machines, and made sure all my TSM stuff
was in a VG on those disks. TSM was installed on the new box equal to the
version on the old box. Move time was simply:
Shut down TSM on old box, and shutdown new box.
Unmount FS's on old box and export VG
FTP dsmserv.dsk, dsmserv.opt, vol history, and device.conf to new box
Move scsi cables for tape drives to new box
Redirect DNS to new box
Boot new box, importVG and mount FS.
Start TSM on new box
Total TSM outage: 30 mins
Al Barth
Zurich Scudder Investments
Ray Pratts
<rpratts@SWBE To: ADSM-L AT VM.MARIST DOT EDU
LL.NET> cc:
Sent by: Subject: Re: Urgent!!!
transferring adsm server into new machine
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MA
RIST.EDU>
04/06/01
09:56 AM
Please
respond to
"ADSM: Dist
Stor Manager"
I've had to do this several times. The only other consideration is any
storage
pools containing disk volume. I've found that the easiest way to handle
these
have been to move the data to a tape storage pool.
The documentation for the dsmserv command is in Appendix A of the Tivoli
Storage
Manager Administrator's Reference for both Windows and AIX.
"Wu, Jie" wrote:
> Hi Zosi,
> I am also going to do the same this weekend, but on AIX. However
the
> procedure should be pretty much the same. These steps are what I am gonna
> take:
> 1). Configure the new machine and decide the layout of your disk
> space. For example:
> drive 1: c:\ for TSM code
> drive 2: d:\ for database and log volumes
> drive 3: e:\ for database and log mirroring
> drive 4: f:\ for stgpool on disk
> 2). install TSM to c:\
> 3). edit dsmserv.opt
> 4). dsmfmt -db d:\dbvol0 8000 (8G database)
> dsmfmt -log d:\logvol0 32 (32M log, if you use roll forward,
> you will need much more)
> 5). dsmserv format 1 d:\dbvol0 1 d:\logvol0. Now in file
dsmserv.dsk
> you should see two entries of the above database and log volumes.
> 6). copy over the devconfig and volumehistory file from the old
> machine.
> 7). define TSM tape drive and library devices. Then modify the
> devconfig file if there is any discrepency.
> 8). dsmserv restore db tod=today This command will check the
> devconfig and volumehistory files and prompt you to load the tape of the
> latest database backup into the tape drive in the library on which the
> devclass used for database backup is defined.
> 9). start the server, login as admin, define licenses, check
around.
> 10). for extra caution, do 'audit db'
>
> If someone think I missed something, please comment. By the way, where
can I
> find the exact syntax for dsmserv command? I could not find any domument
on
> it.
>
> Jie
>
> > -----Original Message-----
> > From: Zosimo Noriega (ADNOC IS&T) [SMTP:znoriega AT ADNOC DOT COM]
> > Sent: Thursday, April 05, 2001 11:37 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Urgent!!! transferring adsm server into new machine
> >
> > Hello to All,
> >
> > I need your help.
> >
> > My ADSM server (3.1.0.2.40) installed on Compac Proliant 5500 with
WinNT4
> > operating system, I want to kill this server and migrate into powerful
> > server IBM Netfinity 7100 with same operating system and version of
ADSM
> > server. Initially, i configured the new server same as the old one,
same
> > server name, ip, partitions, drives, scsi adapters, etc, in short,
> > identical in configurations.
> >
> > Please provide me a procedures in how to transfer the adsm data
including
> > the database, logs, storage volumes into that newly configured
machines?
> > Shall i install first the ADSM software from the CD? And then, export
the
> > database and copy the files (logs and volumes), remove scsi cable from
old
> > and attach to new one machine.
> >
> > Please provide a exact procedures.
> >
> > Your help is really appreciated.
> >
> > Zosi
|
