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.
    • DustinB3403D
      DustinB3403 @coliver
      last edited by

      @coliver said:

      Is Terminated a good thing in this case?

      If it's red, no.

      Green yes.

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

        When it is green, yes. That means the backup finished, I think.

        Edit: Dustin beat me to it.

        1 Reply Last reply Reply Quote 0
        • coliverC
          coliver @DustinB3403
          last edited by

          @DustinB3403 said:

          @coliver said:

          Is Terminated a good thing in this case?

          If it's red, no.

          Green yes.

          Ah, that is a bit confusing (I understand the lights.) I saw that when I did my first backup and assumed terminated means something failed.

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

            We'll have to bug @oliver if it doesn't change after they get the new UI in place, lol.

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

              @olivier -- the xo-server-logs and xo-server are only outputting generic information and don't display anything useful for me to debug this on the screen. Is this written to a file anywhere?

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

                You should see something in the xo-server output right when you trigger the backup job.

                I'm removing the word "Terminated" by "Finished" ASAP.

                coliverC 1 Reply Last reply Reply Quote 1
                • coliverC
                  coliver @olivier
                  last edited by

                  @olivier said:

                  You should see something in the xo-server output right when you trigger the backup job.

                  I'm removing the word "Terminated" by "Finished" ASAP.

                  Perfect thank you. I don't know why when I see terminated I think "this is bad"... especially when it basically means finished.

                  1 Reply Last reply Reply Quote 0
                  • brianlittlejohnB
                    brianlittlejohn
                    last edited by

                    Yea, terminated has a bad connotation to it... i know i immediately equate it to "fired"

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

                      There is maybe a notion of "unexpected finish" for "terminated" word. In French, "Terminรฉ" means "finished". That explains why one of the dev use this word ๐Ÿ˜›

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

                        Done: https://github.com/vatesfr/xo-web/commit/f9028cb366e6a102a5a0fd54755c7c0163e62a3c

                        JaredBuschJ 1 Reply Last reply Reply Quote 0
                        • JaredBuschJ
                          JaredBusch @olivier
                          last edited by

                          @olivier said:

                          Done: https://github.com/vatesfr/xo-web/commit/f9028cb366e6a102a5a0fd54755c7c0163e62a3c

                          Re job 9: Personally, I would not say finished here. Simply state error or Failure or something.

                          I know it IS finished. but say you eventually setup an email on job status. how will I route it with rules if both success and failure say finished?

                          This is how I handle my veeam backup stuff now.

                          So, all my notices are filtered away unless it has some other status.

                          https://i.imgur.com/MPZJ1hR.jpg

                          https://i.imgur.com/D1whu9s.jpg

                          Well except this warning. These are success too. The damned HP recovery partition always fires a warning on space.

                          https://i.imgur.com/vztYv2R.jpg

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

                            I'll need to hire 50 lads to release all those ideas/features ๐Ÿ˜“

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

                              I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).

                              When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.

                              This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.

                              Is this a bug in XO, by any chance? @olivier ?

                              If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?

                              A stacksofplatesS 3 Replies Last reply Reply Quote 2
                              • A
                                Alex Sage @dafyre
                                last edited by Alex Sage

                                @dafyre How does it even know what the public IP is? ๐Ÿ˜•

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

                                  @dafyre said:

                                  I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).

                                  When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.

                                  This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.

                                  Is this a bug in XO, by any chance? @olivier ?

                                  If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?

                                  You're running XO in a vm on the XenServer?

                                  DustinB3403D 1 Reply Last reply Reply Quote 0
                                  • DustinB3403D
                                    DustinB3403 @stacksofplates
                                    last edited by

                                    @johnhooks said:

                                    @dafyre said:

                                    I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).

                                    When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.

                                    This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.

                                    Is this a bug in XO, by any chance? @olivier ?

                                    If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?

                                    You're running XO in a vm on the XenServer?

                                    Yes.

                                    That is normal.

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

                                      @DustinB3403 said:

                                      @johnhooks said:

                                      @dafyre said:

                                      I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).

                                      When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.

                                      This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.

                                      Is this a bug in XO, by any chance? @olivier ?

                                      If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?

                                      You're running XO in a vm on the XenServer?

                                      Yes.

                                      That is normal.

                                      I just wanted to make sure I understood how he set it up.

                                      1 Reply Last reply Reply Quote 0
                                      • DustinB3403D
                                        DustinB3403
                                        last edited by

                                        Now it wouldn't hurt to have a separate host, but on the primary host is also normal.

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

                                          @dafyre said:

                                          I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).

                                          When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.

                                          This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.

                                          Is this a bug in XO, by any chance? @olivier ?

                                          If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?

                                          Another question, is this a bridge for an internal network? Or did they give you a local network for your server?

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

                                            @anonymous said:

                                            @dafyre How does it even know what the public IP is? ๐Ÿ˜•

                                            This is what I'd like to know, lol. I am expecting it is something in the XAPI or something with XenServer configs somewhere... It should be noted that this is a Dedicated machine rented from KimSufi in France. I have exactly 1 public IP that I can use for this server.

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