From: Sven Geisler <sgeisler@aeccom.com>
To: Peter Koczan <pjkoczan@gmail.com>
Cc: Greg Stark <stark@enterprisedb.com>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Anyone using a SAN?
Date: Wed, 20 Feb 2008 09:57:21 +0100
Message-ID: <47BBEB71.5020408@aeccom.com> (raw)
In-Reply-To: <4544e0330802181344q2d98560du6bd4e481a9c9439f@mail.gmail.com>
References: <4544e0330802130856t10582294lfa93bc91e234ed01@mail.gmail.com>
<20080213210655.GL9596@mail.nordicbet.com>
<47B41414.9030004@enterprisedb.com>
<4544e0330802181344q2d98560du6bd4e481a9c9439f@mail.gmail.com>
Hi Peter,
Peter Koczan schrieb:
>
>
> 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?
>
>
There are "hidden costs". The set up of a local disk system is easy. You
need only a few decisions.
This is totally different when it comes to SAN.
At the end of the day you need a guy who has the knowledge to design and
configure such system.
That's why you should buy a SAN and the knowledge from a brand or a
specialist company.
BTW: You can do other things with SAN you can't do with local disks.
- mirroring to another location (room)
- mounting snapshots on another server
Sven.
--
Sven Geisler <sgeisler@aeccom.com> Tel +49.30.921017.81 Fax .50
Senior Developer, think project! Solutions GmbH & Co. KG, Germany
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sgeisler@aeccom.com, pjkoczan@gmail.com, stark@enterprisedb.com, tobias@nordicbet.com
Subject: Re: Anyone using a SAN?
In-Reply-To: <47BBEB71.5020408@aeccom.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox