NB7.5.0.5 Exchange GRT showing 100% full , but still backup is running?

[inn_kam]

NB 7.5.0.5

EXCHANGE 2010 GRT

WIN 2008 R2

Well i m taking  GRT backups of exchange databases And in Job detail status it is showing 100 % complete , but still backup is going and last database is on way to backup

So , is it FIX in NB 7.5.0.5

attache two screen shots of different timings ,cleared from Elapsed time 02:49 with 65238272 kb data and in 2nd screen shot after 4 mints at elapsed time 02:53 with 67639040 kb data ,  and it is showing as 100% complete

[Dyneshia]

Until you see a status 0 , the backup has not finished.

Are you seeing this type of issue only with exchange backups or all backups.

There were some issues in 7.5 :

(ET3106719) <<Fix Downloadable>> After upgrading a master server to NetBackup 7.5.0.5 (or applying NetBackup 5200/5220 Appliances 2.5.2 to an Appliance running as a master server), the Activity Monitor reports inconsistent information on job status for some jobs. Additionally, some jobs may not display in OpsCenter.
 http://www.symantec.com/docs/TECH203521

(NEW) (ET3123528) The NetBackup 7.5.0.x master server appears to "freeze;" administration console hangs as some commands hang indefinitely.
 http://www.symantec.com/docs/TECH204938

(ET3105408) Backup and Duplication jobs to and from an Media Server Deduplication Pool (MSDP) appear to hang or take an extended period of time to complete.
 http://www.symantec.com/docs/TECH201423

[inn_kam]

backup finished with status 0

but only problem it was showing as 100 % complete , issue with only exchange 2010 not with all other backups

[Marianne · Accepted solution]

Backup percentage is based on the previous successful backup. It is therefore an estimate.

Look at 'Estimated Kilobytes'. 
That was the size of the previous backup.

If you look at 'Current kilobytes written', you will see that a lot more data is now getting backed up.

Perfectly normal. NetBackup has always worked like this for as long as I've known the product.

[Dyneshia · Accepted solution]

Please see : http://www.symantec.com/docs/TECH67055