[CASE #07580571] Restore Portal Behavior Change After VB365 v8 Upgrade

[chrisflyckelen]

Hey everyone,

I've been dealing with this issue for the past six months and wanted to share it here in case anyone has encountered the same problem but hasn't reported it to support.
Our VB365 deployment initially started on v7, was regularly updated, and is now running on the latest v8 release. We use a distributed deployment model, as the restore portal is externally published for BaaS purposes.

After upgrading to v8, we noticed a change in the restore portal's behavior. In v7, selecting a restore point would display its contents, and if no restore point existed, it would show backup data close to the selected restore point. However, in v8, this functionality no longer works, and we haven't been able to determine the root cause.

Deployment Details:
- Each service (Exchange Online, OneDrive, etc.) is backed up by a dedicated job to a separate repository using Wasabi cloud storage.
- An immutable backup copy is stored in Azure Archive Blob Storage.

If anyone has encountered a similar issue or has insights into a possible solution, I'd appreciate any input.

Thanks,
Christian

[Mike Resseler]

Hey Christian,

I would need to go through the entire case, but if you select a specific restore point, can you see the data then? Or still does not show the contents?

[chrisflyckelen]

Hi Mike,

Yes, I can see the data for the specific restore point—for example, if an Exchange Online job created the restore point, I can access Exchange Online data only. Similarly, if the restore point was generated by a OneDrive for Business backup job, the corresponding OneDrive data is available.

However, the cumulative view for the user, as mentioned in the Help Center, is not displayed.

Thanks,
Christian

[Polina]

Hi Christian,

I quickly checked your case status - it's currently with RND, and the team is actively researching it. I hope to get an update from the team by the end of this week.

Thanks!

[chrisflyckelen]

Hi everyone,

the support team is still under investigation. They are now trying to reproduce the issue which will take some time.

Thank you,
Christian

[chrisflyckelen]

Hey everyone,

i just received a statement from the support team. The change in behavior came into play after the major upgrade to v8. Veeam chose a different approach here. In my point of view this a big step back in usability and user experience. Especially for service providers the restore portal is not usable anymore.

So, for this reason I would like to change this post to a high-priority feature request. Please bring back the old behavior as soon as possible.

Thank you,
Christian

[chrisflyckelen]

Hi everyone,

I would be happy to get a statement from someone of the product management team.

IMHO this capability is crucial, who is running an environment which was upgraded over the time.

Thank you,
Chris

[t7MevELx0]

I’m considering filing a complaint with Insight Partners and requesting escalation at the investor level.

[Mike Resseler]

All,

We are looking into this. But I have no clear solution for this at this point in time. Bringing back the old behavior is not something that can be switched on I'm afraid. Right now we are investigating different possibilities. We know what the root cause is, it is because you are using different repositories. In v7, we (virtually) merged those to offer the functionality, in v8 we don't do this anymore because it causes a lot of issues.

Unfortunately I don't have a path to resolution yet, as said, since we are examining options.