Migrating configured backup jobs between XO from sources

ewoudstra

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?

olivierlambert

Hi,

Before answering anything, here is my favorite question: what problem are you trying to solve?

ewoudstra

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.

olivierlambert

Update should work, it's easy (git pull && yarn && yarn build). You can export your config in worst case, and re-import it easily.

DustinB

@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.

ewoudstra

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 build

I 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?

olivierlambert

Maybe a cache, let me ask internally

julien-f

@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.

Danp

@ewoudstra Are you on the master branch? What is the output from git rev-parse --abbrev-ref HEAD?