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

    XO - Files Restore

    Scheduled Pinned Locked Moved Backup
    12 Posts 3 Posters 185 Views 3 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.
    • X Offline
      xcplak
      last edited by

      Hi o/

      I'm facing an issue with file restoration.

      On some VMs, I can see the file and restore them :

      11242d2c-4544-4498-bc73-038193ddba6b-image.png

      On other VMs, I can't :

      2cb81d39-d309-4714-aa7b-1c6567ebef44-image.png

      Both VMs are backed up in the same way, using the same job.
      Backups are done on an NFS share, and remote backups are encrypted on XO.

      Any idea why this is happening?

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

        Hi,

        This is highly coupled with the filesystem you use inside the VM (LVM, ext, xfs etc.)

        Since you are not providing any hint on what you use (XOA or XO from the sources?), it's really hard to answer 🙂

        X 1 Reply Last reply Reply Quote 0
        • X Offline
          xcplak @olivierlambert
          last edited by

          @olivierlambert
          My bad, it's on XO from the sources.
          I didn’t take the filesystem into account.
          After checking my backups, I can see files on EXT filesystems but not on LVM filesystems.

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

            Does it work on XOA?

            X 1 Reply Last reply Reply Quote 0
            • X Offline
              xcplak @olivierlambert
              last edited by

              @olivierlambert
              Don’t have XOA on hand.
              Besides that, all backup jobs are already set up on XO…
              Is this a common issue? Is there something I can do to fix it?
              I was thinking of doing the backup on an unencrypted NFS share. Would that fix it?

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

                That's 100% unrelated. If you do file level restore, you need to have an XO environment that's able to mount volumes from LVM. That's why I said you should test with XOA to validate your environment (just import a fresh one, connect to your backup repo and try to file restore).

                X 2 Replies Last reply Reply Quote 0
                • AtaxyaNetworkA Offline
                  AtaxyaNetwork Ambassador @xcplak
                  last edited by

                  @xcplak you can try to install the package lvm2 on your xo source

                  1 Reply Last reply Reply Quote 0
                  • X Offline
                    xcplak @olivierlambert
                    last edited by

                    @olivierlambert

                    Ok, now it's clear!

                    @AtaxyaNetwork
                    Already installed :

                    lvm2 is already the newest version (2.03.16-2).
                    
                    1 Reply Last reply Reply Quote 0
                    • X Offline
                      xcplak @olivierlambert
                      last edited by

                      @olivierlambert
                      Just tried on XOA, I can't mount the NFS share on it. I get :

                      Test remote
                      Unsupported state or unable to authenticate data
                      
                      X 1 Reply Last reply Reply Quote 0
                      • X Offline
                        xcplak @xcplak
                        last edited by

                        I just deployed a new NFS share for testing.
                        The share is mounted on both XO and the newly deployed XOA.
                        I backed up a VM that I can see the files in using XO.
                        I faced the same issue with both XOA and XO, I can’t see the files.
                        I backed up the same VM using XOA and tried to restore the files, same issue.

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

                          You have a remote (backup repo) configuration issue. That's unrelated, check your permissions.

                          X 1 Reply Last reply Reply Quote 0
                          • X Offline
                            xcplak @olivierlambert
                            last edited by

                            @olivierlambert,

                            Why would this issue be related to my NFS share? I can access the share without any problems, read and write operations work fine. Other NFS shares with multiple applications running are also functioning normally.

                            I checked the XO logs and found the following:

                            xo-server[679]: 2025-04-29T21:45:58.276Z xo:api WARN  | backupNg.listFiles(...) [114ms] =!> Error: Command failed: vgchange -ay vg_iredmail
                            xo-server[679]: File descriptor 22 (/var/lib/xo-server/data/leveldb/LOG) leaked on vgchange invocation. Parent PID 679: node
                            xo-server[679]: File descriptor 24 (/var/lib/xo-server/data/leveldb/LOCK) leaked on vgchange invocation. Parent PID 679: node
                            xo-server[679]: File descriptor 25 (/dev/fuse) leaked on vgchange invocation. Parent PID 679: node
                            xo-server[679]: File descriptor 26 (/var/lib/xo-server/data/leveldb/MANIFEST-000103) leaked on vgchange invocation. Parent PID 679: node
                            xo-server[679]: File descriptor 31 (/dev/fuse) leaked on vgchange invocation. Parent PID 679: node
                            xo-server[679]: File descriptor 34 (/var/lib/xo-server/data/leveldb/000356.log) leaked on vgchange invocation. Parent PID 679: node
                            xo-server[679]:   WARNING: Couldn't find device with uuid oWTE8A-LNny-Ifsc-Jmtp-lTkB-dSjt-2AqhwY.
                            xo-server[679]:   WARNING: VG vg_iredmail is missing PV oWTE8A-LNny-Ifsc-Jmtp-lTkB-dSjt-2AqhwY (last written to /dev/xvda4).
                            xo-server[679]:   Refusing activation of partial LV vg_iredmail/lv_root.  Use '--activationmode partial' to override.
                            

                            To me, this looks more like an issue with file restore than the NFS itself.

                            It seems similar to what's reported here:
                            https://github.com/vatesfr/xen-orchestra/issues/7029

                            andrew64k created this issue in vatesfr/xen-orchestra

                            open File level restoration not working on LVM partition #7029

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