Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id B24786331EB for ; Tue, 9 Mar 2010 16:35:20 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 80639-06 for ; Tue, 9 Mar 2010 20:35:06 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ww0-f46.google.com (mail-ww0-f46.google.com [74.125.82.46]) by mail.postgresql.org (Postfix) with ESMTP id C7915632B4B for ; Tue, 9 Mar 2010 16:35:09 -0400 (AST) Received: by wwb39 with SMTP id 39so548865wwb.19 for ; Tue, 09 Mar 2010 12:35:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=cE4pDbQC7dLQeYQPGe8OMCy3Tpg+Sz7lS4L8fzTE1Y4=; b=i+pBGKyWxg/UmUR8kwwmsjDpsUl4FDdeTqRyc8A2xVwhIEDtrCV+NU9VMwi+NiGgJE WiePPd8O2iTIMPyIODRvnZFioezltrSiuHYvp7TeV0EbI+7Cbe+xE6wLUTU+qV8T5VGR m1ILw0SxnAOL7Zvwe3dvPiSntz9ttbMtRCS+o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=I+kx/F+ahx+FR37SOHnfxtNJ+ELlm3TMYsiJG74ZoqcowMLvTeT76Xnv7C+PZfeKVy 6ulXZWyGDiE7FTGOvysY9qqKA+56iJKn1wFnpQInD46lOJqhKY73zG9ZOwF8H5O2YQCB lXrySBBKXfmFVwOgnlWR7anTfBGOXpCakgshw= MIME-Version: 1.0 Received: by 10.216.89.202 with SMTP id c52mr248292wef.84.1268166908328; Tue, 09 Mar 2010 12:35:08 -0800 (PST) In-Reply-To: <4B96AD1B.7070601@alreg.no> References: <4B95E162.7060806@djs-consulting.com> <3769.1268115316@sss.pgh.pa.us> <4B96AD1B.7070601@alreg.no> Date: Tue, 9 Mar 2010 13:35:08 -0700 Message-ID: Subject: Re: linux standard layout From: Scott Marlowe To: Jan-Ivar Mellingen Cc: Tom Lane , pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.34 tagged_above=-10 required=5 tests=AWL=0.259, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/67 X-Sequence-Number: 33866 On Tue, Mar 9, 2010 at 1:18 PM, Jan-Ivar Mellingen wrote: > Regarding 'pulling the plug' on the servers: Physical or virtual, always use > a UPS. You can pull the plug as much as you like. When the power is about to > run out it signals the server, which shuts down cleanly. > Our servers have dual powersupplies, connected to separate UPS'es on > separate power sources... I've watched three redundant UPSes, three redundant power conditioners, and the switch for the diesel generator all fry when the perfect storm of events happened in a job 7 or 8 years ago. Every single machine in the hosting center lost power. Of the hundred or so database servers, mine was the only one that came up. The others all had to rely on off site backups to get up and running. Not one other DBA at that company had performed a power failure test. > In a nutshell, I am heartly recommending virtualization. In a nutshell, you are relying on luck that both heavy iron machines can't lose power at the same time. Sure, it's a low possibility, but it's still a real one. > And - I do not want to start a discussion about it. Just sharing my opinion. Well, you can't throw the post you threw out there and not expect it to start a discussion really. I understand a lot of the reasoning for virtualization. My DB servers run at 75 to 100% capacity during midday, there'd be no real advantage to buying an eve bigger piece of iron to run them on. I see the advantages of virtualization for certain load types, and allowing to easily move services as a single disk image instead of installing the service and configuring it on a new machine. Where I work all the servers (except the nagios box) work hard and there'd be no real advantage to me in putting all my eggs in the virtualization basket there. I do use KVM to run multiple servers on my laptop for testing. It's great for that. But hope is not a method I use when installing my servers.