Yeah, makes sense.
If you’re trying to make a second backup to a second destination then the cloning will work for the initial “split” but when you import the cloned configuration you’ll have to do a database rebuild to get the cloned configuration to recognize the archive files from the original job.
Was referring to this. That would be kind of sucky, to be honest. Assuming one wants an exact clone of the backup, they ought to be able to just copy the raw backed-up (.aes) files and Duplicati should work the same way on/at another device/location, no?
In the mean time, some users have achieved a similar effect by creating a RAM drive and pointed their Duplicati temp folder at that.
That’s pretty smart. I’ve used RAM drives before, they’re pretty easy. Of course, both of those options you mentioned would require a device with lots of RAM if it’s low on disk space.
Well you had darn better get on it right now!