** Statuscode 174 ** 1

[HLui]

Hi !

Server :
- Solaris 8 on station 20
- SunStoredge L 1000
- Netbackup Enterprise Server 5.0

Client :
- any PC-Clients
- Windows XP / 2000 etc.
- Client Software 4.5 or 5.0

Problem :
Since 2-3 weeks i have on any clients, not always the same, statuscode 174 ( media manager - system error occurred ).

Statusmessage -->
------------------------------------------------
15.03.2005 04:57:47 - started process bpbrm (23251)
15.03.2005 04:57:47 - connecting
15.03.2005 04:57:48 - connected; connect time: 00:00:01
15.03.2005 04:57:50 - started process bptm (23253)
15.03.2005 04:57:55 - mounted
15.03.2005 04:57:55 - positioning MAR510 to file 3
15.03.2005 04:58:06 - positioned MAR510; position time: 00:00:11
15.03.2005 04:58:06 - begin writing
15.03.2005 06:39:42 - mounting MAR515
15.03.2005 06:42:12 - mounted; mount time: 00:02:30
15.03.2005 06:42:14 - positioning MAR515 to file 1
15.03.2005 06:42:23 - positioned MAR515; position time: 00:00:09
15.03.2005 08:07:30 - Critical bptm(pid=23257) attempted to write 30 gigabytes, 1104885284 bytes, it is not a multiple of 512
15.03.2005 08:07:31 - end writing; write time: 03:09:25
media manager - system error occurred(174)
15.03.2005 08:09:07 - Error bpsched(pid=22123) suspending further backup attempts for client ebsfiles, policy 1a.MONAT_NT_Erg, schedule NT_FULL_Monat_Erg because it has exceeded the configured number of tries
15.03.2005 08:09:07 - Error bpsched(pid=22123) backup of client ******** exited with status 174 (media manager - system error occurred).
------------------------------------------------------------

- The used tape(s) are new.
- This is the log of the second try.
- the first try is equaly.

I have read and follow the instructions in the troubleshooting guide, but it doesn´t work.

Can anybody help ? Tips ?
What can i try ?

Greets
Holger

 

[lenski]

First thing that will help you to know is that it is not tape or tape drive related. The errors at least in our enviorment happen when for some reason the conection to the client has failed. Normally it means that the Domino server has crashed. That is that the O/S is up but that Lotus notes is no longer up. Now you may not be running Domino but the issue is likely to be the same. The conection to what ever needs backing up has failed. Why the referance to Media Manager I don't know but it has never been a media error here.

 

[HLui]

Hi Lenski !

Wrong Thread ?
I don´t use Lotus or Domino or what else !

Greets
Holger

 

[Stumpr]

Status 174 occurs when backing up Windows clients to a Gigabit interface on a SUN media server. UNIX clients do not experience the 174 error.

http://seer.support.veritas.com/docs/262860.htm

Exact Error Message
Attempt to write 8 gigabytes, 1457249836 bytes, it is not a multiple of 512

Details:
During backups, VERITAS NetBackup (tm) keeps track of the number of bytes sent to it in the backup. It pads all blocks sent to 512 bytes, so after a backup finishes, as an integrity check to make sure that all data has been received, NetBackup divides the total number of bytes by 512. If the number does not divide evenly by 512, then it is assumed that some amount of data was not received. Research has shown that the problem is most often associated with a hardware issue, (i.e. tapes, tape drive firmware, NICs), network issues, or by incorrect NetBackup binaries on the client.

Windows network cards, especially Gigabit Ethernet cards, are known to drop packets when the NIC is under high load and the driver code is not up to date. These problems have been solved with updated WINDOWS NIC driver code.

On the Windows client, go to Start | Settings | Control Panel | Hardware | Device Manager | Network Adapter | Properties to find the NIC vendor and driver version
Download and install the latest drivers from the NIC vendor Web site, not from Microsoft

Ensure the media server's Gigabit card is not in a 33MHz system slot. It should be in a 66MHz system slot or intermittent status 174 can result.

Use the Solaris /usr/platform/`arch -k`/sbin/prtdiag -v command to display the system I/O cards and the slots they reside in
See the details in the SUN document

http://sunsolve.sun.com/search/document.do?assetkey=1-9-41665-1

Ensure the Solaris Gigabit driver patch is up to date on the master or media server. The gigabit drivers are separate from the OS patches.

Run netstat -i to find the gigabit card type
Update it with the latest available fixes at

http://sunsolve.sun.com

Bob Stump
Incorrigible punster -- Do not incorrige

 

[lenski]

I do get 174 errors on UNIX client. As I stated it is normaly related to a problem with the Domino or Lotus notes server. Just because the Veritas documentation states a certain thing does not make it a fact. However I have just checked and the troubleshooter does list 174 as an UNIX error as well as WIN. But the point I was trying to make is that 174 can often be an non media issue. Coming from a failure of the system to comunicate with the client or agent on there. Why it gives 174 which is clearly not the correct error code is anybodys guess.

 

[Stumpr]

Just because the Veritas documentation states a certain thing does not make it a fact." Amen!

Bob Stump
Incorrigible punster -- Do not incorrige

 

[Stumpr]

I think I now have a new signature. Thanx and a tip of the hat to lenski.



Bob Stump
Just because the Veritas documentation states a certain thing does not make it a fact

 

[1781]

Question -- Is this a media server or client server?

 

[HLui]

@1781
(?)
It`s a master- and mediaserver.