Topics created by CodeMercenary

@gskger Great to know, thank you.

I actually already have Ollama installed and running with Open WebUI so I can ask it ahead of time to see what it would be like. I've installed some more code specific models that are better suited to that kind of question.

Running the case fans full blast all the time would be a non-starter so I'm glad you let me know that as I count the costs of attempting this.

I guess I'll partially answer my own question by pointing out that I can background the commands with & so it should run them all at once anyway. Sorry, still new to bash scripting and my Linux skills are a bit rusty but improving.

@julien-f Thank you, that's super helpful and even easier than I thought it would be.

@CodeMercenary i have seen this as well, one of our backup repos was almost out of space, this decreased the backup speed, we thought of issues on the xoa side but it was just related to the repo itself…. So it is good to check both. The 1 gig part makes sense.

A bit after this I started having trouble again. I scrubbed my delta backup sets, switched to using SMB to access the same share and so far I'm a week in with no trouble at all. Remains to be seen if the strange failures will crop up again but so far I think this is the longest I've gone with the delta backups not having some random failure. Usually, it was a backup getting stuck in Started status for a day or two then switching to Interrupted because I'd reboot the XO VM to unstick it, then one of the VM backups will fail because a VDI is attached to DOM0. I know theoretically NFS is better than SMB but for now the one that breaks least often is the better option. Of course, maybe my issue had nothing to do with NFS but for now it's felt like SMB is more reliable.

@olivierlambert Well, last night the backup completed just fine despite me taking no action.

I updated the XO to the latest commit when I got in this morning so hopefully the issue I had back in June don't come back.

@olivierlambert It was DR. I was testing DR a while ago and after running it once I disabled the backup job so these backups have just been sitting on the server. I don't think I've rebooted that server since running that backup.

@andyhhp Well, then I'm glad I spent $35 each on the 2683s while the company spent $125 each on the 2697s. Saved me $180 and it has all the same functionality but just a bit less speed.

Inexplicably, now it's decided to start working right. I didn't do anything to the existing backup job.
f8c9acb1-b4ca-4486-8dfe-b957b94055f3-image.png

I'm glad it seems to be working now but I wish I understood why it wasn't working previously. That makes me nervous that it could stop working in the future without notice.

The only real difference is that I set up a brand new set of VMs to be backed up in the same way to the same remotes using two new backup plans. I guess this is kinda solved...

@lawrencesystems Excellent, that's what I was hoping to confirm.

@olivierlambert Sorry I didn't make this clear. I have multiple servers and one of them will not be used for production VMs. That's the server that happens to have a large amount of storage. I would not store backups on the same hardware as production work and this will not be my only backup of the production data. This server just has more storage than I have a use for so I thought it would be nice to use it for storing backups for the production servers since backups with history need a lot of space.

I do have an older server that I was considering using for backups but it just doesn't have nearly the storage as the one I'm talking about. 8TB as opposed to 90TB and it can't be easily expanded storage-wise. That one would be easier to convert to TrueNAS on bare metal.

It occurred to me last night that I could create 2TB drives for the XO VM on that server and backup to local storage in the VM. Actually one of my instances of XO is running on bare metal, instead of a VM, on that 8TB server so I could use that to backup to local storage if I didn't want to go with TrueNAS but TrueNAS has some other advantages, like providing an ISO share separate from my XCP-ng servers so it likely makes sense to go that route.

I figured, for the purpose of completion, I'd document what I did to solve this problem.

Create a new VM on the target XCP-ng host Attach 6 virtual drives to the VM in the sizes of the VM I need to migrate Install Windows Server 2022 in the target VM Format the additional 5 drives Share the 5 drives over the network From source VM on ESXi Map network drives to each of the 5 drives in the target VM Copy files and folders to each drive Originally tried using RichCopyUI which uses Robocopy but it kept crashing Finally used FreeFileSync over the course of several days and nights to do an initial copy of the data Performed one final mirror of the data from the source to the target Shut down the source VM In vCenter, detach all but the boot drive from the source VM Migrate the VM from ESXi to XCP-ng using XO Attach drive files from target VM to migrated VM Boot migrated VM, it had no network access and the CD wasn't working but a couple reboots fixed it. Only 2 of the 5 extra drives appeared. Two attached automatically but 3 weren't even visible in Disk Manager. Install XCP-ng guest tools and reboot Extra drives now working inside the VM Had to fight a little with network settings and my DHCP server to get the same IP address assigned Did some testing, had to tweak a few things in some software but everything seems to be working normally again without too much work Shut down the old host running ESXi - one step closer to severing ties with VMware and also made my server room quieter and cooler

@florent It is a very old host. In addition to moving to XCP to get away from VMware, we're upgrading to get off the oldest hosts onto a couple new hosts I just added. It's quite possible that the activity was overwhelming that rather weak old host.

@CodeMercenary To answer your questions about backups, they should all be fine, the remote is attached to XO rather than the host itself so XO can backup any VM from any host it has access to, to any remote configured in XO.