<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with backup]]></title><description><![CDATA[A list of topics that have been tagged with backup]]></description><link>https://xcp-ng.org/forum/tags/backup</link><generator>RSS for Node</generator><lastBuildDate>Tue, 13 Oct 2026 03:09:56 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/tags/backup.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 15 May 2026 14:22:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Slow Backups | XOA Performance Test – Upgrading from 2 vCPU to 4 vCPU / 8GB RAM]]></title><description><![CDATA[the last rewrite of the stream processing ( spring 2025 ) focused on stability and memory footprint, and , on a standard cpu, it tops at around 300MB/s per backup job. Your benchmarks are very interesting, and they confirm most of it.
this limit was not really an issue since, in most case the xapi was limiting around 100MB/s per disk , but it will be more a more visible limit
Note that master have some fixes on the memory usage (not related to backups)
That's why we have started an internal workforce focused on performance, with all the teams from the kernel to the backups, including storage, network and xapi.
If I can brag a little :
[image: afd7b59b-a4f0-4a92-88ee-2c7ba52d18bf-image.jpeg]
i9 , nvme disk , backup to a nvme disk in passthrough, xoa and vm are on the same host, so it's quite far from real world data, but it shows where the limit is
]]></description><link>https://xcp-ng.org/forum/topic/12219/slow-backups-xoa-performance-test-upgrading-from-2-vcpu-to-4-vcpu-8gb-ram</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12219/slow-backups-xoa-performance-test-upgrading-from-2-vcpu-to-4-vcpu-8gb-ram</guid><dc:creator><![CDATA[florent]]></dc:creator><pubDate>Fri, 15 May 2026 14:22:22 GMT</pubDate></item><item><title><![CDATA[Warnings with Backups?]]></title><description><![CDATA[@TechGrips Sorry, there is no quick test to be sure the VM is not corrupted. The usual way would be to make a healthcheck. We cannot be sure everything is ok as it concerns multiple tar linked to each other. If it keeps warning you on the same backups, it may be due to a faulty parent. You would need for this to create a new chain of snapshot
]]></description><link>https://xcp-ng.org/forum/topic/12054/warnings-with-backups</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12054/warnings-with-backups</guid><dc:creator><![CDATA[pierrebrunet]]></dc:creator><pubDate>Mon, 06 Apr 2026 00:47:08 GMT</pubDate></item><item><title><![CDATA[VM won't migrate to other host after failed backup.]]></title><description><![CDATA[@Danp Thanks... Just ticked that off and they are migrating. I'll try backup again but something tells me the backup issue will still persist. I'll send logs once that fails.
]]></description><link>https://xcp-ng.org/forum/topic/11153/vm-won-t-migrate-to-other-host-after-failed-backup.</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11153/vm-won-t-migrate-to-other-host-after-failed-backup.</guid><dc:creator><![CDATA[thedobe]]></dc:creator><pubDate>Sat, 09 Aug 2025 11:00:45 GMT</pubDate></item><item><title><![CDATA[Running a Backup Job for a Pool that wasn't previously in said backup job]]></title><description><![CDATA[@Danp said in Running a Backup Job for a Pool that wasn't previously in said backup job:

@DustinB said in Running a Backup Job for a Pool that wasn't previously in said backup job:

Are you suggesting for just this run I remove the old pool from this section and rerun the job?

Yes.

Making those changes now and running the job.
Thanks for confirming
]]></description><link>https://xcp-ng.org/forum/topic/10303/running-a-backup-job-for-a-pool-that-wasn-t-previously-in-said-backup-job</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10303/running-a-backup-job-for-a-pool-that-wasn-t-previously-in-said-backup-job</guid><dc:creator><![CDATA[DustinB]]></dc:creator><pubDate>Thu, 23 Jan 2025 13:07:07 GMT</pubDate></item><item><title><![CDATA[Backup Retention vs Long-Term Backup Retention]]></title><description><![CDATA[@DustinB
Yes
]]></description><link>https://xcp-ng.org/forum/topic/10224/backup-retention-vs-long-term-backup-retention</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10224/backup-retention-vs-long-term-backup-retention</guid><dc:creator><![CDATA[ph7]]></dc:creator><pubDate>Tue, 07 Jan 2025 13:19:23 GMT</pubDate></item><item><title><![CDATA[vdi related to multiple VMs? - Error with backups]]></title><description><![CDATA[We ran into the same issue as well. We removed ALL snapshots of this vm and then it started working again. Comes at a cost since we had to remove the non-backup-related snapshots as well...
]]></description><link>https://xcp-ng.org/forum/topic/10148/vdi-related-to-multiple-vms-error-with-backups</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10148/vdi-related-to-multiple-vms-error-with-backups</guid><dc:creator><![CDATA[hannes]]></dc:creator><pubDate>Fri, 20 Dec 2024 02:36:32 GMT</pubDate></item><item><title><![CDATA[XO (from source): backup error (to Wasabi)]]></title><description><![CDATA[@olivierlambert said in XO (from source): backup error (to Wasabi):

If you need another trial, no problem. To me, the problem is not in XOA (the broken commit was done after the monthly release) and fixed today, so it means it would be never shipped in XOA.

Then I am fine, building XO from Sources provides me with the ability to backup my VMs, which was the only XOA "Feature" I was using...
Thanks anyway!!!
]]></description><link>https://xcp-ng.org/forum/topic/9641/xo-from-source-backup-error-to-wasabi</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/9641/xo-from-source-backup-error-to-wasabi</guid><dc:creator><![CDATA[Lhoust]]></dc:creator><pubDate>Tue, 17 Sep 2024 07:38:40 GMT</pubDate></item><item><title><![CDATA[XOA: backup Active Directory vm]]></title><description><![CDATA[According to Microsoft you need to use their built in backup feature or a software that supports AD and VSS which will tell the VM OS that it is going to be backed up.
Unless you do this there might be corruption of the AD Databases according to Microsoft.
ALL THO we've been backing up our AD servers with XOA snapshots (Both normal backup and incremental) and had only 1 issue since we started using XOA in 2016.
Since that issue we also use a guest agent (From Ahsay CBS) that makes a Windows System State backup and Windows System Backup.
More info about that can be found here:
https://wiki.ahsay.com/doku.php?id=public:version_9:client:9447_system_state_backup_vs_system_backup
]]></description><link>https://xcp-ng.org/forum/topic/9189/xoa-backup-active-directory-vm</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/9189/xoa-backup-active-directory-vm</guid><dc:creator><![CDATA[nikade]]></dc:creator><pubDate>Thu, 13 Jun 2024 07:12:48 GMT</pubDate></item><item><title><![CDATA[Boot Windows VM to check for system corruption]]></title><description><![CDATA[Even with a sfc and cleanup, manually reinstalling the package caused the same behavior. I've got backups of this system and will build a template from the working backup for if it goes sideways.
I've got other stuff to handle.
]]></description><link>https://xcp-ng.org/forum/topic/8495/boot-windows-vm-to-check-for-system-corruption</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/8495/boot-windows-vm-to-check-for-system-corruption</guid><dc:creator><![CDATA[DustinB]]></dc:creator><pubDate>Wed, 28 Feb 2024 21:27:30 GMT</pubDate></item><item><title><![CDATA[Unused VHD and Incorrect Metadata]]></title><description><![CDATA[Are these issues resolved with a Full backup?
Just curious as to how they might come about, and what the implications are.
Thanks again
]]></description><link>https://xcp-ng.org/forum/topic/8345/unused-vhd-and-incorrect-metadata</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/8345/unused-vhd-and-incorrect-metadata</guid><dc:creator><![CDATA[DustinB]]></dc:creator><pubDate>Fri, 09 Feb 2024 15:07:16 GMT</pubDate></item><item><title><![CDATA[Even faster file level restore]]></title><link>https://xcp-ng.org/forum/topic/7577/even-faster-file-level-restore</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/7577/even-faster-file-level-restore</guid><pubDate>Mon, 31 Jul 2023 16:00:06 GMT</pubDate></item><item><title><![CDATA[XO Backup - question on file level restore]]></title><description><![CDATA[I have opened a ticket to support because file level restore doesn't work anymore after latest update.
Best regards
Walter
]]></description><link>https://xcp-ng.org/forum/topic/7299/xo-backup-question-on-file-level-restore</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/7299/xo-backup-question-on-file-level-restore</guid><dc:creator><![CDATA[secureme]]></dc:creator><pubDate>Tue, 09 May 2023 09:29:33 GMT</pubDate></item><item><title><![CDATA[Backup Error with sufficient Space]]></title><description><![CDATA[@felipefonsecabh You need to check the specific checkbox:
https://xen-orchestra.com/docs/full_backups.html#backup-without-snapshot
]]></description><link>https://xcp-ng.org/forum/topic/7219/backup-error-with-sufficient-space</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/7219/backup-error-with-sufficient-space</guid><dc:creator><![CDATA[Darkbeldin]]></dc:creator><pubDate>Wed, 19 Apr 2023 20:27:10 GMT</pubDate></item><item><title><![CDATA[File restore not finding any option]]></title><description><![CDATA[@splastunov said in File restore not finding any option:

If nothing will help and you can't import xva with import VM, I have solution.

Deploy new VM with disk x4 times greater than backup file. OS Ubuntu 16.04 or later.
Copy backup. Take attention. You need always copy backup. Do not move it.
Install xva-img https://github.com/eriklax/xva-img

add-apt-repository ppa:ubuntu-toolchain-r/test &amp;&amp; apt-get update &amp;&amp; apt-get install -y gcc-7
cd to xva-img dir and run next command
cmake ./
make install


Extract xva file

tar -xf my-virtual-machine.xva -C my-virtual-machine
chmod -R 755 my-virtual-machine


In folder my-virtual-machine you will find some directory like Ref :1, but maybe with another number. Remember this number.
Create raw disk from extracted. Replace 1 with number from previous step.

xva-img -p disk-export my-virtual-machine/Ref\:1/ disk.raw


Install qemu-utils

apt install qemu-utils


Convert raw to vhd

qemu-img convert -f raw -O vpc disk.raw [vhd-name-you-like].vhd


Copy vhd to some SR. I'm using local SRs, so in my case path is /var/run/sr-mount/[sr-uuid]
Go to the host, cd to SR folder, get VHD uuid, rename VHD

cd /var/run/sr-mount/[sr-uuid]
vhd-util read -p -n [vhd-name-you-like_from-step-8].vhd
mv [vhd-name-you-like_from-step-8].vhd [uuid].vhd


Rescan SR
Attach VHD to existing VM or deploy new one
Get you files


wow. I am getting on with this in parallel. Thank you again! Results for both suggestions and requests are coming!
]]></description><link>https://xcp-ng.org/forum/topic/7190/file-restore-not-finding-any-option</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/7190/file-restore-not-finding-any-option</guid><dc:creator><![CDATA[damjank]]></dc:creator><pubDate>Mon, 10 Apr 2023 09:31:29 GMT</pubDate></item><item><title><![CDATA[Restore Delta Backup with Full Backup created afterwards]]></title><description><![CDATA[@hannes Full backup interval (and Force full backup in the schedule settings) forces the job to do a full export of the disk and not a delta based on a previous one.
It is not impacted by the retention as XO will always makes sure every chain has at least a full export at the beginning so that all backups are viable.
Which means you will have multiple full backups, always one at the beginning, and, those that have been triggered by the settings above.
]]></description><link>https://xcp-ng.org/forum/topic/7051/restore-delta-backup-with-full-backup-created-afterwards</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/7051/restore-delta-backup-with-full-backup-created-afterwards</guid><dc:creator><![CDATA[julien-f]]></dc:creator><pubDate>Tue, 07 Mar 2023 07:40:30 GMT</pubDate></item><item><title><![CDATA[File Level Restore results in "Error while scanning disk"]]></title><description><![CDATA[You should probably be able to fix this issue by installing the ntfs-3g package.
As you mentioned you're running it on a Synology, you can do that in DSM by opening Docker -&gt; Container -&gt; Select your container -&gt; Details -&gt; Terminal and enter the below in the console.
apk update

apk add ntfs-3g

Let us know if it helped.
]]></description><link>https://xcp-ng.org/forum/topic/6301/file-level-restore-results-in-error-while-scanning-disk</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/6301/file-level-restore-results-in-error-while-scanning-disk</guid><dc:creator><![CDATA[rittmeister]]></dc:creator><pubDate>Fri, 09 Sep 2022 17:09:23 GMT</pubDate></item><item><title><![CDATA[New Smart Backup failure]]></title><description><![CDATA[I did for sure. But I noticed that a new commit(886ff2cd7) was made literally in about the last hour and after updating again to that version all is good!
]]></description><link>https://xcp-ng.org/forum/topic/5662/new-smart-backup-failure</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/5662/new-smart-backup-failure</guid><dc:creator><![CDATA[mguyatt]]></dc:creator><pubDate>Fri, 11 Mar 2022 22:03:13 GMT</pubDate></item><item><title><![CDATA[XO fails to backup 1 specific VM due to: Error: HTTP connection has timed out]]></title><description><![CDATA[@olivierlambert i have created config.httpInactivityTimeout.toml in /opt/xen-orchestra/packages/xo-server with the content from above. Not sure how i can check if thats actually set.
BTW: this is not a CR Backup Problem, i also dont see Tasks running for my "normal" Backup Job. I cant check "how far" the actual Backup runs and if that differs.
https://github.com/vatesfr/xen-orchestra/pull/6315
]]></description><link>https://xcp-ng.org/forum/topic/5636/xo-fails-to-backup-1-specific-vm-due-to-error-http-connection-has-timed-out</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/5636/xo-fails-to-backup-1-specific-vm-due-to-error-http-connection-has-timed-out</guid><dc:creator><![CDATA[Meth0d]]></dc:creator><pubDate>Thu, 03 Mar 2022 19:07:45 GMT</pubDate></item><item><title><![CDATA[Backup failing with "Error: HTTP connection has timed out"]]></title><description><![CDATA[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.
]]></description><link>https://xcp-ng.org/forum/topic/5280/backup-failing-with-error-http-connection-has-timed-out</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/5280/backup-failing-with-error-http-connection-has-timed-out</guid><dc:creator><![CDATA[lawrencesystems]]></dc:creator><pubDate>Sun, 05 Dec 2021 14:02:19 GMT</pubDate></item><item><title><![CDATA[Restored Backups Do Not Boot]]></title><description><![CDATA[Sure, please keep us posted on your experiments  If it's a bug, we'll have more info to be able to work on it!
]]></description><link>https://xcp-ng.org/forum/topic/5124/restored-backups-do-not-boot</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/5124/restored-backups-do-not-boot</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Thu, 28 Oct 2021 04:33:36 GMT</pubDate></item></channel></rss>