Backup for Office365 with VBO
First release of Veeam Backup for Office365 powered backup now integrated into our multi tenant portal.
Blog
JobSession link bug in Rest interface Veeam Office365 Backup
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.
Veeam Backup for Office 365 REST API - The object has not yet been initialized
Are you getting a weird "Object has not yet been initialized" with a fresh install of Veeam Backup for Office365? Simple solution.
Service check and restart after Veeam Backup job has run (post-thaw)
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
Trying the new JSON payload super powers in Veeam Update 4
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
New TenantType node in CloudTenant Schema with Veeam Update 4
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.
Hotfix for Inoperational RESTful API v1_3 & 1_4 support with Veeam Update 4 RTM
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.
Veeam API JSON Support in Update 4
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](/.netlify/images?url=%2Fcontent%2Fimages%2F2019%2F01%2FVeeamCode.png&w=960&h=480)
Node [root] does not exist - Veeam API with Update 4
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.