What generally limits the migration speed? My installation is seeing a phenomenon that might be similar — when migrating between SRs we're only getting about 20 MB/s, while everything is wired together with 10 Gbps links.

I was about to tell you a warning about doing on CR on the same host but you are aware about the risk doing that, so I have nothing to add, it looks OK 😛

🍾

@manilx Just happened on our production Pools. Snapshotting Windows Server 2022 crashes our ERP VM!

Opening official ticket referencing this thread.

You can check if there's an Github issue opened for that. If yes, you can track the status. If not, there's little chance it would be done 😄

@Danp I got around this by using Clonezilla to copy the disks of the 2 VMs I was having an issue with. This is very strange. The VMs booted and ran fine on the old host, I was able to clone them with Clonezilla to the new host where they also boot and run fine. There is something preventing the native tools from migrating these specific disks though.

@propsoft said in Can .keeper files be deleted from the backup share?:

@florent Thank you.
I just like things to be 'tidy' that's why I asked.

Then stop looking at hidden files.... HA

Many thanks @nathanael-h & @shinuza , both approaches indeed work!

@DustinB

As to why you're seeing "VM not found!" I don't know if that is a XO alert or something you added into the screenshot, I've never seen that so I can't speak to it.

I didn't add the text, all I did was highlight it with the red surround.

Just testing the backups again using the 'Delta' method and '[NOSNAP][NOBAK] Data drive' as the name of the second drive , feeling more hopeful about this one though.

I'm starting to like XO the more I use it, would be good to move to this instead of switching between 2 different XCP-ng Center EXEs. depending on the XCP-ng version on the host so I really hope I can get this to work.

The scheduled hourly snapshot while the guest is running looks a great feature, although I need to learn to walk with this first before I go that far 🙂

Permissions will come in XO 6 this year 🙂

@HamiltonWDS Thanks for the report. As it works with wget let use it! I'll switch from curl to wget in doc. In the meantime some colleagues will investigate more.

Sure, happy to have a PR on our doc!

Thank you very much for the clear explanation @HamiltonWDS ! This will be really helpful so we find a solution for that. We might default to IPv4 for a lot higher latency, and in the future maybe having closer location mirrors. Let me discuss this internally and schedule an action for that.

The simple answer here is to use the Continuous Replication backup type. It'll copy the VM to another host on whatever schedule you set.

It couldn't be simpler.

@olivierlambert No, i changed nothing.The boot Mode is UEFI (see first screenshot).
I will check if a downgrade (if it's possible) fix this issue.

Hi!

Yes, we'll develop the hub in the future, we just lack the resource internally to prioritize this against the rest, but as we a growing fast, expect more things coming in here 🙂

I have no idea for the legacy Linux tools, they are badly coded and you can get rid of them entirely We've been using them in prod since almost a year without any issue. 1.0 will come soon but it's already very stable and safe (it's written in Rust). Our goal is to get them in all Linux distro upstream ASAP.

Posted this as I personally found this configuration quite involved, and the permissions earlier in the thread were insufficient to make it work when using AWS KMS for bucket encryption as well as the XO provided encryption secret.

@olivierlambert If you want me to check anything else, just tell me and I will test for you.

Many Thanks

BR
Marco

@mtcoffee Thank you. Just what I need.