• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Drive sharing between NDMP and TSM Server

kvwar

ADSM.ORG Member
Joined
Apr 4, 2009
Messages
51
Reaction score
0
Points
0
I need assistance with device sharing between NetApp controllers and the TSM server.
This is the description of the setup.
ADIC Scalar library wit 4 LTO4 drives.
The library is connected to a brocade FC switch.
I have 2 NetApp controllers connected to the same switch.
The TSM server (6.2 on Windows 2003) is able to see the library and drives fine.
I loaded the IBM TSM drivers for the library.
I am able to perform local backups just fine to the drives.
Now the requirement is to be able to backup the NetApp NAS volumes using NDMP.
The requirement to use the local path and not a remote NDMP.
Hence I added the datamover and created 4 drive paths from the NetApp controller using rst0a 1a 2a 3a.
I pointed all the drives to the local library (LB2.1.0.2)
When I perform backup of a volume I get IO Errors with a message that the drive is not in a state to be used.
Please let me know if I am missing something.


Error message that I am getting is as follows:


ANR8300E I/O error on library LB2.1.0.2 (OP=8401C058, CC=207, KEY=05, ASC=21,
ASCQ=01,
SENSE= 70.00.05.00.00.00.00.0A.00.00.00.00.21.01.00.CF.00.06.,
Description=Device is not in a state capable of performing request). Refer to
the &STGM; documentation on I/O error code descriptions.
ANR8945W Scratch volume mount failed 000011.
ANR8381E NAS volume 000011 could not be mounted in drive CONT1DRIVE1 (rst1a).
ANR1404W Scratch volume mount request denied - mount failed.
ANR8300E I/O error on library LB2.1.0.2 (OP=8401C058, CC=207, KEY=05, ASC=21,
ASCQ=01,
SENSE= 70.00.05.00.00.00.00.0A.00.00.00.00.21.01.00.CF.00.06.,
Description=Device is not in a state capable of performing request). Refer to
the &STGM; documentation on I/O error code descriptions.
ANR8945W Scratch volume mount failed 000012.
ANR8381E NAS volume 000012 could not be mounted in drive CONT1DRIVE2 (rst2a).
ANR1404W Scratch volume mount request denied - mount failed.
ANR8300E I/O error on library LB2.1.0.2 (OP=8401C058, CC=207, KEY=05, ASC=21,
ASCQ=01,
SENSE= 70.00.05.00.00.00.00.0A.00.00.00.00.21.01.00.CF.00.06.,
Description=Device is not in a state capable of performing request). Refer to
the &STGM; documentation on I/O error code descriptions.
ANR8945W Scratch volume mount failed 000013.
ANR8381E NAS volume 000013 could not be mounted in drive CONT1DRIVE3 (rst3a).
ANR1404W Scratch volume mount request denied - mount failed.
ANR1096E NAS Backup process 3 terminated - storage media inaccessible.
ANR0985I Process 3 for BACKUP NAS (FULL) running in the BACKGROUND completed
with completion state FAILURE at 23:08:59.






tsm: PPE-DMA-SVR3>q drive f=d


Library Name: LB2.1.0.2
Drive Name: CONT1DRIVE1
Device Type: REMOTE
On-Line: Yes
Read Formats:
Write Formats:
Element:
Drive State: EMPTY
Volume Name:
Allocated to:
WWN:
Serial Number:
Last Update by (administrator): ADMIN1
Last Update Date/Time: 06/29/2011 23:05:41
Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE


Library Name: LB2.1.0.2
Drive Name: CONT1DRIVE2
Device Type: REMOTE
On-Line: Yes
Read Formats:
Write Formats:
more... (<ENTER> to continue, 'C' to cancel)


Element:
Drive State: EMPTY
Volume Name:
Allocated to:
WWN:
Serial Number:
Last Update by (administrator): ADMIN1
Last Update Date/Time: 06/29/2011 23:05:40
Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE


Library Name: LB2.1.0.2
Drive Name: CONT1DRIVE3
Device Type: REMOTE
On-Line: Yes
Read Formats:
Write Formats:
Element:
Drive State: EMPTY
Volume Name:
Allocated to:
WWN:
Serial Number:
Last Update by (administrator): ADMIN1
more... (<ENTER> to continue, 'C' to cancel)


Last Update Date/Time: 06/29/2011 23:05:34
Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE


Library Name: LB2.1.0.2
Drive Name: CONT1DRIVE4
Device Type: REMOTE
On-Line: Yes
Read Formats:
Write Formats:
Element:
Drive State: EMPTY
Volume Name:
Allocated to:
WWN:
Serial Number:
Last Update by (administrator): ADMIN1
Last Update Date/Time: 06/29/2011 23:05:24
Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE


Library Name: LB2.1.0.2
Drive Name: MT0.0.0.2
Device Type: LTO
On-Line: Yes
more... (<ENTER> to continue, 'C' to cancel)


Read Formats: ULTRIUM4C,ULTRIUM4,ULTRIUM3C,ULT-
RIUM3,ULTRIUM2C,ULTRIUM2
Write Formats: ULTRIUM4C,ULTRIUM4,ULTRIUM3C,ULT-
RIUM3
Element: 257
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 500308C09D04D09C
Serial Number: 1310044557
Last Update by (administrator): ADMIN1
Last Update Date/Time: 06/29/2011 21:56:43
Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE


Library Name: LB2.1.0.2
Drive Name: MT1.0.0.2
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM4C,ULTRIUM4,ULTRIUM3C,ULT-
RIUM3,ULTRIUM2C,ULTRIUM2
Write Formats: ULTRIUM4C,ULTRIUM4,ULTRIUM3C,ULT-
RIUM3
Element: 258
more... (<ENTER> to continue, 'C' to cancel)


Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 500308C09D04D000
Serial Number: 1310044566
Last Update by (administrator): ADMIN1
Last Update Date/Time: 06/29/2011 21:56:43
Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE


Library Name: LB2.1.0.2
Drive Name: MT2.0.0.2
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM4C,ULTRIUM4,ULTRIUM3C,ULT-
RIUM3,ULTRIUM2C,ULTRIUM2
Write Formats: ULTRIUM4C,ULTRIUM4,ULTRIUM3C,ULT-
RIUM3
Element: 259
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 500308C09D04D004
Serial Number: 1310012198
more... (<ENTER> to continue, 'C' to cancel)


Last Update by (administrator): ADMIN1
Last Update Date/Time: 06/29/2011 21:56:43
Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE


Library Name: LB2.1.0.2
Drive Name: MT3.0.0.2
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM4C,ULTRIUM4,ULTRIUM3C,ULT-
RIUM3,ULTRIUM2C,ULTRIUM2
Write Formats: ULTRIUM4C,ULTRIUM4,ULTRIUM3C,ULT-
RIUM3
Element: 256
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 500308C09D04D098
Serial Number: 1310044657
Last Update by (administrator): ADMIN1
Last Update Date/Time: 06/29/2011 21:56:42
Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE
 

chad_small

ADSM.ORG Moderator
Joined
Dec 17, 2002
Messages
2,262
Reaction score
52
Points
0
Location
Gilbert, AZ
Website
www.tsmadmin.com
Try cycling the SAN switch that the NAS is attached to. I had this happen and it was the switch in the i2000 library we were using.
 

TomstaDSM

Newcomer
Joined
Dec 4, 2008
Messages
1
Reaction score
0
Points
0
Location
Tucson
I had this issue earlier today caused by the element being set to AUTODETECT. After explicitly setting the element numbers in the drive definitions, everything worked. It looks like the element value is empty on the drives you're trying to use so if you're still having issues you can try that. Best of luck!
 

Hema

ADSM.ORG Senior Member
Joined
Sep 21, 2006
Messages
343
Reaction score
9
Points
0
Location
India
If I remember, I rebooted the server(operating system) to fix this issue, as I could not fix this, I had to go for reboot finally.
 

inestler

ADSM.ORG Senior Member
Joined
Mar 12, 2007
Messages
159
Reaction score
8
Points
0
Location
europe
I suppose your library is a shared SCSI device. You can't use the local device path of the TSM-Server. you have to define the path from the data mover to the drive with the decice name like rst0a
 

blackram

Newcomer
Joined
Jan 30, 2010
Messages
1
Reaction score
0
Points
0
I had this issue earlier today caused by the element being set to AUTODETECT. After explicitly setting the element numbers in the drive definitions, everything worked. It looks like the element value is empty on the drives you're trying to use so if you're still having issues you can try that. Best of luck!

TomstaDSM, your tip helped me solve my problem, I was exactly the failure described in this post, was to define the element number and the backups via NDMP started to run normally.
Thank you for your help ... was of great value.
Sorry flaws in the text, my english is pessimo and used the google translator to help me post. rs
\ o / \ o / \ o / \ o / \ o / \ o / \ o / \ o / \ o / \ o / \ o /
 

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 22 19.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 67 59.3%
  • Let's be formal and just say Spectrum Protect

    Votes: 15 13.3%
  • Other (please comement)

    Votes: 9 8.0%

Forum statistics

Threads
31,841
Messages
134,915
Members
21,814
Latest member
DavideGrossiTSM
Top