*I run a nightly dump as root: mysqldump --opt rt3 -u root -p > rt3.sql (assuming the root user can perform that dump)
Then scp the file to another system. Since the rest of the system doesn't change much, I don't bother with much of anything else. I have a snapshot of the whole system (my RTs are VMs under VirtualBox, so they're easy to backup (single file)).* * * This is exactly what I do. Is this a decent way to be doing it -- I've always just assumed it was okay. I do it hourly, and then SCP it to another system. Should I be stopping mysql or anything before doing the mysqldump? -- Max McGrath Asst. Network Admin/Systems Specialist Carthage College 262-552-5512 mmcgr...@carthage.edu On Tue, Jan 4, 2011 at 4:56 PM, Joseph Spenner <joseph85...@yahoo.com>wrote: > --- On Tue, 1/4/11, Andy Graybeal <andy.grayb...@casanueva.com> wrote: > > > > Greetings, > > I need a recommendation for backing up RT. > > > > I am planning on using a cron job to run mysqldump to dump > > the db, then rsync the db and /etc/ conf files to a host > > that runs a backup job every night to tape. > > > > What do you guys do? > > > > I run a nightly dump as root: > > mysqldump --opt rt3 -u root -p > rt3.sql > (assuming the root user can perform that dump) > > Then scp the file to another system. > > Since the rest of the system doesn't change much, I don't bother with much > of anything else. I have a snapshot of the whole system (my RTs are VMs > under VirtualBox, so they're easy to backup (single file)). > > > > > >
