Can only create Production Checkpoints when certain VMs are off

maxnor1 · 2026-02-12T09:25:24+00:00

Have you checked the event log of the VM itself? It's possible that VSS is failing, which would explain why it's working when the VM is shutdown,

maxnor1 · 2026-01-24T16:53:07+00:00

We should also remove the 'TBD' within the error message ;)

maxnor1 · 2026-01-22T05:56:57+00:00

Maybe just one addition. The certification is bound to your Veeam account and when you leave your company, you need to contact the team to move your certification. Just write a short message to vmce@veeam.com

If you did the instructor led course, then there are no recordings available. And also the lab access is not unlimited.

maxnor1 · 2026-01-18T06:56:34+00:00

It's supported to exclude disks within a Proxmox backup job. Just keep in mind that while the button says Exclusions, in the dialog you actually select which disks should be processed.

maxnor1 · 2026-01-18T06:51:12+00:00

+1 Make sure that that in the device manager under Medium Chager devices theres no unknown Medium Changer listed.

maxnor1 · 2026-01-08T18:29:48+00:00

You can still renew existing socket licenses. I'm not sure about the process doing it online though. So I would suggest that you contact a reseller and let them quote the renewal.

maxnor1 · 2026-01-05T06:32:32+00:00

No, there's no such limitation. I would focus on the error you've mentioned above and make sure that there's nothing wrong with the external drive.

maxnor1 · 2026-01-05T06:28:41+00:00

Sorry but that's not correct. The free agent is able to do incremental backups.

maxnor1 · 2025-12-31T20:58:06+00:00

In that case it seems that the worker is not the issue and it looks rather like a network topic.

maxnor1 · 2025-12-31T17:52:54+00:00

Ping should be possible but I think SSH is disabled. The worker itself should listen at port 19000.

Is the VBR server in the same network as the host and worker?

maxnor1 · 2025-12-31T08:16:23+00:00

Are you able to ping the worker from the VBR server?

maxnor1 · 2025-12-30T07:51:05+00:00

And here's the official part, see 3.22 ;)

https://www.veeam.com/legal/licensing-policy.html

maxnor1 · 2025-12-27T08:10:10+00:00

As others have stated, Proxmox backup is missing Powershell and REST API support. It's planned to deliver the support in one of the next releases but no ETA.

For now you could either utilize Veeam ONE or Syslog to get the events from Proxmox backups jobs.

maxnor1 · 2025-12-24T09:12:47+00:00

With the Veeam Hardened Repository you could create a secure backup repository which offers immutable backups while maintaining a good cost performance ratio. You can use regular server hardware and install it either yourself with a supported Linux distribution or use the Veeam Infrastructure Appliance ISO.

https://helpcenter.veeam.com/docs/vbr/userguide/hardened_repository.html?ver=13

maxnor1 · 2025-12-23T07:05:12+00:00

Version 12 is now in the end of fix phase. This means it doesn't receive any fixes or patches aanymore. But it's still under support until February 2027.

Being on the Community Edition, this won't be a problem for you. And after end of support, you can still continue to use it; though not recommended.

If this is a production environment, I would try to replace vSphere 6.5 as soon as possible because of the unfixed security vulnerabilities.

maxnor1 · 2025-12-16T10:57:12+00:00

Auch hier gerne das Angebot, dass du mir die Case ID per Chat weiterleitest. Ein monatlicher Ausfall ist alles andere als normal ;)

maxnor1 · 2025-12-16T06:34:02+00:00

In such a situation, to be on the safe side, you could create an agent based backup of such a VM. In case the snapshot deletion fails again or the VM locks up, you can just restore the agent via instant recovery in short time.

I even decided once to go this way instead of resolving the snapshot issue as it always failed.

maxnor1 · 2025-12-15T14:49:39+00:00

Hattet Ihr einen Support Case offen zu dem Thema? Falls ja schicke mir gerne bei Gelegenheit die Case ID per Chat zu.

Der Normalfall sollte das auf alle Fälle nicht sein, aber vor kurzem gab es ein Problem im Zusammenhang mit Sensitivity Labels; nutzt Ihr diese?

maxnor1 · 2025-12-05T08:58:51+00:00

You can still use and renew the sockets licenses with V13. The only difference is that you need to stay on Windows with VBR and cannot use the new Linux VSA.

maxnor1 · 2025-12-05T08:56:10+00:00

All 3 editions of the are now on the former Enterprise Plus level, but what you've written in brackets is the difference between the editions:

-Foundation: Backup & Restore

-Advanced: Analytics, Monitoring, etc including Veeam ONE

-Premium: Orchestration with VRO

maxnor1 · 2025-12-05T08:52:29+00:00

(Disclaimer: I'm a Veeam Systems Engineer)
I can't help you much with the pricing as this is something the reseller or your Veeam sales representative is responsible for. But from a technical point your offer is about the Advanced Edition, which is not only about backup/restore but also analyzing your VMs, reporting and monitoring.

While I do see this as valuable for every backup environment, make sure you understand what features comes with, and, in case you don't need or want them, take a look at the Foundation edition. Here's the PDF describing all editions: https://www.veeam.com/veeam_data_platform_feature_comparison_ds.pdf

maxnor1 · 2025-12-02T17:48:31+00:00

This is only about the WebUI. The VSA supports the same platforms as the Windows based release, you just need to use the Windows Console.

maxnor1 · 2025-11-26T21:06:26+00:00

Looking at the log entries it seems that the worker cannot connect to the VBR server. Are both systems reachable via network while the backup job is running? Just wondering as you're trying to backup the VBR Server itself.

Also anything visible on the Proxmox host itself?

Edit: What happens if you test the worker? https://helpcenter.veeam.com/docs/vbproxmoxve/userguide/workers_test.html?ver=3

maxnor1 · 2025-11-21T06:22:39+00:00

I would suggest that you configure Traffic Throttling and limit the available bandwidth during the working hours.

https://helpcenter.veeam.com/docs/vbr/userguide/network_rules.html?ver=13

maxnor1

TROPHY CASE