Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id CE7929F9B00 for ; Thu, 13 Sep 2007 18:13:49 -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 43692-03 for ; Thu, 13 Sep 2007 18:13:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by postgresql.org (Postfix) with ESMTP id EC69A9F95B7 for ; Thu, 13 Sep 2007 18:13:45 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id u77so1435590pyb for ; Thu, 13 Sep 2007 14:13:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=61mYa0BcA5C4FPEqcNlpLrFw5kkxg8U1yzshxVggIS0=; b=Q8k9zF6ZcFlHGEw2wpTadjolx05eZXvwyT5+Fsg+F3scwgmxa94ztIyYTEp8W9NmlQWBBnwh9ooj/eCDtrInzZ0paBu045YMosP2nnBu2Oop09eXd/2Y/30EFwsst2fIruhKk1+e4sxXnxG3bi+aa7QcNWBpK4DmHiJEL9lT1yo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=GJLDU67AlmWzWJ9JcyYn+nc1dzEO2VcLEG8m4pEeAWR7I/eMctmjmQC4MfJXlATVaoxZrvB6xKRKTtnXXiVPx7a0rI6ZRpW927DvjJTdVfLbaiskLnLRPtMSNYIz+ITdDJ8cUrhcQ4/Dt4ArVH5aa5qJIj1p0VXYEYKxgZwJud8= Received: by 10.78.118.5 with SMTP id q5mr651215huc.1189718023348; Thu, 13 Sep 2007 14:13:43 -0700 (PDT) Received: from ?192.168.1.28? ( [83.11.108.135]) by mx.google.com with ESMTPS id p27sm3569330hub.2007.09.13.14.13.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 13 Sep 2007 14:13:41 -0700 (PDT) Message-ID: <46E9A81D.90309@gmail.com> Date: Thu, 13 Sep 2007 23:14:05 +0200 From: Andrzej Zawadzki User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.8.1.6) Gecko/20070804 PLD/3.0 (Th) SeaMonkey/1.1.4 MIME-Version: 1.0 To: 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> In-Reply-To: <20070913203946.GE6423@easy2.in-chemnitz.de> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/95 X-Sequence-Number: 26856 Użytkownik Tino Schwarze napisał: > On Thu, Sep 13, 2007 at 01:15:34PM -0700, Abu Mushayeed wrote: > >> Can someone help me with moving a postgres database install to a new >> SAN disks. We are getting a new set of faster disk, I would like to >> find out is there a way, without reinstall to move existing database >> and data to the new disks with minimal downtime. > > If you cannot move online with some SAN tools, you may simply > > 1. stop postgres Not yet... > 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. > 3. start postgres with new data directory Minimal downtime I think. Best regards -- Andrzej Zawadzki