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

    Backup error with space available

    Scheduled Pinned Locked Moved
    Xen Orchestra
    ticket closed
    4
    50
    5.5k
    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.
    • B
      Bane
      last edited by marcungeschikts

      I am trying to backup one VM from my XCP-NG to an external 8tb HD. I am seeing the below error with my VM backup.

      Start: Apr 20, 2022, 04:03:19 PM
End: Apr 20, 2022, 04:03:27 PM
 EXT-USB 
 transfer 
Start: Apr 20, 2022, 04:03:27 PM
End: Apr 20, 2022, 04:03:56 PM
Duration: a few seconds
Error: ENOSPC: no space left on device, write

      The VM is about 8gb in size, and I have only 1.1tb in use out of 3.6tb on my SR. I can successfully snapshot the VM, but the backup fails.

      Anyone have any ideas on this?

      DarkbeldinD 1 Reply Last reply Reply Quote 0
      • DarkbeldinD
        Darkbeldin Vates 🪐 Pro Support Team @Bane
        last edited by

        @Bane Hi Bane.

        Could you display the result of a df -h from your dom 0 please?

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

          This is a different error from your initial post on Discord. You had SR_BACKEND_FAILURE_44(, There is insufficient space, ) and now it's ENOSPC: no space left on device.

          So this time, it's an issue on backup storage.

          1 Reply Last reply Reply Quote 0
          • B
            Bane
            last edited by olivierlambert

            df -h output

            Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        1.3G  8.0K  1.3G   1% /dev
tmpfs           1.3G  248K  1.3G   1% /dev/shm
tmpfs           1.3G  9.9M  1.3G   1% /run
tmpfs           1.3G     0  1.3G   0% /sys/fs/cgroup
/dev/sda1        18G  1.9G   15G  12% /
xenstore        1.3G     0  1.3G   0% /var/lib/xenstored
/dev/sda5       3.9G  194M  3.5G   6% /var/log
tmpfs           250M     0  250M   0% /run/user/0

            The drive (EXT-USB) I'm backing up to shows 7.2TiB available.

            storage.png

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

              And what about the "remote" configuration in XO? Do you know that backup storage are mounted in XO and not XCP-ng, right?

              B 1 Reply Last reply Reply Quote 0
              • B
                Bane @olivierlambert
                last edited by

                @olivierlambert I don't see the drive I'm backing up to when I run mount -l, I do see it under remotes in settings.

                remotes.png

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

                  You can spot it here, it's very obvious.

                  Can you see the amount of Total disk available? The path you entered is used inside Xen Orchestra virtual Appliance, not from the host/XCP-ng perspective.

                  There's no such device as /dev/sdf/backup in your XOA.

                  You need to mount it INSIDE your XO VM, then to create a mount point, and finally point to this mountpoint.

                  This is a kind of advanced scenario, ideally, you should rely on a NFS share (the easiest thing).

                  B 1 Reply Last reply Reply Quote 1
                  • B
                    Bane @olivierlambert
                    last edited by

                    @olivierlambert

                    Ok, that makes sense.

                    Thanks

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

                      You are welcome, let us know if you need more assistance on setting the "remote"/backup repo 🙂

                      B 1 Reply Last reply Reply Quote 0
                      • B
                        Bane @olivierlambert
                        last edited by olivierlambert

                        @olivierlambert

                        I have the backup setup now for my NFS share. The NFS remote tests fine and the backup job has some success. I am getting the below failures though on 5 VM's. I am posting one example, let me know if I should post the entire log.

                         Security Onion (gamakbase)  
 Snapshot 
Start: Apr 22, 2022, 04:03:48 PM
End: Apr 22, 2022, 04:03:58 PM
 xcp-ng-backup 
 transfer 
Start: Apr 22, 2022, 04:04:02 PM
End: Apr 22, 2022, 04:38:03 PM
Duration: 34 minutes
Error: HTTP connection has timed out
Start: Apr 22, 2022, 04:03:58 PM
End: Apr 22, 2022, 04:38:03 PM
Duration: 34 minutes
Error: HTTP connection has timed out
Start: Apr 22, 2022, 04:03:48 PM
End: Apr 22, 2022, 04:45:18 PM
Duration: 42 minutes
Error: HTTP connection has timed out
Type: full
                        DanpD 1 Reply Last reply Reply Quote 0
                        • DanpD
                          Danp Vates 🪐 Pro Support Team @Bane
                          last edited by

                          @Bane See this thread for solution to HTTP timeouts -- https://xcp-ng.org/forum/topic/5769/keep-getting-http-connection-has-timed-out-on-my-delta-backup?_=1650710290869

                          B 1 Reply Last reply Reply Quote 0
                          • B
                            Bane @Danp
                            last edited by

                            @Danp

                            I applied the fix mentioned in that thread, and now I have more VM's that succeed. However I still have a few that fail with the same HTTP timeout. Is there anything else I should look at?

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

                              Maybe the huge number of DNS requests could also cause issues. What about testing it? (it's merged on master since recently, be sure to be on the latest commit!)

                              B 1 Reply Last reply Reply Quote 0
                              • B
                                Bane @olivierlambert
                                last edited by

                                @olivierlambert Can you point me to instructions for that?

                                Thanks

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

                                  If you installed XO from our doc, then it's trivial: https://xen-orchestra.com/docs/installation.html#updating

                                  B 1 Reply Last reply Reply Quote 0
                                  • B
                                    Bane @olivierlambert
                                    last edited by

                                    @olivierlambert I updated to the master as you mentioned and I still get the http timeout error on 4 of my VM's.

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

                                      Okay so you are on latest commit? (the commit should be 3ecf099)

                                      B 1 Reply Last reply Reply Quote 0
                                      • B
                                        Bane @olivierlambert
                                        last edited by

                                        @olivierlambert

                                        I'm using the trial with pro support included right now. So, I don't see the commit string in my about section. Is there another way to verify the commit string?

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

                                          Okay, so go on latest release channel and wait for tomorrow's release to make the update 😉

                                          B 1 Reply Last reply Reply Quote 0
                                          • B
                                            Bane @olivierlambert
                                            last edited by

                                            @olivierlambert

                                            When I run the below, I get destination 'xen-orchestra' already exisits.

                                            git clone -b latest https://github.com/vatesfr/xen-orchestra

                                            I'm not an expert so forgive me if this seems like a basic question.

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