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>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL File System Based Backup Restartability |
Date: | 2015-02-17 10:56:57 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B3659C085@ntex2010i.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
girish R G peetle wrote:
> Is PostgreSQL file system based backup restart-ability possible ?
>
> Steps
> - Database size is 1 TB
> - I'll execute pg_start_backup('label');
> - I will traverse through the DATA directory to get the list of directories and files.
> - I will start moving the files to backup media. ( over network )
> - When I'm half way (500GB done), network error happens. So movement of files is halted.
> - Network issue is resolve after 30 minutes (In this time files might have got deleted or added with
> creation/deletion of database/tables )
> - I'll resume moving the files to backup media from where it had halted.
> - When movement of files is done, I'll execute pg_stop_backup()
> - I'll move all the transaction logs that got archived to backup media.
>
> Is PostgreSQL server recovery to a consistent state possible with backup content obtained from above
> steps ?
That should work, but I guess it may depend on what the copy program does if it encounters the
network error. Were there any messages?
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Jan-Peter Seifert | 2015-02-17 13:52:56 | Canceling REINDEX safe? |
Previous Message | girish R G peetle | 2015-02-17 06:06:20 | PostgreSQL File System Based Backup Restartability |