<?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[&#x27;Smart&#x27; Backup Retention Scheme]]></title><description><![CDATA[<p dir="auto">I continue to be impressed with the functionality of XCP-ng/XO; even (especially?) for a small school like ours, it is proving very useful. DR/Backups are, not surprisingly, a major consideration for us. I've latched onto a <a href="https://forum.duplicati.com/t/new-retention-policy-deletes-old-backups-in-a-smart-way/2195" target="_blank" rel="noopener noreferrer nofollow ugc">retention strategy</a> from Duplicati--they call it 'Smart Backup Retention'--that optimizes long-term retention like this:</p>
<blockquote>
<p dir="auto">Assume you run your backup every day, then you have 365 backups during a year which can occupy a lot of storage space. Backup retention will delete old backups in a way that you keep [fewer] backups the older they get. For instance, you can have 7 backups for the last days, 4 backups for the last month, 12 backups for the last year. And all this is happening automatically.</p>
</blockquote>
<p dir="auto">I'm attempting to use this strategy with Continuous Replication and Delta Backup, but it's rather costly in terms of storage (CR) and bandwidth (DB): I have two CR jobs, one hourly, one nightly, and two DB jobs (to BackBlaze B2), one weekly and one monthly. I have included Rolling Snapshots in each of these as well. Obviously, this means multiple full backups (or snapshots) where one would suffice if we had a retention mechanism like Duplicati has designed. Is there a reasonable way to implement this? I can't help with coding, and our school can't help much financially, but we'd be willing to put a little bounty on this.</p>
<p dir="auto">Regards!</p>
]]></description><link>https://xcp-ng.org/forum/topic/7078/smart-backup-retention-scheme</link><generator>RSS for Node</generator><lastBuildDate>Mon, 15 Jun 2026 08:59:33 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/7078.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 13 Mar 2023 15:11:43 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to &#x27;Smart&#x27; Backup Retention Scheme on Tue, 21 Mar 2023 19:13:24 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/darkbeldin" aria-label="Profile: Darkbeldin">@<bdi>Darkbeldin</bdi></a> Done. Thanks for the reply. It took a while to make sure I was understanding it, but I think I've got the hang of it now.</p>
]]></description><link>https://xcp-ng.org/forum/post/60157</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/60157</guid><dc:creator><![CDATA[aknisly]]></dc:creator><pubDate>Tue, 21 Mar 2023 19:13:24 GMT</pubDate></item><item><title><![CDATA[Reply to &#x27;Smart&#x27; Backup Retention Scheme on Wed, 15 Mar 2023 14:00:33 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/aknisly" aria-label="Profile: aknisly">@<bdi>aknisly</bdi></a> Hi Aknisly,<br />
Every contribution to the documentation is really welcomed.<br />
You can find an edit button at the bottom of each documentation page.<br />
<img src="/forum/assets/uploads/files/1678888732918-bb2eee06-d1e5-44be-96e2-df37caebb2c8-image.png" alt="bb2eee06-d1e5-44be-96e2-df37caebb2c8-image.png" class=" img-fluid img-markdown" /><br />
In your case I think you should try to put it in this page <a href="https://xen-orchestra.com/docs/backups.html#interface" target="_blank" rel="noopener noreferrer nofollow ugc">https://xen-orchestra.com/docs/backups.html#interface</a><br />
Don't hesitate to push a pull request we will review it and help you if needed</p>
]]></description><link>https://xcp-ng.org/forum/post/59953</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/59953</guid><dc:creator><![CDATA[Darkbeldin]]></dc:creator><pubDate>Wed, 15 Mar 2023 14:00:33 GMT</pubDate></item><item><title><![CDATA[Reply to &#x27;Smart&#x27; Backup Retention Scheme on Mon, 13 Mar 2023 18:10:04 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/julien-f" aria-label="Profile: julien-f">@<bdi>julien-f</bdi></a> Ah, I've known about the multiple schedule features, but I hadn't (haven't) wrapped my mind around the implications. Are you saying that multiple schedules in one backup job are working off of one 'copy' of the backup? If that is the case, then all we really need is a little documentation to describe the feature--which I would be happy to write.</p>
]]></description><link>https://xcp-ng.org/forum/post/59886</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/59886</guid><dc:creator><![CDATA[aknisly]]></dc:creator><pubDate>Mon, 13 Mar 2023 18:10:04 GMT</pubDate></item><item><title><![CDATA[Reply to &#x27;Smart&#x27; Backup Retention Scheme on Mon, 13 Mar 2023 15:56:45 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/aknisly" aria-label="Profile: aknisly">@<bdi>aknisly</bdi></a> Hello! Thanks for your message, this is indeed an interesting feature and we'll thing about this.</p>
<p dir="auto">In the meantime, you can emulate such a behaviour by using multiple schedules in a single backup job and configuring them with different retentions.</p>
<p dir="auto">It's a bit tedious to use as you need to manually configure them to not overlap, but this is something we have starting thinking about <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=1e2d7c4c493" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
]]></description><link>https://xcp-ng.org/forum/post/59875</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/59875</guid><dc:creator><![CDATA[julien-f]]></dc:creator><pubDate>Mon, 13 Mar 2023 15:56:45 GMT</pubDate></item></channel></rss>