Why cloud backups shouldn't depend on your computer being turned on
I used to think a backup job meant running something on my computer.
A script.
A cron job.
A sync client.
A machine that has to stay online.
But if the source and destination are both already in the cloud, why does my computer need to be involved at all?
That's one of the things I wanted to change with Syncrix.
You can create a workflow like:
Google Drive → S3
Every night at 2 AM.
Or:
OneDrive → Dropbox
Every Sunday.
Once the job is configured, it runs server-side. Your laptop can be closed, your desktop can be offline, and there's no local copy that needs to be downloaded first.
This also makes incremental backups much more practical. The first run moves the data; subsequent runs only need to deal with what has changed.
I'm curious how other people handle this today.
Do you:
run rclone?
use a NAS?
keep a machine running 24/7?
use a cloud VM?
manually copy things when you remember?
or simply don't have an off-site backup?
I'm especially interested in the workflows that almost work but still require annoying manual intervention.
That's usually where the interesting problems are.

Replies