# Inconsistent weekly retentions

**URL:** <https://kopia.discourse.group/t/inconsistent-weekly-retentions/8767>\
**Category:** General Topics\
**Created:** [January 13, 2026, 8:31pm UTC](https://kopia.discourse.group/t/inconsistent-weekly-retentions/8767 "2026-01-13T20:31:20Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![8191](https://avatars.discourse-cdn.com/v4/letter/8/c67d28/32.png) [@8191](https://kopia.discourse.group/u/8191)\
**Post date:** [January 13, 2026, 8:31pm UTC](https://kopia.discourse.group/t/inconsistent-weekly-retentions/8767/1 "2026-01-13T20:31:20Z")

</div>

I’m trying to make sense of the retention labels. Can someone explain why the backup of Jan. 4th has no weekly-3 label?

 ![image](https://global.discourse-cdn.com/free1/uploads/kopia/original/2X/e/e799a3b8399733f4d56c302bfd03037bd08e269b.png)

---

<div class="post-metadata">

**Author:** ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)\
**Post date:** [January 14, 2026, 6:12am UTC](https://kopia.discourse.group/t/inconsistent-weekly-retentions/8767/2 "2026-01-14T06:12:46Z")

</div>

There is no better snapshots retention logic explanation than this post:

> [@Kopia Snapshot Retention Policies Demystified](https://kopia.discourse.group/t/kopia-snapshot-retention-policies-demystified/2941):
>
> With the suggestion of @JayKay729, I decided to create a dummy backup for testing how Kopia choose which backups to save, but in this experiment, I learned much more than I initially planned. In this post, I would like to share these discoveries, along with some examples to demonstrate them. This is a supplement to [his post](https://kopia.discourse.group/t/retention-policies-documentation/2488), so I’ll jump straight to those he hasn’t covered yet. Numbers in Snapshot Retention Except for Latest Snapshots, Kopia considers the number you write here as dura…

---

<div class="post-metadata">

**Author:** ![ingul-buz](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/ingul-buz/32/417_2.png) [@ingul-buz](https://kopia.discourse.group/u/ingul-buz)\
**Post date:** [January 14, 2026, 11:08am UTC](https://kopia.discourse.group/t/inconsistent-weekly-retentions/8767/3 "2026-01-14T11:08:36Z")

</div>

The problem here is that the logic fails: there’s one week left completely without a weekly tag.

- 12/27/2025 snapshot falls on week 52
- 1/11/2026 snapshot falls on week 2
- 1/13/2026 snapshot falls on week 3

So, where is the weekly tag for week 1? 1/4/2026 snapshot falls on that week, but didn’t get a weekly tag assigned. I noticed the same inconsistency with my own backups.

---

<div class="post-metadata">

**Author:** ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)\
**Post date:** [January 14, 2026, 3:01pm UTC](https://kopia.discourse.group/t/inconsistent-weekly-retentions/8767/4 "2026-01-14T15:01:59Z")

</div>

> [@ingul-buz](#):
>
> The problem here is that the logic fails:

We do not know really what the logic is here:) In the linked thread somebody tried to reverse engineer it as kopia docs are missing such details unfortunately.

@8191 What time zone you are on? Are you using kopia server? If yes is it in the same timezone?

---

<div class="post-metadata">

**Author:** ![8191](https://avatars.discourse-cdn.com/v4/letter/8/c67d28/32.png) [@8191](https://kopia.discourse.group/u/8191)\
**Post date:** [January 17, 2026, 12:38am UTC](https://kopia.discourse.group/t/inconsistent-weekly-retentions/8767/5 "2026-01-17T00:38:16Z")

</div>

@kapitainsky I’m in CET (UTC+1). I’m using kopia server and it’s in the same timezone.

When looking at the code I noticed that there are two concepts to how calculate week offsets: Monday starting weeks and Sunday starting weeks. Unfortunately I could not find out how either system is applied - based on timezone or based on locale settings?

@ingul-buz In the meanwhile I’ve filled up week 1 with even more snapshots - unfortunately without effect:

 ![image](https://global.discourse-cdn.com/free1/uploads/kopia/original/2X/d/d76a3024c27dc5aaf2fb05d8e8f172671dffb6ea.png)

As you might have noticed, I’m currently in the process of migrating for another backup tool to kopia. I assume my problem simply vanishes in a few days once kopia created more than 3 weeks of backups. 😄

---

<div class="post-metadata">

**Author:** ![ingul-buz](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/ingul-buz/32/417_2.png) [@ingul-buz](https://kopia.discourse.group/u/ingul-buz)\
**Post date:** [January 18, 2026, 1:43pm UTC](https://kopia.discourse.group/t/inconsistent-weekly-retentions/8767/6 "2026-01-18T13:43:58Z")

</div>

Yes, the week starting on different days in different countries could have something to do with it. But it’s curious that this is the only time I have ever seen this happen. Week numbering at the turn of the year might also have something to do with it. Maybe it’s a combination of different things that clash somewhere just now. But logical it is not.

And yes, fortunately it’s a problem that will eventually vanish as time goes by, if you don’t happen to need that specific snaphot meanwhile. 😅

---

<div class="post-metadata">

**Author:** ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)\
**Post date:** [January 18, 2026, 5:34pm UTC](https://kopia.discourse.group/t/inconsistent-weekly-retentions/8767/7 "2026-01-18T17:34:00Z")

</div>

I’ve been using kopia for some time now and never seen such situation. I assume that it is some edge case when used logic fails a bit.

I wonder whether it has anything to do with the fact that first full week of 2026 only starts on the 5th and ends on the 11th of January. Maybe kopia only counts full weeks within given year?

Unless somebody spends time and studies source code we can only speculate.
