Search results

Thanks again @dakralex !

So if backup works, I can safely set the service QEMU guest agent VSS to start manually and I'm good to go, did I understand correctly?

Hi @dakralex! I don't see any problems with backups, but it seems important that these two services are running: in the Windows section of the Proxmox documentation for Qemu-guest-agent, I read: " After that the qemu-guest-agent should be up and running. ... ... If it is not running, you can...

Hi @dakralex I went to fix the clock synchronization and now Proxmox/DC1/SRV1/SVR2 synchronize with the same NTP server. Attached are QEMU logs of the three Windows Servers and Proxmox backup task logs, all related to a backup that I manually performed at 22:30 last night and the automatic...

Thanks again for your help @dakralex File task-pve3-vzdump-2025-02-28T02_00_03Z.log are the Proxmox logs of the last backup task, which is performed at 3am. I wrote a PowerShell script to extract logs containing the string "QEMU" from the "Application" and "System" Windows event registers. The...

The problem was not solved even by uninstalling and reinstalling the VitIO drivers via the "virtio-win-guest-tools.exe" program located in the root of "vitio-win-0.1.266.iso". Even though the "QEMU Guest Agent VSS Provider" service is stopped, backups seem to continue to run without errors: is...

Thaks for your answer @dakralex Following Windows Guest Best Practices 2019: installing Windows I install the driver for disk (vioscsi\2k19\amd64), network (NetKVM\2k19\amd64) and balloon (Balloon\2k19\amd64) after installing Windows I installed Qemu Guest Agent...

In Proxmox 8.3 I created two VMs with Windows Server 2019 enabling "QEMU guest agent" in Options. In the VMs I installed QEMU guest agent (108.0.2) and set the related services to start automatically at boot. Every morning in these two VMs I find the "QEMU Guest Agent VSS Provider" service...

For some reason the VM disks were located in the OS partition and this was causing the problems...

In a new installation of Proxmox 8.3 I created two VMs with Windows Server. Copying a few GB of files from one to the other, the copy process freeze. Then I noticed that sometimes even the Proxmox interface stops responding (moving in the menus I see the "Loading" message and then "communication...

@_gabriel @cwt Thank you very much! In fact, storage is done with HDD....I will go in depth with Gabriele's suggestions (I don't use Windows much and honestly I wasn't aware of these things ... thank you again!)

I have Proxmox 8.3 on a HP Proliant server with RAM: 128GB and CPU: 48 x Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2 Sockets) No matter how I tried to configure a VM with Windows 11, I always get an extremely slow machine. I use VirtIO drivers for disk (on local zfs filesystem), network and...

Thank you @Fantu ! I discovered the problem: the NAS where these machines are stored was rebuilding the damaged RAID5,

I just updated PVE 8 and after rebooting my two Windows VMs (Windows10 and Windows Server 2019) are stuck (it's been 30 minutes and I'm still waiting to see the login screen appear on the console ...). These are machines configured following best practices (VirtIO driver, host CPU, WriteBack...

My intelligence is well below average (I am not joking), but I try to work hard. Before asking here I searched on the Internet, as I am used to doing, but I couldn't find the solution. Do you want to help me? If you found something, all I need is the link. Thanks in any case

I installed Zimbra mail server in a container where I added a second network interface with an IP in the management VLAN (192.168.10.0) and configured Zimbra to expose its administration interface on this subnet. ip route default via 192.168.10.1 dev eth1 192.168.1.0/24 dev eth0 proto kernel...

Fixed! There were two issues: - the service Type, which being a backup should be oneshot - the timeout settings were probably the cause of the shares being umounted (credits: ChatGptO)

Here I am... From CLI everything is ok: Starting backup: [mainstorage]:host/pbs1/2024-05-11T06:55:01Z Client name: pbs1 Starting backup protocol: Sat May 11 08:55:01 2024 Downloading previous manifest (Mon May 6 15:49:42 2024) Upload directory '/mnt/nas/mainstorage/myshare1' to...

I managed to configure everything, but there is something that doesn't work (which makes me think it is necessary to perform some kind of "reset"). This is what I see after starting the systemd service that run the backup: This is what I see after the backup has finished (ie: no backup...

Thank you very much Chris!