Migrating configured backup jobs between XO from sources
-
I've noticed configured backup jobs exist only in the XO version they were configured in. Is there a way to share those jobs or migrate them without manually removing them from the original and setting them up from scratch on the new XO from sources?
-
Hi,
Before answering anything, here is my favorite question: what problem are you trying to solve?
-
Good question - my problem would be resolved with a manual update of XO (from sources) to current commit level. I don't recall how I installed the older XOs I have and they are 645 commits behind on commit 49089. If it is simple to update XO from sources, that would be ideal. I'm wondering though why backup jobs aren't part of the metadata/config of the pool.
-
Update should work, it's easy (
git pull && yarn && yarn build). You can export your config in worst case, and re-import it easily. -
@olivierlambert said in Migrating configured backup jobs between XO from sources:
You can export your config in worst case, and re-import it easily.
This, just build a new XO installation, and from the existing outdated system export the configuration and import it into your new installation.
If for some reason you were keeping the old version around, be sure to disable the backup jobs at a minimum.
-
I ran the following commands in the xen-orchestra folder and the first time it showed I was totally up to date.
git checkout .
git pull --ff-only
yarn
yarn buildI then tried it again a couple days later when I noticed a was a couple of commits behind and nothing changed, commits behind stayed the same.
Running git pull now says everything is up to date, but the UI shows I'm not.
Thoughts?
-
Maybe a cache, let me ask internally
-
@ewoudstra Simply updating the git repo and rebuilding should be enough, but it depends a lot of how your previous XO.
The data should be kept across version as they are stored in Redis and in a LevelDB database as long as you are using the same ones.
And, as @olivierlambert said, if you cannot figure out the problem, simply export the config of your previous XO and import it into the new one.
-
@ewoudstra Are you on the master branch? What is the output from
git rev-parse --abbrev-ref HEAD? -
@Danp [root@localhost xen-orchestra-202405211937]# git rev-parse --abbrev-ref HEAD
master
-
@julien-f Here is my latest attempt. I added a git pull as the first command and it shows 6 changes files. I rebooted after all of the below commands and no change in the UI for commits behind, now at 8. Note several warnings in the output as well.
[root@localhost xen-orchestra-202405211937]# git pull remote: Enumerating objects: 209, done. remote: Counting objects: 100% (204/204), done. remote: Compressing objects: 100% (58/58), done. remote: Total 209 (delta 150), reused 195 (delta 144), pack-reused 5 (from 1) Receiving objects: 100% (209/209), 86.12 KiB | 4.31 MiB/s, done. Resolving deltas: 100% (150/150), completed with 59 local objects. From https://github.com/vatesfr/xen-orchestra cd2f74cd6..3a21290fd master -> origin/master * [new branch] backups-encryption-chacha20 -> origin/backups-encryption-chacha20 1bc0f8f24..3a21290fd calculate-size-replication-in-sr -> origin/calculate-size-replication-in-sr + 83459b592...60d277ac8 doc-auth-oidc-plugin -> origin/doc-auth-oidc-plugin (forced update) aac46fc1e..6cdff03de doc-gfs -> origin/doc-gfs b165bf9f8..ed0bf9dd5 feat_minimal_2tb -> origin/feat_minimal_2tb + 9ee67f710...76cfabee0 focus-on-console -> origin/focus-on-console (forced update) + f1b000c4e...f5d0a60fc lite/vm-creation -> origin/lite/vm-creation (forced update) + 9f1a4a59b...8b9869198 merged-disk-incorrectly-marked-as-key-disk -> origin/merged-disk-incorrectly-marked-as-key-disk (forced update) * [new branch] web-stack/start-menu-implementation -> origin/web-stack/start-menu-implementation Updating cd2f74cd6..3a21290fd Fast-forward @xen-orchestra/lite/CHANGELOG.md | 1 + @xen-orchestra/lite/src/components/RemoteConsole.vue | 30 +++++++++++++++++++++--------- @xen-orchestra/web-core/lib/components/console/VtsRemoteConsole.vue | 5 +++++ CHANGELOG.md | 12 +++++++++++- CHANGELOG.unreleased.md | 7 ++++--- packages/xo-server-backup-reports/package.json | 2 +- 6 files changed, 43 insertions(+), 14 deletions(-) [root@localhost xen-orchestra-202405211937]# git checkout . Updated 0 paths from the index [root@localhost xen-orchestra-202405211937]# git pull --ff-only Already up to date. [root@localhost xen-orchestra-202405211937]# yarn yarn install v1.22.19 [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... warning bare-os@3.3.0: The engine "bare" appears to be invalid. [4/5] Linking dependencies... warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@6.1.0" has unmet peer dependency "@types/node@*". warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@6.1.0" has unmet peer dependency "typescript@>=5". warning "@typescript-eslint/eslint-plugin > ts-api-utils@1.4.3" has unmet peer dependency "typescript@>=4.2.0". warning " > @xen-orchestra/web-core@0.10.0" has unmet peer dependency "pinia@^2.2.6". warning " > @xen-orchestra/web-core@0.10.0" has unmet peer dependency "vue@~3.5.12". warning " > @xen-orchestra/web-core@0.10.0" has unmet peer dependency "vue-i18n@^9.9.0". warning " > @xen-orchestra/web-core@0.10.0" has unmet peer dependency "vue-router@^4.4.5". warning "workspace-aggregator-e573d02e-9a69-4bf3-8cea-c0c35d448b20 > @vates/event-listeners-manager > tap > @tapjs/test > @isaacs/ts-node-temp-fork-for-pr-2009@10.9.7" has unmet peer dependency "@types/node@*". warning "workspace-aggregator-e573d02e-9a69-4bf3-8cea-c0c35d448b20 > @vates/event-listeners-manager > tap > @tapjs/asserts > tcompare > react-element-to-jsx-string@15.0.0" has unmet peer dependency "react@^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0". warning "workspace-aggregator-e573d02e-9a69-4bf3-8cea-c0c35d448b20 > @vates/event-listeners-manager > tap > @tapjs/asserts > tcompare > react-element-to-jsx-string@15.0.0" has unmet peer dependency "react-dom@^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0". warning Workspaces can only be enabled in private projects. [5/5] Building fresh packages... $ husky install husky - Git hooks installed Done in 8.80s. [root@localhost xen-orchestra-202405211937]# yarn build yarn run v1.22.19 $ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web turbo 2.3.3 WARNING stale pid file at "/tmp/turbod/9f97e4722c2c3e31/turbod.pid" • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web • Running build in 22 packages • Remote caching disabled Tasks: 25 successful, 25 total Cached: 24 cached, 25 total Time: 1.905s Done in 2.10s. [root@localhost xen-orchestra-202405211937]# -
@ewoudstra I assume that you are using a service to start XO. Did you restart the service after performing the update?
-
@Danp Restarted whole server.
-
I decided to install a new server and use ronivay's script from github to install and later update XOCE. It is working well for me and I'm not going to work on fixing the other server now.
