R&D Forums Forum

Thank you. I had a suspicion it may have been some of the exclusions we currently have in place as V13.1 changes things around. I'll re-try the update in the upcoming days and report back with what I needed to do to fix it (hopefully)

Hi Tom, Which type of repository gives you this error? And, btw, I would suggest you upgrading directly to the latest v8.6. Thanks!

Hello, Does Veeam add new update for appliance on specific date or not ? I mean, Microsoft official updates are always the second thuesday of the month. For Veeam, is there something I need to know to plan correctly when I need to update the appliances . Thanks

I have upgraded Veeam Backup for 365 (community edition) to version 8.5. Since upgrading, I am getting a repository version 705 is unsupported error which has prevented the backup from running. Has anyone seen this error before and how to resolve? I have logged a case, ref #08228833 but not had any response.

Hello, I asked internally and one colleague had Ceph before at a customer and the root cause was a rate limit on Ceph side https://docs.ceph.com/en/latest/radosgw ... management If that's not the case, then please open a support case and post the case number Best regards Hannes

I'm sorry to hear about the challenges, but the only way to resolve the issues is through Veeam Support as noted before.

Although I kind of understand the confusion about the api permissions being needed, there are numerous lines in KB4820 that make very clear that EWS is still needed, some quotes: EWS must remain accessible for Exchange Online backups to continue. Keep EWS enabled in your tenant Ensure Veeam's App IDs are on the allow list. Ensure EWS access is enabled An updated product release supporting the full EWS-to-Graph transition is in development. You will need to upgrade to that release when it becomes available. Once EWS access is blocked for your tenant, Exchange Online mailbox backups will fail Personally I don't quite get why Veeam is pushing so hard to get these permissions already in place. Once you upgrade, to whatever version eventually will have backup using graph, that will be the moment to update api permissions. Perhaps functionally might not even be 100% the same, you'd probably have to communicate anyway with your customers. But that's just my line of thinking. The advance push just creates confusion, as apparent in the forums last few months.

+1 Are we honestly going to manage to disable a simple email notification within a year? I’m not holding my breath. Sarcasm aside ...

Ok but I already open cases for v13 I have too much errors and crash my tempo repository server Windows Server 2025 with ReFS, disk attach on Veeam (used before backup copy). I should have never upgraded from my VBR 12 version, which was much more stable. Ever since v13 and all the updates, it's been a total nightmare. For instance, I had to split my backup jobs because having the vCenter and proxy in the same backup job causes issues (there were zero issues on v12). Sometimes VBR server and repository crashes—I'm forced to reboot the servers because the Veeam services won't restart." Mouse bug and not reported (try scroll on Veeam Console with scrollbars) Mousewhell works but not scrollbars (contents dont show when scrollbar move)

Hello, we are trying to backup a CEPH S3 bucket with currently about 400 GB in preparation of backing up a 40 TB CEPH System. Sadly, even incrementally backing up (without reading any changes) the bucket takes nearly a hour for only 1,6 Million objects. Our production storage has 130 Million objects! At that speed even daily backup in unrealistic. We tried adding a Veeam infrastructure appliance as local proxy in the same network and it got even slower... We checked latencies and CEPH shows GET latency of 1,5 - 2 ms. What performance can we expect from Veeam here? Markus

Hi, Thank you for your response. It will be impossible to reconnect performance tier as it is a jbod attached to the physical current Veeam server and we are migrating to an appliance in a VM. Also, backup repos are imported for restore purposes only, there won't be any backup jobs running against them, so there won't be any retention processing, as far as I know, even with a SOBR. (Assuming the retention processing is done by the backup job) I thought we can process retention manually once a month/quarter. Best Regards

I believe the KB ( https://www.veeam.com/kb4820 ) still needs to be updated to reflect the recent changes regarding the automatic assignment of the new Microsoft Graph API permissions. I would also appreciate a clearer statement that, even though the new Graph API permissions are already being created and assigned, the product still appears to rely on EWS for the Exchange Online backup/restore operations. At least that's my current understanding, but the documentation/KBs is not entirely clear on this point. Without that clarification, it's easy to assume that once the Graph permissions are in place, EWS is no longer required, while in reality EWS access may still be necessary until the migration is fully completed.