MySQL backups too big

Guillermo

Verified User
Joined
May 20, 2006
Messages
95
Location
The Netherlands
When directadmin makes a backup of my mysql databases, it makes a full mysql backup called full-mysql.tar.gz, and also makes a seperate mysql backup of each database. So in fact, it's being backupped twice, and taking a lot of extra diskspace.
I don't want the backup to create the full-mysql.tar.gz file. How do i fix that?
 
Is there any other way to do it?

I have a better idea. What if the system replaces the second last backup every day, so there will only be two backups on the disk.
This will save diskspace, and i won;t have to delete the old backups manually anymore.

How can i fix that?
 
Why not just uncheck mysql user backups and just backup the directory that mysql uses.
 
chatwizrd said:
Why not just uncheck mysql user backups and just backup the directory that mysql uses.

Yeah i thought about that. But it's better that the cronjob deletes the second last backup, and replaces it with a new one.
 
Guillermo said:
Yeah i thought about that. But it's better that the cronjob deletes the second last backup, and replaces it with a new one.

Well you would need to edit the backup system located in /usr/local/sysbk

Its an old program and needs updating bigtime. I have thought about rewriting it myself but dont really have the time.
 
chatwizrd said:
Well you would need to edit the backup system located in /usr/local/sysbk

Its an old program and needs updating bigtime. I have thought about rewriting it myself but dont really have the time.

I see, isn't it possible to perform such an operation by cron? Otherwise i'll ask my coder to edit the backup system.
 
Yeah but it wouldnt be using sysbk. You can always write your own shell scripts and set them up via cron.
 
Back
Top