Prompt
How do I archive old application files cheaply?
Latest observation
Oct 12, 2026
OpenAI APIWeb search: off
A cheap way to archive old application files is usually to combine compression + low-cost storage + clear retention rules.
Good low-cost options
1) Compress files before archiving
- Use 7z, zip, or tar.gz for individual projects or folders.
- If files are already compressed formats (images, PDFs, videos, databases), compression may save little.
2) Use cold storage / archive tiers
If you’re using cloud storage, look at low-access tiers such as:
- AWS S3 Glacier / Glacier Deep Archive
- Azure Blob Archive
- Google Cloud Archive Storage
These are cheap for long-term storage, but:
- Retrieval can take time
- Retrieval fees may apply
- Best for data you rarely need
3) Store on inexpensive local media
If you want the cheapest possible approach:
- External HDDs are usually the best cost per TB for offline archives
- Keep two copies on separate drives if the data matters
- Store one copy offsite if possible
4) Use backup software with deduplication
Tools like:
- restic
- borgbackup
- Duplicati
These can:
- Encrypt archives
- Deduplicate repeated files
- Save space over time
- Make restores easier
5) Put old versions in object storage
If you need to keep application builds, release artifacts, logs, or packages:
- Store them in an S3-compatible bucket
- Apply lifecycle rules to move old files to cheaper tiers automatically
Best practice checklist
- Decide what “old” means, e.g. files not used in 1–2 years
- Remove junk before archiving: temp files, caches, duplicates
- Compress and encrypt sensitive archives
- Keep an index or manifest so files are searchable later
- Test restoring a few files to make sure the archive is usable
Cheapest practical setup
For most small teams:
- Put old files into a compressed archive
- Store them on a cheap external HDD
- Keep a second copy in cloud archive storage
- Use a tool like restic or borg if you want versioned, deduplicated backups
If you want, I can recommend the cheapest setup based on your file size, access frequency, and whether you prefer cloud or local storage.