Interesting, but not new. I ran into it moving a V3R7.4 server. The support person's recommendation was that I not loose my special DEVC file that I used to create the manual library needed to do the restore, just in case "I had to do it again", whatever that might have meant.
At 11:11 AM 2/6/2002 -0500, you wrote: >This is interesting. > >Someone else reported this to the list on Jan. 16 of this year, in reference >to Type=ACS libraries. (STK libraries run via ACSLS). I have included the >post below, because I saved it. > >He said also that ACS librares are no longer supported for DB restore, he >had to define the library as manual in TSM 4.2. > >Now I know for a fact this USED to work with ACS libraries, I've done it >many times. >Now YOU are reporting the same error for 3494 libraries. > >I haven't seen anything documented, but I begin to suspect this is a new >"feature" with 4.2 (or is this an anti-feature). I think we will need a >response from Tivoli to find out what is going on. > >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >----Original Message----- >From: Rolf Bogus [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, January 16, 2002 9:50 AM >To: [EMAIL PROTECTED] >Subject: Re: ACSLS Library w/TSM 4.2.1.7 and database restore > > >Hello Alex, > > > Hello, Rolf. I wasn't able to find further information about how STK >ACSLS > > libraries aren't supported during database restore. Where is this > > documented? > >we opened a PMR regarding this a couple of months ago. This PMR was closed >with the comment that the STK ACSLS libraries are not supported in TSM 4.2 >during database restores. Sorry, I cannot remember the APAR number and >cannot look into the closed PMR because it already disappeared. > >Perhaps somebody of the Tivoli server people listing here can tell us >more about it. > >Regards, >Rolf >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >-----Original Message----- >From: Ilja G. Coolen [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, February 06, 2002 3:05 AM >To: [EMAIL PROTECTED] >Subject: Re: TSM Restore Using 349X lib fails. > > >Thanks for your reply's. > But the proper atape and atldd drivers were installed of course. > Using the mtlib command showed the desired response. > > After the manual libtype restore, the system operated like it used >to. This indicated that the drivers were functioning OK. > >To be complete i put a clipping here from the message guide. This was the >message we got during the db restore. > ANR8476E Operation is not supported for the libtype of library >library name. > Explanation: The operation failed because the libtype of the library >is not supported for the operation. > System Action: The operation fails. > User Response: Use a different libtype such as MANUAL to perform the >operation. > >Any suggestions? > > > >Re: TSM Restore Using 349X lib fails. > Forum: ADSM.ORG - ADSM / TSM Mailing List Archive > Date: Feb 04, 10:26 > From: Davidson, Becky <[EMAIL PROTECTED]> > >Did you install atape and atldd? Before using tsm make sure that mtlib can >talk to it. You can test that by simply doing an mtlib -l/dev/lmcp0 -qL >This will tell you if the machine can talk to the tape library. If it can't >make sure that you can ping it and that the /etc/ibmatl.conf is configured >properly. >Good luck >Becky > >-----Original Message----- >From: Ilja G. Coolen [mailto:[EMAIL PROTECTED]] >Sent: Monday, February 04, 2002 3:14 AM >To: [EMAIL PROTECTED] >Subject: TSM Restore Using 349X lib failes. > > >Hello you guru's. > >Last weekend we did a migration to a new AIX/box with our TSM 4.2.1.9 >server. >Everthing was configured, installed. We were unable to test the 3494 library >'cause it was attached to the production environment, and we had no spare >available at the location. > >This is what we did. > >SOURCE >-------------------- >RS/6000 - S70 >AIX 4.3.3 >TSM 4.2.1.9 >1 x 3494 >7 x SCSI 3590E >1 x ESS ( 2 x Fibre Channel point to point) > > > >TARGET >------------------ >RS/6000 - H80 ( New BOX) >AIX 4.3.3 ( Cleanly Installed ) >TSM 4.2.1.9 ( Cleanly Installed ) >1 x 3494 (Moved from source) >7 x SCSI 3590E (Moved from source) >Seperate ESS ( 2 x Fibre Channel point to point) > >Library definitions: >define library libm libt=349x devi=/dev/magstar (lmcp0) >define dev 3590 devt=3590 format=drive mountl=drives >define drive libm drive dev=/dev/rmt1 > >We did these actions before on disaster recovery tests, and it worked fine >all the time. BUT NOW, we have preconfigured the whole environment, and >started a restore db. >We got the message that the library type did not support this action. We >defined all settings like we always did. >We needed to define a manual tape library to do the restore. Automated >restore db's used to work fine. >How come it doesn't work now? >Could this be a bug? >Or did we make a mistake after all? > > > >Ilja G. Coolen > > > > _____ > > >ABP / USZO >CIS / BS / TB / Storage Management >Telefoon : +31(0)45 579 7938 >Fax : +31(0)45 579 3990 >Email : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >Intranet > : Storage <http://intranet/cis_bstb/html_content/sm/index_sm.htm>; >Web > > > _____ > > >- Everybody has a photographic memory, some just don't have film. - > > > > > > > > > >Ilja G. Coolen > > > > >ABP / USZO >CIS / BS / TB / Storage Management >Telefoon: +31(0)45 579 7938 >Fax: +31(0)45 579 3990 >Email: [EMAIL PROTECTED] >Intranet >: Storage Web > > > > >- Everybody has a photographic memory, some just don't have film. -
