Hyper-V settings: Automatic Stop Action: save machine state or shut down guest?

[TwistedHelixis]

Single primary school server host with 2 VMs, VM1=DC /// VM2=data, SQL, SIMS FMS etc.

 

Just wondered what others have the Automatic Stop Action set to in the VM settings, save machine state or shut down guest?

 

Normally I have this set to shut down, but our LA have all there schools set to save machine state so I am now questioning my logic.

 

Thanks :0)

[ChrisMiles]

Single primary school server host with 2 VMs, VM1=DC /// VM2=data, SQL, SIMS FMS etc.

 

Just wondered what others have the Automatic Stop Action set to in the VM settings, save machine state or shut down guest?

 

Normally I have this set to shut down, but our LA have all there schools set to save machine state so I am now questioning my logic.

 

Thanks :0)

 

Shut down is by far the safest option. Windows will safely close open files, stop services and save your data.

Save state can cause so many things to fail, especially if using non-production checkpoints, but even then.

Consider that time still passes so when resuming a server, whatever it was just in the middle of doing inexplicably took x hours instead of a few ms.

There's also file locks, database connections, and other things which can easily get dropped.

 

You only have 2 servers so shutting down and booting up isn't going to take much time.

 

IMO the LA is taking a huge risk, especially with SQL servers and the like.

 

Found this Microsoft Article that might help you:

https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/best-practices-analyzer/avoid-using-checkpoints-on-a-virtual-machine-server-workload-production

[sister_annex]

putting a DC in to a saved state is never a good option - although you only have 1 (another unrecommended setup) which may make that point moot

[TwistedHelixis]

Over the weekend I will shutdown the VMS and switch them over to Shutdown mode.

 

cheers