rsync + mysql backup

gwaitsi · 26. Mai 2015

I have OpenKM 6.3 working on OpenMediaVault NAS server with MySQL as the db engine.

The mysqldata directory has ibdata1 file of 622Mb and I use the following Backup commands for MySQL

Code

# Perform the database dump and compression
echo "Dumping MySQL databases..." >> "$LOGFILE"
mysqldump --user=$user --password=$password --single-transaction --events --all-databases > $backup_path/$dbname-$date.sql


echo "Compressing database backup..." >> "$LOGFILE"
bzip2 $backup_path/$dbname-$date.sql
chmod 600 $backup_path/$dbname-$date.sql.bz2

the file size after the above commands is only 60Mb, can this be right? what is the 600Mb ibdata1 file?

Code

# Synchronise directories ...
echo "Please wait, syncing 
</media/a7e96974-7965-4103-9743-281802f3d956//openkm> to 
</media/854fe912-9f08-423d-9bc8-26a404cae6d0/openkm> ...\n"
rsync
 --verbose --log-file="/var/log/rsync.log" --recursive --times --archive
 --delete --perms --acls --xattrs 
"/media/a7e96974-7965-4103-9743-281802f3d956//openkm/" 
"/media/854fe912-9f08-423d-9bc8-26a404cae6d0/openkm" & wait $!

Are the two things above sufficient to ensure a fullbackup on a daily basis?
The developer has suggested the rsync cannot be restored after 2 or 3 days and that i should use rdiff-backup.

any thoughts?

ryecoaaron · 26. Mai 2015

Database dumps are just a lot of text which normally compresses very well. So, that looks fine. The ibdata1 file is a working database file - saved queries and other info to speed it up. No need to save it.

gwaitsi · 26. Mai 2015

thanks for the clarification ryecoaaron.

What about the rsync command vs the rdiff-backup he recommends?
Will my rsync command ensure i have always the full data backed up?

cheers

ryecoaaron · 26. Mai 2015

Sounds like rsync is backing up openkm. Combine that with the database dump and you should be good to go. Not sure why he recommends rdiff-backup since I have never used openkm before.

Jetzt mitmachen!