WHM/Cpanel Backup not compressing mysql dirs (possible bug?)

[vissa]

I noticed today that the cpanel / whm backup is not compressing the mysql directories even when you select compression (ie even when you do NOT have incremental turned on). If you look in your /backup/cpbackup/daily/dirs/_var_lib_mysql_/ directories, you will see individual mysql databases/tables that are not compressed.

My question is, why is this so? It's causing a large increase in the backup size for my server.

-V

[chirpy]

Just checked on 2 servers and I have no subdirs within daily/dirs/ I would guess that you have an incomplete backup as what you should have is a file called /backup/cpbackup/daily/dirs/_var_lib_mysql_.tar.gz

[vissa]

Just checked on 2 servers and I have no subdirs within daily/dirs/ I would guess that you have an incomplete backup as what you should have is a file called /backup/cpbackup/daily/dirs/_var_lib_mysql_.tar.gz

What do you have set for the following option?

Sql Databases (at least per accounts is needed to use the restore feature)
Per Accounts Only; Per Accounts and Entire Mysql Dir; Mysql Dir Only

I have mine set to "Per Accounts and Entire Mysql Dir;"
I don't think it's incomplete. I have the file you mentioned plus the subfolders.


-V

[vissa]

By the way, I notice that the .gz file you mentioned (which I also have) is one huge file when uncompressed. If someone was to restore an individual user's mysql database, would there be any possible way to use that file or is that only for a complete restore?

-V

[chirpy]

I have "Per Accounts and Entire Mysql Dir;" enabled too. I understood this to create the per user .sql files witin the users account.tar.gz and the big one to simply be everything. Maybe mine is the on not working

I'm not much a whizz with MySQL, so cannot answer the last question.

[vissa]

Can someone officially answer how this is supposed to look in our backup folder?

Thanks
-V

I have "Per Accounts and Entire Mysql Dir;" enabled too. I understood this to create the per user .sql files witin the users account.tar.gz and the big one to simply be everything. Maybe mine is the on not working

I'm not much a whizz with MySQL, so cannot answer the last question.

[cpdan]

Can someone officially answer how this is supposed to look in our backup folder?

Thanks
-V

Its not a bug (referring to th "possible bug" in the subject)

"Per Accounts and Entire Mysql Dir" means each user.tar.gz has their sql ("Per user") and then /backup/cpbackup/daily/dirs/_var_lib_mysql_.tar.gz is the "Entire Mysql Dir" which you would not really need/want to restore an individual account or two.

[vissa]

So then my server must have a problem since it isn't compressing the individual accounts, correct?

Thanks
-V

[cpdan]

no you're misunderstanding

details in the ticket

[vissa]

Cpanel support helped solve the problem (appreciated!). Although maybe you weren't misunderstanding, my problem wasn't being addressed (uncompressed sql backups).

After sending Cpanel Support some directory listings, it turns out there were old uncompressed backed up folders mixed in with the newer compressed backups. I don't think Cpanel automatically deletes old uncompressed backups when you switch to compressed mode. So if a user switches modes, they should know that they manually have to delete the old backup files first. That explains the problem I was having.

Thanks!
-V

no you're misunderstanding

details in the ticket

[cpdan]

Cpanel support helped solve the problem (appreciated!).

No problem

Although maybe you weren't misunderstanding, my problem wasn't being addressed (uncompressed sql backups).

i understood perfectly, you did not get it until I spelled out what I'd been saying step by step:

From Ticket:

> I'm not sure you understand my problem. Is it normal for there to be 3 backups

Yes I do understand

What you are not comprehending is this:

With "Per Accounts and Entire Mysql Dir":

"Per Accounts" = the .sql files inside each `ls -al /backup/cpbackup/daily |grep tar.gz`

"Entire Mysql Dir" = /backup/cpbackup/daily/dirs/_var_lib_mysql_.tar.gz

IE two compeltely seperate backups for the same data basically.

The problem is this:

> drwxr-x--x 45 root root 4096 Feb 4 22:21 _var_lib_mysql_/
> -rw------- 1 root root 350026637 May 17 02:25 _var_lib_mysql_.tar.gz

The directory shouldn't be there.

You'll notice the directory is 3 and a half months old, so its a left over from another time. Feel free to delete it and I imagine it will never show up again.

If it does show up again then backup is unable to remove it for some reason (is it immutable? Is rm broken or not recognize its flags? etc etc)

So if a user switches modes, they should know that they manually have to delete the old backup files first.

No they don't, if that was the case you'd have one directory for each compressed version. Probably it was left over or restored somehow. (the process deleting them was interupted for example)