Hi all,
I'm looking for a way to automate Proxmox backup job creation in VBR based on new Resource Pools appearing in Proxmox VE.
The target workflow would be:
1. Detect new Pools in Proxmox.
2. Create a backup job per Pool (job name = Pool name) with 15-day retention on a given repository.
3. Add the new job as a source to an existing Backup Copy job to keep the infrastructure consistent.
I checked the VBR 13 Swagger (v1.3-rev1) and couldn't find anything Proxmox-related:
- `EJobType` enum does not include any Proxmox value.
- `JobSpec` discriminator mapping has no Proxmox entry, so POST `/api/v1/jobs` rejects it.
- `EManagedServerType` and `EInventoryPlatformType` don't list Proxmox either.
- The only Proxmox reference in the whole spec is in `ELicensePlatformType` (licensing only).
So a few questions:
- Is there any ETA for Proxmox job management in the VBR REST API?
- In the meantime, is the supported workaround to drive this from the PowerShell module (Veeam.Backup.PowerShell) on the VBR server? Are the Proxmox-related cmdlets considered stable for production automation?
- Any other approach the community is using today for this exact scenario (new Pool → new job → attached to Backup Copy)?
Thanks!
-
edh
- Veeam Legend
- Posts: 511
- Liked: 171 times
- Joined: Nov 02, 2020 2:48 pm
- Full Name: Manuel Rios
- Location: Madrid, Spain
- Contact:
Automate task Proxmox Pool to Veeam
Service Provider | VMCE
-
Mildur
- Product Manager
- Posts: 11808
- Liked: 3331 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Automate task Proxmox Pool to Veeam
Hi Manuel,
Proxmox does not yet support a REST API, as you already found out.
V13.1 will add API support for a few important GET endpoints, but PUT endpoints are not expected in v13.1.
PowerShell cmdlets are also not available.
Right now, we prioritize the REST API over PowerShell.
Best,
Fabian
Proxmox does not yet support a REST API, as you already found out.
V13.1 will add API support for a few important GET endpoints, but PUT endpoints are not expected in v13.1.
PowerShell cmdlets are also not available.
Right now, we prioritize the REST API over PowerShell.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 134 guests