Backup strategies

Recommendations

Info

pg_dump system impact●●●●●Runs regular COPY queriesUses single backendDoes not ruin PostgreSQL cache●“ring buffer” strategy usedCan potentially ruin filesystem cacheWriting of dump file causes I/O
pg_dump compression●●Compression happens in pg_dumpCan be used for throttling● Typical “breakpoint” at 3-5●●Higher becomes CPU boundLower becomes I/O bound
Page 5 and 6: But my SAN is 100% up!●●Really?
Page 9 and 10: Logical backups●●●●SQL scri
Page 11: pg_dump●●Supports multiple outp
Page 15 and 16: Restoring from pg_dump●●●Use
Page 17 and 18: Restore performance●●●●Use
Page 19 and 20: Restore performance●●●Turn fs
Page 21 and 22: Physical backups●●●●●Post
Page 23 and 24: Simple snapshot backups●●●Fil
Page 25 and 26: Online base backups●●Integrated
Page 27 and 28: Log archiving●●As log is genera
Page 29 and 30: Log archiving limitations●●Alwa
Page 31 and 32: pg_basebackup systemimpact●●●
Page 33 and 34: Backup strategies
Page 35 and 36: How to back up●●●You definite
Page 37 and 38: Log file/base backup●●●Restor
Page 39 and 40: Lagged behind replicas●●●Usin
Page 41 and 42: Testing your backups●●We all kn
Page 43 and 44: Thank you!Questions?Share your stor

Backup strategies

Create successful ePaper yourself

Delete template?

Save as template?