Assumptions
- Scalix is the messaging server
- SonoraBackup on-line backup is backing up the Scalix Server
Automate the Backup
First, we configure cron to run the ombackup script nightly:
cat >> /etc/crontab << EOF
# Back up the Scalix messaging system at 10PM on weekdays
#+-----------------------Minute (0-59)
#| +-------------------Hour of Day (0-23)
#| | +---------------Day of Month (1-31)
#| | | +-----------Month of Year (1-12)
#| | | | +-------Day of Week (0=Sun,6=Sat)
#v v v v v
00 22 * * 1-5 root /usr/local/bin/ombackup >/dev/null 2>&1
EOF
Scalix Backup Script
Download and modify the ombackup script as needed. Few changes will be required and probably only at the top of the script in the variables definitions.
Move the script to /usr/local/bin and make it executable:
wget http://www.sonoracomm.com/dmdocuments/ombackup
chmod 755 ombackup
mv ombackup /usr/local/bin
Testing
You can get usage info by using the -h switch like this:
/usr/local/bin/ombackup -h
You can test the script at the command line by just running:
/usr/local/bin/ombackup
Warning, the script will stop the Scalix services. You may want to test after hours.
The script logs to this file:
/var/log/ombackup.log
Notes
- this script is meant to be run from cron
- works perfectly from the command line too
- first it backs up individual user mailboxes
- the Scalix services are still running
- secondly, it backs up the entire Scalix installation suitable for a disaster recovery
- the Scalix services are stopped, then restarted after completion
- optionally, the script will do an off-site copy of everything
- the services stay running
- rotating the backups in the script can use a lot of disk space
- use the rotation feature if you have a lot of free disk space
- but be careful about what gets backed up on-line to avoid extra cost
| < Prev | Next > |
|---|
