@DustinB said in "Block migraton" option on the VM´s Advanced tab:
@abudef The English translation is meant to be "Prevent Migration".
I think some lines were crossed ha.
I agree it really needs to actually read "Prevent Migration", that will then make it pretty clear.
@john.c the backup on tape is still on the roadmap but won't be for this step
The main change is that we'll have to rework part of the code to ensure we write data sequentially + the management tools ( which backup is on which tape )
You can try the FS on tape , but the performance penalty is heavy
@andrewperry I myself migrated our rancher management cluster from the original rke to a new rke2 cluster using this plan not too long ago, so you should not have much trouble. Feel free to ask questions
In case someone ran into the same problem here is how I solved it.
I had a feeling this was http mounts issue. I checked and looks like during update process the .xo-server.toml got deleted. I copied the sample one from the /opt/xen-orchestra/packages/xo-server/sample.config.toml , edited the http.mount and bob's your uncle.
I have a feeling this has something to do with the format of that file change. When I originally built from source the file has a slightly different syntax and it was called .xo-server.yaml. At least according tot he directions I used to build. In any case its all back to normal now.
Thanks you everyone for your help.
Thanks, this way we'll have a way to understand what's wrong with this OVA, if it's something really specific or a VMWare way to make something we didn't expected
that's relatively easy to explain, only the naming is doubled:
the backup-hdd are local disks raid1 in xcp-ng and there brought to xcp-ng as a local "vmbackup" volume, called vmbackup
on xcp-ng-volume a disk is created with the name "backup_raid1_1tb" and connected as 2nd disk (xvdb) to XO
[image: 1559158139829-ab68fa1c-49a8-4d15-afcf-ecdc8bcd9d04-grafik-resized.png]
to make the disk available for backup-usage the disk xvdb is mounted via "remote" as a local
now usage for backup-ng is possible, but the usage is not xo_disks
I've replied on github. For sure the VMs should not boot. Of course the source vm has autopower on parameter becouse it's needed.
The problem is big: DR copy of Second Active Directory server is up.... for sure I can expect AD problems in a while...
[image: 1558999805954-724808f6-fc82-4487-9f87-4d0291fc3e92-image.png]
Autopower on is set up:
[image: 1558999897310-e4b71a2e-17cd-4e5f-a863-77f693249847-image.png]
Hi,
Before reporting on issues when you use XO from the sources, you must always fetch the latest code available on GitHub. Because it's likely some issues are fixed since then. Please upgrade, and come back if the problem persists
Okay so maybe there is a race condition somewhere with zstd (gut feeling, about premature EOF and using ZSTD). @johnelse what do you think? Do you need better logs?
