Best posts made by lawrencesystems

@AlexanderK

Clonezilla is my go to for doing that. I have a tutorial where I should how to migrate from Virtualbox to XCP-NG here:
https://youtu.be/wSTk9BLwF5k

@olivierlambert

I work with enterprise companies and they NEED those reminders to let them know they should be using the supported version. I don't really see them as annoying at all.

@bullerwins

It's a wonderful feature, you can have customized filters for VM, storage, Templates, and Pools. Combine that with using lots of tags and it makes larger deployments very manageable.

@CodeMercenary

Under the xo-vm-backups directory is a series of directories named with UUID's that contain everything that belongs to a particular VM's backup. As long as you keep each directory and all the contents nested within it you will be able to restore that VM.

@jasonnix

That is enough to get it working and fine for most homelab environments.

@MichaelCropper
I recently did a video tutorial on how XCP-NG virtual machine dynamic memory management and over allocation works.

https://youtu.be/Lsi2-hAoKSE

@Matteo

If the storage type you have the VM is thick provisioned it will take up more space. Use a thin provisioned storage for better storage efficiency
https://xcp-ng.org/docs/storage.html#storage-types

If you choose 2 storage destinations it will copy to each of them at the same time.

@McHenry

I have a video breaking down how XCP-ng and XO work and at the 14:50 mark in my video here I break down how the XO Proxy works.

https://youtu.be/CEUFHudLO1g?si=UpoCWc6wCrK4iXFX

@nikade
Something to consider is that due to the way XCP-ng isolates for each disk for each VM for better security there can be some performance issues. But because it's per VM (unless your use case is to only running a single VM) this is less of an issues as most people run many VM's.

@olivierlambert

Very well said and an excellent read. Now I need to read https://un.curl.dev/

@olivierlambert

This was a full backup not a delta so that makes sense. I think I need more of my lab servers to be on 8.3 so I can do some more testing. I did not find any issues and nothing broke using it so I need to try harder.

I did some testing with the 8.3 and it all went smooth except for one thing. We did a backup of a VM on 8.3 and if we try and restore it to version 8.2 I get the error

"IMPORT_INCOMPATIBLE_VERSION"

which makes sense and it's just a lab system so nothing critical. Is there a way to bring it back to 8.2 or should I update the rest of my lab to 8.3?

@Danp Thanks, that makes sense. Perhaps is should show "Premium Feature" instead of "netdata plugin is necessary" when using the free versions.

@damjank
I have a video on dynamic memory here:
https://youtu.be/Lsi2-hAoKSE

@isener

I think the XO-CLI has to be registered with XO to get it working and seeing as you are locked out that is not an option. Maybe someone here will offer a way to edit the database if not I would just delete and rebuild XO.

@julien-f

Thanks, that fixed it!

@florent

No encryption on this remote. And if I have time before I leave I will test importing the XVA with CLI and see what error I get.

@AlexanderK This occurs on Synology as well. Without any corresponding errors coming from the TrueNAS target regarding permissions I don't see this as the same bug. It's also not occurring consistently so there is some combination of conditions that has to occur for this bug to trigger which is why I am testing so much.

@florent
I updated to xo-server 5.100.0 and xo-web 5.101.0 and the issue has changed a bit with this version.

I created a new delta backup job to that same remote. It does the first backup as full and the files are there. The next run does the delta, transfers, backup job says success, I do get the Error: EACCES: permission denied, rename in the XO syslog and still no denied error in TrueNAS, then all the files in that directory are gone. When the job runs again it does not see any deltas so does a full and the file for the full is there again.

I am going to setup another share on a different device to see if this is just something weird with SMB in TrueNAS and I might try NFS as well. We have a few other remotes so I have a few scenarios to test.

Since the update I have run full backup that have taken over an hour to complete due to their size and many smaller delta backups and the error has not come up again. I assume whatever was causing the error was fixed in the xo-server 5.84.2 update.