Recent content by eTIC

Hi. In my case above, I have found a temporary solution that has worked well for me. As simple as restoring one of those 8-hour backups to a new VM. From that moment on, the backup time has been reduced to 35 minutes. The reason why it has been solved, would be related to some problem in the...

I had the same error a few days ago. A VM with a Windows Server showed a similar problem. In my case the backup managed to finish, but it went from 45m before the error to 8 hours, with transfer rates for read/write of 10MB/s instead the 180MB/s as in previous days. My Proxmox version: 6.2-4...

HI, Attached is the result of the operation carried out without the need to reboot the 3 nodes in HA in an production enviroment: Commands launched ON EACH NODE: service pve-cluster restart && service pvedaemon restart && service pvestatd restart && service pveproxy restart (Origin URL)...

Thks, I´ll try this night apply that solutions.

Yes, now are unmounted. No, I didn`t restart yet that services with: /etc/init.d/pvestatd restart /etc/init.d/pvedaemon restart I wanted to know if it's safe and if that could be the solution to not rebooting the nodes before doing anything. It's a production environment. Two more questions...

Those NFS storage are no longer in /etc/pve/storage.cfg. They were previously removed by me from Datacenter > Storage

Hi, Yesterday, 3 storage units destined to NFS backup lost connection and their status are gone. With the intention of recovering those states again, they were remounted with the only command that allowed it: umount -f -l ... what happened next, is what I show in the attached picture...