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. -
