There are several lengthy message threads in these forums about the disappearance (in versions 1.6.2 and 1.6.3) of EE’s internal database-backup utility. Having read every word of those threads, I sadly but totally agree with the EE staff decision to remove that necessary utility, even if the observed backup-unreliability problems affected only a small percentage of EE users.
Having said that, the remaining options (PHPMyAdmin, MySQLDumper, various UNIX utilities etc) just don’t cut it. Expression Engine is hugely attractive to Web publishers and developers, not only for its powerful page-design, programming, and available add-ons (not to mention industrial-strength tech-support ), but also for its comprehensive built-in admin utilities. If I was still a computer-magazine editor (a former life), I would slice one full mouse, or maybe a star, off the rating for any modern CMS that lacked a database-backup feature — or at least a well-documented plug-in or external tool which can operate remotely as does EE via the Internet.
I realize that the PHP/SQL and cross-platform universe in which EE operates is way complex, but no internal backup utility is like, well….like opening up your van’s spare-tire compartment (while rain, lightning, and winds howl around you on the Kansas highway), only to discover….
A friend of mine was among the small number of people who lost data on a high profile site with the backup utility (I had no part in it.) Disaster. We say good riddance to the utility.
I do believe the developers said there will be an alternative available in the next version. Indeed, CodeIgniter is already equipped with an arsenal of database tools.
My advice, stick with proven database tools. Nothing is more important than your data.
Edit: Actually, any system can fail. You need multiple methods, means of ensuring data integrity and multiple locations for backups. This is not easy, but it is necessary.
I believe we were that friend mentioned above. Yes we lost hundreds of posts across multiple sites when we found out the hard way that the back-up did not work. Though it is never fool proof, there should be some back-up option or more than one option, to help people protect their data.
Whilst I agree it would be nice if EE 2.0 comes out with some new fangled backup utility I would never ever rely on it 100%. This is no offence intended towards the ExpressionEngine developers but as this is something that is happening over the internet that is one exceptionally big variable that just cannot be allowed for in every instance.
I for one always backup using phpMyAdmin both as separate tables and as a whole file. I also use around 4 other backup utilities as well. Call me overly cautious but I can live with images disappearing or files as they are always backed up as I uploaded them in the first place so already have them on computers, hard-drives and DVD but data that has been hand entered can never be found again. Not something I ever ever want to lose.
So yes it would be great to have some new fangled utility but don’t rely on it - ever. phpMyAdmin has been around for a very long time now and there is a reason why it is installed on most server environments, that being that it is pretty much very stable. Whilst it isn’t always the nicest tool to look at it does generally do the job very well.
Another thing to perhaps look at is to ask your host kindly if they will backup the data for you. If you have a good host worth their salt then they shouldn’t mind doing this for you or they are likely to lose your business if you lose your data. The hosts I go with have always stated that they will do this if required.
So to re-iterate I would love to see a new utility built into ExpressionEngine but I will always backup with other utilities also as my data is my life.
Any system admin worth their salt can set up numerous ways to back up. Entire directories can be tarred, zipped and then downloaded to your computer or another computer. My admin once used rsync (unix utility) to keep an old server and the one I was moving to up to the minute - so that when I moved over, it was instant.
Almost all virtual server companies have backup systems that you, the customer, can access. Mine has something by EMC which I can access through X windows- and then restore any files, directories, etc.
A rudimentary system might just run a cron job once a week, tar and zip everything and move it to a directory where you could ftp it to yourself, and send you an email telling you it was ready.
A rudimentary system might just run a cron job once a week, tar and zip everything and move it to a directory where you could ftp it to yourself, and send you an email telling you it was ready.
I’d be much more worried about the database. The files in my webspace can be replaced easily. Having said that, I agree with EL’s decision to remove the db backup facilty if it does not work reliably. Last thing we need is providing a false sense of security, and then failing when it counts.
Probably the most reliable way to backup your MySQL databases is using the “mysql” commandline utility that comes with it. Very easy to have cron run that once a day, or whenever desired.
I don’t really see this as a software issue but a server issue. mysqldump and a cron job would automate this. Many shared hosts offer a backup solution and if they don’t then move to one that does.
Another element to consider is your ability to recover. If you are running a high traffic “shopping cart” then every minute of downtime can cost money. If your site goes down, you should have a plan to only to ensure everything is backed up but to get back online quickly. A personal site can probably afford a little more downtime.
The ExpressionEngine DB backup and host backups will not help you for fast recovery. If you lose your files but you have backups “somewhere” on your hard drive, you still might have to rebuild, update and then upload everything using your crappy home connection.
Your backup options also depend on the type of site you have. If you have gigs of data then a tar and zip is probably not the best option. Also, backing up can be highly resource intensive so you need to be friendly to your host and neighbors if you are on shared hosting. Even on a dedicated server in cases of huge amounts of data you could be putting a hurting on your own server.
Incremental rsync is a pretty good option for most situations. Rather than pushing your entire file base around for every backup you just update the changes since the last backup. There is also an rsync clone for S3 built in Ruby.
Thanks to all who posted ideas and encouragement for EE/SQL backup utilities. Some I’ve used as a sysadmin, others I’ve only heard of and will check out further.
However, I stand by my opinion that a professional-quality, secure Content Management System such as EE should include its own built-in, one-click backup feature, or at least its own EE-sanctioned, optional plugin for the purpose. Even better would be an EE system-utilities button labeled simply “Import from Backup File” (which accesses a Superadmins-only EE subdirectory). Scheduled auto-backup shouldn’t be hard to add on.
I realize this anti-gearhead approach dumbs down a process normally reserved to the technorati. The same was true of the first authentic DTP program “PageMaker,” which completely hid PostScript programming and allowed publication designers direct WYSIWYG control of their content. Programmers laughed, but PageMaker became a huge hit….
I think thought that the problem comes down to many many factors though. Whilst I’m sure the EE developer team could create a backup facility which would be fantastic there is a lot of work that goes into something like that. Just look at phpMyAdmin and how much work went into that and that’s all they work on. Take into account that the EE team are working their socks off around the clock to work on EE then it gets more complex. Also more importantly that any backup system can still fail as a lot of the time it can be down to memory allocation on the server, your connection to the internet may drop etc…
Even with dedicated servers where you are actually sitting at the computer you can still have problems. It’s unfortunately not an easy one to undertake and I do see the reasons for why they took the utility out of EE and commend them on it. A few people had lost copious amounts of data which just isn’t good.
Sorry to sound negative on this and I’m not having a dig at all but I always backup in around 5 different ways nowadays (totally paranoid about data I am ) but (touch wood) have not had any problems so far. That being said I’m not really working with massive amounts of data either so one day, just one day perhaps I may get that problem but I seriously hope not
), but also for its comprehensive built-in admin utilities. If I was still a computer-magazine editor (a former life), I would slice one full mouse, or maybe a star, off the rating for any modern CMS that lacked a database-backup feature — or at least a well-documented plug-in or external tool which can operate remotely as does EE via the Internet.
