Jump to content

WHM Backup vs. Cpanel Backup


gpx

Recommended Posts

Hey guys so I know that WHMCS 7.3 now has a cpanel backup option which is great but I was wondering if using that is any different from using the automatic WHM backup option? My main concern is my whmcs database which is pretty big about 1.5 GB now and I want to make sure that both ways will backup the database. Cause if WHM backups work up the same way and protect my database than I would prefer using that because then it integrates easier with Google Drive. 

 

And one thing that confuses me in WHM in the backup configuration it asks:

Backup SQL Databases
At least “Per Account” is needed to use the restore feature.
 Per Account Only
 Entire MySQL Directory
 Per Account and Entire MySQL Directory

 
Which option should I select, should it be per account only or Per Account and Entire MySQL Directory? Can someone just please assure me that this option will cover my WHMCS database and if I ever have any issues can restore it from this WHM backup without issue? 
Link to comment
Share on other sites

I recommend Jetbackup or even setting up rsync and linking it to Onedrive or an S3 bucket. I've had success with the integrated WHM backup and using an S3 bucket. You can even set it up to receive daily email alerts / logs of when it's complete. WHMCS admin area has a backup option too. Did you goto the admin area and set that up?

https://docs.whmcs.com/Backups

p.s. - just backup EVERYTHING and make sure it's automatically being done everyday and you keep UPTO a weeks worth of backups at a time.

Link to comment
Share on other sites

Hey guys, thanks for the advice! But I'm confused so right now I got WHM set to backup every day to my Google Drive, and set to keep 5 backups at a time

it seems to be working good, so what would be the benefit of using Jetbackup? I mean I wouldnt mind also using it but it seems to not work with Google Drive which is a bummer

But yeah would WHM backups be good enough I have it set to backup:

 Per Account and Entire MySQL Directory

 
Link to comment
Share on other sites

On 3/10/2018 at 12:36 AM, gpx said:

It seems to be working good

If it 'seems to be working good', then great, however, a few things:

1: Never trust backups at a place you do not control.This includes AWS, Google, anywhere. You need to be in control of your backups, and what they can do.
2: You need more than 5 day's backups, as a 'just in case' scenario
3: Redundancy is key. You need more than one place for backups
4: You need more than one daily MySQL backup
 

As 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. a bad backup plan (which, relying on AWS, Google, etc, not preparing for disaster) is going to be the end of you. I've seen it happen more than once

How is Jetbackup any different from cPanel backups? It's miles away. Jetbackup, for as little as it costs, is just insanely better off than cPanel's backup.


To start with, this resolves #4 in my list above. MySQL is the most fluid thing on any server, production or not. It's going to change , and it's going to change often. Would you like your host to say

Quote

Oh, I'm sorry, we lost the past 24 hours of your MySQL data because we only backup once a day

Or would you rather they said

Quote

Hey, we have multiple backups for XXX day, and we backup every 6 hours. While we understand this is not as frequent as you'd like, this is a pretty decent rotation

Pretty sure  you (and others) would go for the second, as opposed to the first

Multiple jobs, and destinations can exist for Jetbackup, taking care of #3 on that list. Currently? I have 3 spots. One doing just MySQL, one doing snapshots, and one doing account backups (compressed). All in all? I spend about $20/month, including cheap backup servers and JB licensing, for peace of mind. Backup destinations are pretty cheap.

Jetbackup, when using incremental (snapshots) can utilize hard links, which means that you're conserving space pretty well. 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). This means I can reverse the account (or files) to the state they were 45 days ago, with ease. If I wanted to push it, I could go longer, but 45 days works beautifully for me.

Unlike cPanel's backup system, I don't have to restore the whole account just to get a file, or mysql database. Nor do I have to uncompress a big old tarball, or navigate a specific directory. Nope, I simply login as the cPanel user and restore the file, db, or whatever. Pretty slick.

I can set Jetbackup up so that it restores accounts off of a backup server . Say I had a massive catastrophe and had to wipe the server. All I have to do is login to WHM, navigate to JB, and select the accounts and what backup to use. Step away for a few hours (duh) and it will be done. cPanel doesn't have such a facility

Like i said, for the nominal price that JB charges, there's really no reason not to have it

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated