ANR1405W no scratch?!I have 22 scratch types, and MAXSCRATCH=500 for this pool?!

[lullaby]

Hi all,



I have updates TSM Server 5.2.2 to 5.2.3.2 on Windows2000 Server SP4,

IBM ULTRIUM ULT3582 Library with 2 LTO3580 Drives.Connection between TSM Server computer and Library is over fiber net.

my problem seems insoluble to me..!?



I've labeled and checked in my new Ultrium2 types into my new Library one by one from entry/exit (bulk) port:



"label libvolume lb2.1.0.3 checkin=scratch search=bulk overwrite=no labelsource=barcode"



after that I have 22 scratch types in my library:

"

tsm: HEB-BKR-TSM-01_SERVER1>q libv f=d



Library Name Volume Name Status Owner Last Use Home Device Cleanings Left Media Type

Element Type

------------ ----------- ---------- ---------- --------- ------- ------ -------------- ----------

LB2.1.0.3 FBZ016L1 Scratch 4,107 LTO 387

LB2.1.0.3 FBZ017L1 Scratch 4,106 LTO 387

LB2.1.0.3 FBZ018L1 Scratch 4,103 LTO 387

LB2.1.0.3 FBZ019L1 Scratch 4,104 LTO 387

LB2.1.0.3 FBZ020L1 Scratch 4,105 LTO 387

LB2.1.0.3 FBZ021L1 Scratch 4,096 LTO 387

LB2.1.0.3 FBZ022L1 Scratch 4,099 LTO 387

LB2.1.0.3 FBZ023L1 Scratch 4,098 LTO 387

LB2.1.0.3 FBZ024L1 Scratch 4,097 LTO 387

LB2.1.0.3 FBZ025L1 Scratch 4,100 LTO 387

LB2.1.0.3 FBZ026L1 Scratch 4,101 LTO 387

LB2.1.0.3 FBZ027L1 Scratch 4,102 LTO 387

LB2.1.0.3 FBZ028L1 Scratch 4,108 LTO 387

LB2.1.0.3 FBZ029L1 Scratch 4,112 LTO 387

LB2.1.0.3 FBZ030L1 Scratch 4,113 LTO 387

LB2.1.0.3 FBZ031L1 Scratch 4,114 LTO 387

LB2.1.0.3 FBZ032L1 Scratch 4,111 LTO 387

LB2.1.0.3 FBZ033L1 Scratch 4,110 LTO 387

LB2.1.0.3 FBZ034L1 Scratch 4,115 LTO 387

LB2.1.0.3 FBZ035L1 Scratch 4,116 LTO 387

LB2.1.0.3 FBZ036L1 Scratch 4,117 LTO 387

"



my LTOPOOL1 has MAXSCRATCH ALLOWED 500 types



The big problem occurred when I've tried to make a DB backup, or when I've tried to migrate my primary storage pool to LTOPOOL ?!?

No scratch ?! But why ?!?:



"11/01/2004 15:39:32 ANR2017I Administrator ADMIN issued command: BACKUP DB

devclass=ltoclass1 type=full (SESSION: 1)

11/01/2004 15:39:32 ANR0984I Process 10 for DATABASE BACKUP started in the

BACKGROUND at 15:39:32. (SESSION: 1, PROCESS: 10)

11/01/2004 15:39:32 ANR2280I Full database backup started as process 10.

(SESSION: 1, PROCESS: 10)

11/01/2004 15:39:33 ANR1405W Scratch volume mount request denied - no scratch

volume available. (SESSION: 1, PROCESS: 10)

11/01/2004 15:39:33 ANR4578E Database backup/restore terminated - required

volume was not mounted. (SESSION: 1, PROCESS: 10)

11/01/2004 15:39:33 ANR0985I Process 10 for DATABASE BACKUP running in the

BACKGROUND completed with completion state FAILURE at

15:39:33. (SESSION: 1, PROCESS: 10)

"





thank you in advance for your help

best regards

pavel

 

[nezih]

Check your Device Class settings which defined in LB2.1.0.3

 

[lullaby]

hi all,

I find the solution thanks to Bill Colwell from ADSM mailing list.

Thank you Bill !

And here is his letter to me .I think It might be usefull for somebody else :



"

Hi Pavel,

I just went thru this too. The support center pointed me in the right direction, here is

their response.

"This is xxx xxxxx with IBM TSM Support. I am responding to you regarding PMR nnnnn.xxx. I saw what you were referring to w/the number of scratch tapes that show up in the q libvol output. I understand that this error appears to be related to the change back to standard time, but resarech of the ANR1405W error the actlog took me to the following tech doc-

DCF Document ID: 1188134 - IBM Tivoli Storage Manager: After upgrade to TSM Server 5.2.3.0 the message ANR1405W appears

Problem Desc: When using a library LTO2 and a device class configured with format=ULTRIUM2C, after an upgrade to 5.2.3.0 the following error message appears: ANR1405W Scratch volume mount request denied - no scratch volume available Even if there are scratch volumes available.

Solution: Use in the device class format=drives and the error message does not appear again.

Please update your server to reflect this change and try it to verify the fix."

If you have servers that are clients of the library managing server, do the update quickly in all servers

or you will get 100's of messages complaining about a mismatch.

Hope this helps,

Bill Colwell

"

 

[ddlldd2000]

Buddy, thanks for sharing!