Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 2A81A9FB2C9 for ; Thu, 20 Sep 2007 15:16:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 46892-02-6 for ; Thu, 20 Sep 2007 15:16:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id F06C69FB1BC for ; Thu, 20 Sep 2007 15:16:06 -0300 (ADT) Received: from [192.168.1.9] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l8KIG5Qa013143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Sep 2007 11:16:05 -0700 Message-ID: <46F2B8E6.4010108@commandprompt.com> Date: Thu, 20 Sep 2007 11:16:06 -0700 From: "Joshua D. Drake" User-Agent: Thunderbird 2.0.0.6 (X11/20070830) MIME-Version: 1.0 To: Chris Hoover CC: Andrzej Zawadzki , pgsql-admin@postgresql.org Subject: Re: Moving database install to new SAN References: <507905.14268.qm@web57114.mail.re3.yahoo.com> <20070913203946.GE6423@easy2.in-chemnitz.de> <46E9A81D.90309@gmail.com> <1d219a6f0709201110r603e1d4dg8cc4f514201a65ab@mail.gmail.com> In-Reply-To: <1d219a6f0709201110r603e1d4dg8cc4f514201a65ab@mail.gmail.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.1/4349/Wed Sep 19 15:46:46 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Thu, 20 Sep 2007 11:16:05 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/129 X-Sequence-Number: 26890 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Hoover wrote: >>> 2. copy whole data directory over to new SAN >> If database is big, then I think that is much faster to copy running >> database >> to new SAN. >> Then stop postgres and rsync what was changed - but this will be probably >> only a few files. > > > > I believe if you do this, you will not get a function database in the end. > There is a lot of data that is held in memory/buffers that may not be > flushed to the disks. You have no guarantee you will get this data with > this method. The method would work if they are willing to have an outage. Basically you do an initial rsync of the large db... Then you shut down the db. And rsync again, which will be faster than doing a complete move with shutdown. The key here is, if you use this method... there is *zero* way around shutting down the database before the second rsync. Sincerely, Joshua D. Drake - -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG8rjmATb/zqfZUUQRAs5bAJ9Avhtd0KgQfta1YqN5IX75M3I0awCdHuna suRxLPewL/v2t4w1t7K3eyM= =0rQC -----END PGP SIGNATURE-----