Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2017December29 - VMAN Deletes > Predictive recommendation: solve a storage capacity issue

Predictive recommendation: solve a storage capacity issue

Table of contents
No headers
Created by Lori Krell_ret, last modified by Gerald.Prado on Dec 29, 2017

Views: 345 Votes: 0 Revisions: 4

Recommendations solve issues before they occur. As trends calculate for CPU, memory, and capacity usage, network traffic fluctuation, and other VM resource metrics, recommendations tracks the trends and determines areas of potential issues.

For example, a VM trends with a rising and consistent spike of capacity usage in a week. A recommendation triggers with a critical alert due to the speed and consistent usage and decline of free capacity. It provides a severity, message, steps to resolve, and statistics. The recommendation message provides the severity, steps to resolve, and VM statistics. Move the VM to a larger datastore to allow the VM additional disk space. VMs on the critical datastore will then have additional disk space available without hitting critical limits.

  1. Click My Dashboard > Virtualization > Virtualization Summary.

    The Tokyo ESX cluster shows a critical recommendation.


  2. Select the Tokyo ESX 4.1 Cluster or All Recommendations to open the Recommendations page.

  3. Select the recommendation "The space utilization on datastore tok-esx-01:LocalStorage02 has reached critical threshold."


    In the image below, the kmiele-vman is overwhelming the smaller datastore. Move the VM to a larger datastore (LocalStorage01). LocalStorage02 receives more capacity for other assigned VMs and kmiele-vman VM continues service without capacity issues.


  4. Select the Power off option in the step to perform.

    The steps update to power down, move, and power up to migrate the server.


  5. Click Statistics to review the effects of the trending issue to show the recommended solution.

    Each step includes an expandable chart with detailed metrics that show the tracked usage and calculated resolution. In the image below, the capacity dramatically increases for the VM when the datastore moves to a larger host. LocalStorage02 regains about 22 GB of space for other VMs, giving the larger kmiele-vman VM a better datastore for usage needs.


    To investigate further, expand and review the space utilization expectations for LocalStorage01 and details pages on each VM, including kmiele-vman, through More details links.

  6. Click Schedule Recommendation and select a date and time.

    You may be unable to take the servers down during production hours. This option allows you to run the recommendation during a maintenance window.


  7. Click Apply This Recommendation.

    The recommendation moves to the Scheduled tab on the Recommendations page. The recommendation runs at the configured date and time.

Learn more...

To manage recommendations using VIM:

Last modified