Backup Creation Time wrong

[ElmerAcme]

Hello,
after install the latest patch to Build 10.0.1.4854 P20201202 at mid on January, we recognized that the backup creation time of each VM inside the "Home" > "Backups" > "Disk" Tab, changed to the ending time of the Job.
We verified this on 14 different and independent installations. The creation time directly changes without running the job.
It means that the creation time of a VM, which was deleted in the productive environment 2 month ago, will show an actual date. Therefore this information is very misleading.
Regarding the support, it would be in V11 too, as it is not inside an official bug list.
Did someone recognized the same behavior?
Case # 04588896
Regards

[Natalia Lupacheva]

Hello Andreas,

I see you have already planned a webex session with Support engineer.
It's hard to investigate such issues without the logs, so let's wait for Support to come up with a solution.

Thank you!

[ElmerAcme]

Hello,
yes, I already had several sessions with support.
With this post I just wanted to know if we are the only one with this issue. Or someone else have the same?

Example: 1 Job with 10 VMs. If removing 1 VM from backup, this VM will still have the exact same backup creation time as the other 9.
Further, it's not the backup creation time. It's the job ending time.

I would expect that every Veeam user will see this after installing this update. And wondering that this is not a known behavior / bug.
Regards

[FrancWest]

I'm seeing this also. All VMs in the backups -> disk (copy) have the same date under creation time. Even if the VMs aren't present anymore on the system and weren't be backupped. They should have the date of their last backup taken. Good catch.

[pirx]

I just updated to P20201202 today and I can confirm that the date and time is the same for all VMs in a job. To be honest I can't remember if this was different before.

[ElmerAcme]

Hello @ All,
thanks for the replies. Good to hear that this is not a special issue at our environment.
Yes, the date information was different before the update. We verified this with support session during an update.
The date directly changed after the update without running this job.
So for me it seems to be just the wrong information displayed, as inside the detailed information of each VM the date is still correct.
Regards

[Natalia Lupacheva]

Hello @ElmerAcme,

Thank you for sharing the results! Glad you've finally verified this issue (I see you've had a really long discussion with Support).

[Samba222]

Hello @Veeam,
are there any plans to fix this bug? If so, in which version?
It is really annoying when you want to clean up older VMs in Jobs - and in the past it was displayed correctly.

Thx!

[ElmerAcme]

Hello,
the issue isn't fixed in V11 until now.
I got a script for updating a stored procedure in SQL for V10
Unfortunately this isn't available for V11.
Regards

[Samba222]

Ok, thx for this information! I want to upgrade to V11 next week, so how is the official next step from Veeam's side?

[Samba222]

Please, I would look forward to a response from Veeam here. Thx!

[Natalia Lupacheva]

Hi Ronald,

We don't have a universal guide here, so you need to open a Support case. Please share its ID with us so we could monitor your issue.
Also, did you open a Support case previously? Did you get any solutions from Support?

Thanks!

[veeeammeupscotty]

Can anybody confirm if this has been resolved in the 11a release?

[veremin]

Fixed in 11a. Thanks!