Hi Marcin, > [...] Do you guys know if clone-fs.py can pickup where interrupted? Or > basically copy across what was not yet copied like rclone or rsync. [...] it currently cannot do that. It blindly copies over all data.
If you know some Python you could easily tinker with it, tho Either do not put the keys you want to skip in the queue ( https://github.com/s3ql/s3ql/blob/d2baf00236df69878e19466fc1c27f8ff0c89b4e/contrib/clone_fs.py#L168 ) or check if the key already exists in the destination backend and skip the write call. This would be a very naive implementation of the second option: Replace line 122 <https://github.com/s3ql/s3ql/blob/d2baf00236df69878e19466fc1c27f8ff0c89b4e/contrib/clone_fs.py#L122> with this: try:dst_backend.lookup(key)except NoSuchObject:dst_backend.perform_write(do_write, key, metadata) It does not checks whether the metadata is equal (a robust implementation should most definitely do this) -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/0d2a7c5d-e44e-86f7-6ed4-4a5bb50915ec%40jagszent.de.
