Try unchecking and checking back setting (with apply after each action). There is a workflow in docs about what gets requested when, but I would expect NW would use tape ready to be recycled in library from another pool before than tape from the same pool but outside library. If that would be problem I would consider that as design issue and perhaps you could also check that.
If none of that works I would suggest to move to 7.1.4 at least and open that with support in case it doesn't work. It should be pretty straightforward job to reproduce it if this is standard issue.
Well, that should work AFAIK so it could be some old bug... I did use that for some time in 7.2.x and 7.3.x and it worked fine for me (also under HPUX).
It works for me on a bunch of other servers with the same setup (NW7.1.3 and HPUX11.11) but with fewer pools and less complicated pool setups. I tried creating a brand new pool on this server just for testing, and a tape did get recycled into it. But for existing pools it doesn't work. I can't seem to figure this one out.
Problem is with a number of pools that only recycle to themselves, not to other pools. A new test pool that was created worked fine, a tape was recycled to it. It is as if NW is not considering recycling INTO these pools, but is recycling just fine out of them. I did some more testing, and on one of the attempts, NW suggested labeling a tape that was in the same pool and was recyclable, but was not in the library and had it's location field set to "Offsite". For Archive pools, it doesn't suggest relabeling anything, just waits for a volume.
And perhaps silly question, did you try to restart NW? Perhaps its logic needs kick or two... Because tape did recycle to new pool problems obviously seems to be in recycle from relation from pool B according what has been discussed here... so perhaps unselecting recycle from and applying setting and then selecting it again might wake up NW too.
Unbelievable, but unchecking and checking back "Recycle To/From Other Pools" worked. I would love to see a logical explanation for this, but for now I'll settle for one less headache
ble1
6 Operator
•
14354 Posts
•
56186 Points
279
0
Posted September 5th, 2007 13:00
If none of that works I would suggest to move to 7.1.4 at least and open that with support in case it doesn't work. It should be pretty straightforward job to reproduce it if this is standard issue.