Troubles understanding Bpbkar log

I can't but since tar is mentioned I would take a look in the tar debug folder as well - [install_path]\Netbackup\logs\tar

Try also to increase the verbose level as well using the GUI and re-run the operation.

I assume you were using accelerator. Does it fail everytime of just the once? What happens if you turn off accelerator? If it works, then it might be worth re-running a full after renaming the track journal on the client located at:

installpath\VERITAS\NetBackup\track\<media_server>\<storage_server>\<client>\<policy>

the tar folder is not created ( i did not create it) :

23:59:53.919 [5052.6036] <2> fwrite_and_log: fail to write <fix size entry block> for track journal, backup id:<NULL>, file:<desktop.ini>, err_num:<2>, to write:<1>, wrote:<0>
23:59:53.919 [5052.6036] <4> dos_backup::fscp_add_tj_entry(): ct_cat_add_entry() failed, error:<14>.
23:59:53.919 [5052.6036] <16> tar_backup_tfi::fscp_finishfile_state: ERR - fscp_add_tj_entry() failed, error (14).

well, this is the second time that this job fails whit status 14, it is a full backup job and yes accelarator is enabled but i don't have access to  the NBU server neither to media server. i'm preety sure if i re-run te backup it will not fail (as it did last time), but the the problem is that i need to provide an explanation o the error mentionned above..... Any explanatin :)

No explanation from just 3 lines of the log I'm afraid - apart from it seems to be unable to add a track journal entry.

I looked in past cases and there are multiple causes seen before, but not many, one was resolved with an etrack (back in 2012 so this probably doesn't affect you, it was seen in 7.5.0.4) and the other case was when an Appliance was used as a media server and TCP tuning was required.

In other words, the lines you have in your post show the error, but the cause is somewhere else.  The complete bpbkar log would be required to start with.

What logging level is enabled here? 
Level 0 is normal fine for day-to-day troubleshooting, but sometimes higher level is needed.

You will need a bit more info to know what is going on - either more info in the log that you have not posted or else higher level log.
Try logging level 3.

the logging level is 2.

please see attachments for the entire log of the failing job

My guess its a problems with the track journal.

Fist messages is only info <2>, but right after down to the 1/1000 of second we see the error message.

I think  fscp_add_tj_entry is must be read as "File System Copy add Track Journal"

Try rename the existing the track journal and run a new full classic backup

23:59:53.919 [5052.6036] <2> fwrite_and_log: fail to write <fix size entry block> for track journal, backup id:<NULL>, file:<desktop.ini>, err_num:<2>, to write:<1>, wrote:<0>
23:59:53.919 [5052.6036] <4> dos_backup::fscp_add_tj_entry(): ct_cat_add_entry() failed, error:<14>.
23:59:53.919 [5052.6036] <16> tar_backup_tfi::fscp_finishfile_state: ERR - fscp_add_tj_entry() failed, error (14)

Update: Do you got TIR enabled as well ?

True Image Restore with move detection should not be enabled in NetBackup policies where Accelerator has already been enabled.

http://www.symantec.com/docs/TECH216391

The Technote is valid for 7.5 as well and a EEB exist for 7.5.0.7

This looks like an accelerated backup.

If so, when I get Status 13's or 14's, checking the force rescan in the full backup schedule and kicking off a fresh backup clears this up (uncheck it afterwards).

@Nicolai : thanks for the tip :)

@RoundTower_JGL : i don't ahve to the Master server or the Media server :)

i renamed the track journal and the scheduled  job of the full backup run successefuly but the incremental job now failed two time whit the  error 12 :

03:29:20.825 [8904.5244] <8> _tl_read_and_log_: end-of-file encounterd, desc:<catalog info>, entry:<NULL>, errno:<2>, read:<0> of <1>
03:29:20.826 [8904.5244] <16> tracklog_open_w: unable to open current tracklog:<\\?\C:\Program Files\Veritas\NetBackup\track\Mediaa_server\Pure_disk_server\wdkaec2t01-sav.atos-infogerance.fr\Plicy_name\System State\track_journal.v2.dat.accursed_server.fr_1422484232>, error:<13>
03:29:20.826 [8904.5244] <16> dos_backup::fscp_init(): tracklog_open() failed, error:<12>
03:29:20.826 [8904.5244] <16> dos_backup::tfs_scanstart: ERR - fscp_init() failed, error:<12>

So, i also renamed the new track journal and kicked a full backup. now i'm waiting for the result. hope this will solve the issue.

Hi,, 

Make a best use of lv.exe which is available in the \Install\Program Files\Veritas\NetBackup\bin\goodies\lv.exe

I hope it helps a lot..