cancel
Showing results for 
Search instead for 
Did you mean: 

Backup is continuously faling with error 42

Chan_backup
Level 5

Connectivity is fine from Master to client and vice versa, NIC card settings is full duplex.
Backups are running on average spped of 850 KB/s
Master ver : 7.0.1
Client ver :6.5.4
Client : PC-x64, WindowsXP

Dec 23, 2010 3:46:14 AM - requesting resource Storage_Unit_Group_Vdrives_LoadBalancing
Dec 23, 2010 3:46:14 AM - requesting resource XXXXXXX.NBU_CLIENT.MAXJOBS.YYYYYYYYY
Dec 23, 2010 3:46:14 AM - requesting resource XXXXXXX.NBU_POLICY.MAXJOBS.win_prod_prjapp
Dec 23, 2010 3:46:15 AM - granted resource  XXXXXXX.NBU_CLIENT.MAXJOBS.YYYYYYYYY
Dec 23, 2010 3:46:15 AM - granted resource  XXXXXXX.NBU_POLICY.MAXJOBS.win_prod_prjapp
Dec 23, 2010 3:46:15 AM - granted resource  TL0534
Dec 23, 2010 3:46:15 AM - granted resource  HP.ULTRIUM4-SCSI.008
Dec 23, 2010 3:46:15 AM - granted resource  XXXXXXX-hcart-robot-tld-0
Dec 23, 2010 3:46:15 AM - estimated 0 kbytes needed
Dec 23, 2010 3:46:17 AM - connecting
Dec 23, 2010 3:46:17 AM - connected; connect time: 0:00:00
Dec 23, 2010 3:46:17 AM - begin writing
Dec 23, 2010 3:46:42 AM - Warning bpbrm (pid=26849) from client YYYYYYYYY: WRN - can't open directory: System State:\Task Scheduler Writer (WIN32 536935992: Unknown error)
Dec 23, 2010 3:46:42 AM - Error bpbrm (pid=26849) from client YYYYYYYYY: ERR - Error encountered while attempting to get additional files for System State:\
Dec 23, 2010 3:46:42 AM - Warning bpbrm (pid=26849) from client YYYYYYYYY: WRN - can't open directory: System State:\VSS Metadata Store Writer (WIN32 536935992: Unknown error)
Dec 23, 2010 3:46:42 AM - Warning bpbrm (pid=26849) from client YYYYYYYYY: WRN - can't open directory: System State:\Performance Counters Writer (WIN32 536935992: Unknown error)
Dec 23, 2010 4:44:12 AM - Error bptm (pid=26835) system call failed - Connection reset by peer (at child.c.1296)
Dec 23, 2010 4:44:12 AM - Error bptm (pid=26835) unable to perform read from client socket, connection may have been broken
Dec 23, 2010 4:44:12 AM - Error bpbrm (pid=26849) socket read failed: errno = 131 - Connection reset by peer
Dec 23, 2010 4:44:12 AM - Error bpbrm (pid=26849) could not send server status message
Dec 23, 2010 4:44:12 AM - end writing; write time: 0:57:55
network read failed  (42)

how to resolve this error.

1 ACCEPTED SOLUTION

Accepted Solutions

Rajesh_s1
Level 6
Certified

HI Chan,

From the log it states that you are facing issue with system state . Verify the backup by selecting any other drive path or some other and check whether you are able to backup or not .

For system state backup issue in the client run from the command mode and check

"vssadmin list writers " , whether all the vss writers are stable or not . If any of the VSS writers are failed mean then syatem state backup will not work .

For to make VSS writers stable you may need to restart the client machine ..

 

Regards,

raj

 

 

View solution in original post

3 REPLIES 3

USMAN_ALI
Level 3
Partner

Check this TN , if it can help you .....

 

http://www.symantec.com/business/support/index?page=content&id=TECH71846

 

Thanks,

Usman

 

 

 

Rajesh_s1
Level 6
Certified

HI Chan,

From the log it states that you are facing issue with system state . Verify the backup by selecting any other drive path or some other and check whether you are able to backup or not .

For system state backup issue in the client run from the command mode and check

"vssadmin list writers " , whether all the vss writers are stable or not . If any of the VSS writers are failed mean then syatem state backup will not work .

For to make VSS writers stable you may need to restart the client machine ..

 

Regards,

raj

 

 

Marianne
Level 6
Partner    VIP    Accredited Certified

Is it only System_State backup that's failing or filesystem as well?