Separate local and network backup logic. about ruckup

[Deedasmi]

Could I tie the processes together to minimize CPU time?

i.e.

1. Main thread finds a file that needs encrypting
2. Spawn thread to encrypt locally
3. Add file to meta data, and add encrypted file path to network queue, close files
4. Network thread works through queue
5. Queue of files that aren't backed up offsite is stored to be resumed next start

Pros:

• Time and resource efficient

Cons:

• Added complexity
  • Need to automatically recover socket loss, warn if network doesn't resolve
• Strange interactions if network falls significantly behind local encryption.
  • i.e. if local backups exceed max number of versions, and vacuum deletes a file that is still in network queue. How do we know local copy was intentionally deleted?