This isn't quite right.
When adsm comes up, it looks in dsmserv.dsk to find its data base.
If you are doing a restore, ADSM looks in the devconfig file to locate its
tape devices, and looks in the volhistory file to find the last good backup
copy.
So it depends on whether you are planning to do the move by restoring the
data base to new disk on the server, or by physically recabling the old disk
to the new server and importing the volume groups.
If you are going to move the data base by restoring it, ADSM will use the
volhistory file to locate the last good backup, and restore it to the new
data base on your new server. In this case the data base and log on your
new server must be AT LEAST AS LARGE as your old ones, not exactly the same
size..
Regarding the disk storage pools, I have always just deleted them from the
data base after the restore, and redefined them after the dsmfmt. You don't
need them to be correct when the server first comes up, like you do for the
db and log.
> -----Original Message-----
> From: Tom Haddad [SMTP:thaddad AT COLUMBIAENERGYGROUP DOT COM]
> Sent: Thursday, August 12, 1999 2:26 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: ADSM server migration
>
> I received some notes show serveral way to migrate from on ADSM server to
> another (AIX) .. I am documenting steps similar. Your notes were very
> helpful
> and I have included some of them. Heres my last draft. Comments?
> My questions are:
> 1. If I copy dsmserv.dsk from the old server, the database restore process
> on
> the new server will use it to know where (and how many volumes) my db and
> rlog
> reside. Will the database restore look for dsmserv.dsk to do a
> successful
> restore? if so must my new database be allocated to the EXACT same size as
> the
> old one.
> 2. The database houses the definitions for disk storage pools. When
> allocating
> them (DSMFMT), must they also be the same size as my old server?
>
>
> On current server
>
> Stop all client sessions/disable logins.
>
> Empty all disk storage pools to tape.
>
> Produce final(full) database backup.
>
> Copy these files to the new server.
> /etc/filesystems
> /etc/hosts
> /.rshosts
> /usr/lpp/adsmserv/bin/dsmserv.dsk
> /etc/ibmat1.conf
> /usr/lpp/adsmserv/bin/volhist.bk1
> /usr/lpp/adsmserv/bin/devconfig.bk1
> /usr/lpp/adsmserv/bin/dsmserv.opt
> /usr/lpp/adsm/bin/dsm.opt
> /usr/lpp/adsm/bin/dsm.sys
>
> Shutdown ADSM (halt)
> Shutdown AIX (Shutdown )F)
> Unconnect all SCSI tape hardware (note: reconnect to new server in same
> order)
>
>
> On new server
> Install ADSM to current server level
> Atape support is current
> Microcode levels are current
> Allocate database, rlog and disk pools (DSMFMT(same allocations as
> the old??).
> Reconnect all tape hardware
> Verify that configuration files from old server have been copied.
> Restore the ADSM database
> Start ADSM. (ADSM will read dsmserv.dsk to get locations of db and
> rlog volumes)
> Query db and rlog to verify allocation.
> From database, ADSM will get stgpool, device, library, drive
> definitions. (same as old server)
> Test client work (backup,restore).
> Test migration.
|
