AnsweredAssumed Answered

VM Information Not Updating Properly in VMTurbo

Question asked by chrisstengel on Apr 28, 2016
Latest reply on May 5, 2016 by chrisstengel

Hi everyone!


I'm having an issue with workload placement.  I've created some groups to do storage balancing based on a storage groups.  For example SQL servers can only migrate storage to SQL-XX LUNs within VMWare.  This is working great.  However, as I fine tune this by moving disks around to better suite my policy (and my storage environment) I'm finding that VMTurbo information is hanging on to old disk locations.  For example, I have a policy for SQL servers.  They should only be located on the SQL-XX LUNs.  Some disks on the SQL servers were located on the APP-XX LUNs.  I moved them to an SQL-XX LUN and VMTurbo sees that it was moved and adds a disk with the correct location under "consumes" but it is also showing a disk with the old location.  So that server has 3 disks per VMTurbo instead of the actual 2 disks found in VMWare.  Is there something I need to do to get this to flush the old information?  It's messing up my workload placement policy.  Any help is appreciated!




VMTurbo Operations Manager 5.4 (Update 1) (Build 39300) is our build.