Proxmox Backup Job - Full VM not possible

[telnetrix]

I have a job with approx 24 virtual machines that has been running for several months. During a maintenance operation, we purged a GFS copy of one of the VMs (ignored the warnings), and have broken the chain.

We do have offsite copies of this backup stored in Wasabi, so recovery is still possible, but current backups are broken. I attempted to run an active full on the job, but this vm still fails with a missing server.vbm meta file.

As a temporary work around, I created a new job just for this VM and did a full backup into a separate folder.

How do I get the original job to see this server as a "new" server, or otherwise start a fresh full backup?

[david.domask]

Hi telnetrix,

Sorry to hear about the challenges here; the situation sounds a bit unexpected with regards to the job failing with a missing VBM file -- the VBM file is metadata for Veeam backups, and it sounds like you deleted the backups from Veeam itself, correct? (Hence the warning you got)?

Please open a Support Case and let Veeam Support review the situation and see if there isn't a way to recover the original backup chain or at least resolve the missing VBM error. Be sure to include logs for Support to Review.

Please share your case number once created. Thanks!

[telnetrix]

Since we had multiple offsite copies, we did a full reset on the local storage. I didn't trust the chains since warnings where ignored and knowing that the proxmox backups behave differently than other backups in regard to directory structure.

Normally the hardened repository has the job name as a top level folder, and then the VM name under that. With proxmox all backups are stored under the VM name itself, and the job name is not used.

This may be an oversight on the R&D side, and if so, I would prefer to see it consistent with other backups.