a month ago
I asked the agent to setup LiteLLM to sit alongside my production application, and it created a database for it but it inserted my production database instead of the new database in the LiteLLM variables, which is a really rookie mistake which has overwritten my production database and I don't have a backup. I'm on hobby and not pro account, so backups is disabled.
This was an agent error. Is there anything that can be done, please? It's many hours if not days of work for me to re-key and soul destroying.
5 Replies
a month ago
We don't offer data restoration for user-initiated actions like this. Going forward, enable volume backups on your service so you can self-restore if it happens again.
Status changed to Awaiting User Response Railway • 30 days ago
Railway
We don't offer data restoration for user-initiated actions like this. Going forward, enable volume backups on your service so you can self-restore if it happens again.
a month ago
I'm not a pro user so backups aren't an option.
To be quite honest, I think Agents are not ready to offer to when they can make such catastrophic errors with no 'undo'.
Seems like I've learned a hard lesson.
Status changed to Awaiting Railway Response Railway • 30 days ago
a month ago
To correct one thing: volume backups are available on Hobby, not just Pro. You can enable manual or scheduled backups from your database service's Backups tab right now so you have a restore point going forward. We understand this is a painful loss and are sorry it happened, but we're not able to restore data after user-initiated actions, which includes actions taken by the Agent on your behalf.
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
Really?
I quote "Backups and point-in-time recovery (PITR) are only available for customers on the Pro plan."
There is no button for scheduling backups.
Attachments
Status changed to Awaiting Railway Response brody • 30 days ago
a month ago
You're right, and we apologize for the incorrect information in our previous replies. Backups and PITR for Postgres are Pro-only, as your screenshot shows. We should not have told you otherwise. The data recovery policy unfortunately still applies here, but we're sorry for compounding a frustrating situation with inaccurate guidance.
Status changed to Awaiting User Response Railway • 30 days ago
Status changed to Solved Railway • 30 days ago