Is it easy / possible to store separate backups for SQL?
We use the standard CPanel Backup mechanism which stores backups as .tar.gz files on the server and then a separate script takes them off the server and places them on a remote repository.
Would it be possible, and if so how, to set the backup for each account to make two files: 1 file for the full account and another file for JUST the SQL backup of that account? The thing is we have accounts with collossal email data but also with SQL data and so we need to download gigs of backups from an account to open an SQL file that's only a 500kb . If we could get the backup mechanism to make a second MySQL/MariaDB backup at the same time and sstore that alongside the full backup that would be great.
How could we go about making this if it doesn't already exist?
Cheers
-
In the backup manager in WHM there is an option to also back up MySQL databases individually, but these backups are stored in a separate folder than the account backups. 0 -
In the backup manager in WHM there is an option to also back up MySQL databases individually, but these backups are stored in a separate folder than the account backups.
Thanks. This looks like what we need, however it comes with an important qualifier: [QUOTE] Warning: Exercise extreme caution if you select this setting. This setting backs up the data directory without stopping MySQL". This action may cause InnoDB issues with the data directory backup.
Do you know what sort of "Issues" this can cause? Almost all of our DBs are InnoDB. We often run Cron jobs which use the DB late at night, are you aware of any ways we can test and/or mitigate any potential fallover here? Bare in mind these things will be operating at 12-6am so not a time with anyone to hand to fix things! Thanks.0 -
Under Databases, the option is: Per Account Only Use the "mysqldump" command to create backup files with the ".sql" file extension for each account.
0 -
Under Databases, the option is:
Per Account Only Use the "mysqldump" command to create backup files with the ".sql" file extension for each account.
This choice is the one already set, and it does save the SQL, but it zips it up with the rest of the account information which adds magnitude of bloat when needing simply to extract the SQL.0
Please sign in to leave a comment.
Comments
4 comments