ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Xen Orchestra Backup, Single VM Failing

    IT Discussion
    xen orchestra delta backup
    12
    65
    14.1k
    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.
    • travisdh1T
      travisdh1 @dafyre
      last edited by

      @dafyre said:

      If I undo all my iptables trickery, XenCenter and XO work fine if they are run locally from my home network.

      If I leave all my iptables trickery undone, XO works fine if I run it as a VM behind the XenServer, except for backups.

      My problem is that XenServer uses ports 80 and 443 for itself on the public IP address. I need those ports to run my web sites from.

      Install a software firewall of some sort, and assign that the public IP address. Choose a different subnet for XenServer, and forward different ports from the Public IP software router to XenServer's 80 and 443. I wouldn't want my VM host sitting on the public net. Dunno how easy it is to "go touch the box" if you mess something up along the way, but that'd be the minimum to me.

      dafyreD 1 Reply Last reply Reply Quote 1
      • dafyreD
        dafyre @travisdh1
        last edited by

        @travisdh1 said:

        @dafyre said:

        If I undo all my iptables trickery, XenCenter and XO work fine if they are run locally from my home network.

        If I leave all my iptables trickery undone, XO works fine if I run it as a VM behind the XenServer, except for backups.

        My problem is that XenServer uses ports 80 and 443 for itself on the public IP address. I need those ports to run my web sites from.

        Install a software firewall of some sort, and assign that the public IP address. Choose a different subnet for XenServer, and forward different ports from the Public IP software router to XenServer's 80 and 443. I wouldn't want my VM host sitting on the public net. Dunno how easy it is to "go touch the box" if you mess something up along the way, but that'd be the minimum to me.

        This is a physical server hosted @ Kimsufi in France, lol. Physical trips are not an option. 🙂

        If I snafu it that badly, I can wipe & reload the machine through their web interface. Once I get it set up right, I'll be locking down the ports for XenCenter, etc, to only allow connections from my home IP address.

        travisdh1T 1 Reply Last reply Reply Quote 1
        • travisdh1T
          travisdh1 @dafyre
          last edited by

          @dafyre said:

          @travisdh1 said:

          @dafyre said:

          If I undo all my iptables trickery, XenCenter and XO work fine if they are run locally from my home network.

          If I leave all my iptables trickery undone, XO works fine if I run it as a VM behind the XenServer, except for backups.

          My problem is that XenServer uses ports 80 and 443 for itself on the public IP address. I need those ports to run my web sites from.

          Install a software firewall of some sort, and assign that the public IP address. Choose a different subnet for XenServer, and forward different ports from the Public IP software router to XenServer's 80 and 443. I wouldn't want my VM host sitting on the public net. Dunno how easy it is to "go touch the box" if you mess something up along the way, but that'd be the minimum to me.

          This is a physical server hosted @ Kimsufi in France, lol. Physical trips are not an option. 🙂

          If I snafu it that badly, I can wipe & reload the machine through their web interface. Once I get it set up right, I'll be locking down the ports for XenCenter, etc, to only allow connections from my home IP address.

          I haven't tried this myself, but I bet you could get ZeroTier running on a XenServer. I might have to attempt that at work tomorrow actually, would be really handy.

          1 Reply Last reply Reply Quote 1
          • dafyreD
            dafyre
            last edited by

            I have actually considered that. That doesn't fix my underlying problem though. I can't change the ip or ports that XenServer is listening on through config files, etc that I have found.

            1 Reply Last reply Reply Quote 0
            • stacksofplatesS
              stacksofplates
              last edited by

              One more question, are the backups being done on a local folder on the XO server or NFS?

              dafyreD 1 Reply Last reply Reply Quote 0
              • dafyreD
                dafyre @stacksofplates
                last edited by

                @johnhooks said:

                One more question, are the backups being done on a local folder on the XO server or NFS?

                I started with a local folder on XO, and someone else suggested NFS as well. Either makes no difference. I can see in the XO log files that it is connecting to my public IP and failing because by default, IPTables doesn't like hairpin connections.

                1 Reply Last reply Reply Quote 0
                • stacksofplatesS
                  stacksofplates
                  last edited by

                  I'll have to play around with it. I'm using a separate physical NFS share for backups. I wonder if the XO backups don't run through 443? If I get a chance I'll wireshark and see what's going on.

                  1 Reply Last reply Reply Quote 0
                  • dafyreD
                    dafyre
                    last edited by

                    Well, a sudden bright idea later, and my backups are running... . I modified the hosts file on the XenServer to point to my internal IP address, and now XenOrchestra seems to be working... My backup is running as we speak. lol.

                    stacksofplatesS 1 Reply Last reply Reply Quote 3
                    • stacksofplatesS
                      stacksofplates @dafyre
                      last edited by

                      @dafyre said:

                      Well, a sudden bright idea later, and my backups are running... . I modified the hosts file on the XenServer to point to my internal IP address, and now XenOrchestra seems to be working... My backup is running as we speak. lol.

                      Nice!

                      1 Reply Last reply Reply Quote 0
                      • dafyreD
                        dafyre
                        last edited by

                        The only other thing I have an issue with is that XO still tries to connect to the public IP address when I need to connect to the VM consoles and such. (I can't actually install any VMs at the moment, since I can't get console access).

                        1 Reply Last reply Reply Quote 0
                        • olivierO
                          olivier
                          last edited by olivier

                          Hi there!

                          XO just uses the host.address value from XAPI, for all operations (backup which use the XAPI HTTP handler for export but also import, consoles, etc.)

                          You'll have to find a way to have XAPI telling that host.address is the one you want.

                          The XAPI doc says:

                          The address by which this host can be contacted from any other host in the pool

                          See http://xapi-project.github.io/xen-api/classes/host.html

                          1 Reply Last reply Reply Quote 2
                          • 1
                          • 2
                          • 3
                          • 4
                          • 4 / 4
                          • First post
                            Last post