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

    Xen Orchestra - a web solution for XenServer

    IT Discussion
    xen xenserver xcp xen orchestra virtualization open source
    6
    42
    9.7k
    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.
    • olivierO
      olivier
      last edited by olivier

      /teasing:

      edit: blog post is out: https://xen-orchestra.com/blog/xenserver-vm-continuous-replication/

      Currently in QA.

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

        @olivier

        cd xo-server/bin
        git clone https://github.com/rubiojr/vhd-util-convert
        sudo apt-get -y uuid-dev build-essential
        cd vhd-util-convert
        make
        ls
        cp vhd-util ~/xo-server/bin
        

        Appears to work, has the WebGui been updated with a new Backup title for Delta or no?

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

          No new thing in the web UI for continuous delta, it's automatic. If you are on next-release, it should already work now.

          edit: it's the same job/backup thing. So restart after update, and re-run your backup jobs. You'll see the oldest delta merged in the full.

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

            eh, I've completely forgotten how to jump to the next-release....

            Not enough coffee.

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

              Don't forget to copy the vhd-util binary directly in xo-server/bin. The vhd-util-convert folder is useless after the make!

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

                Think I got it.

                Have to test. Does that look correct?

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

                  Yep.

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

                    Due to problem with XAPI and metadata import, I decided it's more safe to write ourselve a solution to avoid use of those metadata. XAPI team told me that the code around this is not in a good shape...

                    So postponed for Monday. Sorry guys, there is some stuff we can't guess before we got trouble inside XAPI ^^

                    edit: at least our QA pass is useful ^^

                    1 Reply Last reply Reply Quote 1
                    • mlnewsM
                      mlnews
                      last edited by

                      Maybe time to update XAPI 🙂

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

                        @mlnews Problem is also in next XenServer version. So we'll have better luck to write our own solution/workaround for this!

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

                          @olivier question for you.

                          I Migrated a VM from a shit-box XenServer, and it's running on the other host, but Xen Orchestra doesn't see this VM on the Host.

                          Any ideas?

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

                            So here is a system that I've been running with the Continuous Backup functionality.

                            Which I scheduled to run every 5 minutes. I would say it works unless the fulls in the 3rd picture should be completely gone.

                            I know the first picture says, "every hour on the hour" it's simply because I changed the frequency in which the backup runs.
                            0_1452892634446_Xen_Orchestra_-_Google_Chrome_2016-01-15_16-16-29.png

                            0_1452892222612_XenCenter_2016-01-15_16-10-15.png

                            0_1452892288734_XenCenter_2016-01-15_16-11-21.png

                            0_1452892257480_XenCenter_2016-01-15_16-10-43.png

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

                              I think because it was a previous delta job, it didn't modified some old files (I'm not certain of the behavior when changing in the middle of a previous delta job, I didn't personally coded this part ^^)

                              So is it still working or not?

                              If not, delete the old backup files, it will re-create the right things accordingly.

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

                                @olivier I'll purge them and have them run every hour.

                                Will post some new picture tomorrow from home.

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

                                  Oh but that was a new backup job that I had built (completely new XO Server as well) so not sure that makes sense.

                                  Maybe it's not compiled right.

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

                                    Anyways a new job is scheduled to run in 30 minutes, and then every hour on the hour.

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

                                      If it's a new job, you shouldn't have multiple copies of a full VHD. Check your build!

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

                                        @olivier Is there somewhere specific I should be looking at to see if I'm "current" ?

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

                                          @DustinB3403 your branch (git branch should be next-release), then be sure you get the latest commit with git log (Merge pull request #200).

                                          npm i also to be sure you have every dependencies (and it will also build)

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

                                            git branch = next release (confirmed)

                                            git log (lots of information, gonna read that later.... 🙂 )

                                            sudo npm i (is running now)

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