Working on documentation - wip 1
This commit is contained in:
parent
8b4beeccb5
commit
a9ae731309
157
README.md
157
README.md
@ -1,166 +1,11 @@
|
||||
# bit-backup
|
||||
|
||||
"Bit Backup" is a tool to manage files.
|
||||
|
||||
## How to run
|
||||
|
||||
Requirements to run "Bit Backup":
|
||||
* Java 21
|
||||
|
||||
### How to setup your environment on Linux
|
||||
|
||||
Add to your .bashrc:
|
||||
|
||||
alias bitbackup='java -jar {path to bit-backup jar with dependencies file}/bit-backup-0.0.0-SNAPSHOT-jar-with-dependencies.jar'
|
||||
|
||||
## How to build
|
||||
|
||||
Requirements to build "Bit Backup:
|
||||
* Java 21
|
||||
* Maven
|
||||
|
||||
```
|
||||
git clone https://code.nanoboot.org/nanoboot/bit-backup
|
||||
cd bit-backup
|
||||
mvn clean install
|
||||
```
|
||||
|
||||
## Features
|
||||
|
||||
### Feature 1 : Bit Rot Detection (to keep your files forever)
|
||||
|
||||
* Hash sum of files is tracked.
|
||||
* If last modification date of file in database and on the disk are the same, but the calculated checksum is different, then a bit rot was detected.
|
||||
* New files are added to the database, deleted files are removed from the database.
|
||||
|
||||
Found bit rots can be probably repaired, but only in case, you use also "Feature 2 : Backup of files"
|
||||
|
||||
Inspired by:
|
||||
|
||||
* https://github.com/ambv/bitrot
|
||||
* https://github.com/laktak/chkbit-py
|
||||
|
||||
#### File .bitbackupignore
|
||||
|
||||
You can create file .bitbackupignore containing the names of the files/directories you wish to ignore
|
||||
* .bitbackupignore is similar to Git file .gitignore
|
||||
* each line should contain exactly one name
|
||||
* lines starting with # are skipped
|
||||
* you may use Unix shell-style wildcards
|
||||
|
||||
#### File .bitbackup.sqlite3
|
||||
|
||||
An SQLite database created and managed automatically by bit-backup.
|
||||
|
||||
#### File .bitbackup.sqlite3.sha512
|
||||
|
||||
Last calculated hash sum of file ".bitbackup.sqlite3"
|
||||
You can find more information in docs directory.
|
||||
|
||||
### Feature 2 : Backup of files
|
||||
|
||||
Inspired by Git, but goals are slightly different.
|
||||
* https://github.com/joshnh/Git-Commands
|
||||
* https://git-scm.com/docs
|
||||
|
||||
#### File .bitbackup
|
||||
|
||||
File .bitbackup is stored in local directory, which you are going to backup.
|
||||
|
||||
Content:
|
||||
|
||||
```
|
||||
remotes=remote1,remote2,remote3
|
||||
```
|
||||
|
||||
#### Features
|
||||
|
||||
* Backing up directory to another location like: local, FTP(S), SFTP, HTTP(S), S3, Bit Backup server and others
|
||||
* Optionally you can set a password to protect your files (if a not trusted external location like FTP or S3 is used)
|
||||
|
||||
* Files are handled in a "Bit Backup repository"
|
||||
|
||||
#### What is not supported
|
||||
|
||||
* Conflict resolution is not supported. (If you wish something not yet supported to be added, please, let's start a discussion here or at forum.nanoboot.org)
|
||||
* "Bit Backup" is not intended to be used by many read/write users.
|
||||
* Several people changing one Bit Backup repository must be avoided.
|
||||
* "Bit Backup" is not intended to be used by many read users and only one read/write user.
|
||||
* One Bit Backup repository can be used by more users, but only one user can change it.
|
||||
* Branches are not supported
|
||||
|
||||
## Bit Backup repository
|
||||
|
||||
* Your files are versioned. You can travel in history and return to an older version of the whole repo or only a changed/deleted directory or file.
|
||||
|
||||
You can:
|
||||
* clone a remote Bit Backup repository
|
||||
* or use an existing local Bit Backup repository
|
||||
* or create a new empty Bit Backup repository
|
||||
* or create a new Bit Backup repository using an existing directory
|
||||
* or save your local repository to a remote repository.
|
||||
|
||||
### Structure
|
||||
|
||||
#### Directory .bitbackup/objects
|
||||
|
||||
.bitbackup/objects/{??}/{?????...}
|
||||
|
||||
#### Directory .bitbackup/pack
|
||||
.bitbackup/pack/pack-{sha-512}.pack
|
||||
|
||||
{sha-512}::::{length in bytes}::::{sha-512}::::{length in bytes}::::{sha-512}::::{length in bytes}::::{sha-512}::::{length in bytes}::::{sha-512}::::{length in bytes}::::::::{bytes -base}{bytes-incremental}{bytes-incremental}{bytes-incremental}{bytes-incremental}{bytes-incremental}
|
||||
|
||||
binary diffs
|
||||
|
||||
#### File .bitbackup/bitbackupindex.{number}
|
||||
|
||||
https://stackabuse.com/linux-display-file-properties-via-terminal/
|
||||
|
||||
##### Content
|
||||
|
||||
```
|
||||
DATE=20231105
|
||||
TIME=102950
|
||||
VERSION=1
|
||||
MESSAGE=
|
||||
TAG=
|
||||
-----
|
||||
PATH FILE_NAME TYPE LINK_TARGET PERMISSIONS SUID SGID STICKY_BIR EXECUTABLE UID GID OWNER GROUP LAST_MOD_TIME LAST_CHANGE_TIME LAST_ACCESS_TIME SIZE HASH PACKAGE_UUID ACL ATTRS IMMUTABLE UNDELETABLE
|
||||
/home/robertvokac doc.txt - rwxrw-r-- 2 2 robertvokac robertvokac 20220110151617999 20220110151617999 20220110151617999 263 {} PACKAGE_UUID 1 1
|
||||
```
|
||||
|
||||
```
|
||||
TYPE DIR d, REGULAR -, LINK l
|
||||
LINK_TARGET The target is in the content of binary object
|
||||
PERMISSIONS rwxrw-r--
|
||||
HASH SHA-512:{}
|
||||
```
|
||||
|
||||
https://superuser.com/questions/283008/binary-diff-patch-for-large-files-on-linux
|
||||
|
||||
https://stackabuse.com/guide-to-understanding-chmod/
|
||||
|
||||
https://www.guiffy.com/Binary-Diff-Tool.html
|
||||
|
||||
```
|
||||
Permission Symbolic Representation Octal Representation
|
||||
read r 4
|
||||
write w 2
|
||||
execute x 1
|
||||
no permission - 0
|
||||
```
|
||||
|
||||
```
|
||||
Creates local .bitbackupindex
|
||||
|
||||
Downloads remote .bitbackupindex – if does not exist, empty file will be returned.
|
||||
|
||||
Compares these indexes, uploads new blobs to object addressed system (SHA-512) – packaged to 7z archives (compression=ultra + other settings)
|
||||
|
||||
The most reliable way would be to make md5 hashes of all the local files you care about and store it in a file. So the file will contain a list of filenames and their md5 hashes. Store that file on your ftp server. When you want to update the files on your ftp server, download the file containing the list, compare that against all your local files, and upload the files that have changed (or are new). That way you don't have to worry about archive bits, modified date, or looking at file sizes, the use of which can never be 100% reliable.
|
||||
|
||||
Using file sizes isn't reliable for the obvious reason - a file could change but have the same size. I'm not a fan of using the archive bit or modified date because either of those could be confused if you backup or restore your local directory with another backup program.
|
||||
```
|
||||
|
||||
#### File .bitbackup/bitbackuplog
|
||||
|
||||
|
||||
12
docs/.gitignore
vendored
Normal file
12
docs/.gitignore
vendored
Normal file
@ -0,0 +1,12 @@
|
||||
#files to ignore
|
||||
|
||||
*.metadata/**
|
||||
*.recommenders/**
|
||||
*target/**
|
||||
*build/**
|
||||
*.idea/**
|
||||
*.iml
|
||||
|
||||
#*.class
|
||||
/target/
|
||||
*generated/*
|
||||
170
docs/LICENSE
Normal file
170
docs/LICENSE
Normal file
@ -0,0 +1,170 @@
|
||||
Creative Commons Attribution-ShareAlike 4.0 International
|
||||
|
||||
Creative Commons Corporation (“Creative Commons”) is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an “as-is” basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible.
|
||||
|
||||
Using Creative Commons Public Licenses
|
||||
|
||||
Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses.
|
||||
|
||||
Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors.
|
||||
|
||||
Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described.
|
||||
|
||||
Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public.
|
||||
|
||||
Creative Commons Attribution-ShareAlike 4.0 International Public License
|
||||
|
||||
By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions.
|
||||
|
||||
Section 1 – Definitions.
|
||||
|
||||
a. Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image.
|
||||
|
||||
b. Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License.
|
||||
|
||||
c. BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by Creative Commons as essentially the equivalent of this Public License.
|
||||
|
||||
d. Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights.
|
||||
|
||||
e. Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements.
|
||||
|
||||
f. Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material.
|
||||
|
||||
g. License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike.
|
||||
|
||||
h. Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License.
|
||||
|
||||
i. Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license.
|
||||
|
||||
j. Licensor means the individual(s) or entity(ies) granting rights under this Public License.
|
||||
|
||||
k. Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them.
|
||||
|
||||
l. Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world.
|
||||
|
||||
m. You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning.
|
||||
|
||||
Section 2 – Scope.
|
||||
|
||||
a. License grant.
|
||||
|
||||
1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to:
|
||||
|
||||
A. reproduce and Share the Licensed Material, in whole or in part; and
|
||||
|
||||
B. produce, reproduce, and Share Adapted Material.
|
||||
|
||||
2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions.
|
||||
|
||||
3. Term. The term of this Public License is specified in Section 6(a).
|
||||
|
||||
4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material.
|
||||
|
||||
5. Downstream recipients.
|
||||
|
||||
A. Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License.
|
||||
|
||||
B. Additional offer from the Licensor – Adapted Material. Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply.
|
||||
|
||||
C. No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material.
|
||||
|
||||
6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i).
|
||||
|
||||
b. Other rights.
|
||||
|
||||
1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise.
|
||||
|
||||
2. Patent and trademark rights are not licensed under this Public License.
|
||||
|
||||
3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties.
|
||||
|
||||
Section 3 – License Conditions.
|
||||
|
||||
Your exercise of the Licensed Rights is expressly made subject to the following conditions.
|
||||
|
||||
a. Attribution.
|
||||
|
||||
1. If You Share the Licensed Material (including in modified form), You must:
|
||||
|
||||
A. retain the following if it is supplied by the Licensor with the Licensed Material:
|
||||
|
||||
i. identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated);
|
||||
|
||||
ii. a copyright notice;
|
||||
|
||||
iii. a notice that refers to this Public License;
|
||||
|
||||
iv. a notice that refers to the disclaimer of warranties;
|
||||
|
||||
v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable;
|
||||
|
||||
B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and
|
||||
|
||||
C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License.
|
||||
|
||||
2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information.
|
||||
|
||||
3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable.
|
||||
|
||||
b. ShareAlike.In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply.
|
||||
|
||||
1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.
|
||||
|
||||
2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material.
|
||||
|
||||
3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply.
|
||||
|
||||
Section 4 – Sui Generis Database Rights.
|
||||
|
||||
Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material:
|
||||
|
||||
a. for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database;
|
||||
|
||||
b. if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and
|
||||
|
||||
c. You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database.
|
||||
For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights.
|
||||
|
||||
Section 5 – Disclaimer of Warranties and Limitation of Liability.
|
||||
|
||||
a. Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.
|
||||
|
||||
b. To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.
|
||||
|
||||
c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
|
||||
|
||||
Section 6 – Term and Termination.
|
||||
|
||||
a. This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically.
|
||||
|
||||
b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates:
|
||||
|
||||
1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or
|
||||
|
||||
2. upon express reinstatement by the Licensor.
|
||||
|
||||
c. For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License.
|
||||
|
||||
d. For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License.
|
||||
|
||||
e. Sections 1, 5, 6, 7, and 8 survive termination of this Public License.
|
||||
|
||||
Section 7 – Other Terms and Conditions.
|
||||
|
||||
a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed.
|
||||
|
||||
b. Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License.
|
||||
|
||||
Section 8 – Interpretation.
|
||||
|
||||
a. For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License.
|
||||
|
||||
b. To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions.
|
||||
|
||||
c. No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor.
|
||||
|
||||
d. Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority.
|
||||
|
||||
Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark “Creative Commons” or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses.
|
||||
|
||||
Creative Commons may be contacted at creativecommons.org.
|
||||
26
docs/content/Development/index.adoc
Normal file
26
docs/content/Development/index.adoc
Normal file
@ -0,0 +1,26 @@
|
||||
= Bit Backup - Documentation
|
||||
|
||||
////
|
||||
weight=100
|
||||
////
|
||||
|
||||
////
|
||||
+++
|
||||
title = "Development"
|
||||
date = "2024-05-21"
|
||||
menu = "main"
|
||||
+++
|
||||
////
|
||||
|
||||
== How to build
|
||||
|
||||
Requirements:
|
||||
|
||||
* Java 21
|
||||
* Maven
|
||||
|
||||
----
|
||||
git clone https://code.nanoboot.org/nanoboot/bit-backup
|
||||
cd bit-backup
|
||||
mvn clean install
|
||||
----
|
||||
1
docs/content/Installation/.LCKindex.adoc~
Normal file
1
docs/content/Installation/.LCKindex.adoc~
Normal file
@ -0,0 +1 @@
|
||||
/rv/data/desktop/code/code.nanoboot.org/nanoboot/bit-backup/docs/content/Introduction/index.adoc
|
||||
26
docs/content/Installation/index.adoc
Normal file
26
docs/content/Installation/index.adoc
Normal file
@ -0,0 +1,26 @@
|
||||
= Bit Backup - Documentation
|
||||
|
||||
////
|
||||
weight=1000
|
||||
////
|
||||
|
||||
////
|
||||
+++
|
||||
title = "Installation"
|
||||
date = "2024-05-21"
|
||||
menu = "main"
|
||||
+++
|
||||
////
|
||||
|
||||
== Requirements
|
||||
|
||||
* Java 21
|
||||
|
||||
== Environment setup on Linux
|
||||
|
||||
Add to your .bashrc:
|
||||
|
||||
alias bitbackup='java -jar {path to bit-backup jar with dependencies file}/bit-backup-0.0.0-SNAPSHOT-jar-with-dependencies.jar'
|
||||
|
||||
|
||||
|
||||
77
docs/content/Internals/index.adoc
Normal file
77
docs/content/Internals/index.adoc
Normal file
@ -0,0 +1,77 @@
|
||||
= Bit Backup - Documentation
|
||||
|
||||
////
|
||||
weight=200
|
||||
////
|
||||
|
||||
////
|
||||
+++
|
||||
title = "Internals"
|
||||
date = "2024-05-21"
|
||||
menu = "main"
|
||||
+++
|
||||
////
|
||||
|
||||
== Structure of "Bit Backup" repository
|
||||
|
||||
=== Directory {REPODIR}/objects
|
||||
|
||||
SHA-256 hash is used (or an alternative hash, if supported)
|
||||
|
||||
objects/{??}/{?????...}
|
||||
|
||||
=== Directory {REPODIR}/pack
|
||||
|
||||
pack/pack-{sha-512}.pack
|
||||
|
||||
{sha-256}::::{length in bytes}::::{sha-256}::::{length in bytes}::::{sha-512}::::{length in bytes}::::{sha-512}::::{length in bytes}::::{sha-512}::::{length in bytes}::::::::{bytes -base}{bytes-incremental}{bytes-incremental}{bytes-incremental}{bytes-incremental}{bytes-incremental}
|
||||
|
||||
binary diffs
|
||||
|
||||
=== File(s) {REPODIR}/bitbackupindex.{datetime}
|
||||
|
||||
==== Content
|
||||
|
||||
----
|
||||
PATH FILE_NAME TYPE LINK_TARGET PERMISSIONS SUID SGID STICKY_BIR EXECUTABLE UID GID OWNER GROUP LAST_MOD_TIME LAST_CHANGE_TIME LAST_ACCESS_TIME SIZE HASH PACKAGE_UUID ACL ATTRS IMMUTABLE UNDELETABLE
|
||||
/home/robertvokac doc.txt - rwxrw-r-- 2 2 robertvokac robertvokac 20220110151617999 20220110151617999 20220110151617999 263 {} PACKAGE_UUID 1 1
|
||||
----
|
||||
|
||||
----
|
||||
TYPE DIR d, REGULAR -, LINK l
|
||||
LINK_TARGET The target is in the content of binary object
|
||||
PERMISSIONS rwxrw-r--
|
||||
HASH SHA-512:{}
|
||||
----
|
||||
|
||||
|
||||
|
||||
----
|
||||
Permission Symbolic Representation Octal Representation
|
||||
read r 4
|
||||
write w 2
|
||||
execute x 1
|
||||
no permission - 0
|
||||
----
|
||||
|
||||
----
|
||||
Creates local .bitbackupindex
|
||||
|
||||
Downloads remote .bitbackupindex – if does not exist, empty file will be returned.
|
||||
|
||||
Compares these indexes, uploads new blobs to object addressed system (SHA-512) – packaged to 7z archives (compression=ultra + other settings)
|
||||
|
||||
The most reliable way would be to make md5 hashes of all the local files you care about and store it in a file. So the file will contain a list of filenames and their md5 hashes. Store that file on your ftp server. When you want to update the files on your ftp server, download the file containing the list, compare that against all your local files, and upload the files that have changed (or are new). That way you don't have to worry about archive bits, modified date, or looking at file sizes, the use of which can never be 100% reliable.
|
||||
|
||||
Using file sizes isn't reliable for the obvious reason - a file could change but have the same size. I'm not a fan of using the archive bit or modified date because either of those could be confused if you backup or restore your local directory with another backup program.
|
||||
----
|
||||
|
||||
=== File(s) {REPODIR}/bitbackupindexinfo.{datetime}
|
||||
|
||||
----
|
||||
DATE=20231105
|
||||
TIME=102950
|
||||
VERSION=1
|
||||
MESSAGE=
|
||||
TAG=
|
||||
----
|
||||
95
docs/content/Usage/General/index.adoc
Normal file
95
docs/content/Usage/General/index.adoc
Normal file
@ -0,0 +1,95 @@
|
||||
= Bit Backup - Documentation
|
||||
|
||||
////
|
||||
weight=1000
|
||||
////
|
||||
|
||||
////
|
||||
+++
|
||||
title = "General"
|
||||
date = "2024-05-21"
|
||||
menu = "main"
|
||||
+++
|
||||
////
|
||||
|
||||
== Features
|
||||
|
||||
* Backing up directory to another location like: local, FTP(S), SFTP, HTTP(S), S3, Bit Backup server and others
|
||||
* Optionally you can set a password to protect your files (if a not trusted external location like FTP or S3 is used)
|
||||
|
||||
* Files are handled in a "Bit Backup repository"
|
||||
|
||||
== What is not supported
|
||||
|
||||
* Conflict resolution is not supported. (If you wish something not yet supported to be added, please, let's start a discussion here or at forum.nanoboot.org)
|
||||
* "Bit Backup" is not intended to be used by many read/write users.
|
||||
* Several people changing one Bit Backup repository must be avoided.
|
||||
* "Bit Backup" is not intended to be used by many read users and only one read/write user.
|
||||
* One Bit Backup repository can be used by more users, but only one user can change it.
|
||||
* Branches are not supported
|
||||
|
||||
== File .bitbackupignore
|
||||
|
||||
You can create file .bitbackupignore containing the names of the files/directories you wish to ignore (don't backup or analyse)
|
||||
|
||||
* .bitbackupignore is similar to Git file .gitignore
|
||||
* each line should contain exactly one name
|
||||
* lines starting with # are skipped
|
||||
* you may use Unix shell-style wildcards
|
||||
|
||||
== "Bit Backup" Repository
|
||||
|
||||
"Bit Backup" repository is a directory with a defined structure, where "Bit Backup" stores backups of directories.
|
||||
|
||||
* Your files are versioned. You can travel in history and return to an older version of the whole repo or only a changed/deleted directory or file.
|
||||
|
||||
You can:
|
||||
* clone a remote Bit Backup repository
|
||||
* or use an existing local Bit Backup repository
|
||||
* or create a new empty Bit Backup repository
|
||||
* or create a new Bit Backup repository using an existing directory
|
||||
* or save your local repository to a remote repository.
|
||||
|
||||
== Directory(ies) to be backed up
|
||||
|
||||
These are 1 or more directories, you want to backup
|
||||
|
||||
== File bitbackupindex
|
||||
|
||||
Created and managed automatically by bit-backup.
|
||||
|
||||
This is a text file with a defined structure.
|
||||
|
||||
In fact, it is a CSV file, where the columns are separated by the tab character.
|
||||
|
||||
Each row represent one file of directory
|
||||
|
||||
Each column represents one of file properties
|
||||
|
||||
== File bitbackupindex.sha256
|
||||
|
||||
Created and managed automatically by bit-backup.
|
||||
|
||||
This file contains the calculated sha256 hash of file bitbackupindex
|
||||
|
||||
== File bitbackupindexold
|
||||
|
||||
Created and managed automatically by bit-backup.
|
||||
|
||||
This is the previous file bitbackupindex.
|
||||
|
||||
== File bitbackupindexold.sha256
|
||||
|
||||
Created and managed automatically by bit-backup.
|
||||
|
||||
This file contains the calculated sha256 hash of file bitbackupindexold
|
||||
|
||||
== File .bitbackup
|
||||
|
||||
File .bitbackup is an optional file. You can save remotes and the credentials here to avoid typing it.
|
||||
|
||||
Content:
|
||||
|
||||
----
|
||||
remotes=remote1,remote2,remote3
|
||||
----
|
||||
26
docs/content/Usage/bitbackup_analyse/index.adoc
Normal file
26
docs/content/Usage/bitbackup_analyse/index.adoc
Normal file
@ -0,0 +1,26 @@
|
||||
= Bit Backup - Documentation
|
||||
|
||||
////
|
||||
weight=900
|
||||
////
|
||||
|
||||
////
|
||||
+++
|
||||
title = "bitbackup analyse"
|
||||
date = "2024-05-21"
|
||||
menu = "main"
|
||||
+++
|
||||
////
|
||||
|
||||
== Description
|
||||
|
||||
WARNING: This command does not involve "Bit Backup" repository. Instead it is intended for additional control of integrity of files.
|
||||
|
||||
This command is intended for creation list of files and directories in the given root directory together with all their file attributes.
|
||||
|
||||
* If the file bitbackupindex exists at the start, then:
|
||||
** file bitbackupindexold (if exists) is deleted
|
||||
** file bitbackupindex is renamed to bitbackupindexold
|
||||
* The output of analyse command (list of files and directories) is stored to file bitbackupindex.
|
||||
|
||||
== Examples
|
||||
33
docs/content/Usage/bitbackup_inspect/index.adoc
Normal file
33
docs/content/Usage/bitbackup_inspect/index.adoc
Normal file
@ -0,0 +1,33 @@
|
||||
= Bit Backup - Documentation
|
||||
|
||||
////
|
||||
weight=900
|
||||
////
|
||||
|
||||
////
|
||||
+++
|
||||
title = "bitbackup inspect"
|
||||
date = "2024-05-21"
|
||||
menu = "main"
|
||||
+++
|
||||
////
|
||||
|
||||
== Description
|
||||
|
||||
WARNING: This command does not involve "Bit Backup" repository. Instead it is intended for additional control of integrity of files.
|
||||
|
||||
This command is intended for Bit Rot Detection (to keep your files forever).
|
||||
|
||||
* Current hash sum of files is tracked in file bitbackupindex.
|
||||
* Previous hash sum of files is tracked in file bitbackupindexold.
|
||||
* Files bitbackupindex and bitbackupindexold are compared.
|
||||
* If the current and previous last modification date of a file are the same, but the calculated checksum is different, then a bit rot was detected.
|
||||
|
||||
Found bit rots can be probably repaired, but only in case, you used commands like init and create
|
||||
|
||||
Inspired by:
|
||||
|
||||
* https://github.com/ambv/bitrot
|
||||
* https://github.com/laktak/chkbit-py
|
||||
|
||||
== Examples
|
||||
13
docs/content/Usage/index.adoc
Normal file
13
docs/content/Usage/index.adoc
Normal file
@ -0,0 +1,13 @@
|
||||
= Bit Backup - Documentation
|
||||
|
||||
////
|
||||
weight=1000
|
||||
////
|
||||
|
||||
////
|
||||
+++
|
||||
title = "Usage"
|
||||
date = "2024-05-21"
|
||||
menu = "main"
|
||||
+++
|
||||
////
|
||||
14
docs/content/index.adoc
Normal file
14
docs/content/index.adoc
Normal file
@ -0,0 +1,14 @@
|
||||
= Bit Backup - Documentation
|
||||
|
||||
////
|
||||
+++
|
||||
title = "About"
|
||||
date = "2024-05-21"
|
||||
menu = "main"
|
||||
+++
|
||||
////
|
||||
|
||||
"Bit Backup" is a backup tool used to manage files.
|
||||
|
||||
Inspired by Borg Backup, but is slightly different.
|
||||
|
||||
9
docs/dog.conf
Normal file
9
docs/dog.conf
Normal file
@ -0,0 +1,9 @@
|
||||
title = Bit Backup - Documentation
|
||||
editURL = https://code.nanoboot.org/nanoboot/bit-backup/edit/develop/docs/content/
|
||||
description = Bit Backup - Documentation
|
||||
author = Robert Vokac
|
||||
showVisitedLinks = true
|
||||
disableBreadcrumb = false
|
||||
disableNextPrev = false
|
||||
titleSeparator=|
|
||||
frontPageName=Introduction
|
||||
7
docs/templates/footer.html
vendored
Normal file
7
docs/templates/footer.html
vendored
Normal file
@ -0,0 +1,7 @@
|
||||
<style>
|
||||
.footer2 a {color:#5dade2;}
|
||||
</style>
|
||||
|
||||
<div class="footer2">
|
||||
Copyright © 2016-2023 The Nanoboot Authors. Made with <a href="https://code.nanoboot.org/nanoboot/dog">Dog</a>.
|
||||
<div>
|
||||
31
docs/templates/header.html
vendored
Normal file
31
docs/templates/header.html
vendored
Normal file
@ -0,0 +1,31 @@
|
||||
<style>
|
||||
|
||||
#nanoboot_banner {
|
||||
|
||||
|
||||
font-size:2em;
|
||||
font-weight: 500;
|
||||
padding-top: 6px !important;
|
||||
padding-bottom: 9px !important;
|
||||
text-align:left;
|
||||
padding-left:60px;
|
||||
|
||||
background: #7cd3ff;
|
||||
background: linear-gradient(180deg, rgba(124, 211, 255,0.4) 10%, white 60%);
|
||||
}
|
||||
|
||||
#nanoboot_banner a {
|
||||
|
||||
text-decoration:none;
|
||||
text-transform: uppercase;
|
||||
color:#4169E1 !important;
|
||||
font-weight: 600;
|
||||
display:inline-block;
|
||||
}
|
||||
|
||||
|
||||
|
||||
</style>
|
||||
|
||||
<div id="nanoboot_banner"><a href="https://docs.nanoboot.org" style="text-transform:none;"><span style="color:blue;">Documentation</span></a> | <a href="https://www.nanoboot.org" target="_parent">Nanoboot</a> Project</div>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user