ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Remap MoRef ID of VMs & avoid backup job failure when replacing a vCenter Server

    Starwind
    1
    1
    413
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • OksanaO
      Oksana
      last edited by Oksana

      alt text

      "Object with reference <vmname> was not found in the hierarchy cache." Have you ever met such an error message during replacing the vCenter Server configured in Veeam Backup & Replication? Or maybe in the case of an inventory change in the vCenter? A similar message pops up when a Virtual Machine's MoRef changes. To complete backup jobs successfully, you need to re-map the MoRef ID of protected VMs, namely to keep same MoRef IDs for all protected virtual machines. How should that be done?

      Read the article by Paolo Valsecchi, a System Engineer, to find out how to remap MoRef ID of protected VMs, avoid backup jobs failure, and replace the vCenter Server safely.

      1 Reply Last reply Reply Quote 2
      • 1 / 1
      • First post
        Last post