Anyone else struggling with Veeam Data Cloud Express Backup?

[dbr]

We've been using Veeam Data Cloud (VDC) for about six months now, and unfortunately we've run into a significant number of issues.

Some examples:

• Overall, the environment is often extremely slow. For example, simply listing objects in the Express Restore dialog can take an unreasonably long time and sometimes throwing following error: "We're experiencing a temporary delay due to a system timeout. Please try again in a few minutes. If you continue to encounter this issue, please reach out to the administrator for further support." > The message is useless, who is meant by "the administrator"?
• The dashboard occasionally displays completely incorrect values.
• The job details view (express job) is very limited, thus proceed with troubleshooting in M365 is quite hard:
  • No filtering options
  • No ability to add additional columns (e.g. upn, email address or object id)
  • No export
  • No sorting
  • Columns cannot be customized properly
  • Error messages are truncated and cannot be viewed in full
• Our OneDrive Express Jobs show incorrect numbers of protected sites. In addition, reported errors are not updated or cleared, even though OneDrive sites have already been successfully provisioned for every user in scope.
• We are also seeing various issues with Exchange Express Jobs.
• We have already opened numerous support cases regarding these and other problems (#08131694, #08131267, #08126140, #08123504...).

At this point, our overall impression is that the product still feels far from production-ready. We understand that every environment is different, but the number of issues we've encountered is making it difficult to maintain confidence in the platform.

My question to the community: Are others experiencing similar problems, or is Express Backup generally working smoothly for you?

I realize this post may sound somewhat unstructured and lacks detailed technical analysis. To be honest, we've reached the point where the level of frustration exceeds the motivation to document every individual issue in depth for now.

Could someone from the Veeam product team please take a look at the referenced support cases and provide some feedback or at least an acknowledgement of these concerns?

Thanks, Daniel

[Mildur]

Hi Daniel,

Thanks for sharing this — and sorry to hear about the experience so far. The behavior you describe is not what we want you to see.
I’ve asked our VDC team to check the referenced support cases. Please continue within your cases for the moment.

A short feedback from my side:
- #08131694 → With our R&D department. Investigation requires involving Microsoft Support. I can see you and our Support team are already in contact with Microsoft through your Microsoft case.
- #08131267 → This issue seems to be fixed since today, correct?
- #08126140 → Root cause is still under investigation with our R&D teams, but it should work for you now, correct?
- #08123504 → Seems to be fixed and the case is closed.

Best,
Fabian

[dbr]

Hi Fabian,

Thanks for having a look to that cases and giving some feedback here. I haven't checked them lately because I'm not in charge for Veeam in our company anymore and I'm working in the M365 team since a few years. But I'm a Veeam veteran and still connected to Veeam cause of VDC . I mentioned all those cases and we will keep working on it, but my intention was more to make the product team aware of our experiences because that was not what I'm used to from Veeam. That's not what you can address by support tickets and I love this forum for that. VBO and VBR always have been such mature products and I loved to use them. Just take my complains as feature request into account. For all technical issues we'll keep working on the support cases. Thanks again, I wouldn't have expected anyone will reply because it was a quite unprecise post. The more I appreciate you replied.

Best regards,
Daniel