Snapshot backups - Mailing list pgsql-general

From James Sewell
Subject Snapshot backups
Date
Msg-id CANkGpBt8agjCS+__CceCKBHBNTEfFsmg5jnFd8MianQh0c0MMA@mail.gmail.com
Whole thread Raw
Responses Re: Snapshot backups  (Magnus Hagander <magnus@hagander.net>)
List pgsql-general
Hey All,

This is a message to confirm my thoughts / validate a possible approach.

In a situation where PGDATA and {XLOG, ARCHIVELOG} are on different SAN/NAS volumes and a backup is to be initiated do pg_start_backup and pg_stop_backup need to be used?

I am using snapshots of each volume for backup.

My thinking is that they are not needed (although I realise it is good practice).

As far as I can tell all they are doing is something like:

pg_start_backup:
  - create backup label
  - trigger checkpoint

pg_stop_backup
  - remove backup label file
  - creates backup history file
  - trigger log switch

There is nothing in here that is *required* from a backup point of view. Am I missing anything?

James Sewell
Solutions Architect

_____________________________________


http://www.lisasoft.com/sites/lisasoft/files/u1/2013hieghtslogan_0.png

Level 2, 50 Queen St,
Melbourne, VIC, 3000

P: 03 8370 8000   F: 03 8370 8099  W: www.lisasoft.com



The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.
Attachment

pgsql-general by date:

Previous
From: Sameer Thakur
Date:
Subject: Archiving and recovering pg_stat_tmp
Next
From: Amit Langote
Date:
Subject: Re: Archiving and recovering pg_stat_tmp