-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attempt to Restore from Linode Backup #55
Comments
https://manager.linode.com/linodes/backups/linode3429883 https://manager.linode.com/linodes/backup_details/linode3429883?id=119009843 Add a new linode for the backup: https://manager.linode.com/linodes/add Go for a walk outside ... |
Trying again from an earlier backup. |
22h later still no acknowledgement on the Linode Support Ticket ... ⏳ 😞 |
https://manager.linode.com/linodes/dashboard/linode14305623 Looks like there's a lot more data on the recovered instance. OK. that appears to be all working. Let's get back to zipping up the data ... dwyl/hits#81 |
Lowering priority as the data was restored from backup. ✅ |
Next:
|
Considering using Docker to run Phoenix and PostgreSQL ... dwyl/learn-docker#15 (comment) |
Continue: https://cloud.linode.com/dashboard |
what's up with the ridiculous 8GB forever log? 🤷♂️ Let's clear them: https://stackoverflow.com/questions/31721860/how-to-clean-foreverjs-logs-for-running-processes
That gives the instance a bit more breathing room. But still going to delete it! |
Zipping the data as part of dwyl/hits#81 appears to have deleted some data ... dwyl/hits#83 😞
Thankfully I'm paying for backups on Linode so now it's time to test the process!
The text was updated successfully, but these errors were encountered: