Hi marcmac,
Thanks for the information and the quick reply.
Quote:
Off the top of my head (I've never tried this) you'll also need:
/etc/{password,shadow,group}
/etc/sudoers
/etc/init.d/whatever
/var/spool/cron/zimbra (assuming linux)
|
The RPMs automatically update the first three of these. I have nothing in /var/spool/cron/zimbra; I assume I should have a cron job for updating ClamAV? I'll add that manually with my Kickstart script.
Quote:
|
Make sure that the user has the same ID if you re-create it. If not, running zmfixperms.sh (as root) after the overlay of the backup might be a good idea.
|
The RPMs are creating the user account and since the Kickstart file executes the RPMs right after OS installation, zimbra is always user 500.
Quote:
|
Any particular reason you wouldn't want to do a backup/restore, rather than go through this process?
|
Perhaps I should've explained a little more in my original post. I've created a backup script that runs nightly and produces zimbra.backup.tar.gz on an external USB drive. If the server suffers a catastrophic failure, then all I have to do is repair/replace the hardware and run my Kickstart installation. Kickstart installs the OS, Zimbra, and restores all Zimbra data from zimbra.backup.tar.gz. Currently (with just a few test mailboxes), I can do this in under 30 minutes.