Unsolved
This post is more than 5 years old
3 Posts
0
4121
Tape Device marks every tape as FULL(without free space) once you start the backup
Hello all,
I have trouble with some Tape Drives configured on NetWorker.
I have installed some storage nodes(implicit clients) on srv’s where the Tape Devices are attached. (each "srv" has attached and it uses one single device/library, with other words the devices aren't shared on multiple Storage nodes)
The Clients, Storage Node’s, Devices, Media Pools, Label Templates were installed and configured step by step correctly.
The encountered problem is present when I start a backup on the Client( that is also the Storage Node), the tape is prematurely marked as FULL..
Errors:
Emergency |
Tuesday 12:14:34 PM |
event |
media |
Continuation, Incorrect function. (Win32 error 0x1), at file 2 record 0 |
Info |
Tuesday 12:14:36 PM |
event |
media |
Suggest manually labeling a new writable volume for pool 'AU-Windows-SRV198-01AU' |
Notice |
Tuesday 12:11:17 PM |
event |
media |
NetWorker media: (Warning) AUWinSRV198AU.003 marked full prematurely. Verify possible error on the device rd=srv198-01au:\\.\Tape0, advertised capacity is 1529 GB marked full at 0 KB |
As additionally infos:
"
- I have made multiple tests with different tapes.
- Inserted new bought tapes LTO5.
- Used the Cleaning Tape for the Drive.
- Changed the Windows Tape Driver
- Made the “manually Labeling”
The HP Library and Tape Tools doesn’t report any problem when you run a scan Hardware of the Device.
From Windows the Tape Devices is correct visible and the status is “Working properly”.
The Devices and the tapes have worked fine on DataProtector…
Upgraded the driver of the device.
"
But we have encountered the same error messages.
Could you please let us know if you can help us with this problem?
Many thanks,
Stolpi
bingo.1
2.4K Posts
0
December 13th, 2016 05:00
Is this a library where you added new tape drives?
Please provide 'inquire' outputs from the server (where obviously the library is attached) and from the storage node(s).
Did you add the appropriate licenses (if needed at all)?
Stolpi
3 Posts
0
December 13th, 2016 06:00
Let's speak only about StandAlone Tape Devices, please.
The StorageNode and the Client are the same. the StandAlone Tape Devices is attached to this server.
And from the logs of the main NetWorker Server (daemon.raw):
"
nsrd NSR info 9 %s %s: %s 3 0 5 media 0 7 warning 0 91 rd=srv198-01au:\\.\Tape0 writing: Incorrect function. (Win32 error 0x1), at file 2 record 1
nsrd NSR info 9 %s %s: %s 3 0 5 media 0 7 warning 0 105 rd=srv198-01au:\\.\Tape0 writing: continuation, Incorrect function. (Win32 error 0x1), at file 2 record 0
nsrd NSR info 9 %s %s: %s 3 11 10 2932:Media 11 12 19362:Notice 49 115 9142 22 %s %s %s on %s is full 4 0 13 LTO Ultrium-5 0 4 tape 22 17 AUWinSRV198AU.005 21 24 rd=srv198-01au:\\.\Tape0
nsrd NSR info 9 %s %s: %s 3 11 10 2932:Media 11 12 19362:Notice 49 114 9143 31 %s %s %s used %s of %s capacity 5 0 13 LTO Ultrium-5 0 4 tape 22 17 AUWinSRV198AU.005 0 4 0 KB 0 7 1529 GB
nsrd NSR info 9 %s %s: %s 3 11 10 2932:Media 11 12 19362:Notice 49 226 71907 138 NetWorker media: (Warning) %s marked full prematurely. Verify possible error on the device %s, advertised capacity is %s marked full at %s 4 22 17 AUWinSRV198AU.005 21 24 rd=srv198-01au:\\.\Tape0 0 7 1529 GB 0 4 0 KB
nsrd NSR info 9 %s %s: %s 3 11 21 2944:Write completion 11 12 19362:Notice 49 65 67896 30 Writing to volume %s completed 1 22 17 AUWinSRV198AU.005
nsrd NSR info 9 %s %s: %s 3 11 10 2932:Media 11 9 2394:Info 49 108 32669 57 Suggest manually labeling a new writable %s for pool '%s' 2 0 6 volume 27 22 AU-Windows-SRV198-01AU
"
I don't understand your question about "Add a license"....
The License is loaded on the main NetWorker Server.
I don't see any error in windows, also with the application: "HP Library and Tape Tools" all the hardware is working properly.
The tapes are new, etc(i've already described all the infos in the first posting)...
Other log's aren't present...
Many thanks for your replay.
ble1
14.3K Posts
1
December 13th, 2016 12:00
Questions:
- are these new tapes or used by data protector previously? If used previously by DP, can you reinit tapes?
- normally, I would jump with gun and say driver, but you already checked that. What about HP tools? Normally, those could interfere as well so you should make sure only driver is there (and most of the time MS driver will be enough)
- the error itself states that bacic command to position after label (fn 2 fr 0) fails (normally you could reproduce this with mt command) and we see error code returned by MS subsystem (net helpmsg 1). So, which driver do you use? MS or HP? And which WinOS is that?
bingo.1
2.4K Posts
0
December 13th, 2016 12:00
Correct - you did not mention any library so far. Sorry, my fault.
Of course you must license remote devices. So dependent on your licensing scheme, you may need to add remote storage node licenses and enter them at the NW server, of course.
It looks like NW will already set the media to r/o with the first data block. Can you label a tape at all?
Does NW's tapeexercise command work?
Which version do you use at all?
bingo.1
2.4K Posts
1
December 13th, 2016 20:00
Another method to gather more information is to run the following command locally on the storage node:
mt -f \\.\Tape0 status
You should also run the following command locally:
tapeexer -vvvvv \\.\Tape0
Post the output for both commands.
You should also use the proper command
nsr_render_log [-S today] daemon.raw > daemon.txt
to replace all variables with their appropriate values.
Stolpi
3 Posts
0
December 21st, 2016 10:00
Hello,
The problem is SOLVED by:
Go on Devices(Main Tab) -> Click Device Folder -> Right Click on the Device(with this problem) -> Modify Device Properties -> Tab Advanced -> and At the Device Block Size -> try all the Value... from biggest to the smallest... I've set'it the Value: 64KB, and it has worked, the job has managed to write to the tape ... without making the tape in full prematurely.
Many thanks for your help, II hope that this information is useful.
Stolpi.