• 使用 pg_dump 进行 PostgreSQL 逻辑备份的理想做法是什么?
• What are ideal practices for taking PostgreSQL logical backup using pg_dump?
• 从备用/从节点进行备份是否理想?如果复制延迟小于 200ms
• Is it ideal to take backup from a standby/slave node? If replication lag is less than 200ms
• 从备用/从节点进行备份是否理想,我们是否需要更改任何特定配置?
• Is it ideal to take backup from standby/slave node, and is there any specific configuration we need to change?
• 哪种方法是进行逻辑备份或物理备份的好方法?数据库经常更新的地方.作为灾难恢复的备份,哪种方法是更快更好的备份和灾难恢复(恢复).
• Which method is a good way for taking backups logical backup or physical backup? where DB is getting updated frequently. As a backup is taken for disaster recovery which method is the faster and better backup and disaster recovery(restore).
更新我们当前的数据库大小为 5GB,复制处于 热备用 模式.我们在从节点上运行备份脚本,但它每 30 分钟从主节点进行一次远程备份.我创建这个问题的原因是为了了解备份何时运行某些 COPY 语句需要 6 分钟才能完成,即使它不会影响数据库上的其他事务,如果一个语句会发生任何其他问题需要更多时间.
updated Our current database size is 5GB and replication is on hot standby mode. We are running the Backup script on slave node but it takes remote backup from the master node every 30 minutes. The reason I created this question is to understand when the backup is running some COPY statements takes 6 mins to complete, even though it will not affect other transactions on DB, is there any other issues occurs if a statement is taking more time.
推荐答案我想到了你写的东西,这里有一些想法给你:
I thought about what you wrote and here are some ideas for you:
您的数据库有 5GB 大,因此任何备份方法都会很快.但是您必须决定是否需要时间点恢复和几乎零数据丢失 - 因此,您是否愿意花时间设置 pg-barman.
Your database is 5GB big so any backup method will be quick. But you have to decide if you need point in time recovery and almost zero data loss or not - so if you will invest time to setting pg-barman or not.
链接:
更多推荐
Postgresql DB 备份的理想做法
发布评论