if i understand correctly i would rephrase the question this way:
does xen-orchestra name the snapshots in a way which is unique to xen-orchestra and does xoa know which snapshots belong to it or does it use the latest snapshots no matter how they are named.
@hsnyder: i dont think you can simply use zfs snapshots without xen snapshots because it dont think that they will be crash-consistent.
if syncoid is similar to zrepl you have to check that is doesnt prune the zfs snapshots from xoa.
@arc1 same situation here. we also had dmesg entries when doing live-migration. but the vm did not have any issues beside that.
@olivierlambert
So when i read the posts from @reiichi001 it is NOT possible to do an implace-upgrade from XenServer-8 to XCP-NG (8.2.1 or 8.3)
Are there any options now? Do you know of someone who has done this sucessfully without backup/restore or such thing?
Greetings, Franz
@ricardowz
No Warning. Updates are from 2. April. I attached the Screenshot.
Can someone confirm that we could just "upgrade" to XCP-NG 8.3 and the VMs will run?
Greetings
@ricardowz Are you able do attach the vhds (vdi) to a new vm after reinstalling with xcpng. so no import but using the old files.
if this works you could export the vdi to a vhd or raw and reimport it.
We didnt update to the latest xenserver version so according to your test we may be safe, but what i dont want is to reinstall with xcpng an than the vms are dead.
we have an old server so i may install xcpng there and migrate over from xenserver. than migrate back afterwards. but this is all very time-consuming in that situation.
They only document the Upgrade from XenServer-7 in your link. I have XenServer 8.4. Thats why i am asking. XenServer-8.4 is ahead of XCP-NG 8.2 and maybe XCP-NG 8.3.
So is ist safe to "upgrade" from XenServer 8.4 to XCP-NG 8.2?
Hi!
We have some hosts with XenServer-8 Trial Edition. XenServer limited the runtime to 90 days so we cannot update anymore to avoid this.
Is there an easy way to migrate to XCP-NG without Backup/Restore or Export/Import of the VMs?
We would prefere XCP-NG 8.2 but if this is not possible XCP-NG 8.3 is also an option.
I have already read to docs but i am not shure how the migration is when you come from Xenserver-8
We do not use any not supported fs (GFS,XFS). We use ext4
XenServer Version according to XO: XenServer Trial Edition 8.4.0 (trial)
Greetings!
@zmk We only had the dmesg entris on Xen, not on VMWare and not on HyperV
@arc1 same situation here. we also had dmesg entries when doing live-migration. but the vm did not have any issues beside that.
Our Issue with commvault was that despite it mounts the snapshots in the proxy VM it has to read them as a whole. So Inc Backups take nearly as long as Full backups. When you want to backup 20TB+ Incs every night, Thats not acceptable. So the Lack of CBT is really a big deal when doing VM Backups.
Performance with CommVault would be not that big of a problem since you can do multiple streams and multiple VMs simultanously but we could not get past 600MB/s which is a Xen Problem as of our Testing. With HyperV we see Performance in access of 1.6GB/s in the same Scenarios. But also this performance would be much to slow to do Incs every night.
We tested XO CBT but it was not stable and for what i read in the posts there seems to be problems with CBT and Live-Migration so that the CBT state seems to be lost. Also a big Problem for us.
When we used CommVault to backup multiple VMs we ran into Blue-Screens of the Xen Toolstack in the Windows VMs when attaching or detaching Snapshot-VDIs to the Proxy VMs. There clearly is a bug in the Xen Windows Drivers. So we had to reduce concurrency which reduced backup speed.
We didn't do a short test with xen, we migrated out internal production Cluster to it from VMWare and used it for about 4 month now (30+ VMs on iSCSI Storage with 3 Nodes) and after we ran into more and more Problems we had many discussions with our team and we had to ask ourselfes what Xen brings to the table that is worth the drawbacks. The only scenario where it fits for us is where we have to map physical hardware into VMs.
We decided to come back in some time to see how the SMAPIv3 drivers work out and if there is a better support for shared storage.
@flakpyro
To be honest we gave up on Xen for our systems where we have shared storage. We swiched to HyperV.
The Lack of CBT Support in CommVault was a major problem. We cannot use XO for backups because it lacks 90% of the features we now have with CommVault (Dedup, Tape, Agents, IntelliSnap of VM disks, AUX Copys,..) and we dont want to combine it with CommVault agents since this complicates our Backups and dies not make real sense.
HyperV with Clustering is free in our setup so it was not a big discussion there. We also can utilize the full potential (performance and feature wise) of our SAN and Network which always was a major issue with Xen.
We keep XCP-NG for now on some specialized installs where we need to map physical hardware into a vm.