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

    increase 24 hour timeout-limit on backup/copy

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    24 Posts 5 Posters 4.4k Views 5 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.
    • mauzillaM Offline
      mauzilla
      last edited by

      Just another reason why XCP / XO is the best! Just ran into this exact same issue and boom, you guys have it sorted 🙂

      1 question, must the XAPI change be setup on both hosts (so the sending and receiving server)?

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

        Yes, if it takes more than 24h to export, it will take more than 24h to import and you'll have the same issue 🙂

        mauzillaM 1 Reply Last reply Reply Quote 0
        • mauzillaM Offline
          mauzilla @olivierlambert
          last edited by olivierlambert

          @olivierlambert Alright I created the conf file described here:

          https://xcp-ng.org/docs/api.html#_24h-task-timeout

          I then did a xe-toolstack-restart (which I assume is needed to updated the configuration). Restart had no errors, said "done" - but the toolstack isnt coming online, when I try and reconnect I get a connection refused, and accessing the host (https://10.1.3.8) also returns connection refused.

          I then deleted the file created, and restarted the toolstack again:

          [15:38 jerry xapi.conf.d]# xe-toolstack-restart
          Executing xe-toolstack-restart
          done.
          [15:38 jerry xapi.conf.d]#
          

          Nothing appears give an indication that something is broken. Is there a log somewhere I can have a look at to see what error may have occurred?

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

            It might be an unrelated bug 🤔 Can you create a ticket so we can take a look remotely?

            mauzillaM 1 Reply Last reply Reply Quote 0
            • mauzillaM Offline
              mauzilla @olivierlambert
              last edited by

              @olivierlambert strange one, thank you Olivier, I created a ticket 7714072

              1 Reply Last reply Reply Quote 1
              • mauzillaM Offline
                mauzilla
                last edited by

                You guys are absolute rockstarts! Yannick connected and was able to resolve the issue, thank you again for all of your hard work!

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

                  \o/ Now you should be able to configure and enjoy a larger timeout on both sides 🙂

                  1 Reply Last reply Reply Quote 0
                  • S Offline
                    sumansaha @olivierlambert
                    last edited by

                    @olivierlambert I've changed the value to 72 hours in source XCP-NG but it doesn't work at all.

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

                      Hi,

                      Without anything more "it doesn't work", it's hard to help you. Please provide more information.

                      S 1 Reply Last reply Reply Quote 0
                      • S Offline
                        sumansaha @olivierlambert
                        last edited by

                        @olivierlambert ![alt text](Screenshot 2023-06-27 at 1.11.18 PM.png Screenshot 2023-06-27 at 1.09.30 PM.png image url)

                        I'm sending the XCP-NG(Source) VM backup to another XCP-NG(Destination) storage using XOA. I've changed the value of pending_task_timeout to 72 hours in source XCP-NG. Still the backup ended just after 24 hours.

                        florentF 1 Reply Last reply Reply Quote 0
                        • florentF Offline
                          florent Vates 🪐 XO Team @sumansaha
                          last edited by

                          @sumansaha hi,

                          can you post the backup log ? It the json file you can obtain by clicking on the bottom facing arrow here :
                          bc639431-fe91-4d90-b51f-ad797c8a22e3-image.png

                          S 1 Reply Last reply Reply Quote 0
                          • S Offline
                            sumansaha @florent
                            last edited by

                            @florent 2023-06-25T18_30_22.009Z - backup NG.txt

                            the log file is attached according to your requirement.

                            florentF 1 Reply Last reply Reply Quote 0
                            • florentF Offline
                              florent Vates 🪐 XO Team @sumansaha
                              last edited by florent

                              @sumansaha is your XO up to date ? I see date in 2020 in the logs

                              also, you can try NBD (enable it in the network used by the backups); it's not a xapi task and won't be killed by the xapi , but you won't have a progres bar on the tasks

                              S 1 Reply Last reply Reply Quote 0
                              • S Offline
                                sumansaha @florent
                                last edited by

                                @florent XO is not updated.
                                I was seeing progress when the backup process was running. 96% was completed . It has dropped on that status.
                                How I can enable NBD.

                                florentF olivierlambertO 2 Replies Last reply Reply Quote 0
                                • florentF Offline
                                  florent Vates 🪐 XO Team @sumansaha
                                  last edited by

                                  @sumansaha you'll need an up to date XO

                                  then you go to pool -> network and there is a drop down menu to enable NDB
                                  3ed39b73-66f9-4e4b-8463-969f1cfe21ea-image.png

                                  (an older xo does not cause this issue, but gives us more tools to help)

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

                                    @sumansaha If you XO is not up to date, you can't ask for assistance. You always MUST be sure to get XO on latest commit before reporting an issue 🙂

                                    That's written in our doc: https://xen-orchestra.com/docs/community.html#report-a-bug

                                    S 1 Reply Last reply Reply Quote 0
                                    • S Offline
                                      sumansaha @olivierlambert
                                      last edited by

                                      @olivierlambert Aha That make sense. Let me update my XO.

                                      S 1 Reply Last reply Reply Quote 0
                                      • S Offline
                                        sumansaha @sumansaha
                                        last edited by

                                        @sumansaha BTW , The issue was fix with a workaround. I've used another XOA where the interface was 1Gbps, Source XCP-NG--->XOA---> Destination SR all were 1Gbps . In that case transfer time has significantly dropped to 5 hours. For continuous replication, from source data stream come to XOA at first and then to the destination.Here I had a misconception , I was thinking backup data directly send to destination from Source XCP-NG.Thanks everyone for your help always.

                                        florentF 1 Reply Last reply Reply Quote 0
                                        • florentF Offline
                                          florent Vates 🪐 XO Team @sumansaha
                                          last edited by

                                          @sumansaha that is a good news

                                          yes, the replication go through the XO VM, the faster the link the better the performances

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