Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
alexis- authored May 6, 2018
1 parent 5d046af commit 2494e87
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,10 +68,11 @@ If you know a work-around for these limitations, please let me know [here](https

Operation | Result | Location | Size | Speed
:---------------:|:-------------------------:|:------------:|:------------:|:------------:
**Snapshot** | This is *similar* to **Ctrl+Z** for files. Every time a snapshot is created, the system memorizes the content of your files. You can [browse](https://raw.githubusercontent.com/alexis-/BitShelter/master/Resources/explorer_2018-05-04_18-00-38.png), [view and restore](https://raw.githubusercontent.com/alexis-/BitShelter/master/Resources/explorer_2018-05-04_17-50-30.png) them to earlier versions. Note: Snapshots work even when files are locked by other Applications | Same drive as data | As much as the difference between each consecutive snapshot | Almost instantaneous
**Backup** | This is *similar* to **Ctrl+C** and **Ctrl+V**: Backups create a *copy* of your files. They can be stored locally or remotely. You can optionaly archive them with compression (e.g. zip, tar.gz), and encrypt them. See [best practices](#best-practices) for recommendations | Local drive, Network drive, Removable device, ... | At most as much as the data, less if compressed | Minutes to hours depending on size, disk speed, compression, encryption
**Cloud sync** | While *BitShelter* knows nothing about Cloud Storage, you can use backups to create copies of your work in Sync folders of popular providers. They will in turn be sent to your space on the Cloud | In the cloud | As much as backups, only counting toward your Cloud Storage space | Minutes to hours, depending on size, upload speed
**Snapshot** | This is *similar* to **Ctrl+Z** for files. Every time a snapshot is created, the system memorizes the content of your files. You can [browse](https://raw.githubusercontent.com/alexis-/BitShelter/master/Resources/explorer_2018-05-04_18-00-38.png), [view and restore](https://raw.githubusercontent.com/alexis-/BitShelter/master/Resources/explorer_2018-05-04_17-50-30.png) them to earlier versions. You can continue your work without interference during the process<sup>1</sup> | Same drive as data | As much as the difference between each consecutive snapshot | Almost instantaneous
**Backup** | This is *similar* to **Ctrl+C** and **Ctrl+V**: Backups create a *copy* of your files. They can be stored locally or remotely. You can optionaly archive them with compression (e.g. zip, tar.gz), and encrypt them. Because Backups operate on Snapshots, you can continue your work without interference during the process<sup>1</sup>. See [best practices](#best-practices) for recommendations | Local drive, Network drive, Removable device, ... | At most as much as the data, less if compressed | Minutes to hours depending on size, disk speed, compression, encryption
**Cloud sync** | While *BitShelter* knows nothing about Cloud Storage, you can use backups to create copies of your work in Sync folders of popular providers. They will in turn be sent to your space on the Cloud | In the cloud | As much as backups, only counting toward your Cloud Storage space | Minutes to hours, depending on size, upload speed

**<sup>1</sup>**: When a snapshot is created, existing data aren't copied. Instead, an index of where the data exist is built and new data written to free space. This is extremely fast, and allow to operate on snapshots concurrently with the "live data". For more information, see [Copy-on-write](https://en.wikipedia.org/wiki/Copy-on-write)

### Requirements

Expand Down

0 comments on commit 2494e87

Please sign in to comment.