Result for 02DAB4FD2AB4431EC776286A5BA0E8914F9F5E98

Query result

Key Value
FileName./usr/share/doc/restic/html/030_preparing_a_new_repo.html
FileSize43853
MD5E34D21DD6E944C62CC236DC512A26EF7
SHA-102DAB4FD2AB4431EC776286A5BA0E8914F9F5E98
SHA-256E88513FA1F6A0583AB8BECA4B84CFD480A221528D553EAD5630F425C45B6F72D
SSDEEP768:4jmJpKFfUb2kqm83GQpLQfF9EmusrcQXxzjKnp9bTA4CjHyvx5HO+PsdlCEfyolk:O/fW2Pm83GSLCF9EmuScQ9Knp9bTA4CO
TLSHT1611351A2C2B34A37013382D3E3E91B29B1EB446EE5960441F3FC836C97DED59750796A
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize8523564
MD52183CA70298644455EBB3F19C808D837
PackageDescriptionbackup program with multiple revisions, encryption and more restic is a program that does backups right and was designed with the following principles in mind: - Easy: Doing backups should be a frictionless process, otherwise you might be tempted to skip it. Restic should be easy to configure and use, so that, in the event of a data loss, you can just restore it. Likewise, restoring data should not be complicated. - Fast: Backing up your data with restic should only be limited by your network or hard disk bandwidth so that you can backup your files every day. Nobody does backups if it takes too much time. Restoring backups should only transfer data that is needed for the files that are to be restored, so that this process is also fast. - Verifiable: Much more important than backup is restore, so restic enables you to easily verify that all data can be restored. - Secure: Restic uses cryptography to guarantee confidentiality and integrity of your data. The location the backup data is stored is assumed not to be a trusted environment (e.g. a shared space where others like system administrators are able to access your backups). Restic is built to secure your data against such attackers. - Efficient: With the growth of data, additional snapshots should only take the storage of the actual increment. Even more, duplicate data should be de-duplicated before it is actually written to the storage back end to save precious backup space.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamerestic
PackageSectionutils
PackageVersion0.9.6+ds-2
SHA-1CF48C4804638EE1AD4C0F683657C007358A5CC1C
SHA-256A895EBF4A225B1F9ABDDA7D416D185DC5B5195DCF78B0D5822CDFB8C4183503F