job still runs for 4 days🙄
Every time it can't write 1 vm backup to 1 of 2 storages. And every time it different vm.
Other jobs works fine with same storage.

The issue was resolved after installing XO from the source on another Debian 11 VM.

@olivierlambert @julien-f 61691ac46b50659f05159594b8c672b6187a9f9c causes my S3 backup failures.

packages/vhd-lib/Vhd/VhdDirectory.js childBlockPath === undefined

@olivierlambert Yes, each job has a unique identifier and willl not touch backup files of other jobs.

What operating system do you have?
Does it run on the same type of real server?
If not.
If VM it is Windows, you must reset (sysprep) or insert the hdd drivers. Acronis is a solution for that, or Dism++ and ImDisk to insert dirvers on vhd.
If VM it's Linux, you don't have the correct disk name or partition ID, the boot partition must be redone. Reinstall kernel, in chroot with live CD, to solve the problem.

For an easier process, I recommend Hyper-V -> VirtualBox -> XCP-ng. With VirtualBox you will have fewer problems when restoring the boot. And VirtualBox is much more compatible with XCP-ng.

@Kajetan321 I think there is a misunderstanding how the ISO repository works vs. the XO remotes.

The remotes on XO are connected to XO and not XCP. XO used them for backups, etc.

The ISO repository is connected to each XCP host server. You can't use an ISO on XCP that is accessible only by XO. So if XO has access to the ISOs it won't help because XCP needs direct access to them.

When you use an ISO to boot or mount in a VM it needs to be accessible to the XCP host and not the XO system.

So if you have a pool of 200 XCP hosts then you add the ISO repository (NFS share) to the pool once.

If you have 200 XCP hosts (not a pool of 200) then you need to add the shared ISO to each XCP host (or each pool that's a group of hosts).

Just script adding it to the servers.

@tjkreidl said in XO spawned VM from template has wrong VIF network order:

I have seen NICs randomly change order on hosts in the past - scary stuff!

This is why Linux switched from eth0 naming to names like enp5s0 etc. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

@olivierlambert said in XO can't connect to XCP-NG host and Issue with Secure Boot:

xe vm-param-set uuid=<UUID> platform:secureboot=false

Thank you! This did the trick! Our Windows Server 2019 is now up and running.

@vbits said in Delta backup fails on SMB remote:

NexentaStor SC216

Yes that was the question 😉 If you have better speed with SMB stay with it NFS should be better in theory but sometime you have to go with real world reality.

@olivierlambert Yes, it seems so. The switches are of different brands between RACs and since a year ago the datacenter was divided in 2 companies and we are not sure how they have organized the networks.
Then I had another error but with "rescan all disks" on the host it was solved.
🙂

Okay thanks for the feedback 🙂 Let's see if we can fix it with a text box/area instead of a simple text field!

Re-ping @julien-f

Ah great 🙂

@Gheppy I will ask @marcungeschikts to take a look at this and talk to dev team about it

@Andrew Hi Andrew,

Metadata backup use the report plugin settings to send mail so you can define the email address there.

You should be able to go to the network tab for the VM, click the network it's currently connected to, and then change it to the new one. If you have the management tools installed this can be done live, otherwise you'd need to shut the VM down.

9fd8274e-8c52-4d2c-83b1-ff14c43e0416-image.png

4278a01c-eee3-49ed-a60c-95a8729312fd-image.png

You can only if you select Cloud init.

Answered on Github.

@olivierlambert OH nice! That will be awesome, I can't wait to try it.

@julien-f Much better! I can add servers/remotes/jobs again. Thanks!