cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Re: DAG duplication failed with error 191

I got the same issue on DAG Duplicate jobs.

Can you please analyse the BPDBM logs as attached.

 

Thank you

5 Replies
Highlighted

Re: DAG duplication failed with error 191

Moved to new discussion from https://vox.veritas.com/t5/NetBackup/Duplication-fails-with-database-system-error-220/m-p/401824

@abd_hadi 
Please share Job Details from failed duplication job. 
It helps if we know which PIDs and timestamps to look for.

Highlighted

Re: DAG duplication failed with error 191

Hi Marianne,

 

Thanks for yor fast response,

Herewith attached the Job logs for your kind perusal.

 

Thank you.

Highlighted

Re: DAG duplication failed with error 191

Logging level is unfortunately too low. All we see is this:

04:12:19.671 [6856.6684] <16> extend_list_add_files: get_file_rec() error: -1 image: D:\Program Files\Veritas\NetBackup\db\images\dag01\1552000000\ExchangeDB_NEW_1552665792_FULL.f nfiles: 0
04:12:19.671 [6856.6684] <2> bpcr_disconnect_rqst: bpcr received the following message:
04:12:19.671 [6856.6684] <2> bpcr_disconnect_rqst: bpcr received the following message:
04:12:19.702 [6856.6684] <2> process_request: request complete: exit status 220 database system error; query type: 248

Please increase bpdbm logging level to 3 and restart NBU on the master server. 

Highlighted

Re: DAG duplication failed with error 191

I found this TN:  https://www.veritas.com/support/en_US/article.100006891

With increased logging level and nbfsd log on Exch client, you should be able to confirm if you have the same issue. 

PS:
Any reason why you are still on NBU 7.6? 

Highlighted

Re: DAG duplication failed with error 191

It's good to start a new post on this. The old forum was from 2011.

Please tell us the following.

- NetBackup versions on both client and master server, including any EEBs (patches from Veritas).
- Is master server Windows?
- Exchange version, including CU.
- Does the DAG have an IP? Can you ping it from the master server?