On Mon, Mar 26, 2018 at 11:52:53AM +0000, Amee Sankhesara - Quipment India wrote:
> Warning : The failed archive command was: copy
> "D:\PostgreSQL\9.6\data\pg_xlog\0000000100000A88000000F8.partial"
> "\\10.0.0.35\Archive_Replication\0000000100000A88000000F8.partial" |
> copy "D:\PostgreSQL\9.6\data\pg_xlog\0000000100000A88000000F8.partial"
> "\\10.0.0.35\Archive_PITR\0000000100000A88000000F8.partial"
Am I reading that correctly or you are trying to copy twice the same
file? Why? Using only copy may cause corruptions if you are not
careful as a disabled write caching would cause the data to go to the OS
cache on Windows and not directly to disk.
> Due to this it has stopped to take backup of PITR
>
> So we like to know how to clean up the ".partial" file from pg_xlog and run PITR backup smoothly
> Also like to know is there any database consistency related issue ?
This is the last, partial WAL segment from the previous timeline.
Normally such things are able to archive correctly, so you may want to
consider a more advanced archive command able to handle duplicates.
It is impossible to give a strict answer before knowing what you are
looking for in terms of WAL archive redundancy.
You may need to use target_timeline = 'latest' in your recovery.conf
settings as well.
--
Michael
