cancel
Showing results for 
Search instead for 
Did you mean: 

estimated 2633314 kbytes needed

Nitesh
Level 4
hi..

can any one tell me posible ression for this problem ..

y it's happening like this..



09/12/2009 08:08:24 - requesting resource bkpsvr_stu_LT03
09/12/2009 08:08:24 - requesting resource bkpsvr.NBU_CLIENT.MAXJOBS.rootdc02.tcs.com
09/12/2009 08:08:24 - requesting resource bkpsvr.NBU_POLICY.MAXJOBS.TW_PR_DF_ROO_
09/12/2009 08:08:26 - granted resource  bkpsvr.NBU_CLIENT.MAXJOBS.rootdc02.tcs.com
09/12/2009 08:08:26 - granted resource  bkpsvr.NBU_POLICY.MAXJOBS.TW_PR_DF_ROO
09/12/2009 08:08:26 - granted resource  8769L3
09/12/2009 08:08:26 - granted resource  IBM.ULT3580-TD3.08
09/12/2009 08:08:26 - granted resource  bkpsvr_stu_LT03
09/12/2009 08:08:26 - estimated 2633314 kbytes needed


i am using netbackup 6.5

Thanks
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified
Why do you say it's a PROBLEM?
It merely says "ESTIMATED" based on the backup size of the previous similar backup, plus a small %. It does not scan the client filesystem to do a calculation.
It does not fail the job because of the estimation, right? That would be a problem...

View solution in original post

2 REPLIES 2

Marianne
Level 6
Partner    VIP    Accredited Certified
Why do you say it's a PROBLEM?
It merely says "ESTIMATED" based on the backup size of the previous similar backup, plus a small %. It does not scan the client filesystem to do a calculation.
It does not fail the job because of the estimation, right? That would be a problem...

Andy_Welburn
Level 6
It's a best guess of how much is going to be saved based on its previous run of that particular schedule & so is nothing at all to worry about.
I've never known it to guess very well tho' as it always seems to over-estimate by at least 10% ;)

It also uses the same "calculation" to estimate the % complete whilst the job's running & also time remaining. Altho' the latter is very mis-leading if the job has been queued for some time as it uses the time the job initially started & not the time it actively started backing up.