Xen Orchestra - a web solution for XenServer
-
If it's a new job, you shouldn't have multiple copies of a full VHD. Check your build!
-
@olivier Is there somewhere specific I should be looking at to see if I'm "current" ?
-
@DustinB3403 your branch (
git branch
should be next-release), then be sure you get the latest commit withgit log
(Merge pull request #200).npm i
also to be sure you have every dependencies (and it will also build) -
git branch = next release (confirmed)
git log (lots of information, gonna read that later.... )
sudo npm i (is running now)
-
Just the first line will give you the last commit message, be sure it's my merge of a pull request 200.
-
That is what I have..
-
You forgot to
git pull
to get last changes -
git pull
On the right pull (now)
-
Better! So
npm i
nowedit : and restart
xo-server
. Now got you the Continuous Delta -
-
Only warnings, go ahead.
-
Awe-YEAH!
Rebooting!
(put a tiny version id on the web console somewhere)
-
So it worked as expected?
-
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"
-
Currently uploading new XOA's, but:
- code is already merged in stable
- existing XOAs can already upgrade!
-
@olivier can you please give us a quick guide on how to update to to the lastest version if your running from source?
-
@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?