4 ms·

Yeah, I think a cron job to move/rsync is the most robust method.

em-bee 5y ago
doesn't work for me, because the cron job doesn't know when i no longer need the file on the phone. if i sync deletes from the backup device to the phone then a cron job to move files would potentially cause files to be removed from the phone before i am done with them. rsync would cause the files to be duplicated (although i could still hardlink using rsync)
- karlicoss 5y ago
  Hmm, what if you use a special directory where you could move the files on your phone once you don't need them? And then the cron job would move stuff from that directory ah for rsync I meant with --remove-source-files flag -- it's just sometimes rsync is easier to use than move, depending on the hierarchy of your files
  - em-bee 5y ago
    from the phone i want the files synced to the backup as soon as they are created. if i only sync those that i don't need then the once i do need never get synced. unles you mean to sync first, then move files i want to keep on the backup only out of the way and rsync --remove-source-files those files again. the problem with that is that when i do remove files on the phone, then it's because i need the space. at which point i don't want to wait. syncthing does what i want. that is not the problem. them problem is only that it is easy to forget to set up ignore-delete, and that it's hard to monitor the sync status of the backup from the phone. i appreciate the suggestions, but they don't really do much to help my case. what is really needed is an improvement of the syncthing UI and in particular a redesign of the way the status is handled. for my backup maybe i'll set up an rsync with hard-links to create a second version of all files which protects them from accidental deletion.
- pcnix 5y ago
  How I do this: * Create a unidirectional push only sync between the phone and a remote * Remote has a cron that syncs to backblaze regularly, and deletes from the server (this does not affect the phone) * Delete from the phone whenever I want

doesn't work for me, because the cron job doesn't know when i no longer need the file on the phone. if i sync deletes from the backup device to the phone then a cron job to move files would potentially cause files to be removed from the phone before i am done with them. rsync would cause the files to be duplicated (although i could still hardlink using rsync)

karlicoss 5y ago
Hmm, what if you use a special directory where you could move the files on your phone once you don't need them? And then the cron job would move stuff from that directory ah for rsync I meant with --remove-source-files flag -- it's just sometimes rsync is easier to use than move, depending on the hierarchy of your files
- em-bee 5y ago
  from the phone i want the files synced to the backup as soon as they are created. if i only sync those that i don't need then the once i do need never get synced. unles you mean to sync first, then move files i want to keep on the backup only out of the way and rsync --remove-source-files those files again. the problem with that is that when i do remove files on the phone, then it's because i need the space. at which point i don't want to wait. syncthing does what i want. that is not the problem. them problem is only that it is easy to forget to set up ignore-delete, and that it's hard to monitor the sync status of the backup from the phone. i appreciate the suggestions, but they don't really do much to help my case. what is really needed is an improvement of the syncthing UI and in particular a redesign of the way the status is handled. for my backup maybe i'll set up an rsync with hard-links to create a second version of all files which protects them from accidental deletion.
pcnix 5y ago
How I do this: * Create a unidirectional push only sync between the phone and a remote * Remote has a cron that syncs to backblaze regularly, and deletes from the server (this does not affect the phone) * Delete from the phone whenever I want