Re: [vchkpw] Proper server backup
Thanks a lot John... you're work in qmail is excellent truthly... congratulations mate truthly... [EMAIL PROTECTED] wrote: If I had a server hardware failure... and my hardware breaks... so I need to set up a new one qmail server... what should I have backed up in my actual qmail server and how could I recover all data? see http://qmail.jms1.net/backup.shtml ... explained in full. I suppose I should overwrite /home/vpopmail and /var/qmail fully with my backed up version? no. the web page explains exactly what needs to be backed up and restored. the backup scripts i run on my own server and my clients' servers use this list, and i've actually done several recoveries (from dead hard drives and dead servers) where nothing was lost except new mail which arrived after the most recent backup. but this couldn't cause later problems with courier-imap compiled binaries? because they're compiled with just have installed vpopmail libraries and not with backed ones? when courier-imap (or more specifically, courier-authlib) is compiled, it is STATICALLY linked with libvpopmail.a. this means that the libvpopmail.a file needs to be in place while courier-authlib is being compiled, but it doesn't need to be there (or it doesn't need to be the exact same version) when it's running. one of the design goals of vpopmail 6 is to have a dynamic library. when this happens, and if courier-authlib is changed so it uses the dynamic library, the libvpopmail.so file will need to be in place for courier-authlib's authdaemond process to run. however, minor updates to the libvpopmail.so file (re-compiles, minor upgrades to fix bugs, etc... things which don't change the API) will still allow authdaemond (and other programs which dynamically link against the library) to work correctly. the whole point of dynamic libraries is that the functions in the library are found by name at run-time, rather than having an explicit address or function number be hard-coded into the executable. -- | John M. Simpson--- KG4ZOW ---Programmer At Large | | http://www.jms1.net/ [EMAIL PROTECTED] | | http://video.google.com/videoplay?docid=-1656880303867390173 | !DSPAM:4734293b32001891920651!
[vchkpw] Proper server backup
Hi, If I had a server hardware failure... and my hardware breaks... so I need to set up a new one qmail server... what should I have backed up in my actual qmail server and how could I recover all data? I mean... I suppose I should compile, install and use the same vpopmail and qmail version. I suppose too I should have a backup of the mysql vpopmail database, /var/qmail directory and /home/vpopmail directory too, is enough having only this backed up? and later... I suppose I should overwrite /home/vpopmail and /var/qmail fully with my backed up version? but this couldn't cause later problems with courier-imap compiled binaries? because they're compiled with just have installed vpopmail libraries and not with backed ones? Thanks a lot mates Hope I have explained :)
Re: [vchkpw] Proper server backup
[EMAIL PROTECTED] wrote: Hi, If I had a server hardware failure... and my hardware breaks... so I need to set up a new one qmail server... what should I have backed up in my actual qmail server and how could I recover all data? I mean... I suppose Everything! We include /var/qmail in our nightly general backups , which is a rolling 7 days, its also included in weekly backups which are kept forever. /home/vpopmail is rsync'd daily, on a rolling 7 day basis. The MySQL DB is backed up hourly on a rolling 7 day basis, yes a lot of files, but having only 24 hours is no good if something is not noticed for 3 days :) and doing it every hour in that 7 days means if something is screwed up at 1030pm, we have not lost 10.5 hours of entries, only half an hour. One thing, however, you should make it known to your users that some or all of their email may or may not be included in system backups for disastor recovery etc etc etc, for legal reasons ( depending no your country) you could be in serious trouble for keeping copies of their mails. I should compile, install and use the same vpopmail and qmail version. I We also do full system weekly rsyncs, so we can grab the src and do a quick install, we have tar files of our sources kept in many different places including disks . suppose too I should have a backup of the mysql vpopmail database, you mean you dont /var/qmail directory and /home/vpopmail directory too, is enough having only this backed up? and later... I suppose I should overwrite You should do system nightly backups that encompass critical stuff that can change, like /etc and anything else thats critical to your operation. /home/vpopmail and /var/qmail fully with my backed up version? but this couldn't cause later problems with courier-imap compiled binaries? because they're compiled with just have installed vpopmail libraries and not with backed ones? I have dumped courier, for the faster Dovecot. but tis config is in /etc so its also backed up. Thanks a lot mates Hope I have explained :)
Re: [vchkpw] Proper server backup
[EMAIL PROTECTED] wrote: Hi, If I had a server hardware failure... and my hardware breaks... so I need to set up a new one qmail server... what should I have backed up in my actual qmail server and how could I recover all data? I mean... I suppose I should compile, install and use the same vpopmail and qmail version. I suppose too I should have a backup of the mysql vpopmail database, /var/qmail directory and /home/vpopmail directory too, is enough having only this backed up? and later... I suppose I should overwrite /home/vpopmail and /var/qmail fully with my backed up version? but this couldn't cause later problems with courier-imap compiled binaries? because they're compiled with just have installed vpopmail libraries and not with backed ones? Thanks a lot mates Hope I have explained :) I'm pretty sure (someone will confirm?) that you *can't* backup the qmail queue and restore it elsewhere because it's designed around the inode numbers on the filesystem that you ran it on initially. For this reason, I would say don't backup /var/qmail/queue/* Howie
Re: [vchkpw] Proper server backup
Howard Jones wrote: [EMAIL PROTECTED] wrote: Hi, If I had a server hardware failure... and my hardware breaks... so I need to set up a new one qmail server... what should I have backed up in my actual qmail server and how could I recover all data? I mean... I suppose I should compile, install and use the same vpopmail and qmail version. I suppose too I should have a backup of the mysql vpopmail database, /var/qmail directory and /home/vpopmail directory too, is enough having only this backed up? and later... I suppose I should overwrite /home/vpopmail and /var/qmail fully with my backed up version? but this couldn't cause later problems with courier-imap compiled binaries? because they're compiled with just have installed vpopmail libraries and not with backed ones? Thanks a lot mates Hope I have explained :) I'm pretty sure (someone will confirm?) that you *can't* backup the qmail queue and restore it elsewhere because it's designed around the inode numbers on the filesystem that you ran it on initially. For this reason, I would say don't backup /var/qmail/queue/* Pretty much flush or otherwise empty the qmail queue first, shut qmail services down and then backup. Or just backup /var/qmail/control /var/qmail/users /var/qmail/rc supervisescripts /var/qmail/alias and restore these over a fresh qmail installation.
