Recent content by Sasha Sandow

All these volumes were virtio-block before having the issue with backup file size and I can't recall ever having a space issues. I know I can probably wipe out the server, reload and configure a new version of Proxmox and restore all VM backups but this will take time (almost a whole weekend and...

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...

I can only speak for myself, but I have been following this discussion for a while now. I am very disappointed that it has been several months and Proxmox thinks that it is acceptable to offer a hypervisor/vitalization solution that does not support either differential or incremental backups...

I just need to say, if I had to license all physical cores in Server 2016 running as a guest OS, then you are saying I would need to licensing all physical cores over 5X since I am running multiple MS Servers (Guest OSs) under a single physical server running Proxmox.

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?

Awesome...Thank you so much... Very simple solution that allows me to protect the server from the DMZ but still allows me to program all my security on our firewall (hardware).... Did not realize that was an option... And yes still have full management from our LAN (or VPN) which is on a whole...

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...

Alex, You are saying I need to license all the physical core on my server, even though the Windows Server 2016 will be running as a guest VM under my Proxmox and only have 8 virtual-cores allocated to it? Or if I need 8 cores in my Windows Server 2016 standard do I really need to allocate 16...

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...

I would like to try this patch out and give some feedback for out network, but what file exactly do you insert this into? I don't think it is the qm.conf file? To add a little more to this, while the idol CPU usage is high and this makes everything on the VMs get much higher then they should be...