Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
media manager - system error occurred(174)
- Thread starter 1781
- Start date
Hi, below is what you need. Read very carefully, as the actual resolution for you might be different - ie different tape drives etc etc - this workaround was for status 174 and/or status 84......
Regards
Richard
Changed the below line in /kernel/drv/st.conf . This setting is supposed to stop backups failing with status 174 - 'log.113001:20:06:22 [22807] <16> write_data: write of 32768 bytes indicated only 1 bytes were written, errno = 0'. This error is recorded in log files in bptm directory.
- changes tape drive to variable mode instead of fixed mode - errors above occur as backup reaches end of tape and cannot continue.
was - #DLT7k-data = 1,0x38,0,0xD639,4,0x82,0x83,0x84,0x85,2;
now - DLT7k-data = 1,0x38,0,0x19639,4,0x82,0x83,0x84,0x85,3;
- i can't honestly remember why i used the 0x19639 param above, i must have found it somewhere !!.
- You had best investigate this whole fix thoroughly. But at least it gives you a major clue as to why the status 174's are happening - check the bptm logfiles as stated above.. Also, see below for explanation of the st.conf fields...
Regards
Richard
Changed the below line in /kernel/drv/st.conf . This setting is supposed to stop backups failing with status 174 - 'log.113001:20:06:22 [22807] <16> write_data: write of 32768 bytes indicated only 1 bytes were written, errno = 0'. This error is recorded in log files in bptm directory.
- changes tape drive to variable mode instead of fixed mode - errors above occur as backup reaches end of tape and cannot continue.
was - #DLT7k-data = 1,0x38,0,0xD639,4,0x82,0x83,0x84,0x85,2;
now - DLT7k-data = 1,0x38,0,0x19639,4,0x82,0x83,0x84,0x85,3;
- i can't honestly remember why i used the 0x19639 param above, i must have found it somewhere !!.
- You had best investigate this whole fix thoroughly. But at least it gives you a major clue as to why the status 174's are happening - check the bptm logfiles as stated above.. Also, see below for explanation of the st.conf fields...
- Thread starter
- #3
Oddly, DLT drives write in variable length mode by default!
Although defining it does add scsi reserve/release for SSO environments and the biggie- hardware compression.
Check the messages file for hardware errors when you see a status 84 write error
There's usually another error leading up to the 174-
mkdir
/usr/openv/netbackup/logs/bpcd
on the master server
grep on '<16>' to find the errors
Although defining it does add scsi reserve/release for SSO environments and the biggie- hardware compression.
Check the messages file for hardware errors when you see a status 84 write error
There's usually another error leading up to the 174-
mkdir
/usr/openv/netbackup/logs/bpcd
on the master server
grep on '<16>' to find the errors
- Status
Similar threads
- Locked
- Question
- Locked
- Question