# Long term archive **URL:** \ **Category:** General Topics\ **Created:** [January 15, 2026, 3:58pm UTC](https://kopia.discourse.group/t/long-term-archive/8769 "2026-01-15T15:58:58Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![peterm](https://avatars.discourse-cdn.com/v4/letter/p/a9adbd/32.png) [@peterm](https://kopia.discourse.group/u/peterm)\ **Post date:** [January 15, 2026, 3:58pm UTC](https://kopia.discourse.group/t/long-term-archive/8769/1 "2026-01-15T15:58:58Z")
I want to store files as long term archive (after any changes have finished) to locations such as AWS Glacier/S3 Deep Archive. The archived content will not change, so Kopia’s complex file handling is not needed. I would like to use the same tool (Kopia) to write encrypted versions of the file, under same/similar name, in such a way as a simple decrypt operation can be used from anywhere (so not reliant on using Kopia). Once verifying the file was received by the storage engine, the source archive file would then be removed by Kopia. Is this possible? Thanks ---
**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 16, 2026, 5:27am UTC](https://kopia.discourse.group/t/long-term-archive/8769/2 "2026-01-16T05:27:44Z")
> [@peterm](#): > > locations such as AWS Glacier/S3 Deep Archive. Kopia [does not support](https://kopia.io/docs/advanced/storage-tiers/#using-archive-storage-with-delayed-access) AWS Glacier. > [@peterm](#): > > I would like to use the same tool (Kopia) to write encrypted versions of the file, under same/similar name, in such a way… Nothing like this is supported by kopia today. ---
**Author:** ![budy](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/budy/32/38_2.png) [@budy](https://kopia.discourse.group/u/budy)\ **Post date:** [January 16, 2026, 7:22am UTC](https://kopia.discourse.group/t/long-term-archive/8769/3 "2026-01-16T07:22:50Z")
And probably never will, because that’s not in the scope if its very purpose… ---
**Author:** ![seized](https://avatars.discourse-cdn.com/v4/letter/s/e480ec/32.png) [@seized](https://kopia.discourse.group/u/seized)\ **Post date:** [March 24, 2026, 4:16am UTC](https://kopia.discourse.group/t/long-term-archive/8769/4 "2026-03-24T04:16:07Z")
You probably want RClone for this kind of use case, it can write an encrypted one to one original file to encrypted version in a destination.