{"id":106388,"date":"2023-01-19T00:26:22","date_gmt":"2023-01-18T22:26:22","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/dostupna-sistema-rezervnogo-kopirovaniya-restic-0-15"},"modified":"2023-01-19T00:26:22","modified_gmt":"2023-01-18T22:26:22","slug":"dostupna-sistema-rezervnogo-kopirovaniya-restic-0-15","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/dostupna-sistema-rezervnogo-kopirovaniya-restic-0-15","title":{"rendered":"The restic backup system 0.15 is now available","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

The release of the backup system restic 0.15 has been published, providing encrypted backup storage in a versioned repository. The system is initially designed for backups to be stored in untrusted environments, ensuring that the exposure of a backup does not compromise the system. Flexible rules for including and excluding files and directories during backup creation can be defined (the rule format is similar to rsync or gitignore). It supports operation on Linux, macOS, Windows, FreeBSD, and OpenBSD. The project code is written in Go and is distributed under the BSD license. <\/p>\n

Backups can be stored in local file systems, on external server<\/a> with access via SFTP\/SSH or HTTP REST, in cloud services such as Amazon S3, OpenStack Swift, BackBlaze B2, Microsoft Azure Blob Storage, and Google Cloud Storage, as well as in any storage systems for which rclone backends are available. A special rest server can also be used to organize storage, providing higher performance compared to other backends and capable of operating in a supplement-only mode, which prevents the deletion or alteration of backups in case the original is compromised server<\/a> and access to encryption keys. <\/p>\n

Snapshots are supported, reflecting the state of a specific directory with all files and subdirectories at a given point in time. Each new backup creation generates an associated snapshot, allowing restoration of the state at that moment. Snapshots can be copied between different repositories. To save bandwidth during the backup process, only changed data is copied. For a visual assessment of the repository contents and simplified restoration, the snapshot with the backup can be mounted as a virtual partition (mounting is done using FUSE). Commands are also provided for analyzing changes and selectively extracting files. <\/p>\n

The system manipulates not whole files, but blocks of variable size, selected using Rabin signatures. Information is stored in relation to content rather than file names (associated names and objects are determined at the block metadata level). Deduplication is performed based on the SHA-256 hash of the content to eliminate unnecessary data copying. On external servers, information is stored in an encrypted form (SHA-256 is used for checksums, AES-256-CTR for encryption, and authentication codes based on Poly1305-AES to ensure integrity). There is functionality to verify backups using checksums and authentication codes to confirm that file integrity has not been compromised. <\/p>\n

In the new version: <\/p>\n