I’ve had to on multiple occasions restore a full server. No issues at all.
What is your disaster recovery plan in production?
- Edited
JohnB I obviously have the Enhance Bckup role, and each Enhance node(Backup role included), is Rsync to a off site, and I am using Google Cloud Enterprise states which are taken every hour. I have Google whole VM backups running too just in case.
I also have nable running also forgot to mention.
So in total, Enhance Back Up, RSYNC, State Backups, and Image Backups.
Zoinkies I see, thanks. So how would you restore a server from the offsite Rsync? The rest rely on the provider's (google) infustructure.
Let say one of the nodes with 50 (or however many is impractical to manually restore) sites goes offline and the google state or VM backup isn't available for whatever reason.
Fairly easily, it's how most backup plugins work under the hood. It's just a lightweight tool to add a layer of protection.
And no, N-Able is separate infrastructure from Google, and my R-Sync, Google's Images are exported to my Dropbox.
So, I could restore from R-Sync, N-Able, Whole Machine Image, or using Google's States or Enhance's site backups.
- Edited
Zoinkies I understand. Could you share your restore script for R-Sync?
I've tried backing up enhance several times and restoring the websites I can do but the control panel always freaks out and leads to a white screen and errors in appcd. I'm probably not backing up the right files or restoring correctly.
Are you just backing up the /var/www/ folder, mysql db dump, postgres db dump and then on a fresh machine you install enhance, restore files and dumps?
- Edited
As mentioned by others, how are you pulling this off inside enhance?
Clarification
You run enhance on GCP?
You have GCP Enterprise States
As JohnB mentioned, curious how you handle what amounts to manual backup/restore into Enhance. Also, we're NOT restoring to Enhance presently, but our previous LSE, PHP, MySQL dedicated servers. I'd be curious to know how Zoinkies is pulling this off.
digitalexpanse Exactly my questions as well. And interesting! I had the same idea. I currently use LXC and could write a script that could restore backups into my current setup but at that point I just wont use enhance lol.
@JohnB
Exactly, unfortunately, we're not using Enhance at scale and sidelined over one required feature.
And I've tried extensively to get core requirements prioritized over trivial shit but hit a wall every time, zero flexibility. I offered to sponsor a core feature for $5,000, but no, apparently, the development team was at full capacity stating (we have to prioritize the features which are relevant to the majority of our customers first).
I followed that up by offering a 200k investment, and they said, "We're quite well funded and more money won't speed up development", which makes about as much sense as not prioritizing core requirements.
digitalexpanse I understand everything you say but you know in practice as you're an entrepreneur that you can't just let your users invest in your company at the early stage. Based on what valuation? Also, every new investor requires time and effort to be brought in the capital. They have no time for that I assume.
If we were to invest in the development of a feature, how would things be accounted for? Would the feature belong to you or Enhance? It looks simple and generous but it's complicated.
Last we are not the only users and there are probably many other people interested in investing in a company like Enhance.
I think all demanding and experienced users can find something right now not working exactly the way we want in Enhance. But if we look at the big picture, the team behind it, the roadmap, do you share their vision? If yes, then we all need to be patient and supportive.
I hope I can hold my own commitments (sometimes I have a bad mood and I get frustrated) which are:
1/ Never ask to Enhance team when an update is coming. So far I managed.
2/ Supporting the team by being always patient and positive. I partially failed when I got upset like a newbie at Upmind. Read my crying posts in the community ;-)
3/ Being grateful to them for the challenge they are in. From what I've heard, building a CP like this one is an absolutely delicate and complex task.
4/ Keep pushing our feedback and defending our vision while testing, and testing.
I'm ready to bet that all the issues that are holding us back will get resolved this year. If this was cPanel, Runcloud, Gridpane, etc... it would take another 5 more years.
- Edited
@Adrien monumentally overthought and overcomplicated, this is a shit way to look at things. I'd pay/invest purely to get a feature prioritized.
Big difference between something you make complicated vs actually being complicated.
Pay 5k, get a 5k credit towards services; anyone using Enhance will no doubt be spending the money anyway. Hell, even 200k is fuck all if anyone actually plans on scaling this out and is actually in the industry and not just dicking around.
There is a monumental difference between something missing and not working which is a want rather than a need. As it stands 99% of the items listed on the roadmap have zero impact on us scaling.
Grand scheme of things, look at this from a positive, benefit and consider for a moment some people just want to help, and actually make an effort. This is how I built my company, by actually helping website owners versus fucking them around.
digitalexpanse Agreed. I'm a developer and business owner myself. Projects run late sometimes and they are right that adding additional programmers often isn't the solution. But the problem isn't that they are late its how they prioritize. Be late on the cloudflare integration or some other nice to have, not backups and recovery lol. This is why I don't have patience.
14 days later
Have to agree with some of what is said here.
The focus for some things seems very off to core "needs".
Lots of things being done for webservers, or WordPress, or even visual changes whilst core mail functionality is severely lacking (queue, SRS, ability to filter incoming messages externally etc).
Same thing with cPanel migrations, that's all well and good but realistically, anyone with a sizeable cPanel base is going to get complaints when core functions just don't exist (even as basic as catch-all email).
We are using just for testing and internal needs but I think like many, we've not pushed the button on making it a live service because the risks in doing so are too great, especially around email currently.
- Edited
XN-Matt The focus for some things seems very off to core "needs".
The issue is that everyone's core needs are different. Some people tell us they only run WordPress and everything else is unimportant. We have other customers who only use Enhance to host email. The majority are somewhere in the middle.
We have a lot of time scheduled for development of email over the next 2-3 months. We will be launching an email queue manager as well as a customer "email trace" tool so they can self diagnose any delivery issues.
Also just to add, a lot of the roadmap is dictated by the fact that many of of the features are inter-dependent. For example, to offer SSL on mail.{customerDomain} we need the nginx feature so we can spin up a lightweight web server for the LetsEncrypt validation, where the customer has a standalone email server.