Proxmox jobs - no way to MAP a backup to a job

[mdiver]

Faster than expected we have the first customers using the Proxmox integration productively.

While migrating a repository with Proxmox and vSphere backups inside, I just realized that there is no map backup functionality for the Proxmox jobs.

So, we have to go through another full backup now.
Any reason why this is missing here? Or does the engine maybe map files automatically, if they are sitting in the repo?

Thanks,
Mike

[nathano]

you mean mapping a pve job to a vmware job backup?

[rovshan.pashayev]

Hello @mdiver

We are actively working on improving the product and upcoming releases will bring additional features.

[mdiver]

you mean mapping a pve job to a vmware job backup?

I actually meant mapping Proxmox to Proxmox.
Cross-HV-mapping would not make sense, I guess. You need some V2V process here.

Best
Mike

[nathano]

ah yep, I've re-read your original post now.

another little annoyance I found is when you create a new pve job and want to use the resource pools to define the VMs (until tags are supported), it only shows you pools that have VMs in them. not empty ones. doco mentions it (although have suggested wording is tweaked) but still a bit annoying when you want to setup all the jobs in advance..

[rovshan.pashayev]

Hello Nathan,

As you mentioned, your feedback regarding resource pools is off-topic, but nevertheless, it has been noted.

[FrancWest]

Hi,

just as with v12, in v13 the map backup option is missing for Proxmox backup jobs. Is there a technical reason for this? When migrating to a new server without doing a configuration restore, I'm unable to use my existing backups.

Franc.

[Mildur]

Hi Frances,

I've moved your question to the existing topic in our Proxmox subforum.

There's no "technical reason"—the feature was simply never implemented for Proxmox workloads.
Your request is noted, but there's no ETA for this feature yet.

Thanks,
Fabian