![duplicacy rename backup duplicacy rename backup](https://forum.duplicacy.com/uploads/default/original/1X/5e3fc150ec6405f0c97151a8445cf231c02794d1.png)
So I guess the best would be to backup flash and appdata and dockers to a share, then have that share sync to something like Dropbox? And if things go wrong, somehow restore to a new flash drive? Would that be it, or is there a better way? I'm getting a bit confused on what to do. So backing up directly to a stick doesn't make so much sense in this case.
![duplicacy rename backup duplicacy rename backup](https://forum.duplicacy.com/uploads/default/original/2X/1/1c640002dc4fe12446de1f602a3f8811db4fe67f.jpeg)
Also, does this backup my complete setup? Meaning, will this backup my dockers, configuration, etc? Or do I have to set up additional backup measures for this?īasically, what would I need to do to get my server back up to exactly how it was before a crash / boot USB failure?
#Duplicacy rename backup download#
Is there any way to automate the backup so it happens periodically? Right now, that function download the backup to my hard drive, and I would rather like it to backup to a spare USB connected to the unRAID machine itself.
![duplicacy rename backup duplicacy rename backup](https://gamblisfx.com/wp-content/gallery/duplicacy/duplicacy-screenshot-1.png)
That will take a bit longer but they have always been very accommodating to reasonable requests. IF you should have a problem, you can always contact Customer Support. If you have a proper backup of your Unraid boot drive, you can be up and running in a few minutes after a USB failure. LimeTech tries to make it very easy to get a replacement key. You can find more details on the exact procedure for getting a new. Under the Flash Device Settings section/tab, you will find a "Flash Backup" button. The easiest way to make this backup is go to Main under the Boot Device section/tab, click on the blue 'Flash' listing under the 'Device' column. Making a backup of the current working USB drive will suffice to recover from a future USB failure. Unraid always requires that it be booted from a USB drive. Try the deduplication again by renaming, copying and moving files and you will see that the remote data (.DBLOCK files) will not increase.So if the current USB gives up the ghost, this will allow me to boot from another device without loss of data? And what about the registration? How does that get transfered? For situations where insertion of data is common (text files), there is not much space to save, these filetypes are often very small. In common situations, data is added to the end of an existing file instead of inserted. Reason for using fixed block size is that the algorithm for dynamic block sizes is much more difficult and probably doesn’t save much space. In all other situations, data in each block is shifted and thus will be different from existing remote blocks. If you merge multiple files into one file, the individual block data will be different, unless the file sizes are exactly a multiple of the block size. Block data must be identical for deduplication to apply. Default block size is 100KB, but can be adjusted before the initial backup is made.Įach file will be separated in 100KB chunks of raw data (the last block is probably smaller and contains the last part of the source file). I ran Duplicati twice coz the result seemed out of line but it turns out to be consistentĭuplicati uses a fixed block size for deduplication. Given that last is 128MB files - it can’t be because of chunks exceeding the file size right?
#Duplicacy rename backup full#
For the last, the file sizes are big enough that dedup kicks in for others to a virtually full extent but Duplicati is still struggle. For the smaller sizes all programs struggle but Duplicati clearly still behind. As the combined file is simply a concatenation of the components, a perfect dedup algorithm could attain 100% efficiency (and no changes in the backup size sans small metadata impacts)ĭuplicati seems to be having real difficulty. The backup size was compared after each run. When researching found the following thread on Restic board which I thought would be useful to add to test suite ( )Īs per thread linked above - it is a back-to-back backup of component files and then a combined file comprised of urandom files of the following sizes: Not here to start flame war on which is better / worse just want to curious on technical reasons.ĭuplicati seems to not be really deduplicating files which are theorectically 100% deduplicatable (is that a word?)ĭoing some benchmarking / comparison work as documented here ( )