[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kroupware
Subject:    Backup of 3.0 Installation
From:       Johannes Graumann <johannes_graumann () web ! de>
Date:       2013-12-10 5:18:03
Message-ID: l86854$a24$1 () ger ! gmane ! org
[Download RAW message or body]

Hello,

Before going live with my 3.0 installation I wanted to check whether someone 
here has comments on the backup strategy I'm using.

I follow http://docs.kolab.org/administrator-guide/backup-and-restore.html 
and here's what's being backed up:

1) /etc

2) The output of
	yum list installed
3) 389 like so:
for dir in `find /etc/dirsrv/ -mindepth 1 -maxdepth 1 -type d -name 'slapd-
*' | xargs -n 1 basename`; do
  for nsdb in `find /var/lib/dirsrv/${dir}/db/ -mindepth 1 -maxdepth 1 -type 
d | xargs -n 1 basename`; do
    ns-slapd db2ldif -D /etc/dirsrv/${dir} -n ${nsdb} -a /tmp/$(echo ${dir} 
| sed -e 's/slapd-//g')-${nsdb}.ldif >/dev/null 2>&1
  done
done

4) mysql like so (backing up the backup directory of automysqlbackup)
	automysqlbackup >/dev/null 2>&1

5) Cyrus:
	/var/spool/imap/
	rm -f <LOCATION>/var/spool/imap/cyrus.squat
	rm -f <LOCATION>/var/spool/imap/cyrus.cache.NEW
	rm -f <LOCATION>/var/spool/imap/cyrus.expunge.NEW
	rm -f <LOCATION>/var/spool/imap/cyrus.index.NEW

Does that look right? What else might I consider. CentOS is not my weapon of 
choice, so any input regarding what to save to be able to quickly recover is 
highly appreciated ...

Sincerely, Joh

_______________________________________________
users mailing list
users@lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
[prev in list] [next in list] [prev in thread] [next in thread]