TiloBox
Back to directory
Restic project preview

Restic

Fast, secure, and efficient backup program with cryptographic deduplication.

LicenseBSD-2-Clause
GitHub stars25.5k
Last commit1 weeks ago
Tags6 topics
CliBackupDisaster RecoveryEncryptionDeduplicationGolang
Overview

Why consider Restic?

Restic is an open-source CLI backup program written in Go. It provides AES-256 encrypted backups, content-defined deduplication, and native support for S3, B2, Azure, and SFTP destinations.

Guided learning

Learn Restic by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of Restic

Restic creates verifiable snapshot backups with zero unencrypted metadata leakage. Its deduplication algorithm ensures incremental snapshots consume only newly modified bytes.

Initializing and Running a Backup

bash
1# Initialize encrypted repository
2restic init --repo s3:s3.amazonaws.com/my-backup-bucket
3
4# Create snapshot
5restic -r s3:s3.amazonaws.com/my-backup-bucket backup /home/user/data

Restic is distributed under the BSD 2-Clause License.

Related tools

More options with a similar category or technology profile.

Restic FAQs

Restic is listed as a Security tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

Restic is listed under the BSD-2-Clause license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

Restic is listed as an alternative to CrashPlan. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.