>> As a note; I'd suggest you turning your ASSP box into a VM, this >> way you may just make a copy of the VM, replace the V1 with >> the V2 in the VM, try the V2 and, if you won't like it, just put back >> the copy and start the virtualized V1
> This is a wise suggestion. I must say that I have many 'ducks to get > in a row' in order to accomplish this. The hardware we are running > these email servers on is getting old, and due for an upgrade. Well, turning your running box into a VM shouldn't be an issue, here's some kinda/sorta of a plan; let's say you have your new hardware (or at least a free box with enough RAM) to run the VM host 1 install the VMware converter on the phys box, run the converter (while the box is running, no need to stop it) letting it generate the VM image files onto a networked disk 2 pick the fresh VM image and, using a different host (the phys box will still be running) fire up the VM and ensure it starts, proceed to tune whatever parameter 3 if all ok swap the phys box with the VM and let it do the job; let it run for a while to ensure all's ok - in case of issues you will just be able to swap back the "old iron" in a matter of minutes :) from that point on you'll be running the *same* system inside a VM; now, to test the v2 you'll just need to pick the original VM image, bring it up on the VM host (or on a separate "temp" host) and proceed uninstalling the V1, upgrade the Perl and the modules, install and tune the V2 setting it up as needed; done that, you may just swap the "boxes" or, in case you're on the same iron, switch off the V1 VM and switch on the V2 one ... still being able to rollback and not just with VMs, you will *still* have your original hardware system :) (don't throw it away or "rebuild" it until you won't be sure everything is ok since it will be your "insurance" :D) >> Sure it does; but properly setting up things you should be able to >> run your ASSPv2 on a 2GB RAM system and sustain quite a load >> w/o issues, then YMMV ... as usual > Are there other metrics that you would recommend? My guess > is that we will be able to run both of our mail servers on one piece > of physical hardware in the future. We are looking at a hardware > upgrade around the 4th quarter or the first of the year. Well... it mostly depends from the kind of setup you're planning, see, personally, whenever possible, I prefer having the ASSP running on its own, dedicated machine (be it a VM or not); that "box" will run ASSP (plus the various programs like clamd etc), a DNS cache/resolver (optionally an rbldsnd), and an SMTP MTA used to route email - the mailserver then sits on separate box; this gives you plenty of flexibility and avoids a lot of issues as for the metrics... well ... keep in mind that the hardware on which your VMs will be running needs RAM for itself, so if you plan to run two VMs allocating 2GB each, you'll need to have enough installed RAM to avoid the need for the host to "swap" and btw loose performance; also, ensure to have a common storage for the VMs; a fiber/iSCSI separate storage with good RAID setup will ensure you'll have all your stuff safe and won't have to run like crazy in case a VM will have issues :) also, CPU plays a role, a "modern" quad-core system or even a multi CPU one capable of scaling up to 2 CPU - 8 Cores will probably fit the bill, just... avoid investing in monster systems better having a number of smaller ones and being able to escalating by adding another box than using a few "huge irons" since in the latter case, when you'll reach the limit of expansion you'll still need to buy a new box but at that point you did already spend buckets of money to expand those big critters :) What else... once you'll be running on virtual, hardware upgrade will cease to be an issue, you may just buy new h/w, setup the VM host and move your VM from the old h/w to the new one w/o the need to reinstall/rebuild stuff ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
