Unsolved
This post is more than 5 years old
2K Posts
0
722
Automatic Media Pickup
We are using NW 732 Jumbo 11, Red Hat ES4.
We faced this problem yesterday when the groups did not complete waiting for a writable volume. NW did not automatically use the appendable volume available for the pool. When we manually mounted the volume, it completed the backups.
Another observation is that for this volume, even after doing a complete inventory - the location field under volumes is blank although the location field for other volumes has the repesctive volume names.
Any suggestions.
We faced this problem yesterday when the groups did not complete waiting for a writable volume. NW did not automatically use the appendable volume available for the pool. When we manually mounted the volume, it completed the backups.
Another observation is that for this volume, even after doing a complete inventory - the location field under volumes is blank although the location field for other volumes has the repesctive volume names.
Any suggestions.
amediratta
2K Posts
0
April 5th, 2007 01:00
I am trying to check if it works after updating the location field manually.
ble1
14.3K Posts
1
April 5th, 2007 01:00
I have no idea why do you see difference between nsrjb and media db, but you could quickly workaround that by dumping volume list via nsrjb and then use that as input for mmlocate to update mdb. There were few issues with mmlocate which got fixed with 7.3.2. Is this existing install or upgraded environment?
ble1
14.3K Posts
0
April 5th, 2007 02:00
ble1
14.3K Posts
0
April 5th, 2007 02:00
ble1
14.3K Posts
0
April 5th, 2007 03:00
However this seems to be something else related to location field only. For now try to set this manually and see if this resolves issue completely. location problem I was referring to was issue with versions earlier than 7.3.2 and patched in 7.3.2 itself (no jumbo).
amediratta
2K Posts
0
April 5th, 2007 03:00
Infact, we shifted the equipment a couple of days back so we did reconfig. the jukebox as well.
We have now set the location manually & it is working fine now.
Do you think upgrading to update1 would help avoid such situations? I saw this in another pure Windows setup recently which was an upgrade from 6.x to 732 Jumbo 11. We could afford to relabel a tape there as we did not check whether the location field was in use or not.
This time the tape was index & bootstrap tape so relabelling could not even be thought of.
amediratta
2K Posts
0
April 5th, 2007 23:00