BUG? Snapshot age

[hyvokar]

Hi!

I just installed Veeam One and found out that one of the guests had 450 days old snapshot
I removed the snapshot and the error went away from Veeam One. However, it left a warning saying that latest snapshot is older than the defined threshold - even that the snapshot was already gone. This lasted for like 12 hours and warning went away only after VBR created a new snapshot.

[Shestakov]

Hi,
Do you have any other snapshots except that 450days-old? The warning gone after you made the new snapshot as expected by design.
What are your thresholds for the snapshot age?
Thanks.

[jb1095]

Hi!

I just installed Veeam One and found out that one of the guests had 450 days old snapshot
I removed the snapshot and the error went away from Veeam One. However, it left a warning saying that latest snapshot is older than the defined threshold - even that the snapshot was already gone. This lasted for like 12 hours and warning went away only after VBR created a new snapshot.

I noticed the same thing within our environment. It actually did go away eventually but in our case, it took a few days. I was looking for an orphaned snapshot that maybe was not reporting in the datastore but there were none to be found.

[Vitaliy S.]

Do you guys have our latest update 1 for Veeam ONE v8 installed?

[jb1095]

Do you guys have our latest update 1 for Veeam ONE v8 installed?

yes sir. This is not a big deal for me anyway. The alarm goes away and any good admin should be double checking what is being reported. No big deal IMO, I just wanted to let the OP know that we experienced the same issue.

[Shestakov]

Thanks for the feedback, Jon.
If the behavior repeats, please contact Veeam technical support to review the logs and find out the issue.

[hyvokar]

Hi,
Do you have any other snapshots except that 450days-old? The warning gone after you made the new snapshot as expected by design.
What are your thresholds for the snapshot age?
Thanks.

Nope. That was the one and only snapshot. Patch1 is installed.

[Shestakov]

Could you please contact Veeam technical support for the issue investigation? I believe logs are need to be reviewed here.
Thanks!

[hyvokar]

Hi!

I will, if I run across this again. I guess in this case the trail is getting a bit cold.

[Shestakov]

Yes, we`ve not experienced the issue during software testing, but since at least two of you mentioned the behavior, it is great to review logs and find the root.
So, yes once the issue repeats, please contact Veeam support and provide us your support case number.
Thanks!