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 5C15052A1E for ; Sat, 30 Jul 2005 17:00:51 -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 34559-07 for ; Sat, 30 Jul 2005 20:00:47 +0000 (GMT) Received: from mxsf28.cluster1.charter.net (mxsf28.cluster1.charter.net [209.225.28.228]) by svr1.postgresql.org (Postfix) with ESMTP id E79A5529BD for ; Sat, 30 Jul 2005 17:00:45 -0300 (ADT) Received: from mxip03a.cluster1.charter.net (mxip03a.cluster1.charter.net [209.225.28.133]) by mxsf28.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id j6UK0jWm024748 for ; Sat, 30 Jul 2005 16:00:46 -0400 Received: from 68-186-58-148.dhcp.mghl.ca.charter.com (HELO irene) ([68.186.58.148]) by mxip03a.cluster1.charter.net with SMTP; 30 Jul 2005 16:00:46 -0400 X-IronPort-AV: i="3.95,155,1120449600"; d="scan'208,217"; a="1199758829:sNHT184467592" Message-ID: <01a201c59541$59648560$6401a8c0@irene> From: "N/A" To: Subject: Question on placing database on a network attached storage device Date: Sat, 30 Jul 2005 13:00:32 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_019F_01C59506.AB745F00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.433 tagged_above=0 required=5 tests=DNS_FROM_RFC_POST, HTML_30_40, HTML_MESSAGE X-Spam-Level: * X-Archive-Number: 200507/258 X-Sequence-Number: 18314 This is a multi-part message in MIME format. ------=_NextPart_000_019F_01C59506.AB745F00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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. =20 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. 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). 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? ------=_NextPart_000_019F_01C59506.AB745F00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I'm putting together a mission critical = application=20 which will use a Postgresql database, and I am trying to decide if = I should=20 place my Postgresql database on a network attached storage appliance or = on local=20 disks. 
 
If I place the database on the NAS, it = will get=20 "backed up" by the NAS device's "snap" type of images.  That means = the NAS=20 will make a copy of the delta, or difference, between the current = version of the=20 files on it, and the version from the last time the "snap" was = done.  The=20 "snap" images will be dumped to tape at some interval of = time.
 
I'm concerned about using a "snap" of = an open and=20 active database to restore the database if the need arises.  Now,=20 postgresql is pretty good about keeping checkpoints and recovering, but = I'm=20 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=20 archive groups of files that have to be kept together in order for the = data in=20 those files to be meaningful, (a group of files could be in the process = of being=20 archived to the database, the NAS takes a "snap" when only some of the = files=20 have been written in the database, and then the rest of the files are = written in=20 the database).  There is also the question of speed, Network = attached=20 storage vs. local disks, (network speed is pretty good 100 Meg and will = be going=20 to 1 Gig in the future).
 
I suppose I could place the database on = the NAS,=20 shutdown the database when a backup of the database is desired, have=20 Postgresql create the database re-creation script, let the NAS take = it's=20 "snap", and then bring the database back up.
 
Any suggestions, experiences, or=20 observations?
------=_NextPart_000_019F_01C59506.AB745F00--