Search results

I can't say for certain, but unfortunately the issue may just be down to your raidz2 array and the design of Proxmox Backup Server. The backup process intercepts write calls from the VM and backs up the relevant block [1]. We cache some blocks in memory, but generally if the backup storage is...

Sorry, I meant to check the containers weekly report, to see if any spiked in memory. It shouldn't be too tedious as one you change the period for one, it sets it for them all. Ah I hadn't considered it with ZFS, but yes I guess there are still some issues there.

The message indicates a process was killed though, which may have been why everything looked normal following the incident. In the top right corner of the summary page, you can set the time resolution of the graphs from hourly to weekly. Could you do this and check if you can identify the spike...

Yeah in all regards it looks fine. Are you still seeing the out of memory logs? I would keep an eye on it over the next days, to see if you notice any gradual increases or memory spikes.

Hi, sorry I couldn't get to the question in time, but I'm glad the recovery process went smoothly :) I can't say I have much personal experience with USB passthrough, but I haven't come across many recent issues with it. Are you using Host or Spice USB passthrough? Could you also post the...

Given your description, the Proxmox VE cluster doesn't sound like the issue, and if there is a dedicated link to the Proxmox Backup Server, a bandwidth limitation on Proxmox Backup Server shouldn't be necessary. Could you provide some more information on your backup server, such as disk types...

Not a command, but if you go to the "Search" panel of the node or datacentre, you can get a good rundown of stats for each running guest.

Are the VMs also located on an NFS? You could try limiting the network traffic to the Proxmox Backup Server [1], so that the network is not saturated during the backup. [1] https://pbs.proxmox.com/docs/network-management.html#traffic-control

Can you still see the disk virtual disk in whatever storage HP1 was using? If so, it may be possible to recover the VM by moving the VM's config file back to HP1. You should be able to move the config by powering off the VM and then running: mv /etc/pve/nodes/HP2/<VMID>.conf...

Hi, Do you know what was running on the host/vm which led to the issue? Have you tried rebooting the VM? Can you post the output of pveversion -v and cat /etc/pve/qemu-server/100.conf?

It looks like you started the installer in "Debug Mode"? You should instead select the option "Install Proxmox VE". In the screenshot, it says that you can type 'exit' or press CTRL-D to continue with the startup. You don't need an external graphics card for Proxmox VE :)

Unfortunately there's no easy way to convert the backup files to PBS as PBS uses an entirely different storage mechanism, in which data is stored in small separate chunks [1], whereas tar/VMA is a full archive of a single container/VM. If you would like, you can still store the old backups on...

Sorry, I clearly needed a bit of coffee yesterday. The linked forum post seems irrelevant to your issue (as it deals with an actual failed mounting of proc).. Could you try changing this to create=dir (see lxc.mount.entry [1])? [1]...

From this screenshot, it doesn't look like it. /usr/bin/kvm relates to one of your running virtual machines. I don't recognize the command running under it, as it's been cut out of the screenshot. But it may be worth looking into, if it was taking 14% of your system memory. Apologies, I misread...

I believe it's only run when you're on the VM's summary page, as Proxmox VE gets the guest IP address information using the guest agent. I'm not sure you can (or should) disable guest-agent logging messages.

You can either run pvesm set <storage> --preallocation off or set it from the "advanced" options of the edit storage window.

There's another recent thread [1] where users experienced similar issues. For some it was due to a non-default 'proc' entry in /etc/fstab, and for another it was due to some third party software. Can you take a look at it, and see if it helps with your issue? If not, please post: pveversion -v...

If you run top -c on the host and press 'Shift+m' you can sort processes by the percentage of memory used (top's '-c' flag shows the full command).

To some extent, it's a standard/expected. While it is possible to create some file systems directly on a block device (I believe ZFS creates partitions automatically), you don't really gain anything from it. On the other hand, without a partition table, some OSes may be confused by the device...

While there is no direct "move snapshot" functionality, you can configure a remote [1] with 'localhost' as the address, and set up a sync job [1] in order to pull data from another local datastore. As of Proxmox Backup Server 2.1, you can also configure group filters [1] for a sync job, from the...