From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Message-Id: <20031016133727.469620f0.threshar@torgo.978.org> In-Reply-To: <200310161009.27379.josh@agliodbs.com> References: <200310160949.59442.josh@agliodbs.com> <20031016130637.535f633f.threshar@torgo.978.org> <200310161009.27379.josh@agliodbs.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [linux-lvm] Re: [PERFORM] backup/restore - another area. Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Date: Thu Oct 16 14:06:09 2003 List-Id: Content-Type: text/plain; charset="us-ascii" To: Josh Berkus Cc: markw@osdl.org, pgsql-performance@postgresql.org, linux-lvm@sistina.com, pgsql-admin@postgresql.org On Thu, 16 Oct 2003 10:09:27 -0700 Josh Berkus wrote: > Jeff, > > > I left the DB up while doing this. > > > > Even had a program sitting around committing data to try and corrupt > > things. (Which is how I discovered I was doing the snapshot wrong) > > Really? I'm unclear on the method you're using to take the snapshot, > then; I seem to have missed a couple posts on this thread. Want to > refresh me? > I have a 2 disk stripe LVM on /dev/postgres/pgdata/ lvcreate -L4000M -s -n pg_backup /dev/postgres/pgdata mount /dev/postgres/pg_backup /pg_backup tar cf - /pg_backup | gzip -1 > /squeegit/mb.backup umount /pg_backup; lvremove -f /dev/postgres/pg_backup; In a nutshell an LVM snapshot is an atomic operation that takes, well, a snapshot of hte FS as it was at that instant. It does not make a 2nd copy of the data. This way you can simply tar up the pgdata directory and be happy as the snapshot will not be changing due to db activity. -- Jeff Trout http://www.jefftrout.com/ http://www.stuarthamm.net/