cancel
Showing results for 
Search instead for 
Did you mean: 

29 <failed trying to exec a command>

traghav86
Level 5

Good day 

Please assist with below sybase backup failure, Sybase is running on Linux and 

01/01/2016 20:56:30 - Info nbjm (pid=6636) starting backup job (jobid=15896) for client XXXXX, policy XXXXX_sybase, schedule Daily_Full
01/01/2016 20:56:30 - Info nbjm (pid=6636) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=15896, request id:{4800ABF7-3E31-499B-A710-40D8CE8DB701})
01/01/2016 20:56:30 - requesting resource XXXXX-stu
01/01/2016 20:56:30 - requesting resource XXXXX.NBU_CLIENT.MAXJOBS.XXXXX
01/01/2016 20:56:30 - requesting resource XXXXX.NBU_POLICY.MAXJOBS.XXXXX_sybase
01/01/2016 20:56:30 - granted resource XXXXX.NBU_CLIENT.MAXJOBS.XXXXX
01/01/2016 20:56:30 - granted resource XXXXX.NBU_POLICY.MAXJOBS.XXXXX_sybase
01/01/2016 20:56:30 - granted resource XXXXX-stu
01/01/2016 20:56:31 - estimated 0 kbytes needed
01/01/2016 20:56:31 - Info nbjm (pid=6636) started backup (backupid=XXXXX_1497293790) job for client XXXXX, policy XXXXX_sybase, schedule Daily_Full on storage unit XXXXX-stu
01/01/2016 20:56:31 - started process bpbrm (pid=7000)
01/01/2016 20:56:48 - Info bpbrm (pid=7000) XXXXX is the host to backup data from
01/01/2016 20:56:48 - Info bpbrm (pid=7000) reading file list for client
01/01/2016 20:56:51 - connecting
01/01/2016 20:57:02 - Info bpbrm (pid=7000) starting bphdb on client
01/01/2016 20:57:02 - Info bphdb (pid=25672) Backup started
01/01/2016 20:57:02 - Info bphdb (pid=25672) Processing sybase_SLH_backup.sh
01/01/2016 20:57:02 - Info bphdb (pid=25672) Waiting for the child status
01/01/2016 20:57:02 - connected; connect time: 0:00:00
01/01/2016 20:57:03 - Error bpbrm (pid=7000) from client XXXXX: ERR - Script exited with status = 29 <failed trying to exec a command>
01/01/2016 20:57:03 - Error bpbrm (pid=7000) from client XXXXX: ERR - bphdb exit status = 6: the backup failed to back up the requested files
01/01/2016 20:57:14 - Info bphdb (pid=25672) done. status: 6: the backup failed to back up the requested files
01/01/2016 20:57:14 - end writing
the backup failed to back up the requested files (6)

Rahul
3 ACCEPTED SOLUTIONS

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

This is a completely different status code to 29.

NetBackup status code 245: the specified policy is not of the correct client type

All I can suggest is to carefully work through this excellent article:
https://vox.veritas.com/t5/Articles/Netbackup-for-Sybase-step-by-step/ta-p/810308

Open the .pdf attachment. Skip to +- p.24 and work with your Sybase admin to double-check the script.
Editing the script is covered in detail from p.27 onwards.

Important to know that when the policy is initiated from the master, the script on the client is run as root.
So, the user name and password in the script must be correct and policy/schedule names in the script must be double-checked

 

 

View solution in original post

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

That snippet does not help at all.

According to the Sybase doc, 2 policies are needed. 
A Sybase policy and a Standard policy with User Shedule.

Can you confirm that all are in place?

View solution in original post

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

The doc that I shared explains it CLEARLY.

I am sure the Sybase for NBU manual as well.

I am not a database expert, that is why I use the documentation whenever I need to assist with database backups.

View solution in original post

13 REPLIES 13

Thiago_Ribeiro
Moderator
Moderator
Partner    VIP    Accredited

Hi,

This information is not enough, you only sent the Detailed Status of job. Please send us these logs.

/usr/openv/netbackup/logs/bphdb
/usr/openv/netbackup/logs/sybackup

Thanks.

Regards,

Thiago Ribeiro

Hi 

looks like scheduled backup ran at sometime , but manual initiating giving this error.

Rahul

ERR - Script exited with status = 29 <failed trying to exec a command>

Basically there is a problem with executing the sybase_SLH_backup.sh script.

Being on linux I would start with checking that the script has the execute right set.

Besides that see:

https://vox.veritas.com/t5/NetBackup/General-database-backup-error-troubleshooting/m-p/675381

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

" ... looks like scheduled backup ran at sometime , but manual initiating giving this error."

Manual initiating from where? Master or Sybase client?

The previous advice about checking logs still stands.

Hi Mariane 

Initiated from client is working.

latest error log from bphdb

10:06:09.282 [17267.17267] <2> logparams: -sb -rdbms sybase -S XXXX -to 300 -c XXXX_sybasedb -s Daily_Full -clnt SABCXJSLRPA1 -FULL -kl 28 -b XXXX_1497341140 -jobid 16085
10:06:09.315 [17267.17267] <2> debuglog: <4> bphdb: INF - setenv SYBACKUP_POLICY=XXXX_sybasedb
10:06:09.315 [17267.17267] <2> debuglog: <4> bphdb: INF - setenv SYBACKUP_SCHED=Daily_Full
10:06:09.315 [17267.17267] <2> debuglog: <4> bphdb: INF - setenv SYBACKUP_SERVER=sabcxjbck201
10:06:09.315 [17267.17267] <2> debuglog: <4> bphdb: INF - setenv SYBACKUP_CLIENT=SABCXJSLRPA1
10:06:09.315 [17267.17267] <2> debuglog: <4> bphdb: INF - setenv SYBACKUP_FULL=1
10:06:09.315 [17267.17267] <2> debuglog: <4> bphdb: INF - setenv SYBACKUP_INCR=0
10:06:09.315 [17267.17267] <2> debuglog: <4> bphdb: INF - setenv SYBACKUP_USER_INITIATED=0
10:06:09.315 [17267.17267] <2> debuglog: <4> bphdb: INF - setenv SYBACKUP_SCHEDULED=1
10:06:09.315 [17267.17267] <2> debuglog: <4> bphdb: INF - BACKUP START 17267
10:06:09.769 [17267.17267] <2> debuglog: <4> bphdb: INF - CONTINUE BACKUP message received
10:06:09.769 [17267.17267] <2> debuglog: <4> bphdb: INF - Processing /usr/openv/netbackup/ext/db_ext/sybase/scripts/sybase_SLH_backup
10:06:09.770 [17267.17267] <2> debuglog: <4> bphdb: INF - Waiting for the child status
10:06:09.770 [17270.17270] <2> debuglog: <4> bphdb: INF - Child executing /usr/openv/netbackup/ext/db_ext/sybase/scripts/sybase_SLH_backup
10:06:10.770 [17267.17267] <2> debuglog: <4> bphdb: INF - Script exited with status = 0 <the requested operation was successfully completed>
10:06:10.770 [17267.17267] <2> debuglog: <4> bphdb: INF - bphdb exit normal
10:06:10.770 [17267.17267] <2> debuglog: <4> bphdb: INF - EXIT STATUS 0: the requested operation was successfully completed

Rahul

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You are confusing me...
Manual backup from client is working but not from master?

bphdb log (generated by backup from master)  above shows successful backup.

Please try to give us something to work with....

Hi Marianne

Backup which is intiating from client from DB side is working. in Activity monitor is see all Blue with byte count.

but as soon as i start from NB policy as manual backup its failing with "245" in activity monitor.

Rahul

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

This is a completely different status code to 29.

NetBackup status code 245: the specified policy is not of the correct client type

All I can suggest is to carefully work through this excellent article:
https://vox.veritas.com/t5/Articles/Netbackup-for-Sybase-step-by-step/ta-p/810308

Open the .pdf attachment. Skip to +- p.24 and work with your Sybase admin to double-check the script.
Editing the script is covered in detail from p.27 onwards.

Important to know that when the policy is initiated from the master, the script on the client is run as root.
So, the user name and password in the script must be correct and policy/schedule names in the script must be double-checked

 

 

Hi Marianne 

i did double checked with policy and client all looks fine and compared with script too.

backup is running fine but one stream is failing with 245 error. attached screenshot.

Rahul

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

That snippet does not help at all.

According to the Sybase doc, 2 policies are needed. 
A Sybase policy and a Standard policy with User Shedule.

Can you confirm that all are in place?

why do we need "Standard" policy ? this is for file level backup.

i have created only for Sybase DB.

Rahul

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

The doc that I shared explains it CLEARLY.

I am sure the Sybase for NBU manual as well.

I am not a database expert, that is why I use the documentation whenever I need to assist with database backups.

franciscotorres
Level 4

It has happened to me several times, as they say several times in this post is simply that they are not declared or the name of the server, or the name of the policy or the name of the schedule EXACTLY in the script as in the policy itself, just check twice.