Duplicacy preference file how to#
Duplicacy preference file zip file#
Duplicacy preference file full#

This method does not require a distributed locking mechanism on top of the file storage. Instead, it performs a much simpler file lookup by using file names derived from the hash of each chunk.

Chunks of data that are the same across multiple websites only need to be stored once.ĭuplicacy also uses what’s called “Lock-Free Deduplication”, which means it doesn’t require a centralized indexing database for keeping track of backup data.

Chunks require no further modification once saved (and thus data corruption is far less likely to occur due to their immutability).

Chunks are each saved to their own individual file with their own hash which functions as the file name.

As backups are all stored as chunks, this format that is non-human readable and so they don’t exist in the same way that a plugin backup, for example, would exist on your server.

Duplicacy preference file zip file#

When a backup is to be restored, the system collects all the data chunks relevant to that specific backup and reconstitutes it.Ī common question we get asked is “ where is my site backup stored?” with the expectation that they will be accessible in a zip file somewhere on the server. During backup creation, it compares them to existing chunks and shares identical chunks between backups.

Duplicacy preference file full#

After the first initial full backup, each backup builds upon the previous data.ĭuplicacy uses deduplication, which stores chunks to your local server and/or cloud storage using content hashes as file names.

This means that each time your websites are backed up, the data is de-duplicated and compressed. Setting Up Remote Website Backupsīoth our V1 and V2 backup systems use incremental backups. To jump straight into setting up V2 backups for your websites, please see the following 2 articles for local and remote backups: Exporting previous, existing backups for download over SFTP.Remote backups to 4 different external providers: AWS S3, Backblaze B2, Dropbox, and Wasabi.Lock-Free Deduplication (which has numerous benefits).Improvements over the older V1 system that runs on Borg include: – On its own, without any of the configurations our team has created for its WordPress implementation and integration into GridPane, the software would cost you $50/year per server. V2 backups run on a custom implementation of the exceptional Duplicacy, a cross-platform cloud backup solution. Backup retention time and adjusting the pruning schedule.

Duplicacy preference file how to#

In part 2 we’ll look at how to get started with local backups, and in part 3 we’ll look at setting up your remote backups. This is part 1 of 3 of our V2 documentation, and in this article, we’ll look at how you can configure and manage your backups using the new V2 system, and answer all of the common questions we’re asked about how things work and where things are stored.

Our new V2 backups system offers multiple significant improvements over our original V1 system.