[VBO365] Veeam <-> ExaGrid S3 Bucket

[AbdelO]

Hello Experts !

I’m seeking assistance with configuring an S3 bucket in Veeam using an ExaGrid appliance on-premises. Despite my best efforts, I couldn’t find any detailed documentation or guidance on this specific setup

Here’s a brief overview of what I’ve done so far :

- I have an ExaGrid appliance configured and operational on-premises.
- Veeam for Office 365 is installed and running, and I’d like to use the ExaGrid appliance as an S3-compatible object storage for backup repositories.

I’m unsure about:
- How to integrate this with Veeam to create an object storage repository.
- Any potential pitfalls or best practices specific to this setup.
If anyone has experience with a similar configuration or can point me toward useful resources, I’d greatly appreciate your help.

Thanks in advance

[Polina]

Hi,

To add an S3-compatible repository, please follow the steps described here: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80
For general considerations and best practices, see: https://bp.veeam.com/vb365/guide/buildc ... orage.html
For the (unofficial) list of compatible object storages, see: post438369.html#p438369

[AbdelO]

Thanks, but I'm having another problem with my backup taking so long. I saw that there were some actions to do on the M365 side (EWS) and that it was recommended to add several auxiliary backup applications (I created 5) the time of the first backup (Full), but despite that, it's still too long.

Knowing that I have 2 fortigate firewalls that manage my Internet output and that I have no traffic shaping. Are you aware of any best practices in this situation? I've consulted the various Veeam sections (BP, Helpcenter...) but apart from what I've already done, I can't find anything more.

Thanks in advance

[Polina]

How do you estimate if the backup takes too long or whether it's an expected and normal speed? The initial full backup always takes time, and often is impacted by Microsoft throttling as well.

Throttling limits vary depending on the tenant size (larger tenants get more released throttling limits). For Exchange, it used to be possible to request a temporary turn-off of throttling, though I'm not sure if it's still relevant today. Auxiliary applications work only for SharePoint data (they have no impact on Exchange due to the difference of how throttling mechanisms are applied to different workloads), and today it's not recommended to have more than two such apps (i.e. you have one app which you used to add your organization to VB365 and you can configure one more auxiliary app).

[AbdelO]

Hi Polina,

We're still having problems with our Veeam Exchange Backups. Despite having put in place all the necessary prerequisites (adapted infrastructure, optimized configurations, etc.), backups are still very slow.

What's more, we encounter recurring errors that we don't understand:

- Processing mailbox <mail@org.com> failed with error: Mail item data export failed. Unable to read data from the transport connection: An existing connection must have been closed by the remote host... An existing connection must have been closed by the remote host.
- Processing mailbox <mail@org.com> failed with error: Mail item data export failed. The operation has timed out.

Out of 800 items, only 240 are successful, with proxy pool with 2 windows servers (each with 8 vCPU and 16GB RAM) and in terms of bandwidth we're averaging 6-9 MB/s. Total volume is around 2TB.

A case is underway at Veeam... but still no answer.

Thanks in advance

[Polina]

Hi AbdelO,

Please provide your case ID so that I could check it internally.

Also, the recommended proxy configuration is 8 CPU/32 GB RAM - I'd suggest you add more memory to your proxies for better performance.

Thanks!

[AbdelO]

Hi,

Here is the case ID #07530481

I'll try to add memory to the proxies

Thanks!