<?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 delta]]></title><description><![CDATA[A list of topics that have been tagged with delta]]></description><link>https://xcp-ng.org/forum/tags/delta</link><generator>RSS for Node</generator><lastBuildDate>Sun, 13 Sep 2026 04:48:39 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/tags/delta.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 07 Jan 2025 13:19:23 GMT</pubDate><ttl>60</ttl><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[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[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[XO Backups Failing since upgrading to 5.33]]></title><description><![CDATA[Answered on the XO forum, thank you 
]]></description><link>https://xcp-ng.org/forum/topic/843/xo-backups-failing-since-upgrading-to-5-33</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/843/xo-backups-failing-since-upgrading-to-5-33</guid><dc:creator><![CDATA[julien-f]]></dc:creator><pubDate>Wed, 16 Jan 2019 13:45:52 GMT</pubDate></item></channel></rss>