Reply to Re: Migration of 338

*** Original Author:  ADSM-L @ MARIST - ** Remote User **; 11/14/96 02:03pm

>Received: from VM.MARIST.EDU by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V3R1)
>   with TCP; Thu, 14 Nov 96 14:03:44 CST
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
>   with BSMTP id 9410; Thu, 14 Nov 96 14:58:01 EST
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
> (LMail V1.2b/1.8b) with BSMTP id 0855; Thu, 14 Nov 1996 14:57:59 -0500
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8b) with NJE
>          id 8763 for ADSM-L AT VM.MARIST DOT EDU; Thu, 14 Nov 1996 14:57:56 
> -0500
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
>          V1.2b/1.8b) with BSMTP id 0839; Thu, 14 Nov 1996 14:57:56 -0500
>Received: from UBVM.cc.buffalo.edu by VM.MARIST.EDU (IBM VM SMTP V2R3) with
>          TCP; Thu, 14 Nov 96 14:57:54 EST
>Received: from UBVM.CC.BUFFALO.EDU by UBVM.cc.buffalo.edu (IBM VM SMTP V2R3)
>          with BSMTP id 8362; Thu, 14 Nov 96 14:59:34 EST
>Received: from UBVM (NJE origin TKSSTEVE@UBVM) by UBVM.CC.BUFFALO.EDU (LMail
>          V1.2a/1.8a) with BSMTP id 7273; Thu, 14 Nov 1996 14:59:34 -0500
>Message-ID:  <ADSM-L%96111414575600 AT VM.MARIST DOT EDU>
>Date:         Thu, 14 Nov 1996 14:55:34 EST
>Reply-To:     "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>Sender:       "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>From:         "Steven P. Roder" <TKSSTEVE AT UBVM.CC.BUFFALO DOT EDU>
>Organization: State University of New York at Buffalo
>Subject:      Re: Migration of 3380-3390 (VM, ADSM V1)
>To:           Multiple recipients of list ADSM-L <ADSM-L AT VM.MARIST DOT EDU>
>In-Reply-To:  Message of Thu, 14 Nov 1996 13:43:07 -0500 from
>              <zellers AT blue.vm.temple DOT edu>
>
On Thu, 14 Nov 1996 13:43:07 -0500 Terrence W. Zellers said:
>Could anyone please give me a summary of how to move a server
>with all disks on 3380's to 3390's.  We've tried export server -
>it apparently tried to copy the tapes as well.  We've combed
>the manuals, but haven't been able to put it all together: this
>"high concept" documentation is for the birds.  No high concept
>here: the '80's are going out the door; we need ADSM moved to
>the '90's with all current data intact, and we don't need to
>spend a week copying tapes with good data already on them.

I am going to be doing this also, and my plan is to define new database
and log disks on the 3390's (RAMAC, in our case), and then issue the
ADSM "delete" command against the database and log disks on the 3380's.
It is my assumption that this will cause ADSM to migrate all the data to
the 3390's.

Another way would involve issuing the dumpdb command, reinitializing the
server with the 3390 disks, and then doing a loaddb, followed by an
auditdb.

Anyone see any problems with either of these two methods?  Of course, using
method one, the server will still be available, whereas the dump/load/audit
will have the server unavailable, and this process could take several days
to complete.


Steve (unVMix Systems Programmer) Roder
(tkssteve AT ubvm.cc.buffalo DOT edu | tkssteve AT acsu.buffalo DOT edu | 
(716)645-3564 ,
   | http://ubvm.cc.buffalo.edu/~tkssteve)

*** Comments From: STEWAJM - Stewart, Mike; 11/15/96 07:55am

I've used your first option (define the new datasets, add to
ADSM, and tell him to delete the old) several times
to move the DB etc. from volume(s) to volume(s).
Works fine for me.