04-02-2020 07:06 AM
Has anyone else seen Status code 29's for legacy DB backups using scripts? I can't figure out why it's happening. Sometimes the DB backup is successful but the parent job still ends with a status 29.
1: (29) failed trying to exec a command
04-02-2020 02:25 PM
I suspect it will be that the script isn't in an allowed path.
Have a review of the following article and see if this helps https://www.veritas.com/support/en_US/article.100039639
I think you need to add or set the DB_SCRIPT_PATH = to include the location where your scripts reside (or move them to a trusted location - /usr/openv/netbackup/db_ext or <installPath>\NetBackup\dbext).
04-03-2020 01:01 PM - edited 04-03-2020 01:02 PM
The scripts are in the allowed path which is in the bp.conf
BPCD_WHITELIST_PATH = /oracle/<DB Name>
DB_SCRIPT_PATH = /oracle/<DB Name>/121/dbs
It also doesn't happen every time the backup runs.
04-06-2020 06:37 AM
It does not seem to be a 'known issue'.
All I can suggest is to dig into logs...
script output, dbclient, bphdb.
There will hopefully be a clue in one these logs.
04-16-2020 07:38 PM
04-17-2020 10:23 AM
You have a busy master server? How many jobs run per day? Are you using the default client time-out parameters?
04-17-2020 12:41 PM - edited 04-17-2020 12:42 PM
04-17-2020 12:45 PM - edited 04-17-2020 12:46 PM
Master server has 30,000 jobs a day give or take.
Timeouts are not default on the media servers.
The status 29 can get thrown during busy times and also when their is little to no use going on.
Currently have a ticket open with Veritas but they have only asked that we add stdout/stderr outputs throughout our script which hasn't produced anything.
04-18-2020 05:05 AM
You would try to use the following parameters on master.
echo "1000000" > /usr/openv/netbackup/db/config/BPSCHED_THRESHOLD
echo "25000000" > /usr/openv/netbackup/db/config/RBALLOC_KBYTES_THRESHOLD
echo "3600" > /usr/openv/netbackup/db/config/REPORT_RAW_KBS
echo "25000" > /usr/openv/netbackup/MAX_ENTRIES_PER_ADD
echo "20"> /usr/openv/netbackup/bin/DBMto
echo "0" > /usr/openv/netbackup/NET_BUFFER_SZ
Had that issue happening intermitently and above worked for me.
04-19-2020 03:37 AM
All of the mentioned toch files has been created, also deployed the recommended EEB's from Veritas
still backup is failing, we disabled all policies and run only one RMAN backup it go without any issues for 6 hours then failed with same error???
04-20-2020 06:27 AM
Takes too much time to close the allocated channels at the end of the backup? Is it the behaviour you've seen?
01-13-2021 08:47 PM
Just checking but did you get a resolution to this? Im having the same issue with RMAN backups post 8.2 upgrade and have applied the suggestions from this forum.
01-14-2021 08:46 AM - edited 01-14-2021 08:47 AM
No resolution. Veritas just pointed at our scripts saying they were the issue (They had no issues till that upgrade). We eventually coaxed the DBA's to abandon legacy backup and let us implement OIP backups for the Oracle DB's.
01-18-2021 08:51 AM