Thursday, June 30, 2016

VMware SRM Recompute Device Groups Occurence

Setup


VMware vCenter 6.0 Update 1b
SRM 6.1
NetApp SRA 2.1P1

Issue


We have upgraded DR vCenter Server to 6.0 U1b and DR SRM Server to 6.1. After upgrading and configuring SRM we observed that Production vCenter keeps generating Re-compute Device Groups tasks every 30 seconds

Analysis


The re-computes are triggered by the SRA. Under normal circumstances Datastore Group computation is triggered by the following events:

  • Existing VM is deleted or unregistered
  • VM is storage vmotioned to a different datastore
  • New disk is attached to VM on a datastore previously not used by the VM
  • New datastore is created
  • Existing datastore is expanded


In our case none of this was happening, there are APD for other datastores in PROD vCenter however it is not included in the SRM Configuration. SRM is configured with single datastore in Array Managers Volume include list

I am wondering if anyone else has come across similar issue like this

10 comments:

  1. We're running into this too and have a ticket open with VMware support. So far we've got nowhere on it.

    Shaun

    ReplyDelete
  2. You guys make any progress on this? I am seeing the same issue.

    Thanks,
    Jeff

    ReplyDelete
  3. We are seeing the same issue in our environment and have a ticket open with VMware. Troubleshooting thus far has not yielded any result.

    ReplyDelete
  4. All,

    I'm working with vmware support as well and will post back if I discover anything of use.

    Thanks,
    Jeff

    ReplyDelete
  5. Apologies for late response. I have actually moved to a different Project hence I was not sure what is the current status. I spoke with our internal contact. He said our case is still open with VMware. They have asked additional logs from Production and our Customer has gone unresponsive. Looks like this seems to be pretty common issue. Please share the resolution once you have it from VMware

    ReplyDelete
  6. This comment has been removed by the author.

    ReplyDelete
  7. On protected site verify whether you have any "unknownXX" VM in the inventory, this will cause the issue, once removed that should fix the issue in SRM.

    ReplyDelete
  8. Hello, I have the same problem. Some idea? Could someone solve this problem? Thanks!

    ReplyDelete
  9. https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2152001&sliceId=1&docTypeID=DT_KB_1_1&dialogID=518554569&stateId=0%200%20635748238


    See KB2152001

    ReplyDelete
    Replies
    1. Thank you for posting, Marge! I have applied and will let everyone know the results.

      Jeff

      Delete