| From: | Doug McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
| Cc: | victor moran <diadian(at)yahoo(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Hosting a data file on a SAN |
| Date: | 2003-03-04 00:19:36 |
| Message-ID: | m3isv0ouef.fsf@varsoon.wireboard.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
> On Fri, 28 Feb 2003, victor moran wrote:
> > Can someone here help me find out whether or not I can run postgresql 7.2.3
> > while keeping its data files on a SAN device across a Fibre Channel link?
> That said, storing your data on a SAN/NAS presents some issues.
>
> (If someone else is reading and doesn't know what they mean:
> NAS=Network Attached Storage, SAN = Storage Area Network)
SAN and NAS are not the same. NAS is a fancy name for "dedicated
NFS/SMB server". SAN means SCSI over some kind of switched fabric,
usually Fibre Channel. The main difference is that SAN devices look
like disks to the OS, while NAS looks like one or more network
filesystems.
Running a database on NAS may be an issue; running on a SAN shouldn't
be, as long as the overlying filesystem has the right semantics.
-Doug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Gearon | 2003-03-04 00:33:11 | Re: almost there on a design |
| Previous Message | Stephan Szabo | 2003-03-04 00:18:43 | Re: almost there on a design |