Question

Is there a recommended procedure for backing up a MySQL FogBugz database?

Answer 1

mysqldump is a decent way to backup your FogBugz (or any other) MySQL database:

mysqldump --opt --user=user --password=password fogbugz | gzip --best > /BackupPath/fogbugz.sql.gz

The gzip bit at the end is optional but it keeps your backup file smaller.

You can also checkout How do I back up my FogBugz installation?

Answer 2

There's some tables you can skip:

IndexFile IndexFilePage IndexDelta

When you first load that backup with FogBugz, hit the default.asp?pg=pgForceDatabaseCheck to recreate those tables.

You can add

--ignore-table=fogbugz.IndexDelta --ignore-table=fogbugz.IndexFile --ignore-table=fogbugz.IndexFilePage

to your mysqldump to make your backups smaller.

Answer 3

We back up in such a way so that each table is backed up to its own SQL dump. This presents a problem, though, when attempting to restore the Attachment and BugEvent Tables. When loading these we receive Out of Memory errors (on a box with 32GB RAM).

Would backing up the whole database into 1 file be a better way of doing this?

Caio

Answer 4

Hi,

our fogbugz database has 20GB. Using mysqldump was to slow and needs quite some extra space. So what we do is the following: First do a regular systme backup using rsync, excluding the mysql database. Then a second run, only the mysql database. We need to shut down mysql for that, which means that fogbugz is unavailible for ca. 20minutes in the night. From what I've learned, the only way to prevent that and get a decent backup speeed is to setup a slave server that you can stop, backup and resync. Should in theroy be possible either on the same host, the backup host or on a third one. However right now I don't considre the additional configuration and administrtion effor worth. The Collegues sleep at night, and emails are stored in the mailboxes for that time ;)

regards Alex