Below is a condensed summary of the current status of things in the project - which current issues we are aware of, what’s being worked on now and what’s on the roadmap for the future. This posting is a wiki post and will be updated from time to time.
Before filing a new issue for a problem, please search the issues [on GitHub](https://github.com/restic/restic/issues] and review the information on this page, as we will try our best to keep it current and up to date. If you’re lucky, there’s already a notice for an issue you encounter, and you’ll then be able to find the corresponding issue to get more information and if needed add your input to it.
Known issues (currently actively investigated/resolved or generally often raised):
Much memory is needed for pruning, in general restic does use way too much memory #1723.
What we’re working on right now:
- Internal restructuring, reworking the index handling implementation (@fd0)
What we’ll focus on next:
Implement compression, allowing to reduce the size of backups by also compressing files (aside the current deduplication). See #21.
Update the repository format, in preparation for additional features
Look into reducing the memory usage
What’s on the roadmap in the long run:
Asymmetric encryption, enabling enhanced security and more resilience in certain scenarios, as well as more flexible key handling, see #187.
Pull-mode backups: restic process (A) on one machine logs into a different machine via
sshand runs restic (B) locally there, the process B reads the data and sends it to process A, which then stores it into some repository, see #299