XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    always getting "unhealthy VDI chain"

    Scheduled Pinned Locked Moved Xen Orchestra
    3 Posts 2 Posters 713 Views 1 Watching
    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.
    • I Offline
      icecoke
      last edited by

      I have an delta backup job in xoa, which is backing up 28 VMs. 26 of them has never any problems, 2 of them (different storages, different xenserver hosts) have always (or at least nearly always, as some manual retries did it) this error:

      Reason: (unhealthy VDI chain) Job canceled to protect the VDI chain

      When I rerun the job for these two machines, sometimes it get's thru. When running it automatically, it never runs thru.

      How can I get more detailed information about the real reason. Which logs can show more?

      interesting: I even made a copy of the vdi to have that chain thing cut and used the copy (not a fast one or clone) as storage, but the same error occurs. As far as I can see, there is no VDI chain, with no parent or childs. So where could lay the problem?

      Any help is welcome!
      Jimmy

      1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        Have you read the docs? https://xen-orchestra.com/docs/backup_troubleshooting.html#vdi-chain-protection

        1 Reply Last reply Reply Quote 1
        • I Offline
          icecoke
          last edited by

          @Danp - thank you. Yes, I did, but that was not helping in this case.
          Found the solution:

          Both machines are on a hostserver, which has NOT all networks. So the real reason must be a network problem, therefore a quite missleading error message 🙂

          After moving both VMs to the master of this pool (which is connected to the same network where the xoa resides), everything went fine. Same storage, same vhds.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post