After the year of development of is presented Release system backup restic 0.13 providing tools to save backup copies in a versioned repository, which can be placed on external servers and in cloud storage. Data is stored in encrypted form. It is possible to define flexible rules to enable and exclude files and directories when creating a backup. Supported work in Linux, MacOS, Windows, FreeBSD and OpenBSD. The project code is written in GO and distributed under the BSD license.
Main features:
- support for storing backups in local FS, on an external server with access via SFTP / SSH or HTTP REST, in Amazon S3 clouds,
OpenStack SWIFT, Backblaze B2, Microsoft Azure Blob Storage and Google Cloud Storage, as well as in any repositors for which there are rclone backends. For the organization of storage can also be used by special REST Server , providing higher performance compared to other backends and capable of working in only mode For a supplement that will not allow you to delete or change backups in case of compromising the source server and access to encryption keys. - Support for the definition of flexible rules to exclude files and directories when creating backups (for example, to exclude from a backup of logs, temporary files and easily reproducible data). The format of ignoring rules is essential and resembles RSync or Gitignore.
- Easy installation, use and recovery of information. To work with backups, it is enough to copy one executable file that can be used without additional settings. For the executable file, a repeated assembly is provided, which allows you to make sure that the binary assembly is formed from the source-provided texts.
- supports snapshots, reflecting the state of a specific directory with all files and invested directories at a specific point in time. Each time you create a new backup, the snapshot associated with it, which allows you to restore the state at the moment. It is possible to copy snapshots between different repositories.
- To save traffic, only changed data is copied during the process of creating backups. To ensure efficient storage, the data in the repository is not duplicated, and additional snaps cover only the changed data. The system manipulates not entire files, and the blocks of floating size selected using the Rabin signatures . The information is stored in binding to content, and not file names (data-related names and objects are determined at the block metadata). Based on the SHA-256 hash of content, deduplication is performed and excluding extra copying data.
/Media reports.