In this user guide, we will discover some possible causes that might cause Netbackup error scan for device log error 20 and then provide potential recovery methods that you can try to fix the problem.
Quick and Easy PC Repair
Last published: May 27, 2021
Grades: 14 1st
This is “Issue 2: Corrupt Certification Authority (CA) Certificate” mentioned in the main CRL Troubleshooting article.
In case the CA certificate is corrupted and unreadable, the copy/will fail with the following behavior:
In the case of protection, the media server is a company with a corrupted CA certificate, copies hang after a resource request:
September 5, 2017 09:42:59 AM – Search for resource nbmedia2-hcart2-robot-tld-1. Waiting for resources.
::: The server is not connected to the media at present only to the master server, a multimedia computer: nbmedia2,
Waaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa (number): TLD (1), ID Support: N / A, the name of the reader: N / A, the name of the reader
Volume Pool: NetBackup, Storage Unit: nbmedia2-hcart2-robot-tld-1, Disk Scan Host: N/A,
Check Media Server next to Media and Device Management –> Devices –> Media Indicates that the server is generally offline, although almost all processes are running.
If the client is the subject of a corrupted CA certificate, the backup may fail with status 7625.
Sep 1, 2017 5:01:36 PM Error – bpbrm (PID = 27612) [PROXY] received status: 7660 with a message that the certificate map file could not be read.
5. Sep 2017 11:29:31 AM – error bpbrm (pid = 21674) [PROXY] Score received: Error with message 7625 SSL Restrictor. Status: 5 Message: A fatal I/O error has occurred. The SSL error string was empty
5. Sep 2017 11:29:31 AM Error; bpbrm (pid=21674) bpcd on nbclient1 exited with status 7625: Failed to activate SSL socket
5. Sep 2017 11:29:31 AM Error -bpbrm (pid = 21674) Connection host [PROXY]: nbmaster2..fqdn.com
5. Sep 2017 11:29:31 AM – Error bpbrm (pid=21674) cannot send mail because BPCD stopped on nbclient1 with status sixty-one: vnetd proxy encountered a useful error
Sep 2017 5, 11:29:31 ‚ÄĒ bpbkar (pid=0) information is complete. Location: 7625: An SSL socket connection was terminated.
Error communicating with SSL socket. (7625)
For media servers and large clients, the problem can be confirmed by running Nbcertcmd -listCACertDetails.
nbcertcmd: -listCACertDetails operation failed.
EXIT STATUS young ballerina: Failed to read file
Development overview The nbcert log file showed that the CA certificate could not be displayed,” PEM_X509_INFO_read_bio’ failed and received value // exit status thirteen.
10:23:59.973 [3436.3556] <2> Get started: nbcertcmd: NetBackup 8.1 Created: 0
10:23:59.973 [3436.<2>3556] nbcertcmd: nbcertcmd -listCACertDetails
10:24:00.098 [3436.3556] <2> nbcertcmd: Displaying information about a trusted CA…
10:24:00.098 [3436.3556] <2> getCACertPath: Certification Authority Path Certificate [C:Program FilesVeritasNetBackupvarwebtruststorecacert.pem]
10:24:00.098 [3436.3556] <2> DisplayTrustedCADDetails: Certificate access successful
10:24:00.098 [3436.3556] DisplayTrustedCADDetails: <2> BIO created successfully
10:24:00.098 [3436.3556] <16> displaytrustedcadetails: PEM_X509_INFO_read_bio could not be executed
10:24:00.098 [3436.3556] <16> nbcertcmd: DisplayTrustedCADetails failed. return value = 13
10:24:00.098 [3436.3556] <2> nbcertcmd: EXIT STATUS 13: Failed to carefully read file
Another symptom of this problem is that bptestbpcd returns an error. 7625:Click here to download the software that will fix common PC problems.