Hi Nagori, 

It is a breakdown of the time the job is spending on the different tasks. In this instance 82% of the time is spent reading data from the client, 10% is spent doing DDB lookups and so on. 

It offers a high level overview of any performance constraints. If this job is performing badly then you can see that most of the time is spent reading the data on the client and that would be the place to start for any review. 

HTH 

Niall 

Hi

Thank you for your prompt response, it mean if we have “Write” number is higher then “Read” does it mean it is good backup or restore job, 

And what does mean by “Network” number does it mean data is flowing over network 

And last if “DDB lookup” number is higher like 70 is good or bad 

Thanks 

@Nagori the write being higher or lower than the read does not indicate good or bad as it all depends on the type of job, if it is deduplicated, the rate of change, etc.

Network is the amount of data moved over the network.

hi  !

If the higher percentage is on the WRITE, it means this job spends most of its time writing to your device. This could be the bottleneck, like your target disks/library/tape is too slow.

If the higher percentage is on the NETWORK, it means it’s mostly spending time transferring data from source to target.

As written earlier, it can depend on the configuration, dedup or not, brand new client, etc. But this provides information that can be useful to identify bottlenecks, or check that it’s performing as expected.

Laurent.