Incorrect backup job size estimation

[matteu]

Hello,

I create backup job to backup all vm without any tag.
I have 0 VM with no tag.
I select my vcenter as object and exclude all VM with "Backup" category tag and uncheck template.



When I check size, it's not 0 because it's the vcenter size. If I exclude disk from vcenter, size is 0.



If I launch my job, I have no VM to process.

[HannesK]

Hello,
I would call it "optimization for performance" instead of a bug... imagine the wizard would have to calculate all the exclusion live for thousands of disks

Best regards,
Hannes

[matteu]

Hello,

Thank you for your answer.
What do you mean exactly ?

If I want to backup all my vcenter infrastructure and I exclude all my VM why I don't see 0 GB on the size ?

[Gostev]

I would call it "optimization for performance" instead of a bug... imagine the wizard would have to calculate all the exclusion live for thousands of disks

This actually works fine today... see the screenshot in the original post: when he excluded all disks using disk-level exclusions, job size is updated correctly.

In any case, the number of disks does not matter as he excludes entire VMs using tag. Whereas it should not behave any different from excluding VMs via VM Folder for example, or any other virtual infrastructure object, or just manually putting all his VMs in the exclusions lists.

[Gostev]

@matteu as a quick troubleshooting step, if you populate backup job with a tag (instead of adding the entire vCenter), does it show the job size correctly?

[HannesK]

This actually works fine today.

hmm, then I also need to report bugs when I see similar issues again. I got the recommendation many years ago to use the "test credentials" button to figure out what would really be covered by a job. Since then I ignore that calculation

On the tag question: I also marked all my VMs in my vCenter now with a backup tag. Then I excluded that tag. I did not exclude disks.

The calculation is done correctly, it shows 0



(I have to admit that my first tries had wrong calculations for the templates. but as I tried it again, it worked)


Did you try the "recalculate" button?

[matteu]

@gostev

Thanks for your answer.
If I add my backup category TAG only and exclude it with all other default settings, it's correct 0GB.
If I add my vcenter only and exclude backup category TAG it shows 240GB.

For me it's a bug .
All is excluded except vcenter appliance size I think here...

[HannesK]

If I add my vcenter only and exclude backup category TAG it shows 240GB.

as far as I see, I did exactly that and it shows 0 B. so it seems to be an issue in your environment. did you press the "recalculate" button?

as I cannot reproduce it I see two options:
1) upgrade to the latest version if not already done
2) open a support case and post the case number. then it can be fixed

[matteu]

I have no issue in my lab too.
That means it's related to my customer environment yes !

On this client I find it :

If I add the vcenter and I exclude the datacenter -> 0GB
If I add the vcenter and I exclude all cluster in the datacenter -> 240GB

It's some object between cluster and datacenter.

Thanks for your answer

[Gostev]

Well, in that case you owe us reading and memorizing the first 3 sentences of this post the very reason we ask to confirm (with our support or by yourself) that the issue is not environment-specific before posting, is so that my small team doesn't end up wasting time on threads like this. For example, instead of trying to reproduce a non-issue above today, Hannes could have spend this same time working on improving the product, speccing new features or enhancements.

[matteu]

I'm sorry about it.
I cannot change the title but I would remove BUG if I could...