Aliysa_Enhance Nice PR response
Version 12.1.0 released
Looks like they dropped a few things of the original 12.1.0 release
12.1.0
Scheduled
Estimated: March 2025
Added
Ability to download an archive backup of a website and import it to another cluster.
This simplifies the process of winning a customer from another hosting provider who uses Enhance.
The backup/restore will retain mailbox, FTP and database passwords.
Ability to browse backups of hard deleted websites, to remove the data, download the backup or restore to a new website.
Firewall management interface.
Email queue management interface.
Not sure, but it looks like version 12.1.0 may have fixed the backup timing issue.
SolidNetwork So, as an update up to my post, I have now completed my v12.1 upgrade directly from v11.0.4
Everything went smoothly by following the guide:
https://enhance.com/docs/getting-started/upgrading-from-v11.html
(Also used the cPFence guide to have it uninstalled and reinstalled again after the upgrade).
The only weird behavior I noticed during the upgrade, was that you really need to stick to the guide above and do not follow echoed commands that appear in the command line, as in my case those should be executed later on in the guide.
The only lengthy process of the upgrade was the fix backup permissions command (took around 4 hours) but I guess that's normal for 200GB of files on HDD storage. But that was no issue as it did not affect the host server (App+DB). Apart from that the whole process would be completed within minutes.
Another plus is that there was no noticeable downtime on the hosted websites, less than 2-3 minutes when shuting the host server for a full snapshot and then another 2-3 minutes when restarting the server after running apt update && apt upgrade. Same goes for the mail server. The 3xDNS Role setup really payed off here. I did not have to restart the servers after the upgrade and will probably do so during the night in the next patch update.
The v12 speedup is very noticeable especially on the panel role server as I constantly had over 50% RAM load but now its always around 11% (my panel server has 12GB RAM). Also the CPU load is much more stable around 0.2 now.
I'm now monitoring the backups, first thing I noticed was that Mail backup is now separate from Files + DB. I'll post if I notice any new bugs.
cPFence Yes, I can confirm that backups are happening at fixed time now (hopefully) but team should include bug fix log in release logs or did it just get fixed by itself lol
V12 - The resource usage deduction is fantastic. Everything else...
- Backups being weird
- Staging/cloning. It seems you need to change the URL in phpmyadmin database after cloning sometimes, as it just directs to the production site.
- DR issues as mentioned as mentioned in detail by a user recently. Database doesn't restore.
- Can't use SFTP yet? (Not sure only checked 3-4 days ago)
I love Enhance and will be using it for a long time yet, but its only using one OS(ubuntu) and yet the upgrade was kind of buggy. Doing an upgrade during testing you would notice the backup permission errors I would of thought. But hey what do know LOL
SolidNetwork the MOST critical issue after upgrading to V12 us is not mentioned on the guide is OOM kill on Ubuntu , it might kill your web server or mysql , none of them are set to restart automatically in such case .
High ram usage can happen due to bugs, I am not gonna list them here, or natural causes like traffic peaks, it's a GOOD idea to adjust your services to mitigate such issues .
Personally I don't use auto restart on mysql but I do on the web server .
- Edited
I think the community pressure played a part, hence the recent changes to the roadmap(removing the dates).
I would have preferred to use V11 for as long as we needed and get a stable update for V12. The business is starting to see a boost, and it's only a matter of time before one of the backups or staging clones fails
SolidNetwork The only weird behavior I noticed during the upgrade, was that you really need to stick to the guide above and do not follow echoed commands that appear in the command line, as in my case those should be executed later on in the guide.
This got a lot of people.. I think we can add to this message here,
We have this : "WARNING
It is very important that these steps are followed in the exact order. Most issues with the upgrade process come from steps being missed."
Prompts saying 'do this' during an upgrade are deadly. A little more notice not to input any prompts directed from the terminal and ONLY follow the guide would be ideal. When you say this "Most issues with the upgrade process come from steps being missed.", not following what the terminal tells you could be confused with exactly that, missing a step.
- Edited
Upgraded to 12.1.0 with 0 hiccups following the instructions! Thanks Enhance.
mikejc Prompts saying 'do this' during an upgrade are deadly. A little more notice not to input any prompts directed from the terminal and ONLY follow the guide would be ideal. When you say this "Most issues with the upgrade process come from steps being missed.", not following what the terminal tells you could be confused with exactly that, missing a step.
Thats really unacceptable because to me if step 1 is "run x command" and step 2 is "run y command" and x command tells me to do something, I'm going to assume thats just part of the first step and run it and then move on to step 2. Its natural.
@Adam you guys need to fix this.
mikejc
Yea, I'm guilty and partly responsible for typing the wrong commands in places they shouldn't go and it did some real damage!
The original instructions were even more funky.
For a retail product the scripts should have had better inbuilt safety's built into them (maybe they do now). Each of the servers know their own roles. A script intended to be a run on a controller server should have aborted if it was run on a DNS Only server.
Done the upgrade several more times on other clusters and it works well and smoothly.
Annoyingly what the terminal prompts is not the same order and sequence as the documentation.
Just read the instructions twice over before starting. Do not have multiple server windows open! Have a tickbox of each step for each server.