Hello.

I have been reading the wiki articles regarding backup & restore. I've been searching the forums and looked through user published scripts in regards to backups.

All backup strategies inclusive the ones in the wiki basically says; "pack up /opt/zimbra, move it somewhere, in case you need a restore, unpack it". This works. But this is not a smart backup strategy.

What files under /opt/zimbra can I exclude?

Do I need to take backup of binaries which exist within the .deb/.rpm files and will be restored by a clean install before unpacking my config anyhow?

Is there some "minimal" list of files that can be backed up in order to perform a full backup of my contents?

And also, while migrating this installation inbetween versions. Upgrading one to the next. I end up with a file tree looking like:

Code:
root@imix:/opt/zimbra# ls -1
[...]
amavisd
amavisd-new-2.4.3
amavisd-new-2.5.2
amavisd-new-2.6.4
[...]
clamav
clamav-0.90.2
clamav-0.91.2
clamav-0.92
clamav-0.95.3
[...]
cyrus-sasl
cyrus-sasl-2.1.21.ZIMBRA
cyrus-sasl-2.1.22.3
cyrus-sasl-2.1.22.3z
cyrus-sasl-2.1.23.3z
[...]
java
jdk1.5.0_08
jdk1.5.0_15
jdk1.5.0_17
jdk1.6.0_02
jdk1.6.0_04
jdk1.6.0_16
jetty
jetty-6.1.15
jetty-6.1.22.z6
jetty-6.1.5
[...]
postfix
postfix-2.2.9
postfix-2.4.3.3
postfix-2.4.3.3z
postfix-2.4.3.4z
postfix-2.4.7.5z
postfix-2.6.2.2z
postfix-2.6.5.2z
Can these earlier versions be cleaned up? Why doesn't the install script do so? Is there any risk associated?

Mikael