Roundup Tracker

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2009-02-19 20:41:07 →
Size: 1216
Editor: localhost
Comment: Fix formatting
← Revision 3 as of 2009-02-20 00:17:38 → ⇥
Size: 1219
Editor: localhost
Comment: Add a line-continuation char to help with copy-n-pasting :)
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
ftp-upload -h $HOST -u $USER --password $PASS -b --as `date -I`_rb.tar.gz /tmp/$BACKUP_FILENAME.tar.gz ftp-upload -h $HOST -u $USER --password $PASS -b --as \
`date -I`_rb.tar.gz /tmp/$BACKUP_FILENAME.tar.gz

This is a simple script that runs on my server from the following cron entry:

  • 5 5 * * * /root/roundup_backup.sh

The script:: 

#!bin/sh
# simple script to backup roundup database
# this script uses "ftp-upload" Debian package
# Alex Chekholko 2004-07-18
#set these variables appropriately
TRACKER_HOME=put your tracker home here
BACKUP_FILENAME=tracker_backup
HOST=hostname
USER=username
PASS=password
# make the "exported" directory in TRACKER_HOME and uncomment this line
# if your backend is PostgreSQL or MySQL
#roundup-admin -i $TRACKER_HOME export $TRACKER_HOME/exported/
cd $TRACKER_HOME
tar cf /tmp/$BACKUP_FILENAME.tar *
gzip -f --best /tmp/$BACKUP_FILENAME.tar
ftp-upload -h $HOST -u $USER --password $PASS -b --as \
`date -I`_rb.tar.gz /tmp/$BACKUP_FILENAME.tar.gz

Cons: insecure data transmission method; no error-checking; no logging. In case you're wondering about backup file sizes, my PostgreSQL based tracker with ~800 issues, ~1100 messages, ~5 files takes up ~500KB.

From unknown Wed Jul 28 04:42:02 -0400 2004 From: Date: Wed, 28 Jul 2004 04:42:02 -0400 Subject: Message-ID: <20040727144202-0400@www.mechanicalcat.net>

RoundupRestore