8.1.1

8 Topics

Backup Failure on Multiple Clients with Exit Status 40
I have received this case over a month ago and have been wracking the mind of my senior engineer at a solution. We appear to be at a standstill and possibly a fresh set of eyes may help. You may see that we're missing a part of the conversation in the attached logs, we've attempted to get the right logs three times. Each time we had to wait until the completion of a backup, which took a long time. Unfortunately, I cannot go back and ask for more logs from the customer, he's been patient thus far for a resolution, not for more logs...understandably so. During a meeting we saw the customer conducts a checkpoint every 7 minutes. One of his clients, bkoweb26, began to backup successfully after creating an exclusions list. Also noticed a timeout of infinity in bpbrm, see snippet. We have made suggestions and recommendations, below. Some were made, but not all. Snippet of the backup log: Mar 28, 2020 5:53:14 AM - Error bpbrm (pid=10289380) db_FLISTsend failed: network connection broken (40) Mar 28, 2020 5:53:15 AM - Info bpbrm (pid=7471230) sending message to media manager: STOP BACKUP bkoweb26_1585391368 Mar 28, 2020 5:53:17 AM - Info bpbrm (pid=7471230) media manager for backup id bkoweb26_1585391368 exited with status 150: termination requested by administrator Mar 28, 2020 5:53:17 AM - end writing; write time: 0:23:42 network connection broken (40) Snippet of Media bpbrm 00:07:52.377 [18415728.1] <2> db_getdata: timeout is 0 (infinite) 00:07:52.390 [18415728.1] <2> db_end: Need to collect reply 00:07:52.390 [18415728.1] <2> db_getdata: timeout is 0 (infinite) Environment info: Master: nmbackup01, configured on third-party, NBU version 8.1.1, Platform: AIX ver. 7.1 Media: nmbpmed05, configured on third-party server, NBU version 8.1.1, Platform AIX ver. 7.1 Clients: nmocmi02, bkoweb26 and bkoweb25 Logs attached: Clients (nmocmi02, nmsplkstore01): bpbkar Master (nmbackup01): bpbrm, bptm Media (nmbmed03, nmbpmed05): bpbrm, bptm Recommendations: Increase checkpoints to every 60min. (not done) Decrease timeouts to 7200 instead of infinite (not done). I'm thinking these areCLIENT_READ_TIMEOUT or CLIENT_CONNECT_TIMEOUT = 7200 in bp.conf Since exclusions helped one client succeed, I wondered if the test in this technote could apply to this situation:https://www.veritas.com/support/en_US/article.100003560 Check for communication related patches (tried but did not find any online) Run bppllist and bpplinfo on media. Run bpgetconfig from a failing and a successful client, to compare. (not done) Any other recommendation you may have, will be very much appreciated!
KameliaB
5 years ago Place NetBackup
3KViews
0likes
11Comments
Upgrading from Netbackup 8.1.1 to 8.2
I am in the midst of upgrading from 8.1.1 to 8.2. We have 2 Windows masters communicating through AIR SLP's. Each master is a Windows cluster. We are also using 4 Veritas 5240 appliances. What is the suggested order of upgrading the Netbackup environment (master server, media servers, appliances, clients) ?
Solved
gaapeio
5 years ago Place NetBackup
2.4KViews
0likes
3Comments
Error message in sap oracle detail log.
Error message occurs in the detail log during sap backup. What should I check? 2019.12.27오후3:42:03-Infonbjm(pid=13885)startingbackupjob(jobid=23683)forclientbxddev,policybxddev_SAP,scheduleDefault-Application-Backup 2019.12.27오후3:42:03-Infonbjm(pid=13885)requestingSTANDARD_RESOURCEresourcesfromRBforbackupjob(jobid=23683,requestid:{FE1420F4-2873-11EA-87DC-C738CC064B28}) 2019.12.27오후3:42:03-requestingresourcestu_adv_hkpbma2 2019.12.27오후3:42:03-requestingresourcehkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019.12.27오후3:42:03-requestingresourcehkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019.12.27오후3:42:04-grantedresourcehkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019.12.27오후3:42:04-grantedresourcehkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019.12.27오후3:42:04-grantedresourceMediaID=@aaaab;DiskVolume=/advanceddisk/dp1/advol;DiskPool=dp_adv_hkpbma2;Path=/advanceddisk/dp1/advol;StorageServer=hkpbma2;MediaServer=hkpbma2 2019.12.27오후3:42:04-grantedresourcestu_adv_hkpbma2 2019.12.27오후3:42:04-grantedresourceTRANSPORT 2019.12.27오후3:42:04-estimated0kbytesneeded 2019.12.27오후3:42:04-Infonbjm(pid=13885)startedbackup(backupid=bxddev_1577428924)jobforclientbxddev,policybxddev_SAP,scheduleDefault-Application-Backuponstorageunitstu_adv_hkpbma2 2019.12.27오후3:42:04-startedprocessbpbrm(pid=301944) 2019.12.27오후3:42:05-connecting 2019.12.27오후3:42:08-connected;connecttime:0:00:00 2019.12.27오후3:42:09-Infobpbrm(pid=301944)bxddevisthehosttobackupdatafrom 2019.12.27오후3:42:09-Infobpbrm(pid=301944)readingfilelistforclient 2019.12.27오후3:42:10-Infobpbrm(pid=301944)listeningforclientconnection 2019.12.27오후3:42:11-OpeningFibreTransportconnection,BackupId:bxddev_1577428924 2019.12.27오후3:42:12-Infobpbrm(pid=301944)INF-Clientreadtimeout=3600 2019.12.27오후3:42:12-Infobpbrm(pid=301944)acceptedconnectionfromclient 2019.12.27오후3:42:12-Infobpbrm(pid=301944)startbpbkaronclient 2019.12.27오후3:42:12-beginwriting 2019.12.27오후3:42:13-Infodbclient(pid=20932)Backupstarted 2019.12.27오후3:42:13-Infodbclient(pid=20884)Backupstarted 2019.12.27오후3:42:13-Infobpbrm(pid=301944)bptmpid:301952 2019.12.27오후3:42:13-Infobptm(pid=301952)start 2019.12.27오후3:42:14-Infobptm(pid=301952)using262144databuffersize 2019.12.27오후3:42:14-Infobptm(pid=301952)using16databuffers 2019.12.27오후3:42:14-Infobptm(pid=301952)USING262144databuffersizeforFT 2019.12.27오후3:42:15-Infobptm(pid=301952)startbackup 2019.12.27오후3:42:18-Errorbpbrm(pid=301944)fromclientbxddev:ERROR:V-3-20003:Cannotopen/dev/sapvg01/lvol6:Permissiondenied 2019.12.27오후3:42:28-endwriting;writetime:0:00:16 2019.12.27오후3:42:30-Infodbclient(pid=20884)bpbkarwaited133timesforemptybuffer,delayed149times 2019.12.27오후3:42:30-Infodbclient(pid=20884)done.status:0 2019.12.27오후3:42:30-Infobptm(pid=301952)waitedforfullbuffer1445times,delayed11337times 2019.12.27오후3:42:32-Infobptm(pid=301952)EXITINGwithstatus0<---------- 2019.12.27오후3:42:32-Infobpbrm(pid=301944)validatingimageforclientbxddev 2019.12.27오후3:42:32-Infodbclient(pid=20884)done.status:0:therequestedoperationwassuccessfullycompleted therequestedoperationwassuccessfullycompleted (0)
kyounYong
5 years ago Place NetBackup
992Views
0likes
1Comment
Catalog Failed to get status 2520
When trying to run a catalog backup i get (2520) Failed to get status code information. I noticed this started to happen when i had jobs running for a long time and i stop and started the netbackup services via command line. Now i get (2520) Failed to get status code information when running a catalog backup. I also have noticed that VMWare policies when run it's stuck on active and will never finish. Any assistance would be greatly appreciated.
zekebett
5 years ago Place NetBackup
1.6KViews
0likes
1Comment
Can't delete SRT in LOCKED_WRITE state on Windows Boot Server
Hi, I have more than one SRT in the Locked_write state and I need to delete them I found a guide to break the Locked_write state but it's only for Linux Boot Servers How can I do the same for a Windows Boot Server? NetBackup version 8.1.1 Windows OS 2008 R2 enteprise Thank you in advance db
bordio27
6 years ago Place NetBackup
609Views
0likes
0Comments
MS SQL Server DB backups failing with "Error: Failed to query database metadata for..."
Our MS SQL Server DB backups scheduled in NetBackup were running successfully till few days back when they suddenly started failing. FYI... We're using the legacy/traditional "bch" script based method for taking DB backups as many of our SQL Servers are configured as Availability Group Clusters. I checked the dbclient logs and found the below errors, 13:38:12.797 [20988.19888] <2> check_vnetd_process_dup_permission: OpenProcessToken() failed: 5 13:52:13.069 [20988.19888] <4> CGlobalInformation::DeleteDSN: INF - Failed to remove DSN. Attempting operation with next installed ODBC Driver <ODBC Driver 13 for SQL Server> 13:52:13.073 [20988.19888] <4> CGlobalInformation::DeleteDSN: INF - Failed to remove DSN. Attempting operation with next installed ODBC Driver <SQL Server> 13:56:20.245 [15484.17208] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <28000>, SQL Message <18456><[Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'sa'.>. 13:56:22.133 [15484.17208] <4> CGlobalInformation::CreateDSN: INF - Failed to connect. Attempting operation with next installed ODBC Driver <ODBC Driver 13 for SQL Server> 13:56:22.267 [15484.17208] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <28000>, SQL Message <18456><[Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed for user 'sa'.>. 13:56:22.403 [15484.17208] <4> CGlobalInformation::CreateDSN: INF - Failed to connect. Attempting operation with next installed ODBC Driver <SQL Server> 13:56:54.486 [15484.17208] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <18><[Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error>. 13:56:56.072 [15484.17208] <16> CDBbackmain::LoadUserLogin: ERR - Internal error. See the dbclient log for more information. 13:56:56.131 [15484.17208] <32> CDBbackmain::LoadUserLogin: ERR - Error 64 has been returned from GetCurrentDSN 13:56:56.132 [15484.17208] <4> CDBbackmain::dbbackup: INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\All_DB_Full.bch>: <0> operations succeeded. <0> operations failed. 13:57:16.202 [15484.17208] <4> CGlobalInformation::DeleteDSN: INF - Failed to remove DSN. Attempting operation with next installed ODBC Driver <ODBC Driver 13 for SQL Server> 13:57:16.202 [15484.17208] <4> CGlobalInformation::DeleteDSN: INF - Failed to remove DSN. Attempting operation with next installed ODBC Driver <SQL Server> When I shared the error "Login failed for user 'sa'" with the SQL team, they said they've done hardening for user "sa" and so now all backups have to be scheduled by user "sysbackup". So I updated the connection properties of NetBackup SQL Client with "sysbackup" user credentials. After that the "Login failed for user 'sa'" error stopped but was still getting the below errors, 17:08:48.370 [1936.19556] <2> check_vnetd_process_dup_permission: OpenProcessToken() failed: 5 17:14:11.001 [1936.19556] <4> CGlobalInformation::DeleteDSN: INF - Failed to remove DSN. Attempting operation with next installed ODBC Driver <ODBC Driver 13 for SQL Server> 17:14:11.005 [1936.19556] <4> CGlobalInformation::DeleteDSN: INF - Failed to remove DSN. Attempting operation with next installed ODBC Driver <SQL Server> 17:14:59.264 [14700.7380] <2> check_vnetd_process_dup_permission: OpenProcessToken() failed: 5 17:15:04.732 [14700.7380] <8> CDBbackupView::ClassDropDownList: WARN - Error: bppllist not found in C:\Program Files\Veritas\NetBackup\bin\admincmd\bppllist.exe. 17:15:16.035 [14700.7380] <8> CDBbackupView::ClassDropDownList: WARN - Error: bppllist not found in C:\Program Files\Veritas\NetBackup\bin\admincmd\bppllist.exe. 17:15:50.710 [9780.15764] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <master> 17:15:52.731 [9780.15764] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <model> 17:15:54.745 [9780.15764] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <msdb> 17:15:56.759 [9780.15764] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <ReportDB> 17:15:58.774 [9780.15764] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <ReportDBTTSL> 17:16:00.787 [9780.15764] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <SQLPerfMon> 17:16:02.788 [9780.15764] <4> CDBbackmain::dbbackup: INF - Results of executing <C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\__17_15_50_219_00.bch>: <0> operations succeeded. <6> operations failed. 17:16:51.977 [14700.7380] <4> CGlobalInformation::DeleteDSN: INF - Failed to remove DSN. Attempting operation with next installed ODBC Driver <ODBC Driver 13 for SQL Server> 17:16:51.980 [14700.7380] <4> CGlobalInformation::DeleteDSN: INF - Failed to remove DSN. Attempting operation with next installed ODBC Driver <SQL Server> I explored a lot and came to know that the errors were related to permission issues and found that the "NetBackup Client" and "NetBackup Legacy Client" services on the client system have to be run with a user having sufficient privileges. So I changed both the services' "Log On As" user from "Local System" to the Domain user configured as local Administrator, which we're using for SQL administration purpose. After that most of the errors ceased but no matter how much I try the below errors still remains. 16:15:23.689 [8860.20884] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <master> 16:15:27.750 [8860.20884] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <model> 16:15:33.811 [8860.20884] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <msdb> 16:15:37.870 [8860.20884] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <ReportDB> 16:15:41.926 [8860.20884] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <ReportDBTTSL> 16:15:45.974 [8860.20884] <4> CDBbackrec::CDBbackrec: INF - Error: Failed to query database metadata for <SQLPerfMon> 16:15:50.008 [8860.20884] <4> CDBbackmain::dbbackup: INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\All_DB_Full.bch>: <0> operations succeeded. <6> operations failed. When I run the backup locally on the client system usingNetBackup SQL Client utility, I still get the same set of errors as below, INF - Error: Failed to query database metadata for <master> INF - Error: Failed to query database metadata for <model> INF - Error: Failed to query database metadata for <msdb> INF - Error: Failed to query database metadata for <ReportDB> INF - Error: Failed to query database metadata for <ReportDBTTSL> INF - Error: Failed to query database metadata for <SQLPerfMon> INF - Results of executing <C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\__22_24_31_032_00.bch>: <0> operations succeeded. <6> operations failed.
Solved
Muzaffar_Ansari
6 years ago Place NetBackup
9.1KViews
0likes
2Comments
inventory robot misspath
Hello everyone, I have problem with inventory robot on NBU 8.1.1. We have a master server and three media server. I was changing one of the media servers because of the slow tape write ratio. There is two HBA card with four path two four drives, each ahve asigned to one drive. Now When we add the robot in robot section, after some time the robotic path shows "MISSING-PATH". I add the drives normally and at the same time I have problem wiht SLP policies. They do not start them and stuck at "begin reading" or "started process bpdm (pid=XXXX)". I have removed and added robots and drives alot and have changed the pathes physically with different fiber cables. Thanks for any giude.
Solved
greatashkan
6 years ago Place NetBackup
2KViews
0likes
6Comments
can't connect to client (58)
These are some of the things I tried before reaching out to everyone. -I can ping the client in question. -Netbackup can see this clients properties under Host Properties -I can ping the master from the client, and the client from the master successfully -I ran thebptestbpcd.exe -client client123 on the master; returned the right ip info. -Tried backing up the client using it's ip address; same result. The jobs do not fail immediately. This is a 8.1.1 environment; master is a Windows 2012 cluster and media servers are appliances. Client is a Windows 2012 physical server. Your help greatly appreciated.
Solved
gaapeio
6 years ago Place NetBackup
2.2KViews
0likes
8Comments