Is it possible to seed a new storage location by copy the chunks from another storage location into the chunk folder of the new storage location?
Yes, you can use the copy command to copy chunks between two compatible storages. To make compatible storages, you can provide the -copy option when adding the second storage.
You can also use other apps to copy over the chunks directory directly (as well as the file named config). If you go this route, however, please make sure the two storages have the same chunk structure. The chunks directory on drive-based and SFTP storages are hierarchical, while for most cloud storages it is a flat one. You can’t copy chunks using third-party apps between two storages with different chunk structures.
Ok… Thanks for the info. Will give it a try.
You have mentioned this before about adding storages. Did not pick up that it is the same for seeding.
Great program… by the way.
To expand on this…
Is it possible to:
- backup the first revision of a repository to an external hard drive.
- attach this external hard drive to a local or remote server (sftp in my case)
- use this server&ext. hard drive combo for revision 2 and onwards.
This would greatly reduce the time needed to perform the first backup.
Yes, this is one of the core advantages of Duplicacy over most other backup tools. All you need to do is to change to the storage url in the .duplicacy/preferences file to point to the sftp server after the initial backup.