Multiple Hyper || bptm system call failed - Connection reset by peer (at ../child.c.1289)

[114]

Hi,

Multiple Hyper V backups are getting failed with status code of 6: -

11 Jul, 2023 7:56:19 PM - Info nbjm (pid=14417936) starting backup job (jobid=887677) for client EMS-DB, policy VM-HYPERV-HYPVGRCLU-FULL_BKP, schedule Full_Backup
11 Jul, 2023 7:56:19 PM - estimated 0 kbytes needed
11 Jul, 2023 7:56:19 PM - Info nbjm (pid=14417936) started backup (backupid=EMS-DB_1689085579) job for client EMS-DB, policy VM-HYPERV-HYPVGRCLU-FULL_BKP, schedule Full_Backup on storage unit netback-hcart3-robot-tld-0
11 Jul, 2023 7:56:19 PM - started process bpbrm (pid=13042118)
11 Jul, 2023 7:56:43 PM - Info bpbrm (pid=13042118) EMS-DB is the host to backup data from
11 Jul, 2023 7:56:43 PM - Info bpbrm (pid=13042118) reading file list for client
11 Jul, 2023 7:56:45 PM - connecting
11 Jul, 2023 7:56:46 PM - Info bpbrm (pid=13042118) starting bpbkar on client
11 Jul, 2023 7:56:47 PM - connected; connect time: 0:00:00
11 Jul, 2023 7:56:49 PM - Info bpbkar (pid=10556) Backup started
11 Jul, 2023 7:56:49 PM - Info bpbrm (pid=13042118) bptm pid: 6094948
11 Jul, 2023 7:56:49 PM - Info bpbkar (pid=10556) archive bit processing:<enabled>
11 Jul, 2023 7:56:50 PM - Info bptm (pid=6094948) start
11 Jul, 2023 7:56:50 PM - Info bptm (pid=6094948) using 524288 data buffer size
11 Jul, 2023 7:56:50 PM - Info bptm (pid=6094948) setting receive network buffer to 262144 bytes
11 Jul, 2023 7:56:50 PM - Info bptm (pid=6094948) using 256 data buffers
11 Jul, 2023 7:56:50 PM - Info bptm (pid=6094948) start backup
11 Jul, 2023 7:56:50 PM - Info bptm (pid=6094948) backup child process is pid 16974258
11 Jul, 2023 7:56:50 PM - Info bptm (pid=6094948) Waiting for mount of media id C034L6 (copy 1) on server netback1.
11 Jul, 2023 7:56:50 PM - mounting C034L6
11 Jul, 2023 7:56:51 PM - Error bptm (pid=6094948) media manager terminated during mount of media id C034L6, possible media mount timeout
11 Jul, 2023 7:56:51 PM - Error bptm (pid=16974258) system call failed - Connection reset by peer (at ../child.c.1289)
11 Jul, 2023 7:56:52 PM - Error bptm (pid=16974258) unable to perform read from client socket, connection may have been broken
11 Jul, 2023 7:56:53 PM - Error bptm (pid=6094948) media manager terminated by parent process
11 Jul, 2023 7:56:53 PM - Error bpbrm (pid=13042118) could not send server status message to client
11 Jul, 2023 7:56:57 PM - Critical bpbrm (pid=13042118) unexpected termination of client EMS-DB
11 Jul, 2023 7:58:00 PM - Info bpbkar (pid=0) done. status: 6: the backup failed to back up the requested files
11 Jul, 2023 7:58:00 PM - end writing
the backup failed to back up the requested files  (6)

Master/ Media NBU is AIX 8.1.1
Client is windows 2012 r2

Please suggest.

[114]

Hi,

Please suggest.

[davidmoline]

Hi @114 

Given it errors so quickly, I susspect a problem with the library or drive or connection. 

I'd suggest using robtest on the media server to see if it can load and unload tapes to a drive. Then enable volmgr debugging and see what that indicates. 

Are the drives all up and available? Have you also tried restarting LTID on the media server?

Cheers
David

[inn_kam]

also check if it is tape error

do this error is coming with every job?

enable the bptm logs with verbose 5 and check

also try backup (workaround is to disable the Media Mount Timeout in the NetBackup Master Server Properties)

u r using very old version

upgrade to latest version for the whole netbackup environment

.

[meuhassan]

The error message "the backup failed to back up the requested files (6)" indicates that the backup was unable to complete successfully. The most likely cause of this error is a network issue between the media server and the client. This could be due to a problem with the network connection, the firewall, or the routing.

Another possible cause of this error is a problem with the media itself. The media could be corrupt or damaged, or it could be full.

To troubleshoot this issue, you can try the following steps:

1. Check the network connection between the media server and the client. Make sure that the network is up and running, and that there are no firewall rules that are blocking the traffic.
2. Check the routing between the media server and the client. Make sure that the routing is correct, and that the client can reach the media server.
3. Check the media itself. Make sure that the media is not corrupt or damaged, and that it is not full.

If you have tried all of these steps and the issue is still occurring, you may need to contact Veritas support for further assistance.

Here are some additional things to keep in mind:

• The error message "the backup failed to back up the requested files (6)" can also be caused by other issues, such as a problem with the backup policy or the client configuration.
• If you are using a proxy server, make sure that the proxy server is configured correctly.
• If you are using a firewall, make sure that the firewall is configured to allow traffic for the NetBackup client.

I hope this helps! Let me know if you have any other questions.