Skip to content
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

Closed
nelsonic opened this issue Jun 3, 2019 · 23 comments
Closed

Attempt to Restore from Linode Backup #55

nelsonic opened this issue Jun 3, 2019 · 23 comments

Comments

@nelsonic
Copy link
Member

nelsonic commented Jun 3, 2019

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!

@nelsonic
Copy link
Member Author

nelsonic commented Jun 3, 2019

https://manager.linode.com/linodes/backups/linode3429883
Screenshot 2019-06-03 at 08 33 57

https://manager.linode.com/linodes/backup_details/linode3429883?id=119009843
Screenshot 2019-06-03 at 08 35 23

Add a new linode for the backup: https://manager.linode.com/linodes/add
image

Wait ...
image

Brand new:
image

Try the restore again:
Screenshot 2019-06-03 at 08 40 27

Modal ...
image

Wait ...
image

Keep waiting ...
image

Go for a walk outside ...

@nelsonic
Copy link
Member Author

nelsonic commented Jun 3, 2019

Failed:
image

@nelsonic
Copy link
Member Author

nelsonic commented Jun 3, 2019

Trying again from an earlier backup.

@nelsonic
Copy link
Member Author

nelsonic commented Jun 3, 2019

Failed:
image

@nelsonic
Copy link
Member Author

nelsonic commented Jun 3, 2019

Opened support ticket:
image

image

Ticket: https://manager.linode.com/support/ticket/11990994

@nelsonic
Copy link
Member Author

nelsonic commented Jun 3, 2019

Failed again: 😞
image

@nelsonic
Copy link
Member Author

nelsonic commented Jun 3, 2019

Attempting to restore from the oldest available backup:
image

Failed:

Restore failed, 283556 troubled files DEBUG: {"symlnk":1056,"zero_length":230,"create":282267,"sparse":3} 

image

@nelsonic
Copy link
Member Author

nelsonic commented Jun 3, 2019

Unable to boot the instance:
image

Network Helper did not run: could not determine distribution or distribution version  

Which means we cannot actually run the instance.
This is a horrible UX because it says "Success" but then we cannot actually access the instance!

@nelsonic
Copy link
Member Author

nelsonic commented Jun 4, 2019

22h later still no acknowledgement on the Linode Support Ticket ... ⏳ 😞
https://manager.linode.com/support/ticket/11990994
image

@nelsonic
Copy link
Member Author

nelsonic commented Jun 4, 2019

Got reply from Chris @ Linode Support:
image

Attempting to restore again so that they can help me.
(I deleted the failed instances because they were useless to me ...)

@nelsonic
Copy link
Member Author

nelsonic commented Jun 4, 2019

This is further than it's got in previous attempts:
image

Still failed:
image

Replied to Chris:
image

@nelsonic
Copy link
Member Author

nelsonic commented Jun 5, 2019

Got a reply from Tim at Linode:
image

Sadly, the restore Tim attempted did also failed with the same error:
image

Waiting for another reply ...

@nelsonic nelsonic changed the title Restore Linode Backup Attempt to Restore from Linode Backup Jun 5, 2019
@nelsonic
Copy link
Member Author

nelsonic commented Jun 6, 2019

Latest reply from Linode Support:
image

Going to try and boot the image now ... 🤞

@nelsonic
Copy link
Member Author

nelsonic commented Jun 6, 2019

https://manager.linode.com/linodes/dashboard/linode14305623
image

Running:
image

image

Looks like there's a lot more data on the recovered instance.
going to attempt to run the app.

image

image

image

OK. that appears to be all working. Let's get back to zipping up the data ... dwyl/hits#81

@nelsonic
Copy link
Member Author

nelsonic commented Jun 8, 2019

image

@nelsonic
Copy link
Member Author

nelsonic commented Jun 8, 2019

Lowering priority as the data was restored from backup. ✅

@nelsonic
Copy link
Member Author

Next:

  • log back in to restored server: ssh [email protected] and download old logs
  • log in to production server ssh [email protected] and download latest logs
  • attempt to insert text (ALF) log into PostgreSQL using script on localhost
  • investigate simplified Elixir (Phoenix) deployment: Effortless Elixir releases and deployment learn-elixir#129
  • decide if we are going to continue using Linode or switch to AWS for PSQL-as-a-Service?
  • Deploy to chosen environment
  • Update LetsEncrypt to autorenew if possible
  • Update DNS to point to Phoenix server.
  • Monitor the service!

@nelsonic nelsonic added the T1d label Feb 15, 2020
@nelsonic nelsonic self-assigned this Mar 28, 2020
@nelsonic
Copy link
Member Author

Considering using Docker to run Phoenix and PostgreSQL ... dwyl/learn-docker#15 (comment)
Reading: https://pspdfkit.com/blog/2018/how-to-run-your-phoenix-application-with-docker/

@nelsonic
Copy link
Member Author

Continue: https://cloud.linode.com/dashboard

@nelsonic
Copy link
Member Author

linode-cpu-threshold

https://cloud.linode.com/linodes/3429883/summary
image

@nelsonic
Copy link
Member Author

ncdu-linode

@nelsonic
Copy link
Member Author

Screen Shot 2021-05-22 at 11 33 46 PM

du -S . | sort -nr | head -25

Screen Shot 2021-05-22 at 11 38 14 PM

what's up with the ridiculous 8GB forever log? 🤷‍♂️
Screen Shot 2021-05-22 at 11 43 17 PM

Let's clear them: https://stackoverflow.com/questions/31721860/how-to-clean-foreverjs-logs-for-running-processes

forever cleanlogs

That gives the instance a bit more breathing room. But still going to delete it!

@nelsonic
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant