All I have to do is login to WHM, navigate to JB, and select the accounts and what backup to use. Say I had a massive catastrophe and had to wipe the server. I can set Jetbackup up so that it restores accounts off of a backup server. Nope, I simply login as the cPanel user and restore the file, db, or whatever. Nor do I have to uncompress a big old tarball, or navigate a specific directory. Unlike cPanel's backup system, I don't have to restore the whole account just to get a file, or mysql database. If I wanted to push it, I could go longer, but 45 days works beautifully for me. This means I can reverse the account (or files) to the state they were 45 days ago, with ease. Right now, I've got incrementals set to keep 45 days of backups, and that's only using about 2x the space of my main server, or about 160 gigs total). Jetbackup, when using incremental (snapshots) can utilize hard links, which means that you're conserving space pretty well. All in all? I spend about $20/month, including cheap backup servers and JB licensing, for peace of mind.
One doing just MySQL, one doing snapshots, and one doing account backups (compressed). Multiple jobs, and destinations can exist for Jetbackup, taking care of #3 on that list. Pretty sure you (and others) would go for the second, as opposed to the first Using cPremote restore feature, we can restore full backups including home directories, email accounts. It is quite easy to manage and has restore feature too. cPremote supports incremental, compressed and uncompressed backup with seven days retention.
While we understand this is not as frequent as you'd like, this is a pretty decent rotation It has a WHM interface which helps server admins and cpanel users to manage their backups. Hey, we have multiple backups for XXX day, and we backup every 6 hours. It's going to change, and it's going to change often. MySQL is the most fluid thing on any server, production or not. To start with, this resolves #4 in my list above. Jetbackup, for as little as it costs, is just insanely better off than cPanel's backup. How is Jetbackup any different from cPanel backups? It's miles away. a bad backup plan (which, relying on AWS, Google, etc, not preparing for disaster) is going to be the end of you. You need more than one place for backupsĤ: You need more than one daily MySQL backupĪs someone who's been in the business long enough to see bad crap happen on a (repeated) basis, you really need to take that advice to heart. You need to be in control of your backups, and what they can do.Ģ: You need more than 5 day's backups, as a 'just in case' scenarioģ: Redundancy is key. If it 'seems to be working good', then great, however, a few things:ġ: Never trust backups at a place you do not control.This includes AWS, Google, anywhere.