Our team is working on getting back to you as soon as possible. In the meantime, we've found the following might help you get unlocked faster:

• 🧵 Restore Backup MYSQL Instance into another instance

• 🧵 Not able to deploy a new PostgreSQL database

• 🧵 Postgres Crashed

If you find the answer from one of these, please let us know by solving the thread! Otherwise, we’ll be in touch.

Nevermind. I figured it out:

1. Click "Restore backup". Click the scary red "Confirm" button

2. Railway will stage a change

3. Click "Review changes"

4. Delete the change that mounts the backup restore as the new database volume. Keep the change that mounts the backup to a new volume.

5. Deploy the change (just the backup volume getting added)

6. Create new Postgres database

7. Right click the YYYY-MM-DD backup volume, choose "Mount volume" and select the new Postgres database

8. Copy all the variables from the original Postgres to the copy Postgres

9. Submit the changes

10. Connect to the new Postgres database and extract whatever data you need

Glad you were able to figure it out! Do you have any feedback on how the Restore backup flow could be made more clearer, etc?

Yeah, I definitely have a lot of feedback:

1. Clicking the "Restore backup" button is very scary. The button is red and you have no idea what it's going to do. At first I thought for sure it would replace my current DB's volume with the backup, which would be really bad. Adding more information here about what will happen would be helpful. Although, since the button here is fairly benign and there's a separate confirmation step later before you apply the deployment changes, maybe the confirmation isn't needed at all.

2. Give me a "Restore this backup to a new DB" button. That would be excellent! Instead of 10 manual steps, it would reduce the pain down to just 1 click.

3. After creating a new Postgres instance I wasn't always able to mount the backup volume to it. I'm not sure what ultimately did it, but for a long time the option to mount the volume to that new Postgres instance wouldn't show up. Eventually it did, but it would be nice if it was available right away. ie. User should be able to change a Postgres node's volume at anytime.

Thank you so much, appreciate you sharing and have passed it along to our product team

I just had to recover a backup again today and I saw the team made some immediate text changes. Thank you! This is much more clear.