Recent content by hmelgers

The first one ooks very similar. Didn't know the vm speed became the same as pbs, is that the case even in snapshot mode ? This would make using a remote PBS less attractive for busy vm's. Concerning your theorie, yes. I guess the VM OS stayed in that state till the reboot with some kind of...

yes, only because of processes failing suddenly. Turns out it actually was never rebooted yes, no particular reason besides inexperience. We will do that asap, thanks for the remark!

Network storage: Theoretically yes, but the storage is on the LAN while pbs is on the other side of the country. Also, we have other vm's running on the same storage that kept running (and backup) without problems. There's one thing that stood out in the PVE syslog and that was an old nfs...

We just experienced the exact same thing, never saw it before on pbs1 but we updated to pbs2 last week. The backup failed with "backup write data failed: command error: protocol canceled", I suspect because of some network timeout (the pbs is on another location). That does happen sometimes...

Running a cluster on NFS One of the guests (Ubuntu 20) does also have shares on 2 nfs servers that are also mounted on PVE for f.i. iso or images. Both PVE and guest are on the same network 10.0.1.x and are using the same ip's (10.0.1.8 & 10.0.1.50) After a network failure a couple of weeks ago...

You're absolutely right Dylan, that must be the cause. I do have another 301 from that different user, wasn't aware that id was all leading. It would be nice to have some prefix digits for each vm on a pve to be set to avoid these kind of circumstances. Thanks for your help!

Hi, I'm running a 3 node pve cluster that use the same pbs. After adding a first vm to a second node and trying to backup i get this error: 301: 2021-09-01 20:00:02 ERROR: VM 301 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (evuser@pbs !=...

Could it be some timeout setting ? I notice both messages follow 15 seconds after starting the backup job

Hello all, I keep getting these annoying errors when running a backup voor all vm's in proxmox. I've searched on the forum but i couldn't find a real solution for the problem. This machine has been running without issues for months, then suddenly these errors started to show up for some vm's...

The webinterface came back after the backup nfs got online again. Thanks for your help!

Will do, but a question in general, how safe is restarting those ? I need to be sure no vm's will go down doing this. I'm waiting for new hardware for the backup server and i don't want to end up with a failing server and no recent backups available.

Thanks spirit, but that didn't work (after login spinning wheel, then network error). Or did you mean remove ALL nfs storage from storage.cfg ?

Noone ? I get the login screen but nothing happens after login.

Last night I had a failing nfs server while this proxmox was backing up to it. The server is still operational with all vm's running. I killed the vzdump processes but the webinterface shows nothing but greyed out questionmarks. Of course this has something to do with the failed nfs mount. I...

Totally overlooked that one, thanks!