Hey! You’re right, the snapshot feature right now is a little barebones. We do have plans down the line to make it more robust but for the time being it does the job. To answer your questions:
Right now, you can’t create a snapshot, we do nightly snapshots (every 24 hours) of a pg database automagically. We haven’t yet exposed a way to take a snapshot manually, though the building blocks are there for that later down the line. Also, retention policies for snapshots are currently 3 days.
As in the above point, snapshots are automatic and not user configured right now, so there’s no way to specify a schedule.
If I’m understanding your question correctly, you could replace a volume by creating a new volume that uses the snapshot id of an existing volume (sort of like a copy) and then delete the volume that you wanted to replace. Perhaps something like:
Thank you, I will! I’m just glad to hear that you understand the issue, that it’s on the radar and that you work in a logical order and solving critical issues like this (reliability + control over data) before “nice-to-haves”. Also plus to get fast feedback.