When using object storage the data is being processed at the proxies. Metadata is stored in a cache based on a JetBlue database, before the actual data is written to the object storage target. The cache is being used intensively during every backup run to compare the source data with the target data.
The following diagram shows the flow of data with the major firewall ports. Please see the Helpcenter for a complete list of the firewall ports.
When objects are written to an object storage target they are checked for consistency. The process can be described in the following way:
- Veeam Backup for M365 downloads the data from Microsoft M365
- Veeam Backup for M365 create the objects, and calculates a MD5 hash on the objects
- Veeam Backup for M365 then sends the objects to the object storage (AWS/ Azure/ S3-compatible)
- The object storage itself calculates also a MD5 hash and returns it to us.
- If that matches our calculated hash, the data is written away correctly
When using local storage the data is being processed at the proxies and written to JetBlue databases as a target.
The following diagram shows the flow of data with the mayor firewall ports. Please see the Helpcenter for a complete list of the firewall ports.