Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 90F719FC0F5 for ; Fri, 22 Jun 2007 10:53:06 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 17845-07 for ; Fri, 22 Jun 2007 10:52:52 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 1BB389FBB76 for ; Fri, 22 Jun 2007 10:52:57 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l5MDqlxt020156; Fri, 22 Jun 2007 06:52:48 -0700 Message-ID: <467BD479.5090603@commandprompt.com> Date: Fri, 22 Jun 2007 06:54:01 -0700 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Toru SHIMOGAKI CC: Steve Atkins , PostgreSQL Performance Subject: Re: PITR Backups References: <7E0807EE-B970-4869-A248-B838E42AD9EE@hi5.com> <9761.1182472005@sss.pgh.pa.us> <467B3459.9030808@oss.ntt.co.jp> <467B7A89.3080300@oss.ntt.co.jp> In-Reply-To: <467B7A89.3080300@oss.ntt.co.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 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]); Fri, 22 Jun 2007 06:52:52 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/536 X-Sequence-Number: 25569 Toru SHIMOGAKI wrote: > > Steve Atkins wrote: > >>> - When we take a PITR base backup with hardware level snapshot operation >>> (not filesystem level) which a lot of storage vender provide, the >>> backup data >>> can be corrupted as Dan said. During recovery we can't even read it, >>> especially if meta-data was corrupted. >> >> I can't see any explanation for how this could happen, other >> than your hardware vendor is lying about snapshot ability. > > All of the hardware vendors I asked always said: > > "The hardware level snapshot has nothing to do with filesystem > condition and of course with what data has been written from operating > system chache to the hard disk platter. It just copies byte data on > storage to the other volume. Right that has been my understanding as well. Joshua D. Drake > > So, if any data is written during taking snapshot, we can't assurance > data correctness *strictly* . > > In Oracle, no table data is written between BEGIN BACKUP and END BACKUP, > and it is not a problem REDO is written..." > > I'd like to know the correct information if the explanation has any > mistakes, or a good way to avoid the probrem. > > I think there are users who want to migrate Oracle to PostgreSQL but > can't because of the problem as above. > > > Best regards, > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/