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

    MESSAGE_METHOD_UNKNOWN(VDI.get_cbt_enabled)

    Scheduled Pinned Locked Moved Solved Backup
    11 Posts 2 Posters 305 Views 2 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.
    • J Offline
      joneill
      last edited by

      Re: Getting MESSAGE_METHOD_UNKNOWN(VDI.get_cbt_enabled) with XenServer 7.1

      We had had this issue in early August then updated our XOAs to resolve it. Ran an update this morning and now my XOA is having this problem again.

      • Start time: Monday, October 7th 2024, 2:04:43 pm
      • End time: Monday, October 7th 2024, 2:07:57 pm
      • Duration: 3 minutes
      • Error: MESSAGE_METHOD_UNKNOWN(VDI.get_cbt_enabled)

      1 Reply Last reply Reply Quote 0
      • J Offline
        joneill @olivierlambert
        last edited by

        @olivierlambert we were using the 'stable' channel. Support had me switch to the 'latest' channel now. That looks like it may have resolved it. My backups are running now will report back once it is completed.

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Hi,

          There's a PR in draft that should fix it once for all: https://github.com/vatesfr/xen-orchestra/pull/8038

          fbeauchamp opened this pull request in vatesfr/xen-orchestra

          closed fix(backups): support system without cbt (XS< 7.3) #8038

          J 1 Reply Last reply Reply Quote 1
          • J Offline
            joneill @olivierlambert
            last edited by

            @olivierlambert Any updates on this? Our backups are still not working. Is there a way to rollback this update where this function is working?

            Thanks.

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              If you have a subscription, I would suggest to open a ticket. If you don't, then just wait for the PR to be merged and update again.

              J 1 Reply Last reply Reply Quote 0
              • J Offline
                joneill @olivierlambert
                last edited by

                @olivierlambert Thanks. I opened a support ticket Ticket#7730113.

                1 Reply Last reply Reply Quote 1
                • J Offline
                  joneill
                  last edited by

                  @olivierlambert FYI, I ran the latest XOA updates today and it broke again after it was patched. I have re-opened the existing ticket.

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by olivierlambert

                    Are you on latest? I mean, "latest" channel.

                    J 1 Reply Last reply Reply Quote 0
                    • J Offline
                      joneill @olivierlambert
                      last edited by

                      @olivierlambert we were using the 'stable' channel. Support had me switch to the 'latest' channel now. That looks like it may have resolved it. My backups are running now will report back once it is completed.

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        Great news! Indeed, latest is shipped with the latest release (ie the one from Halloween/October) while stable is updated to the September release. Since the fix was done only in the last release, this explains the result 🙂

                        Anyway, what you can do on November the 30th, is to switch back to "stable", which be the exact same release than your current "latest".

                        J 1 Reply Last reply Reply Quote 0
                        • olivierlambertO olivierlambert marked this topic as a question on
                        • olivierlambertO olivierlambert has marked this topic as solved on
                        • J Offline
                          joneill @olivierlambert
                          last edited by

                          @olivierlambert Confirmed that the backup completed successfully using the 'latest' channel. Thanks again!

                          1 Reply Last reply Reply Quote 1
                          • olivierlambertO Offline
                            olivierlambert Vates 🪐 Co-Founder CEO
                            last edited by

                            Excellent 🙂 Happy to see our fix solved your problem and enhanced our compatibility with older XenServer version. Don't forget to upgrade, the path to get to XCP-ng is relatively straightforward 🙂

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