I highly recommend switching to something more like Arq and then using whatever backend storage that you want. There are probably some other open source ways to do it, etc, but Arq scratches the itch of having control over your backups and putting them where you want with a GUI to easily configure/keep track of what is going on.
Maybe there's something newer/better now (and I bought lifetime licenses of it long ago), but it works for me.
That said, I use Arq + Backblaze storage and I think my monthly bill is very low, like under $5. Though I haven't backed-up much media there yet, but I do have control over what is being backed-up.
I have used Arq for years. It has always been the least problematic, least intrusive, most reliable backup and restore option for me. Appreciative to Stefan Reitshamer for creating and maintaining it.
Arq saved me a few hours of work recently when VS Code's GitHub Copilot looped out on a Playwright screenshot (>8k pixel height) and I had to manually edit the JSONL chat history, but accidentally restored to the previous checkpoint. That was one time I really appreciated that I set Arq to back up hourly. (I only restore from Arq maybe 2-3 times a year.)
Maybe there's something newer/better now (and I bought lifetime licenses of it long ago), but it works for me.
That said, I use Arq + Backblaze storage and I think my monthly bill is very low, like under $5. Though I haven't backed-up much media there yet, but I do have control over what is being backed-up.