ADSM-L

Re: BACKUP STGPOOL or MOVE DATA Error

2006-02-09 12:37:53
Subject: Re: BACKUP STGPOOL or MOVE DATA Error
From: TSM User <tsmusr AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 9 Feb 2006 14:37:29 -0300
What it happens is that if we make move data of disc to disc, there are no
problems and does not find objects corrupt.  We already moved all the
volumes to others in disc.

 ....


On 2/9/06, L'Huillier, Denis (GTI) <denis_lhuillier AT ml DOT com> wrote:
>
> Ionocopy "on" is what you want.  The fact that you had this option "off"
> at one time, as I did, exposes you to the data corruption problem.  This
> is kind of good news since there is a PTF that can be applied to recover
> the data.  There is also a PTF available which includes a fix for the
> ANR999D errors which prompted the use of IONOCOPY in the options file in
> the first place.
>
> I recommend you contact IBM support immediately.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Gee, Norman
> Sent: Thursday, February 09, 2006 11:59 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: BACKUP STGPOOL or MOVE DATA Error
>
>
> I was first told to put in ionocopy off in my server options file to
> resolve one problem and then latter I was told to remove this option as
> it cause other problems.  When I query ionocopy option it now shows on.
> Your statement is if it is enable then remove it from your option file.
> Is 'ON' enable or disable, sorry the query shows on or off and not
> enable or disable.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> L'Huillier, Denis (GTI)
> Sent: Thursday, February 09, 2006 7:52 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: BACKUP STGPOOL or MOVE DATA Error
>
> Contact support.  I had a similar situation.  Here's the synopsis:
>
> The data is corrupt but may be recoverable via a PTF.  New storage pools
> defined with 5.3 will verify the data before moving to a different pool.
> If the data is corrupt it will not move the data so recovery efforts can
> be initiated.
>
> There is a known problem which you may be experiencing and is
> recoverable.
>
> All your disk pools should have the "verifyData=True" option setting
> which can only be viewed via "show sspool".
> If "verifyData=False" then "upd stg xxxxx VERIFYDATA=YES" should be
> issued.   This option will give you the error below instead of moving
> corrupt data to another pool.
>
> Issue "q opt ionocopy" from the server.  If this is enable remove it
> immediately from your server options file.
> --------------------------------------------------------
>
> If you are not an intended recipient of this e-mail, please notify the
> sender, delete it and do not read, act upon, print, disclose, copy, retain
> or redistribute it. Click here for important additional terms relating to
> this e-mail.     http://www.ml.com/email_terms/
> --------------------------------------------------------
>

<Prev in Thread] Current Thread [Next in Thread>