11-04-2016 12:53 AM
Windows Master 7.6.0.4
Windows Media 7.6.0.4
Windows 2008 R2 SP1
Duplication from LTO1(Using LTO3 Drive) Tape to LTO4(using LTO4 Drive) tape failling with below error message.
I troubleshooted and found that it is failling it only on 2 drives. When I made those drives down it runs fine the same job successfull on other drives.
I replaced these drives but I am still having the same issue.
0/17/2016 11:14:40 PM - positioned B14911; position time: 0:00:00
10/17/2016 11:15:40 PM - Critical bptm(pid=27488) Amount of data read (610432) does not match the fragment kbytes (1056128) for backup id XXX_1221131992, copy 1, fragment 37
10/17/2016 11:15:45 PM - Error bpduplicate(pid=25200) host master backup id XXX_1221131992 read failed, media read error (85).
10/17/2016 11:15:46 PM - Error bpduplicate(pid=25200) host master backup id XXX_1221131997 read failed, media read error (85).
10/17/2016 11:15:46 PM - Error bpduplicate(pid=25200) Duplicate of backupid XXX_1221215840 failed, media read error (85).
10/17/2016 11:15:51 PM - Error bpduplicate(pid=25200) Duplicate of backupid XXX_1221131992 failed, media read error (85).
10/17/2016 11:16:04 PM - Error bpduplicate(pid=25200) host master backupid XXX_1221131997 write failed, termination requested by administrator (150).
10/17/2016 11:16:04 PM - Error bpduplicate(pid=25200) Duplicate of backupid XXX_1221131997 failed, media read error (85).
10/17/2016 11:16:06 PM - Info bptm(pid=10128) EXITING with status 0 <----------
10/17/2016 11:16:14 PM - Error bpduplicate(pid=25200) Status = no images were successfully processed.
10/17/2016 11:16:14 PM - end Duplicate; elapsed time: 1:01:24
BPTM with verbose 5
23:15:40.710 [27488.6800] <4> report_throughput: VBRT 1 27488 4 1 BAY_Legacy_DLT_Drive02_L2 B14911 0 2 0 1 610432 589056 1199488 (mpxrestore.c.1497)
23:15:40.710 [27488.6800] <2> set_job_details: Tfile (4439671): LOG 1476771340 32 bptm 27488 Amount of data read (610432) does not match the fragment kbytes (1056128) for backup id XXX_1221131992, copy 1, fragment 37
23:15:40.710 [27488.6800] <2> send_job_file: job ID 4439671, ftype = 3 msg len = 163, msg = LOG 1476771340 32 bptm 27488 Amount of data read (610432) does not match the fragment kbytes (1056128) for backup id XXX_1221131992, copy 1, fragment 37
23:15:40.710 [27488.6800] <32> mpx_read_data: Amount of data read (610432) does not match the fragment kbytes (1056128) for backup id XXX_1221131992, copy 1, fragment 37
Solved! Go to Solution.
11-16-2016 12:25 AM
This is solved. The problem was with the IO blade in the library. These were the only 2 drives on that IO blade, when we replaced the IO blade everything started working as expected and I am not getting fragment errors.
11-04-2016 01:18 AM
Can you double-check tape drivers used in Windows Device Manager for all LTO3 tape drives?
Can you check output of 'tpautoconf -t' to see if all LTO3 drives are on the same firmware?
Are all LTO3 drives connected to same or different HBA?
Can you confirm that all settings and drivers for hba's are the same?
11-04-2016 01:52 AM
Can you double-check tape drivers used in Windows Device Manager for all LTO3 tape drives?
Yes it shows it fine in the device manager. Shows fine in the scan output as well.
Can you check output of 'tpautoconf -t' to see if all LTO3 drives are on the same firmware?
All the IBM drives are on the same firmware level 93GM
Are all LTO3 drives connected to same or different HBA? These are 10 drives shared amoung 1 master and 4 media servers
Can you confirm that all settings and drivers for hba's are the same? yes they should but let me cross verify.
11-05-2016 08:19 AM
Yes setting are same.
11-07-2016 01:01 AM
The 2 "failing" tape drives, are they connected to the same media server as the others ?
The values are very off the regular buffer settings, buffer setting must be the power of 2 (64K, 127K, 256K etc etc).
mount of data read (610432) does not match the fragment kbytes (1056128) for backup id XXX_1221131992, copy 1, fragment 37
11-07-2016 02:04 AM
Yes these 2 drives are connected with others. That is the data read it shows in that error, it is not the fragment size.
I checked that these were written with buffer size of 131072 in the past, 128K.
I logged a call with Quantum but they are not finding anything on the library side.
11-16-2016 12:25 AM
This is solved. The problem was with the IO blade in the library. These were the only 2 drives on that IO blade, when we replaced the IO blade everything started working as expected and I am not getting fragment errors.
11-16-2016 02:35 PM
Good find on that issue - I suspect that was a slightly difficult one to find.