Unsolved
This post is more than 5 years old
14 Posts
0
857
March 31st, 2010 05:00
Volume is read only, but only 20GB used?
Hi all,
I am having a problem where my tape media has the status of read only e.g. 000037L3 (R)
When i check in the Networker GUI, under the 'Used' column is states 20GB, in the '% Used' column it states Full, but only 20GB? FYI, i am using LTO3 tapes.
Then I started to check the rest of the medias, there is also a few 'Full' medias but its usage is less than 400GB (LTO3 tapes).
Can someone explain how does Networker manages its media for backups? How did the tape became read only? And why the tapes was not fully utilised, but i was Full?
Additional Info:
Windows 2003 Std SP2
Networker 7.4.2
Dell TL2000 tape library (OEM frm IBM)
Backup to Disk then cloned to tapes
Thanks in advance!
masonb
445 Posts
0
March 31st, 2010 05:00
Jeffz,
The tape volume was most likely marked as full due to the drive reporting an I/O error while it was mounted. We assume there is something wrong with the volume and mark it as full. You can make it appendable again by changing the status via the GUI, then check to see it does not report any issues next time it is used for backup. If it reports errors again then its most likely a bad tape, otherwise just an error you can sometimes get when accessing tape drives.
Regards,
Bill Mason
Jeffz1
14 Posts
0
March 31st, 2010 05:00
Hi Bill,
Thanks for the prompt reply. Is there anywhere that Networker would log the errors? Sorry if this has been asked before, I am totally new to Networker, previously have worked with Backup Execs.
TIA
Jeffz1
14 Posts
0
March 31st, 2010 06:00
Hi Bill,
Thanks again. Will do that when i am back to my office. Its currently 9:30PM here. Will keep u posted on the result.
Regards,
Jeffz
masonb
445 Posts
0
March 31st, 2010 06:00
Jeffz,
Sure you should see something reported in the daemon.log files. If you do not "render" them you can use nsr_render_log daemon.raw > daemon.log file to get a more user friendly log file to read. There may be older logs which you have to look at - just substitute the name of the old log with daemon.raw above and change to say daemon1.log for the output.
Then search the files for your volume name and you should see an error. You could use mminfo -q volume=
Regards,
Bill Mason