Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 1AB022E0033 for ; Mon, 18 Feb 2008 17:44:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 02627-06 for ; Mon, 18 Feb 2008 17:44:41 -0400 (AST) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by postgresql.org (Postfix) with ESMTP id D23D22E003C for ; Mon, 18 Feb 2008 17:44:41 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so3766662waf.5 for ; Mon, 18 Feb 2008 13:44:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=yLJ8G04z+Yad+cTowOCiPxX47WHfzdFHQKroOCnoR3E=; b=W3fMKB6MhtFJ+4HPOWIhj+FVL+nutZiIQaBsho8xe8+Jv9/DN+qbmy7E+MMjn5o8OIGfSREHSJeFvn5XUz0l2URQZxF1Yr8IW5Gghzd7PLd3IvubZS/f3DXKSUAxhhQSqaQJI2BbNDCqJde1ELwltCJwW5o9BpiwmcfFDWOeT6s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=a2S0mUjz+kk9LKj6QC4I4rXgnbzXHjUlGvaYWEv2Ayq7MXsnYRH1nDnBl3FfjQGJf5FD4x0N+EljnssLT5qDq9zvl4LHrOUU/ICdwg0AuPZKQ5qqvYR22HRdDY6yXo+Hn38fjqIVyNuZK9dFAGS/ikZP8EvNB0l+Qj4yQUAX8fo= Received: by 10.114.148.1 with SMTP id v1mr1812111wad.21.1203371080576; Mon, 18 Feb 2008 13:44:40 -0800 (PST) Received: by 10.114.199.20 with HTTP; Mon, 18 Feb 2008 13:44:40 -0800 (PST) Message-ID: <4544e0330802181344q2d98560du6bd4e481a9c9439f@mail.gmail.com> Date: Mon, 18 Feb 2008 15:44:40 -0600 From: "Peter Koczan" To: "Greg Stark" Subject: Re: Anyone using a SAN? Cc: "Tobias Brox" , pgsql-performance In-Reply-To: <47B41414.9030004@enterprisedb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4544e0330802130856t10582294lfa93bc91e234ed01@mail.gmail.com> <20080213210655.GL9596@mail.nordicbet.com> <47B41414.9030004@enterprisedb.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/208 X-Sequence-Number: 28750 > That's true about SANs in general. You don't buy a SAN because it'll > cost less than just buying the disks and a controller. You buy a SAN > because it'll let you make managing it easier. The break-even point has > more to do with how many servers you're able to put on the SAN and how > often you need to do tricky backup and upgrade procedures than it > doeswith the hardware. One big reason we're really looking into a SAN option is that we have a lot of unused disk space. A typical disk usage scheme for us is 6 GB for a clean Linux install, and 20 GB for a Windows install. Our disks are typically 80GB, and even after decent amounts of usage we're not even approaching half that. We install a lot of software in AFS, our networked file system, and users' home directories and project directories are in AFS as well. Local disk space is relegated to the OS and vendor software, servers that need it, and seldom-used scratch space. There might very well be a break-even point for us in terms of cost. One of the other things I was interested in was the "hidden costs" of a SAN. For instance, we'd probably have to invest in more UPS capacity to protect our data. Are there any other similar points that people don't initially consider regarding a SAN? Again, thanks for all your help. Peter