There is no reason to restore the ADSM database or DSMFMT new
storage pools if you meet these criteria:
All of the ADSM data, log and storage pool devices are on SSA disks;
those SSA disks are plugged into the new box;
all the VGs are imported;
all the filesystems mounted;
and the proper dsm configuration files are transferred from the old server
(especially the dsmserv.dsk)
If all requirements are met, the ADSM server will come right back up
without ever knowing it is on a different box. I have done this 4 times, and
it worked every time. If you have a test environment, I'd suggest you test
all the steps out there to confirm they work in your environment.
Ben
Micron Technology Inc,
Boise, ID
> -----Original Message-----
> From: Tom Haddad [mailto:thaddad AT COLUMBIAENERGYGROUP DOT COM]
> Sent: Thursday, August 12, 1999 12: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.
>
|
