X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EA36452AC7 for ; Sat, 30 Jul 2005 17:44:11 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 43880-02 for ; Sat, 30 Jul 2005 20:44:05 +0000 (GMT) Received: from mail.travelamericas.com (unknown [206.130.134.147]) by svr1.postgresql.org (Postfix) with SMTP id 8E43C5292D for ; Sat, 30 Jul 2005 17:44:00 -0300 (ADT) Received: (qmail 3390 invoked from network); 30 Jul 2005 20:44:01 -0000 Received: from unknown (HELO ?10.0.0.253?) (10.0.0.253) by verkiel.travelamericas.com with SMTP; 30 Jul 2005 20:44:01 -0000 Message-ID: <42EBE690.2040100@metatrontech.com> Date: Sat, 30 Jul 2005 13:44:00 -0700 From: Chris Travers User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: N/A Cc: pgsql-admin@postgresql.org Subject: Re: Question on placing database on a network attached storage References: <01a201c59541$59648560$6401a8c0@irene> In-Reply-To: <01a201c59541$59648560$6401a8c0@irene> Content-Type: multipart/mixed; boundary="------------090100090707010005050201" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.062 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200508/50 X-Sequence-Number: 18369 This is a multi-part message in MIME format. --------------090100090707010005050201 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit N/A wrote: > Hi, > > I'm putting together a mission critical application which will use a > Postgresql database, and I am trying to decide if I should place my > Postgresql database on a network attached storage appliance or on > local disks. Wherever possible, I think that local storage is almost always best as it is a less complex system (hence less can go wrong). However, you will probably get better answers if you tell us what sort of NAS you are looking at using, how it will connect to your system, etc. > > If I place the database on the NAS, it will get "backed up" by the NAS > device's "snap" type of images. That means the NAS will make a copy > of the delta, or difference, between the current version of the files > on it, and the version from the last time the "snap" was done. The > "snap" images will be dumped to tape at some interval of time. > How internally consistant is this snap? I.e. if the file is changed while the snap is being taken, what happens? This behavior may be product-dependnant and has serious ramifications for your data. > I'm concerned about using a "snap" of an open and active database to > restore the database if the need arises. Now, postgresql is pretty > good about keeping checkpoints and recovering, but I'm still concerned > about data integrity, (who knows what state any internal pointers are > in when the "snap is taken), and as my application will need to > archive groups of files that have to be kept together in order for the > data in those files to be meaningful, (a group of files could be in > the process of being archived to the database, the NAS takes a "snap" > when only some of the files have been written in the database, and > then the rest of the files are written in the database). There is > also the question of speed, Network attached storage vs. local disks, > (network speed is pretty good 100 Meg and will be going to 1 Gig in > the future). Personally I think that there are better approaches than NAS for this, but again I am unwilling to say "never use it." > > I suppose I could place the database on the NAS, shutdown the database > when a backup of the database is desired, have Postgresql create the > database re-creation script, let the NAS take it's "snap", and then > bring the database back up. > > Any suggestions, experiences, or observations? Best Wishes, Chris Travers Metatron Technology Consulting --------------090100090707010005050201 Content-Type: text/x-vcard; charset=utf-8; name="chris.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="chris.vcf" begin:vcard fn:Chris Travers n:Travers;Chris email;internet:chris@metatrontech.com x-mozilla-html:FALSE version:2.1 end:vcard --------------090100090707010005050201--