SynapseDirect

I've had some more thought about this.

I can spawn a server process that does the backup to S3, and you can get a report back in the client instead.

Once the files are on S3, there is no longer a need for them to be stored locally - because they can be served from S3 storage instead.  It might even be a little faster if you're using Synapse as an ASP.

One scenario is that I often see patients out of town.  I take a copy of the remr.fdb with me in case I can't access the main server ... but there are just too many files in the cache-listener for me to take as well.  So, in that case I rely on the metadata.  But if I had S3 storage, I could choose to download from there instead of my localhost server, or, my remote server.