Well in fact here is what we backup :
/usr/local/interworx (so all soft and datbase)
/etc/passwd /etc/group /etc/shadow /etc/hosts.allow /etc/hosts.deny /etc/resolv.conf /etc/hosts /etc/proftpd.conf
In fact we do not tar or rsync /home, we create a full backup with iworx backup tool. As in every backup file there is in it a tar file containing the /home files and the database we can extract the tar file of home files from this backup file.
Why we do this :
- In case of siteworx accounts problem we can just restore this account
- In case of /home corruptions we can extract all /home tar files from iworx backup files (we have a script that do this)
- In case of database pbm, we can choose between restore the database files from the :
a) a siteworx backup account
b) all siteworx baclup accounts
c) our backup of /var/lib/mysql
- In case of interworx corruption. We can choose to reinstall or restore the /usr/local/intterworx and to restore the interworx database and the iworx.ini file
- In case of a complete migration : We can use all home the tar files contained in every siteworx account backups, restore mysql users databases, restore interworx database file and iworx.ini file and qmail config and etc conf files
- In case of drive failure : we have hardware raid 1, so…
I think we found the best compromit. The problem we had is to choose between :
-a- do a backup off all siteworx accounts and all others data WITHOUT /home
-b- do a backup off all siteworx accounts and all others data WITH /home
-c- Do not perform a siteworx backup and only perform rsync or whatever of all needs files
The b method should be the best one, but it is really time, cpu, load average usage consumming. Do a full rsync or tar of /home is heavy and perform a full siteworx backup too.
So we thought of only perform a siteworx backup, + all others files without /home. We just have to find a way to extract fron every siteworx account the /home backup file.
This method is not the best one, but one more time do a backup off siteworx accounts and /home is really usage consumming.
The --only-structure option in backup could help, but we think it may be very usefull to also have a full siteworx backup.
Well in fact the best could be, to analyse all the possibilities of failure and found the best compromit for an easy and less time restore. If we do a full list of what might happend and try to find the best solution for every ones we maybe could find the best to way of backup.
All interworx users, staff may help and try to give a “red book” of the best backup of interworx box
The list of what may happen
- Siteworx Accounts failure
- Interworx failure
- Vital directory compromised or vital data lost (which are they)
- drive failure
- server migration
This list in not exhaustive and may be completed
Maybe interworx team might tell us what are they backup and recovery plan at Nexcess.