![]() The downside is that if you over provision a datastore and then all of your virtual machines decide they need to grow you could run that datastore out of space. The benefit of thin provisioning is that you can assign a VM a hard drive that is larger then you might actually need, without tying up that space and making it unavailable to other virtual machines. Basically you start out using no space, and then as a virtual machine starts to use space, VMware will start to grow that virtual machine on the datastore as needed. Provisioned space is something that comes into play when you thin provision your virtual machines. The other piece that we need to monitor is the amount of provisioned space. This is a little misleading because it only shows the total size of the datastore, as well as the amount of actual free space that is available. When you click on one of your physical servers and then look over to the right you will see a box that looks like the first picture. The goal of this article is to explain the possible risks that you take by over provisioning your datastores without regularly monitoring the free space. They admitted that they didn’t fully understand what over provisioned meant… after all there was free space on the datastore… so what was the problem ? They asked because while all of their datastores were showing plenty of free space they remembered that I had mentioned that some of them were very over provisioned. SRM you will get even more alarms to have a play around with.Last week I was asked by a customer which datastore would be the best location for a new virtual machine. Also when you install additional components e.g. Every environment is different and you may use more or less alarms than I have mentioned.ĭon’t forget that depending on which vSphere licenses you have might see extra default alarms for items such as FT. Naturally, this isn’t a complete list of alarms, however it is the default alarms that I would configure in most, if not all environments. Insufficient vSphere HA Failover Resources Hopefully these alarms shouldn’t need any explanation, as they should ALWAYS be enabled. If you have this set to high for all servers then it can cause alarms when backup software rolls back snapshots depending on how big the VM is. I tend to leave VM Monitoring Only and Medium and then change individual VM’s monitoring to High if required. VSphere HA Virtual Machine Monitoring Error this alarm works in conjunction with Virtual Machine Monitoring. If for some reason none of your other alarms work then at least you know that a VM has been restarted by HA. VSphere HA Failover In Progress this resides on the nice to have. With this in mind, I set the Warning to 90% and Critical to 95% so I have some room to either more VM’s around either by Storage vMotion or Cold Migration. Then when the Datastore is provisioned only use 1TB so you have room for expansion quickly and easily if needed. if you need 1TB for a Datastore, ask for an extra 25%. I recommend always asking for slightly more than need e.g. From the presented LUN how much space has been provisioned as a Datastore. Well it also manages ‘lost storage path redundancy’ and ‘degraded storage path redundancy’ so if you have an if your ESXi host has multiple connections to it’s storage, you will be notified if one of these is lost.ĭatastore Usage On Disk quite an important one. Big deal you say, I can see that in vCentre. If the host loses connection to the storage then the VM’s will be restarted using HA. We are now going to run through some of the default alarms, with some suggested thresholds.Ĭannot Connect To Storage why would we want to configure this? Well essentially this is a per host setting. In the previous post setting up and configuring alarms in vCenter 5 Part 1 we looked at the initial configuration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |