![]() I should warn you though… my friend Duco Jaspars tipped me about this KB article: “ Defining alarms on datastore folders can cause vCenter Server 4.x to becomes unresponsive“, although I have not yet ran into this issue with the customers were I implemented this. See how the next image gives you much less alarms and only shows warnings and alarms on datastores that really are below 40GB. The alarms you see are now “real” alarms that really require your attention. This will give you a much better view of your datastores and alarms. There is an easier way, you can create folders and assign alarms to folders and move datastores of the same size into these folders. ![]() Unfortunately in most environments, not all datastores are equal in size and you would have to change the alarm on each datastore. Those 40GB free space I would like to monitor through my vCenter alarms which is very easy if all datastores would be equal in size, you could than edit the default alarm to reflect the new % settings. Usually these 40GB can accomodate enough snapshot space during nightly backups and storage migrations to prevent the datastore from filling up. In general I use as a rule of thumb a required free space per datastore of 40GB. In most cases this is much too soon as the next image shows you. These false alarms happen because the default values right out of the box are set at 75% for a warning to trigger and 85% for an alarm to trigger. When I show them the datastore overview in the VI Client that shows the warnings and alerts for the datastores, it turns out that they don’t often look at this page because it gives too many false alarms. When visiting customers I noticed that the VMware admin often doesn’t really know how much free space is left on the datastores and wether action is needed to free up space or get extra capacity.
0 Comments
Leave a Reply. |