OPSCenter Report Issue: some clients show 0 data written

It would help if you post some evidence, not quite sure what you're trying to explain,

Hi Riaan,

thank you for your reply.

you can see below a part of a report from OPSCenter ("Client Summary Dashboard"). it's about 2 client (standard backup policy, backup selection was about / on 2 linux server). backup was OK for both these clients, BUT OPSCenter report shows that NO Data (VOLUME KB column) for CLIENT_B. (in BAR console interface i can see there are actual data ready to be restored)

Please note that total number of successful job is 30 for both clients.

Regards

Hi,

What do you get if you run say "Jobs by Application" for only the affected clients? Does it also show ZERO bytes?

Hi Riaan,

yes, same behaviour here (moreover, this report shows that a lot of files were backed up):

Regards

Hi,

Ok we could dig into this a lot more but in the end I think it would require something to be fixed in your database. So rather open a support case, something seems to be wrong there.

Thank you for you support Riaan,

i'll open a support case, 

regards.

Try running a custom report, historical, selecting just that client, and set Y1 axis to report on "Job Protected Size", "Total".  Does that work?

If that looks right, then go back and change the Y1 axis to just "Job Size".  See what the report comes up with.

Hi Ron,

thank you for your reply, here are what i got from the 2 reports:

1) "Job Protected Size" report: it shows jobs from 5GB (incremental bck) to 40GB (full bck)

2) "Job Size" report: it gives me a "no data available" warning.

regards,

Alberto

Based on your other posts, it looks like you are using Media Server Deduplication Pools, which has created problems with OpsCenter's original, default reports because, for some reason, OpsCenter's default reports are using the value in "Job Size", which is the number of kilobytes actually sent when factoring in deduplication, instead of the value in "Job Protected Size", which is the number of kilobytes in all the files before deduplication.  I don't know why it still shows zero kilobytes when there were at least a few KB sent, but that's what it does.

The only way to fix this, from our standpoint, was to create our own custom reports similar to the default ones, and tell it to use the Job Protected Size. Then it matched the reports generated from the NetBackup Java GUI, and matched what we expected to see when comparing historical reports before we started using MSDP's.

Hi Ron,

That issue you're referring to relates to the domain_jobarchive.byteswritten and domain_jobarchive.presissize figures.

The Jobs size report incorrectly uses domain_jobarchive.byteswritten (deduped figure in the case of MSDP) which as you say messes up the figures when using MSDP (DD and Tape work fine). But in that case it would show an incorrect (lower) value, this case shows nothing.

That is concerning.