Protected VMs are set with 'Disabled Methods' in vCenter on running Planned Migration using VLSR 9.0.4
search cancel

Protected VMs are set with 'Disabled Methods' in vCenter on running Planned Migration using VLSR 9.0.4

book

Article ID: 418688

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:

  • Post running Planned Migration, protected VMs at Source site are set with 'Disabled Methods':

    (Path in vSphere Client : Virtual Machine (i.e. protected by VLSR) > Configure > Disabled Methods).




  • These Disabled Methods appear only on running Planned Migration and is set at the Source site (i.e. Actual Protected site).


  • SRM server logs (vmware-dr.log) at Protected site reports the following list forwarding the request to vCenter:

    YYYY-MM-DDTHH:MM:SS.###Z verbose vmware-dr[02087] [SRM@6876 sub=LocalSite.LocalVcServer opID=########-####-####-####-############-failover:e1:v5:5c-deactivate:wa] [AuthorizationDomain] Calling DisableMethods called for 'vm-#####':
    --> [(vim.AuthorizationManager.DisabledMethodRequest) {
    --> method = "vim.VirtualMachine.reset",
    --> reasonId = "Disabled by Site Recovery Manager"
    --> }, (vim.AuthorizationManager.DisabledMethodRequest) {
    --> method = "vim.VirtualMachine.revertToCurrentSnapshot",
    --> reasonId = "Disabled by Site Recovery Manager"
    --> }, (vim.AuthorizationManager.DisabledMethodRequest) {
    --> method = "vim.VirtualMachine.exportVm",
    --> reasonId = "Disabled by Site Recovery Manager"
    --> }, (vim.AuthorizationManager.DisabledMethodRequest) {
    --> method = "vim.VirtualMachine.createSnapshot",
    --> reasonId = "Disabled by Site Recovery Manager"



  • As a response to call from VLSR, vCenter disables the requested methods:

    YYYY-MM-DDTHH:MM:SS.###Z verbose vpxd[06997] [Originator@6876 sub=MoAuthMagr opID=########-####-####-####-############-failover:e1:v5:5c-deactivate:wa-1a] Methods disabled: methods:[vim.VirtualMachine.reset, vim.VirtualMachine.revertToCurrentSnapshot, vim.VirtualMachine.exportVm, vim.VirtualMachine.createSnapshot, vim.VirtualMachine.rebootGuest, vim.VirtualMachine.powerOn, vim.VirtualMachine.makePrimary, vim.VirtualMachine.customize, vim.VirtualMachine.removeAllSnapshots, vim.VirtualMachine.clone, vim.VirtualMachine.promoteDisks, vim.VirtualMachine.reloadFromPath, vim.VirtualMachine.migrate, vim.VirtualMachine.relocate, vim.VirtualMachine.markAsVirtualMachine, vim.VirtualMachine.standbyGuest, vim.VirtualMachine.suspend, vim.VirtualMachine.markAsTemplate], entities:[vm-#####], sourceID:[com.vmware.vcDr]
    YYYY-MM-DDTHH:MM:SS.###Z verbose vpxd[06997] [Originator@6876 sub=MethodValidator opID=########-####-####-####-############-failover:e1:v5:5c-deactivate:wa-1a] [LoadRetentionTimer] Method is disabled by VMWare solution.
    YYYY-MM-DDTHH:MM:SS.###Z verbose vpxd[06997] [Originator@6876 sub=MethodValidator opID=########-####-####-####-############-failover:e1:v5:5c-deactivate:wa-1a] [LoadRetentionTimer] Method is disabled by VMWare solution.

Environment

vSphere Live Site Recovery 9.0.3

vSphere Live Site Recovery 9.0.4

Cause


Setting of 'Disabled Methods' on VMs at Source site on running Recovery i.e.  is an expected behavior as per design with VLSR 9.0.4 (and 9.0.3).

Resolution

  • VLSR 9.0.4 (and 9.0.3) sets 'Disabled Methods' on Protected VMs ensuring these VMs are not inadvertently powered-on while recovered VMs are running at Recovery site.

  • These Disabled Methods are cleared off on running 'Reprotect' and failback ('Planned Migration'  in reverse direction)

  • This is how VLSR is designed to work protecting VMs from any operations at vCenter layer.