@olivierlambert
Yep! Thanks, I'll ask them now.

We have a Hyper-V server with 3 VMs. The client has finally given us the green light to upgrade the ancient hardware and also migrate to XCP-ng. Yay!

However we are having difficulty. We have exported one VM's VHD and are trying to import it into XO. We have set up a temporary network share for the purpose of making the VHD available. Here are the steps we are trying to follow:

1. Copy the VHD onto the network share.
2. Create a VM in xcp-ng with no disks.
3. Attach the VHD to the new VM.
4. Move the new VM's disk to local storage.

Any guidance or tips or guides on migrating from Hyper-V to xcp-ng would be great.

I have one question about all this though: The xcp-ng host is set up to use LVM. Given that VHDs are used in EXT mode, is the fact that we have xcp-ng with LVM set up possibly what is causing us problems with using VHDs?

Hi there,

I would like to start using NBD backups so we can get reliable off site backups over WAN links working. I've been waiting for this for a while, but I've not seen any updates on this front and Google keeps pointing to the same old forum posts I've always seen.

Where might I find up to date information on NBD backups, and any guides I might need if I were to start using them?

TIA!

@olivierlambert said in Backup remotes and resume:

edit: if you use XO from the sources for a business case which is multi-sites, I have to admit I'm a bit shocked on my side that you never considered to support the project anyway, your feedback is still welcome

We're a small MSP, just starting out, and as soon as we can convince a client of ours to pay for commercial support, you'll get a cheque from us. Which we will physically mail because sending it electronically is not supported

@olivierlambert
I know I'm speaking out of ignorance here, and I'm sure there's some good technical explanation, but I just can't wrap my head around "can copy data to portable drive and carry it physically, but cannot tar it up and send it in a resumable way".

Hi all,

I have a fleet of xcp-ng hosts running xoce. I have one central XOCE instance, with a huge disk array. The intent was to have all of the remote hosts backing up their delta backups to the central location for offsite backing up.

The problem is that if the initial backup is interrupted, then it has to start over because there is no resume. The "official" solution is to bring the initial seed over with a physical disk.

Given that there are multiple hosts that are geographically separated, and that a full backup is done once every week or so, physical transportation is not feasible.

What, if any, are the other solutions here?

On a side note, to be honest, I'm shocked that resume of large transfers is not considered a critical feature, especially given this specific use case.

@Danp
OMG it's set to 1.

How does this setting interact with full backup interval? If it's only backing up the latest 1 backup, and a full backup was more than 1 backup run in the past, how is it possible to restore even the latest backup?

Hi there,

I have an XCP-ng host with a few VMs. Delta backups are set up to send their backups to a SMB remote. it appears to be working, jobs are reporting success. We have backups every 12 hours, with a full backup interval of 10.

I am now trying to restore an old backup. When I try to restore one, however, I can only see the latest snapshot in the restore list. I cannot seem to select an older backup.

How do I restore an older snapshot?

@olivierlambert
Yep! Thanks, I'll ask them now.

@olivierlambert

Yes, sorry, I'm using the Jarli01 script:
https://github.com/Jarli01/xenorchestra_installer

Sorry, I thought Jarli01 was an xcpng developer. I will post this issue to that github account.

Hi all, I just used the update script, and it resulted in XO not starting. Here is the log for when I try to start the XO server:

Jun 07 18:39:54 xoa-HVM-domU systemd[1]: Started XO Server.
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]: (node:2709) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]: (Use `node --trace-warnings ...` to show where the warning was created)
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]: /opt/xen-orchestra/packages/xo-server/dist/xapi/mixins/index.js:2
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]: import _gpu, * as __gpu from "./gpu";
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]: ^^^^^^
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]: SyntaxError: Cannot use import statement outside a module
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]:     at wrapSafe (internal/modules/cjs/loader.js:984:16)
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]:     at Module._compile (internal/modules/cjs/loader.js:1032:27)
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]:     at Module.load (internal/modules/cjs/loader.js:933:32)
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]:     at Function.Module._load (internal/modules/cjs/loader.js:774:14)
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]:     at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29)
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]:     at ModuleJob.run (internal/modules/esm/module_job.js:152:23)
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]:     at async Loader.import (internal/modules/esm/loader.js:177:24)
Jun 07 18:39:55 xoa-HVM-domU xo-server[2709]:     at async Object.loadESM (internal/process/esm_loader.js:68:5)
Jun 07 18:39:55 xoa-HVM-domU systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Jun 07 18:39:55 xoa-HVM-domU systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 07 18:39:56 xoa-HVM-domU systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 5.
Jun 07 18:39:56 xoa-HVM-domU systemd[1]: Stopped XO Server.
Jun 07 18:39:56 xoa-HVM-domU systemd[1]: xo-server.service: Start request repeated too quickly.
Jun 07 18:39:56 xoa-HVM-domU systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 07 18:39:56 xoa-HVM-domU systemd[1]: Failed to start XO Server.

Anyone have any ideas?
Thanks!