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

    Backup and Backup copy with XO Proxies. Bug or by design ?

    Scheduled Pinned Locked Moved Backup
    13 Posts 3 Posters 360 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.
    • J Offline
      jshiells @Pilow
      last edited by

      @Pilow not easily. as an Telco/ISP we run massive multiple 40 to 100gb/s links across the country so data transfers from site to site is not an issue allowing us to have priv routed IP networks spanning anywhere. Much harder todo for SMB deployments.
      may also involve adding more vnics and IP's to XOA and XOA-PROXY

      SiteA:
      XOA
      proxy-A
      Storage-A-SR
      Backup-A-SR

      priv network routing in both directions to:

      SiteB:
      proxy-B
      Storage-B-SR
      Backup-B-SR

      so XOA, Proxy-A, Proxy-B ALL have access to:
      Storage-A-SR
      Backup-A-SR
      Storage-B-SR
      Backup-B-SR

      sorry.. this is probably not helpfull for most people 😞
      1250fe45-cf70-4fb9-9424-9f0cb0aafbc6-image.png

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

        @Pilow a Backup job cannot mix proxy and non proxy remote
        The goal of the proxy is to keep the data flow out of XO, mixing both will contradict this goal

        since you seem to want to access a remote by the proxy and the xoa, you can attach the remote twice ( one to the proxy, the other to xoa) and chose it it's better to have one read locally and write remotely or the opposite

        The only things that should be noted when using multiple xo/proxy to a remote is that you may have "lock already held" error if both are trying to read and write the same VM (but for mirror job, at worse, it means that the transfer will be done on next run

        @jshiells you had the right idea (and you have one nice network)

        P 1 Reply Last reply Reply Quote 1
        • P Offline
          Pilow @florent
          last edited by Pilow

          @florent I get your point.

          I could duplicate the remotes, one with proxy, one without proxy

          buuuuuuuuut... when i select a proxy, i only see ONE remote attached to it.
          So it defeats the possibility to use proxies in a VM MIRROR job.

          And my XOA will have to do the transfers, on remote without proxies

          Screenshot WITH proxy : i'm forced on ONE remote
          4553dd3f-a1f5-492d-82bb-7265c4dde762-{E11C3922-17E7-43B7-846B-E5B117BFB97A}.png

          Screenshot WITHOUT proxy : I can see all my remotes (but XOA is the only involved)
          bdf3a198-4e42-4173-8e2b-3add6598bbf9-{995C67D3-30A6-48AF-9A14-FD758D595EDF}.png

          I just want to do a VM MIRROR backup job, by proxies.
          Can't do that because I am FORCED to have the same remote in SOURCE and TARGET... Mirroring to the same remote makes no sense.

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

            @Pilow can you show us you remote settings ?

            let's say you have remoteproxy and remotexoa and you want to mirror the backup from remoteproxy to remotexoa

            You create a second remote on the proxy, called remotexoafromproxy that point exactly to the same folder as remotexoa, but is set on the proxy

            then you should be able to do a mirror from remoteproxy to remotexoafromproxy

            You can do the same from proxy1 to proxy2 or xoa to proxy.

            A backup job can only run on one VM , be it a proxy or a xoa. So this VM must have access to all the relevant remote

            P 1 Reply Last reply Reply Quote 1
            • P Offline
              Pilow @florent
              last edited by

              @florent okaaaay, I was taking it the wrong way.

              I managed to have one proxy to see two remotes as intended, thanks to your advice.
              Need to do some routing (DC1 and DC2 are on two distant datacenters, separate subnets) to make each proxy see the good route to each distant remote.

              Thank you !

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

                @Pilow nice, inform us if everything is ok

                P 1 Reply Last reply Reply Quote 1
                • P Offline
                  Pilow @florent
                  last edited by

                  @florent everything is okay now.
                  It's tedious to have some duplicate remotes (to be accessible from different XOproxies) but it is working.

                  side question !
                  the FOLDER param of a S3 Remote is defined on the BR itself...
                  Could you think of a way of putting this parameter also/inplaceof in the backup job definition ?

                  Say I have an S3 server, and want to differenciate the backup folders of different clients in an MSP solution based.
                  Today I have to create a BR by client for each job with subsequent folder on the SAME remote.

                  Would be easy to monitor globally the occupied space by client in different main client folders, than parsing the UUID of Jobs/VMs in a big BR full of all client VMs.

                  any idea if this could be implemented ? would be a great addon of functionnality for MSP/CSP partners using S3 BR like us

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

                    @Pilow what would need to change a lot of things. We are starting a project to rewrite the ACL, and I think it's a better way to handle it. But it will take time before releasing it.

                    1 Reply Last reply Reply Quote 0
                    • P Offline
                      Pilow
                      last edited by

                      okay we will dev the matching of vm/jobs UUIDs in the meantime to aggregate "backup size by clients"

                      or look after the api calls you do in XOA where you have the total backup size (by VM).

                      we lack the TAGS here by the way 🙏
                      we can tag VMs, but can't tag backups... neither filter VM backups by VM tag

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

                        @Pilow This one should be doable, I am adding it to our backlog

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