Recommended way to copy database files on Windows OS (to perform file system level backup)
Hi all, We are facing this problem while performing file system level backup of database files: As each database will form a directory inside Base directory which consists of files representing the tables, when some tables are dropped during backup, We get error while copying since the files do not exist anymore. So we would like to know how you recommend copying PostgreSQL database files in Windows OS to perform file system level backups. (For Example - The recommended way in Linux is to use tar format.) Thanks, Yashwanth ***Legal Disclaimer*** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." **
Will Altering and Modifying tables during backup result in a corrupted server after the restore?
Hi All, We are trying this scenario: Here are the steps being done: 1. Creating a big table. Identify the physical file on the disk. 1. While backup process is backing up a file associated with the table - update the rows , add a column. 2. Restore the server with transaction logs We are backing up (copying) the entire postgres data directory. The database/table file being backed up (copied), is modified by running alter/update queries on the table. When we restore the copied data directory and replay/apply the transaction logs, will the server be restored to an healthy state? (The files modified during backup can be corrupted, will this affect the restore?) Thanks, Yashwanth ***Legal Disclaimer*** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." **
