With support now baked into v4 to backup Office365 data into object storage providers will be looking at migrating their block-backed repositories. Here is a quick run down of how to add one.
How to configure reverse proxy using IIS Application Request Routing with SSL Offloading to a Minio Server (or any other internal web service)
First release of Veeam Backup for Office365 powered backup now integrated into our multi tenant portal.
If you fetch the job sessions for a job, the link for "log" is incorrect, have logged with Veeam which will hopefully patched in a future release.
Are you getting a weird "Object has not yet been initialized" with a fresh install of Veeam Backup for Office365? Simple solution.
I came across an set of application servers in an environment which were not fault tolerant at all to service disruption at all. Most often caused aro
We now know with Veeam U4 you can specify an application/json accept header [https://benyoung.blog/veeam-api-json-support-sort-of/] and have your req
Starting with Veeam U4 and assuming you are logging in with either v=latest or v=v1_4 there are some modifications you will need to make for editing cloud tenants.
Last week was pretty frustrating, debugging and discovering an issue / new "feature" with JSON support which broke some things. After resolving those I was still seeing having an issue with CloudTenant editing.
While testing our integration library and immediately running into issues I discovered some weirdness if the json accept header was specified (anywhere) that some requests failed it got me thinking. What if they now supported json, wouldnt that be nice! No more clunky XML to deal with.
![Node [root] does not exist - Veeam API with Update 4](/content/images/2019/01/VeeamCode.png)
Fired up some debugging and realised that most of the GET requests looked ok, but any of the POST and PUT requests started throwing HTTP 400 Bad Request Errors.
