Highlighted

SQL Backups failed with invalid status

Hi dear all, I am trying to backup SQL server with intelligents policy, but backup failed with status 1073741571 !! 

This is a job details:

07/30/2017 09:44:21 - Info nbjm (pid=3166) starting backup job (jobid=1333765) for client client_name, policy pilicy_name, schedule full
07/30/2017 09:44:21 - Info nbjm (pid=3166) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=1333765, request id:{F202F748-74E5-11E7-A542-ABAABE7E0703})
07/30/2017 09:44:21 - requesting resource media_storage_unit
07/30/2017 09:44:21 - requesting resource master_name.NBU_POLICY.MAXJOBS.pilicy_name
07/30/2017 09:44:21 - granted resource master_name.NBU_POLICY.MAXJOBS.pilicy_name
07/30/2017 09:44:22 - estimated 0 kbytes needed
07/30/2017 09:44:22 - Info nbjm (pid=3166) started backup (backupid=client_name_1501391662) job for client clien_name, policy pilicy_name, schedule full on storage unit
07/30/2017 09:44:23 - started process bpbrm (pid=17275)
07/30/2017 09:44:23 - connecting
07/30/2017 09:44:24 - connected; connect time: 0:00:00
07/30/2017 09:44:28 - end writing
07/30/2017 09:44:55 - Info bpbrm (pid=17275) client_name is the host to backup data from
07/30/2017 09:44:55 - Info bpbrm (pid=17275) reading file list for client
07/30/2017 09:44:55 - Info bpbrm (pid=17275) starting bphdb on client
07/30/2017 09:44:56 - Info bphdb (pid=4748) Backup started
07/30/2017 09:44:59 - Error bpbrm (pid=17275) from client client_name: ERR - exit status: <-1073741819>
07/30/2017 09:44:59 - Error bpbrm (pid=17275) from client client_name: ERR - bphdb exit status = 1073741819: invalid error number
07/30/2017 09:45:00 - Info bphdb (pid=4748) done. status: 1073741819: invalid error number
Invalid Status Code (1073741819)

 

and this is client bphdb log

09:48:23.542 [2568.6616] <2> logparams: -sb -rdbms sql_server -S master_hostname -to 300 -c policy_name -s full -clnt client_name -intelligent_db_opts -FULL -auto -kl 28 -b client_name_1501391467 -jobid 1333763
09:48:23.542 [2568.6616] <2> debuglog: <4> bphdb: INF - BACKUP START 2568
09:48:23.542 [2568.6616] <2> debuglog: <4> bphdb: INF - CONTINUE BACKUP message received
09:48:23.839 [2568.6616] <2> debuglog: <4> bphdb: INF - Processing "C:\Program Files\Veritas\NetBackup\bin\dbbackex.exe" -np -s master_hostname -ipf "input.2568.0.0730117.094823" -pjobid 1333763
09:48:27.902 [2568.6616] <2> debuglog: <16> bphdb: failed executing command <"C:\Program Files\Veritas\NetBackup\bin\dbbackex.exe" -np -s master_hostname -ipf "input.2568.0.0730117.094823" -pjobid 1333763>
09:48:27.902 [2568.6616] <2> debuglog: <16> bphdb: ERR - exit status: <-1073741571>
09:48:27.902 [2568.6616] <2> debuglog: <16> bphdb: ERR - Error code: 1073741571
09:48:27.902 [2568.6616] <2> debuglog: <16> bphdb: ERR - bphdb exit status = 1073741571: invalid error number
09:48:27.902 [2568.6616] <2> debuglog: <4> bphdb: INF - EXIT STATUS 1073741571: invalid error number
09:51:38.535 [4748.208] <2> logparams: -sb -rdbms sql_server -S master_hostname -to 300 -c test-for-mssql-client_name -s full -clnt client_name -intelligent_db_opts -FULL -auto -kl 28 -b client_name_1501391662 -jobid 1333765
09:51:38.535 [4748.208] <2> debuglog: <4> bphdb: INF - BACKUP START 4748
09:51:38.535 [4748.208] <2> debuglog: <4> bphdb: INF - CONTINUE BACKUP message received
09:51:38.816 [4748.208] <2> debuglog: <4> bphdb: INF - Processing "C:\Program Files\Veritas\NetBackup\bin\dbbackex.exe" -np -s master_hostname -ipf "input.4748.0.0730117.095138" -pjobid 1333765
09:51:41.863 [4748.208] <2> debuglog: <16> bphdb: failed executing command <"C:\Program Files\Veritas\NetBackup\bin\dbbackex.exe" -np -s master_hostname -ipf "input.4748.0.0730117.095138" -pjobid 1333765>
09:51:41.863 [4748.208] <2> debuglog: <16> bphdb: ERR - exit status: <-1073741819>
09:51:41.863 [4748.208] <2> debuglog: <16> bphdb: ERR - Error code: 1073741819
09:51:41.863 [4748.208] <2> debuglog: <16> bphdb: ERR - bphdb exit status = 1073741819: invalid error number
09:51:41.863 [4748.208] <2> debuglog: <4> bphdb: INF - EXIT STATUS 1073741819: invalid error number

 

Thanks

Tags (2)
8 Replies

Re: SQL Backups failed with invalid status

hey

Please provide the logs for dbclient...

Re: SQL Backups failed with invalid status

Hi, client dbclient log folder is empty! :/

Re: SQL Backups failed with invalid status

bphdb couldn't start dbbackex.exe
&nbsp;
"C:\Program Files\Veritas\NetBackup\bin\dbbackex.exe" -np -s master_hostname -ipf "input.2568.0.0730117.094823" -pjobid 1333763&gt;
end exited with error code&nbsp;&lt;-1073741819&gt;. I think it's because of UAC or permissons of account your NetBackup services use.&nbsp;
&nbsp;
&nbsp;

Re: SQL Backups failed with invalid status

Please provide all relevant info.
Windows version, NBU version, SQL version on client, user account for NBU Client Service, member of cluster?

Re: SQL Backups failed with invalid status

Netbackup on client and master are 7.7.2, client is windows 2012 and MSSQL 11.1.3000.0,

Servers not memebr of any cluster,

User account for NBU Client Service not configured, just install agent by domain admin user

thanks

Re: SQL Backups failed with invalid status

Hmm

Are you in-line with below??

Check this out from NBU MSSQL admin guide:

"Configuring the NetBackup services for SQL Server
backups and restores (SQL Server Intelligent Policy)
NetBackup uses the NetBackup Client Service and the NetBackup Legacy Network
Service to access the SQL Server when it performs backups and restores. With
the proper configuration, these services can log on with the Local System account
or another account that has the necessary privileges.
The logon account for the services requires the following:
■ The SQL Server “sysadmin” role.
■ If you want to use Local System for the logon account, the requirements depend
on the SQL Server version:
■ For SQL Server 2005, the sysadmin role is automatically applied to the NT
AUTHORITY\SYSTEM and BUILTIN\Administrators groups.
■ For SQL Server 2012 and later, you must first apply the sysadmin role
manually to the NT AUTHORITY\SYSTEM or the BUILTIN\Administrators
group.
■ Additional requirements depend on the credentials option you chose to register
the instance(s).
■ For Use these specific credentials, the NetBackup services can use the
Local System logon account. If you want to use a different logon account, it
must have the privileges to Impersonate a client after authentication and
Replace a process level token. See “Configuring local security privileges
for SQL Server” on page 29. Both services can use the same logon account
or separate logon accounts.
■ For Use credentials that are defined locally on the client, the logon
account for the services can be either the SQL System administrator or Local
System. Both services must use the same logon account."

Re: SQL Backups failed with invalid status

The SQL version that you mention is confusing. There is no such version mentioned in NBU 7.7 DB and Application Agent CL:  http://www.veritas.com/docs/000025230 

Can you please show us a screenshot of the "All Instances"  properties?

Re: SQL Backups failed with invalid status

Make sure you use a account to run SQL backups.

That account must be part of BUILTINADMINISTRATORs Group and Must have SYSadmin privilages in SQL server.

Also that account must be used for running NetBackup Client & legacy network services.

Also always follow the practice to run anything as an admin

eg: Start> Netbackup for MS SQL> right click> Run as Administrator