One installation of Proxmox is running 5.1-41, we were having issues with backups growing larger (presumably because of un-reclaimed space). We made sure all the Server2008R2 VM had "sutil behavior set DisableDeleteNotify 0" enabled but this was not helping. Even though it was a newer OS we ran...
It seems that there is no eroding hardware on both servers so I am suspecting an update that caused this.
It has also slowed my backups down by almost 600%. Does anybody have an ideas about this error?
If anybody could help point me in the right direction, I am still fairly new at Proxmox
I have just setup a new Windows server on a dedicated NIC (on it's own network bridge), this is connected directly to a DMZ port on our hardware firewall. The problem is I want to block all access to the...
The basic (minimal) license for Windows server 2016 standard is 16 cores. I believe if I create a guest VM and assign 16 cores, it should be fine as far as MS is concerned.
However my Proxmox server has dual 14 (physical) core CPUs, but because of hyper-treading, Proxmox reads it as 56 cores...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.