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

    New Backup setup failures

    Scheduled Pinned Locked Moved Xen Orchestra
    11 Posts 3 Posters 355 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.
    • P Offline
      packetthrower
      last edited by

      Good morning,

      running Xcp-ng 8.2 with Docker XOA setup. I'm attempting to push Backups to SMB share on a Seagate Personal NAS for about 3 months but encountering errors:
      c60c5a13-edc6-46a9-ade6-0225c77c795b-image.png

      It sees the Share correctly, it tests fine but after the full hour of backups I get this.

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

        Try switching to an NFS share instead of SMB.

        P 1 Reply Last reply Reply Quote 0
        • P Offline
          packetthrower @Danp
          last edited by

          Danp I wish this little thing did NFS. Seems like I need to repurpose a device and install FreeNas.

          Thank you!

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

            I would be sure to use a recent version of XO (there's no XOA Docker version, so you are probably using a 3rd party one). As stated in https://xen-orchestra.com/docs/community.html you should probably report the issue in the Github repo providing you the install script.

            P 1 Reply Last reply Reply Quote 0
            • P Offline
              packetthrower @olivierlambert
              last edited by

              olivierlambert

              Yes sir, third party. Sorry about that, Good day.

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

                No worries 🙂 Feel free to report if it's not due to the environment but an actual XO bug!

                P 2 Replies Last reply Reply Quote 0
                • P Offline
                  packetthrower @olivierlambert
                  last edited by

                  olivierlambert Will do, thank you very much :).

                  1 Reply Last reply Reply Quote 0
                  • P Offline
                    packetthrower @olivierlambert
                    last edited by

                    olivierlambert I've contacted the 3rd party creator and he's assisted me. This was the fix:

                    It works after removing the # by privileges: true. In the docker-compose.yml file.

                    Thanks!

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

                      Yes, this is completely unrelated to XO but the environment 🙂 I suppose now you get why we can't support 3rd party scripts/containers and why we only offer pro support on a controlled env (ie XOA VM)

                      P 1 Reply Last reply Reply Quote 0
                      • P Offline
                        packetthrower @olivierlambert
                        last edited by

                        olivierlambert Yes sir. I'd totally utilize pro support for a client's infrastructure setup.

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

                          No worries, just explained how hard it is to support uncontrolled environments 🙂 Enjoy XO!

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