Overview
Veeam Backup & Replication is backup software rather than storage. It runs backup jobs against virtual machines, physical servers with agents, file shares and cloud workloads, writes restore points into backup repositories, and records the outcome of every session. The information it holds is about protection state: which workloads are covered by a job, when each one last produced a good restore point, how far back the retained restore points go, which sessions failed and how much space each repository has left.
The ReadyWorks connector is a JSON REST client for a Veeam management endpoint, running on the json_rest_api.php driver. You supply the API domain, a username and password and a server-side working path, and it authenticates with a Base64-encoded HTTP Basic header. Veeam exposes more than one REST surface depending on which components are deployed, and they do not all accept HTTP Basic for the data calls, so confirm which endpoint your deployment presents before you build jobs against it.
Backup state is one of the more valuable things to hold in the estate because it gates action rather than describing it. A device that has no recent restore point should not be migrated, rebuilt or decommissioned, and in most organisations nobody can answer that question quickly across the whole estate. Reconciling Veeam’s protected-workload list against the ReadyWorks device inventory exposes the gap in both directions: machines that exist and are not being backed up, and backup jobs still running against machines that were retired months ago. Repository capacity and job failure history feed the same readiness view.
The connector is registered as bidirectional. Inbound jobs pull Veeam records into staging. The outbound side posts a record from ReadyWorks to an endpoint you nominate and captures status, message and record key from the reply. Neither direction ships with a Veeam endpoint configured.
NOTE: Veeam data ages faster than most estate data. A restore point that was current last night is stale evidence by the end of the week, so schedule these jobs at least daily if you intend to use them as a readiness gate.
Connector Properties
Authentication Methods
Veeam offers a single authentication method, using a username and password sent as an HTTP Basic credential.
Method 1: Basic Authorization: Username / Password (VEEAM_a8ea7747de)
Connect to a GET method API with a username / password
Joins the connection’s username and password, Base64-encodes them and sends them as an Authorization: Basic header. Use a Veeam account with a read-only role so that ReadyWorks can read job, session and repository state without the ability to start, stop or delete backups.
Connection Configuration Fields (5)
Authentication Configuration
Headers sent on the authentication call:
cURL options:
NOTE: Username and Password are both marked optional even though the Basic credential is assembled from them, so a connection can be saved with no working credential.
NOTE: There is no Single Authentication control on this connection form, so the authentication phase repeats on every pagination and enumeration loop.
Inbound Job Fields Enabled (44)
Inbound jobs expose the full REST field set, including three levels of enumeration and all five pagination modes.
NOTE: Several labels and tooltips in this form carry defects inherited from the shared ETL5 field templates: the Enumeration 1 Node label reads “Enumaration”, the Append New Data label reads “Exisiting”, and the help text on Enumeration 1 Keys End Point and Enumeration 3 Fields both refer to enumeration 2. The underlying fields behave as their labels say.
Outbound Job Fields Enabled (13)
Outbound jobs expose the REST posting field set, including the outbound field list, the return data mapping and an optional raw JSON body template.
Inbound Job Templates (1)
Veeam ships one inbound template, and it is the generic REST skeleton rather than a backup job, session or repository pull.
Job Template Configuration
Settings
NOTE: Session and restore-point collections grow with every backup run, so any job cloned from this template needs both a Pagination Type and a date or session filter before it is enabled.
Outbound Job Templates (1)
One outbound template ships, and it is the matching generic REST skeleton.
Job Template Configuration
Settings
Job Parameters and Enumeration
Rest POST API
Outbound fields list:
Return data fields: