Search results

Hi Was there any conclusion to this? Is this resolved with a specific QEMU or kernel version?

It's not an ideal solution, but all I did was : # mv /usr/sbin/smartctl /usr/sbin/smartctl.orig and then I forced it to return a 0 exit status by putting the following in /usr/sbin/smartctl #!/bin/sh /usr/sbin/smartctl.orig $* exit 0

And a final comment, this update is now available on the enterprise repo as libpve-access-control_7.2-4

We configure our vdisks with "discard=on" via the web UI which I assume is the same thing you are referring to. Our ceph cluster is 100% NVMe.

Just to close this thread out, after an unfortunately slow start, the Proxmox support team have been working well on this problem. It appears to be a bug regarding a rare race condition in the rotation of the auth keys. There's discussion of a patch on the dev mailing list. Let's hope this...

Hi Installing the dashboard on our lab cluster was very simple. But it doesn't show any of the performance or monitoring data I was looking for. The Ceph documentation says to just enable it with cephadm but that's obviously a bad idea on a PVE orchestrated ceph cluster. So is there a PVE...

Tom, no you are wrong, please re-read the ticket. If we are logged into the Web UI we get errors in the VM status pane etc. Eventually we just get kicked out of the Web UI and we have to try to log in again, which may or may not work. So it's a PVE problem. At the same time we are seeing...

No, your proxmox team sadly. Anyway, got any suggestions or some education as to how the ticket auth works so we can try to figure this out?

I've tried to get help with this via a support ticket but the responsiveness has been absolutely terrible and the information unhelpful. So, I'll ask here. We are seeing the dreaded "Invalid PVE ticket (401)" yet again. It happens every couple of months for no reason we can find. Restarting...

Hi. Sure, I'll open a ticket for this. As far as inconsistency is concerned, yes, it's not ideal, but in this case it's better than the issues caused by the fs-freeze. It's basically the same as backing up a VM that isn't running the agent, or grabbing a SAN snapshot, or a ceph export, or...

We've made a simple change to the QemuServer code in VZDump and have resolved the problem for us. It's not elegant but it'll do for us to continue testing PBS without breaking customer SQL backups. Adding this properly would be super simple, either as a "no-freeze" backup mode or a "Dont use...

Disabling the guest agent isn't ideal as We'll need to coordinate a VM stop and start with all customers to disable it We use the agent functionality for other things We agree the fs-freeze has "unwanted side-effects" on windows so can you provide us an option that does a backup without...

Does the agent play any part in guest memory ballooning ?

Ok, thanks for the info. Look like we can only really move to PBS once the windows agent gets the new feature, and we get our clients to upgrade the agent on the windows VMs, and get the clients to set a custom reg key. That's not going to happen quickly at all. Shame.

Look like this guy had the same problem but wasn't doing differentials so it didn't break things. He's still seeing the SQL backups that are being triggered by the PBS backup. https://forum.proxmox.com/threads/phantom-sql-backup-job-related-to-pbs-backup.103210/

Hi No, there's no VEEAM involved. The customer is just running normal "Full / Differential / Translog" backups locally. It's happened twice over the last 4 days and both times the SQL backup logs clearly show that a backup was triggered exactly when PBS started a backup of the VM. The...

Hi After a couple of weeks of testing we're pretty impressed by PBS. We've started running it in parallel to our usual backup process on some production customer VMs. We've just started seeing a problem triggered by PBS that I believe is the interaction of the QEMU GA under Windows and MS...

Ok, understood. Thanks for the clarification. We may run it more frequently then :)

Oh, so if you delete a backup from the PVE storage it doesn't delete the chunks even if that was the last reference to the chunks? I assumed the chunks would be reclaimed as soon as nothing was actually using them. Are you saying that running the GC is the only way to reclaim that space?

Ok, thanks Fabian. So if we are only backing up from PVE and we are using a per-job retention config, we don't need to rely on PBS pruning at all, and GC should be run every now and then just in case something's left unreferenced?