From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "girish R G peetle *EXTERN*" <giri(dot)anamika0(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL File System Based Backup Restartability |
Date: | 2015-02-18 08:25:46 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B3659C6DD@ntex2010i.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
girish R G peetle wrote:
> After executing pg_start_backup, we will generate a file 'Backup file' which will contain list of all
> the folders n files under DATA directory.
>
> Then we read entry from 'Backup file' sequentially and use copy command/script to move it to backup
> media.
>
> When network encounters copy script will fail stating couldn't backup the file.
>
> Say copy command throws error at 20th file entry. When backup is resumed copy command resumes from
> 20th file entry.
That should work just fine.
I'd still test the result by restoring such a backup and running "pg_dump -f /dev/null" on it,
just to be sure and because you cannot test your backups often enough.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Valentina Tedone | 2015-02-18 08:38:36 | execution time |
Previous Message | Iñigo Salvat | 2015-02-18 07:24:20 | Re: High availability with Postgres |