My 2 cents... Excellent scripts!!! Used them last week to move to a new server. I noticed one thing also that could be usefull though. The day after I moved servers, I got calls about peoples squirrelmail addressbooks. So maybe include /var/lib/squirrelmail/prefs/
Scott > > On Sep 22, 2006, at 8:50 AM, Jake Vickers wrote: > >> Craig Smith wrote: >>> The backup and restore scripts are excellent, I've just spent the >>> past 2 >>> days testing them thoroughly for our systems and they work a >>> charm. The >>> only thing I came across eventually, was the lack of spamassassin >>> backup/restore or the tcp.smtp file for access. Our local.cf for >>> spamassassin contains a fair amount of edited items as well as 2 >>> custom >>> rulesets in the folder. The tcp.smtp contains several entries for >>> various >>> clients that are allowed to relay through us. >>> >> Thanks for the suggestions and code. I need to sit down and revamp >> these scripts anyway. There has also been a request to include >> Squirrelmail configs into the backups. Soon! > > heh, while you're at it... a little while back i was trying to add > rsync-over-ssh support to the backup/restore scripts, but got bogged > down and didn't finish the project. here's my basic idea for how to > do it: > > for backups: > > 1) create the tarball locally. > 2) check to see if the name of the previous tarball has been saved > (it would be in, say, /last-toaster-backup). > 3) ssh to the backup server and check to see if there's a tarball > with the same name as the file named in /last-toaster-backup; if > there is, make a copy of it with the same name as the current tarball. > 4) use rsync-over-ssh to push the differences between the previous > tarball and the current tarball over the network (if you have a slow > connection, or a large toaster installation, you should see > significant savings). > 5) if the rsync succeeds, delete the local copy of the current tarball. > 6) ssh to the backup server and delete the previous tarball (unless > you want to save multiple revisions) > 7) make note of the name of the current tarball in /last-toaster-backup. > > for restores: > > 1) ssh to the backup server and find the name of the most recent > tarball. > 2) use rsync-over-ssh to pull a copy of the most recent tarball over > to the local machine. > 3) do the restore. > 4) make note of the name of the current tarball in /last-toaster-backup. > 5) delete the local copy of the current tarball. > > does this make sense? the trickiest part is keeping a persistent > record of the filenames. > > -steve > > -- > If this were played upon a stage now, I could condemn it as an > improbable fiction. - Fabian, Twelfth Night, III,v > > > > > --------------------------------------------------------------------- > QmailToaster hosted by: VR Hosted <http://www.vr.org> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
