Cloud Provider Integration

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 around the time the virtual machine was

veeam

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 and have your requests returned as a nice JSON payload which is neat.In a super basic example here

veeam

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.

veeam

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

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, wouldn't that be nice! No more clunky XML to deal with.

veeam

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.