I quick question, related to proxmox + nas + vm/windows+sqlserver
Imagine that I need to restart the NAS where the vm is stored.
I wonder if I can pause each VMs running on proxmox+nas and wait for the nas to reboot, then just unpause the VMs without any loss? Especially for those VMs running sql server.
Regards
BTW, I have a test VM (windows 2012 r2 + sql server 2008 r2) , that I paused for some minutes, even days and I remember to not perceived any bad effect; of course, the vm is almost not used by anyone just for me for some migrations test.
I’m preparing for when I use a productive VM for our payroll system. (w201x+sql201x)
On second thought, I think the most sensible thing would be to turn off the MV and not play with fire.
I was curious, because just tonight I need to restart the NAS, to see if it shows an application I installed that doesn’t show up to assign permissions.
As I’ve mentionned before: I use mostly Synology NAS at my several clients.
These NAS do get updates, maybe 6-9 a year - and these DO need reboots.
Now, your question IS a legit, intelligent question.
If you have heavy traffic, you can do a script which will do the “pausing” for you…
That would be the cleanest way.
But, to be honest, I’ve simply set my Synologys to do the updates automatically over the weekends at 3:00 early in the morning. This takes 2-3 minutes at most. Proxmox can cache the writing to NFS for that amount of time - no one notices!
Additional Note:
My VM Backups are all finished before 03:00, so I’m still on the safe side!
One thing I notice with my nethserver VM is that sometimes the VM doesn’t stop when I shutdown it from the GUI, and if I don’t watch and ask the Proxmox Server to restart, it can take as long as 15 minutes (hopefully) or wait forever.
I learned this the hard way, that time I had to run to the office at night and see the server that had already rebooted after +40 minutes.
Having learned this, I now check the VM and if I see that after N minutes it doesn’t shut down, I force the shutdown with “# qm stop 100”
Check the VM console on Proxmox (Do a planned reboot just to correct this!)…
In my cases, it was often the fail2ban service.
You may need to click in the proxmox console for it to actually show something, but you will see there what’s blocking your reboot/shutdown!
But with the forced shutdown after 180 seconds / 3 minutes, it works well!
wow!
