mirror of
https://github.com/gilbertchen/duplicacy
synced 2025-12-10 13:23:17 +00:00
Expanded Wasabi documentation
@@ -63,8 +63,25 @@ Storage URL: s3c://region@host/bucket/path/to/storage
|
||||
Storage URL: s3://us-east-1@s3.wasabisys.com/bucket/path/to/storage
|
||||
```
|
||||
|
||||
[Wasabi](https://wasabi.com) is a relatively new cloud storage service providing a S3-compatible API.
|
||||
It is well suited for storing backups, because it is much cheaper than Amazon S3 with a storage cost of $.0039/GB/Month and a download fee of $0.04/GB, and no additional charges on API calls.
|
||||
[Wasabi](https://wasabi.com) is a relatively new cloud storage service providing a S3-compatible API. It is well-suited for storing backups, because it is much cheaper than Amazon S3 with a storage cost of $0.0039/GB/month (see note below) and a download fee of $0.04/GB, and no additional charges on API calls.
|
||||
|
||||
### S3 and Billing
|
||||
|
||||
Wasabi's billing model differs from Amazon's in that any object created incurs charges for 90 days of storage, even if the object is deleted earlier than that, and then the monthly rate thereafter.
|
||||
|
||||
As part of the [process for purging data which is no longer needed](https://github.com/gilbertchen/duplicacy/wiki/Lock-Free-Deduplication#two-step-fossil-collection), Duplicacy renames objects. Because S3 does not support renaming objects, Duplicacy does the equivalent by using S3's copy operation to create a second object with the new name then deleting the one with the old name. S3-style renaming with Wasabi will incur additional charges during fossilization becasue of the additional objects it creates. For example, if a new 1 GB file is backed up in chunks on day 1, the initial storage will incur fees of at least $0.0117 (three months at $0.0039 each). If the file goes away and all snapshots that contained it are pruned on day 50, renaming the chunks will create an additional 1 GB of objects with a newly-started 90-day clock at a cost of $0.0117.
|
||||
|
||||
|
||||
### Snapshot Pruning
|
||||
|
||||
Wasabi's 90-day minimum for stored data means there is no financial incentive to reduce utilization through early pruning of snapshots. Because of this, the strategy shown in the documentation for the [`prune`](https://github.com/gilbertchen/duplicacy/wiki/prune) command can be shortened to the following without incurring additional charges:
|
||||
|
||||
```
|
||||
# Keep all snapshots younger than 90 days by doing nothing
|
||||
$ duplicacy prune -keep 7:90 # Keep 1 snapshot every 7 days for snapshots older than 90 days
|
||||
$ duplicacy prune -keep 30:180 # Keep 1 snapshot every 30 days for snapshots older than 180 days
|
||||
$ duplicacy prune -keep 0:360 # Keep no snapshots older than 360 days
|
||||
```
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user