Xen Orchestra - a web solution for XenServer

DustinB3403

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.

DustinB3403

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

olivier

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

DustinB3403

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

olivier

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

DustinB3403

git branch = next release (confirmed)

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

sudo npm i (is running now)

olivier

Just the first line will give you the last commit message, be sure it's my merge of a pull request 200.

DustinB3403

That is what I have..

olivier

You forgot to git pull to get last changes

DustinB3403

git pull

On the right pull (now)

olivier

Better! So npm i now

edit : and restart xo-server. Now got you the Continuous Delta

DustinB3403

olivier

Only warnings, go ahead.

DustinB3403

Awe-YEAH!

Rebooting!

(put a tiny version id on the web console somewhere)

olivier

So it worked as expected?

olivier

Made a test by using the "old" Delta backup first with a retention of 3 (stopped after 6 manual calls):

As you can see we got 2 full disks rolled. Then upgrading to the new system and restart the backup:

Old files are correctly "garbage collected"

olivier

Currently uploading new XOA's, but:

Alex Sage

@olivier can you please give us a quick guide on how to update to to the lastest version if your running from source?

DustinB3403

@anonymous said:

@olivier can you please give us a quick guide on how to update to to the lastest version if your running from source?