Hi mark
Here the output attach ....look at destnation corect storage pool
Regards Robert
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Mark D. Rodriguez
Sent: Wednesday, August 10, 2005 9:19 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Server to Server migration question
Robert,
Could you please post the output of the following commands:
q mg standard active
q co standard active t=a f=d
Then I can see a little more clearly what might be going on.
--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.
===============================================================================
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced
Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM
and Linux Red Hat Certified Engineer, RHCE
===============================================================================
Robert Ouzen wrote:
>Hi Mark
>
>First thanks for the response ......
>
>I didn't mention before but I thought too and I made an archive copy
>group with destination I2000_SERVER1 , active archive policy correct
>too
>
>Make no sense
>
>I did before an export node from the source server to the target server
>with domain=standard and toserver=server2, he wrote correctly on a
>scratch tape under I2000_SERVER1
>
>Regards
>
>Robert
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
>Of Mark D. Rodriguez
>Sent: Wednesday, August 10, 2005 8:54 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Server to Server migration question
>
>Robert,
>
>When you are doing virtual volumes like you are doing the virtual volume on
>the target server is actually managed as an archive object.
>Therefore, I would bet that the archive copygroup for that management class is
>pointing at the diskpool. Also, it is a good practice to put server nodes for
>virtual volumes into a separate domain so as not to get them confused with
>other nodes policies. Remember that although it is using an archive copygroup
>the only attribute it cares about is the destination storage pool. Retention
>time is irrelevant since it is managed by the source server.
>
>Good luck and let us know how you made out.
>
>--
>Regards,
>Mark D. Rodriguez
>President MDR Consulting, Inc.
>
>=======================================================================
>========
>MDR Consulting
>The very best in Technical Training and Consulting.
>IBM Advanced Business Partner
>SAIR Linux and GNU Authorized Center for Education IBM Certified
>Advanced Technical Expert, CATE AIX Support and Performance Tuning,
>RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE
>=======================================================================
>========
>
>
>
>Robert Ouzen wrote:
>
>
>
>>Hi to all
>>
>>I tried to make a server to server migration here the steps I made:
>>
>> On source Server named SERVER1
>> 1. I define a server SERVER2 (target server) 2. I define a devclass
>>SERVERCLASS with device type SERVER and servername SERVER2 3. I
>>create a stg SERVER1_POOL with devclass SERVERCLASS
>>
>> On target Server named SERVER2
>>1. I define a server SERVER1 (source server) with nodename POSTBACK 2.
>>I create a nodename of type SERVER named POSTBACK 3. I add this
>>nodename to the STANDARD policy with a copypool destination named
>>I2000_SERVER1 (tape storagepool) 4. Activate the STANDARD policy
>>
>>I update my primary stg on SERVER1 (source server) named primarypool
>>with next stg SERVER1_POOL
>>
>>The migration start I see both on the source and target server activity on
>>the actlog but I got always this error message:
>>
>>08/10/2005 20:05:23 ANR0520W Transaction failed for session 23881 for node
>> POSTBACK (Windows) - storage pool DISKPOOL is not
>> defined. (SESSION: 23881)
>>
>>Why trying to store on DISKPOOL storage ???? I doubled check my STANDARD
>>policy and my copygroup is I2000_SERVER1 (I activate several times the
>>STANDARD policy and check the active policy to see that I2000_SERVER1 is
>>correct in did !!!!
>>
>>My TSM version on the source server is 5.2.4.0 Windows O.S
>>My TSM version on the target server is 5.2.4.2 AIX-RS/6000 O.S
>>
>>Any suggestion ?????
>>
>>Regards
>>Robert Ouzen
>>e-mail: rouzen AT univ.haifa.ac DOT il
>>
>>
>>
>>
>>
>
>
>
STANDARD.TXT
Description: STANDARD.TXT
|
