Hi Rodrigo,
The ADSM Server-to-Server redbook
(http://www.redbooks.ibm.com/abstracts/sg245244.html) talks about issues with
moving nodes around from one server to another.
regards,
Trevor
> -----Original Message-----
> From: Laura G. Buckley [mailto:buckley AT STORSOL DOT COM]
> Sent: Saturday,23 October 1999 14:24
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: challenging server-to-server implementation !
>
>
> Hi Rodrigo,
>
> Unfortunately, the process you described for moving the node
> from server 1
> to server 2 with server-to-server virtual volumes will not
> work. This is
> because when you create the copy storage pool on server 1
> using the server
> device class (sending the data to server 2) the data is
> stored as archive
> objects on Server 2 in a filespace belonging to Server 1.
> Server 2 has no
> knowledge that this data represents a copy storage pool for
> Server 1. Server
> 1 uses a "virtual volume" to indicate the data actually
> resides on Server 2.
> Bottomline: You won't be able to create a primary stg pool
> on Server 2 and
> restore from the copy stg pool that server 1 stored on server 2.
>
> I am trying to think of an alternative solution, but haven't
> come up with
> one yet...
>
> Laura G. Buckley
> Storage Solutions Specialists, Inc.
> PO Box 51313
> Colorado Springs CO 80949-1313
> (719)531-5133, FAX (719)260-5991
> buckley AT storsol DOT com
> www.storsol.com
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On
> Behalf Of
> Rodrigo Gazzaneo
> Sent: Friday, October 22, 1999 3:52 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: challenging server-to-server implementation !
>
>
> Hi List,
>
> Challenging ... at least for me !
>
> I will be implementing a server-to-server solution, with
> a smaller site with a single 3590-B11 library and a second
> bigger with a 3494 and 4 drives.
>
> The bigger site will provide copy pool for the first one,
> as SERVER class.
>
> After some time I will be migrating some of the clients
> on site 1 to site 2. How can I achieve it ?
>
> I thought I should take these steps :
>
> 1. run backup stgpool on site 1 to sync both the pools
> 2. export node A on site 1 with no data
> 3. import node A on site 2
> 4. create a primary stgpool on site 2
> 5. restore copypool to primary stgpool
>
> Then node A4s data will be recognized in site 24s new
> primary pool. And a valid client.
>
> Is it wrong ? Will it work ?
>
> I can4t export the client with data because I have the
> infamous single drive constraint on the smaller site.
>
> Do I have other options ?
>
> best regards,
> Rodrigo
>
>
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
>
|
