01-25-2019 07:54 AM
Backup is failing of al the servr with erro code 42 even after retriger its failing with error 42 but after reboot of master and media server its working fibe
its happening atleast once in a month
error code: network read failed (42)
01-28-2019 02:22 AM
Please tell us which NBU version and OS on Master and Media server.
Have you perhaps checked for updated firmware/drivers for the NICs in the Master/Media server?
Do you have bptm and bpbrm logging enabled (level 3) on media server?
01-29-2019 09:03 AM
@MarianneBelow is teh details
Please tell us which NBU version and OS on Master and Media server.
NBU Version: 8.1.1
OS (Media) :Windows Server 2012 R2 Standard
OS (Master) :Windows Server 2012 R2 Standard
Have you perhaps checked for updated firmware/drivers for the NICs in the Master/Media server?
, firmware versions
Master server………………..2.0(8g)
Media server………………..3.0(3a)
Do you have bptm and bpbrm logging enabled (level 3) on media server?
yes, i found entries for both belwo si the path
D:\VERITAS\NetBackup\logs\bpbrm
D:\VERITAS\NetBackup\logs\bptm
01-29-2019 12:03 PM
Ranjit,
Can you upload your bptm and bpbrm logs so that we can take a look at them.
02-01-2019 07:20 AM - edited 02-01-2019 07:21 AM
02-04-2019 09:09 AM
Take a look at your vnetd logs and attach if you can.
I see this in the logs you attached.
03:02:32.437 [6480.2788] <16> dump_proxy_info: statusmsg: The proxy protocol has been violated. The remote connector of connection ([local] [AF_INET:[10.195.132.147]:49837] -- [remote] [AF_INET:[10.195.132.146]:1556]) is not correctly using the proxy., nbu status = 7647, severity = 2, Additional Message: [PROXY] Encountered error (CERT_PROTOCOL_READING_JSON_LENGTH) while processing(CertProtocol)., nbu status = 2, severity = 1
vnetd log info - https://www.veritas.com/support/en_US/doc/15179611-127304775-0/v127651106-127304775
02-05-2019 01:48 AM
The level 5 logs are massive amd covers only a small period -
bptm between 03:02 and 03:04.
bpbrm between 02:06 and 03:07.
You really only need maximum logging levels if you want to log a Support call with Veritas and prepared to upload ALL logs that covers the start and end of at least one failing job.
This is how failures are tracked through the logs:
You will see PIDs for bpbrm and bptm in Job Details.
You now need to locate those PIDs in the relevant logs and extract all entries for those PIDs (or the Support engineer will do that if Job Details is supplied along with all logs).
We can see in bpbrm log that a backup job started at 02:06 :
02:06:31.829 [6688.5124] <2> set_job_details: Tfile (2190416): LOG 1548093991 4 bpbrm 6688 MCDCSFLNX113 is the host to backup data from
So, if we follow PID 6688 in this log, it seems that this job completed successfully one minute later:
02:07:41.272 [6688.5124] <2> send_job_file: job ID 2190416, ftype = 3 msg len = 99, msg = LOG 1548094061 4 bpbkar32 8027 done. status: 0: the requested operation was successfully completed
None of this appears in bptm log supplied, because this log is for a different period.
The errors that we see in bptm (PID 5572) is possibly a 'red herring' because the job that is associated with bptm PID 5572 has actually completed successfully:
03:03:56.765 [5572.6464] <4> write_backup: successfully wrote backup id mcdcsfdapp4129_1548097263, copy 1, fragment 1, 150432 Kbytes at 9337.803 Kbytes/sec
03:03:57.124 [5572.6464] <2> send_job_file: job ID 2190656, ftype = 3 msg len = 61, msg = LOG 1548097437 4 bptm 5572 EXITING with status 0 <----------
If you intend loggin a Support call with Veritas, please keep all logs at max level, but then you need to gather all logs for a failed backup to submit to Veritas.
If you would like this community to assist, please drop logging level to 3.
Select a failed job in Activity Monitor, post all text in Job Details, then copy the relevant bptm and bpbrm logs that contains the relevant PIDs from start to end of job.
02-05-2019 02:47 AM
@Ranjit1 wrote:
, firmware versions
Master server………………..2.0(8g)
Media server………………..3.0(3a)
If those are firmware versions for the same make/model NIC, maybe consider updating fimware and drivers to latest levels on master and media server?