{"id":105367,"date":"2022-10-23T21:36:56","date_gmt":"2022-10-23T19:36:56","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-utilit-dlya-rezervnogo-kopirovaniya-rsync-3-2-7-i-rclone-1-60"},"modified":"2022-10-23T21:36:56","modified_gmt":"2022-10-23T19:36:56","slug":"vypusk-utilit-dlya-rezervnogo-kopirovaniya-rsync-3-2-7-i-rclone-1-60","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-utilit-dlya-rezervnogo-kopirovaniya-rsync-3-2-7-i-rclone-1-60","title":{"rendered":"Release of backup utilities Rsync 3.2.7 and rclone 1.60","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Rsync 3.2.7 has been released, a utility for file synchronization and backup that minimizes traffic through incremental copying of changes. It can use ssh, rsh, or its own rsync protocol as transport. Support for setting up anonymous rsync servers ideal for maintaining mirror synchronization is included. The project code is distributed under the GPLv3 license. <\/p>\n
Among the added changes: <\/p>\n
\n
Support for SHA512, SHA256, and SHA1 hashes for authenticating user connections to the background rsync process has been added (previously only MD5 and MD4 were supported).\n
The ability to use the SHA1 algorithm for calculating file checksums has been implemented. Due to the large size of the SHA1 hash, it has been assigned the lowest priority in the hash negotiation list. To forcibly select SHA1, the option «—checksum-choice» can be used.\n
To reduce the likelihood of collisions, the xattr attribute hash table has been switched to using 64-bit keys.\n
The ability to output information about supported algorithms in rsync in JSON format has been provided (enabled by duplicating the —version option («-VV»)). Additionally, the script support\/json-rsync-version has been added, which allows generating similar JSON output based on the information provided in text form when the «—version» option is specified once (for compatibility with previous versions of rsync).\n
The «use chroot» setting in rsyncd.conf, which regulates the use of the chroot call for additional process isolation, is by default set to «unset», allowing the use of chroot based on its availability (for example, enabling it when rsync is run with root privileges and disabling it when run under a non-privileged user).\n
The performance of the algorithm for searching for base files for missing target files, applied when the option «—fuzzy» is specified, has been approximately doubled.\n
The representation of time in the protocol, used when interacting with older versions of Rsync (up to branch 3.0), has been changed — 4-byte epoch time is processed as «unsigned int» in this case, which does not allow time to be transmitted before 1970 but solves the problem of specifying time after 2038.\n
The absence of a target path when invoking the rsync client is now interpreted as an error. To revert to the old behavior, where an empty path was treated as «.», the option «—old-args» has been proposed. <\/ul>\n
Additionally, the release of rclone 1.60 has been announced, which serves as an alternative to rsync, designed for copying and synchronizing data between local systems and various cloud storage, such as Google Drive, Amazon Drive, S3, Dropbox, Backblaze B2, OneDrive, Swift, Hubic, Cloudfiles, Google Cloud Storage, Mail.ru Cloud, and Yandex.Disk. The project's code is written in Go and is distributed under the MIT license. <\/p>\n
In the new release: backends for storing backups in Oracle object storage and SMB\/CIFS have been added. The S3 storage backend now supports versioning, and the ability to work through the IONOS Cloud Storage and Qiniu KODO providers has been implemented. The local backend now includes the ability to add filters to ignore errors related to access rights. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"