I'm not sure what our support team meant by that, but we do use Dynamic Memory as of http://myhosting.com/statusblog/2011...ervice-update/.
We heavily monitor our servers in general and for RAM usage and if there were any concerns that purchased RAM levels couldn't be met this would be addressed well in advance.
That makes sense, I didn't see that mentioned anywhere else on the site.
Funny timing, as I was reading that article I got a notification that Node 31 (Which my server is hosted on apparently) will be down for about 90 minutes to replace a faulty memory chip (http://myhosting.com/statusblog/2012...p-replacement/).
This sort of conflicts with the statement made in the post you mentioned:
HA (High Availability) Clustered Environment – Whether by routine maintenance on the host machine, or a hardware failure, client Hyper-V virtual servers will remain available during such outages as they’re automatically moved to another host machine as soon as a problem is detected. This can result in as little as a single ping loss during transition!
This is true unfortunately, our cluster has been having considerable problems in the last while that we have been unable to resolve with Microsoft support to a degree we are satisfied with. As a result, we have begun migrating users off of the cluster until those issues can be addressed. We had been running Hyper-V servers with an incredible deal of success prior to making use of the clustered environment so it was decided best to revert this for the current time.