Search results

And what about your Proxmox version? Is it updated to the latest release?

Ok, thank you all for your comments.

Have you tried to disable Qemu Guest Agent on the virtual machines or update it to te latest version?

Then for a production environment will be better to use Windows Serve 2019 until 2022 is more stable over Proxmox, right ?

It is advisable that you make backups too, because if the SSD disk gets corrupted you will loose all your virtual machines. With a PBS (Proxmox Backup Server) server you can make backups of your virtual machines keeping several versions for each VM and even sync these backups to a remote location.

It seems a hardware issue. I understand that when this happens the only solution is power off/on the server, is it right ? Do you have an IPMI interface or similar? If the answer is yes, then you can access it and see analyze the logs, maybe you can find the explanation to the problem here.

I agree with this, exposing IPMI to the internet is like leave your home's door open all the time. It is better access IPMI using a VPN.

Maybe this can explain the infection. Do you have PBS (Proxmox Backup Server) for recover the VMs? We have customers with a PBS and backups every hour for minimize the consequences of infections like this.

You are welcome!

TCP port 8007, you will have to NAT this port.

Knowing which file-encrypting Trojan perhaps helps to solve the mystery. Which one?

Hi, where is the Proxmox log ? I think you forgot to include it in the post.

You can use monitoring tools like checkmk for monitor CPU temperature and lot of critical parameters of your Proxmox server.

Creat! Good luck and if you need more help do not hesitate to contact me again.

I don't see any problem using HDD for Ceph, but have in mind that the I/O performance would be better if you use SSD or NVMe disks instead. If you have different kinds of disks (for example, HDD and SSD) you can create pools that use only HDD disks and pools that use only SSD disks. This way...

Hi, I think that a Proxmox cluster using Ceph as the distributed filesystem is a perfect option for you. With this setup you can have all your VMs replicated in all hosts using a Ceph pool and in the event of a cluster node failure you will be able to start the virtual machines in the other...

Ok, great. Thank you very much for your help.

Conclusion: The optimal solution for our scenario is: Setup the Proxmox/Ceph cluster to make backups over the LOCAL PBS. In the LOCAL PBS setup the prune policy for keep the last 30 snapshots, 24 weekly and 12 monthly. Setup a sync job in the REMOTE PBS for sync the datastore from the LOCAL...

You are welcome. I think that the best and simplest solution is the multiple dirty-bitmaps, but meanwhile the solution I have explained can be valid. But I would like that the Proxmox staff confirms that it is right.

Correct. I think that the Proxmox team is making changes for allow several bitmaps for avoid this problem, but I don't know the status of this development. Perhaps some of the Proxmox staff members may inform us about it.