![Page 1: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/1.jpg)
giovedì 4 ottobre 12
![Page 2: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/2.jpg)
GABRIELE BARTOLINIPostgreSQL Sessions - Paris, 4 October 2012
giovedì 4 ottobre 12
![Page 3: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/3.jpg)
GABRIELE BARTOLINI
• Co-Founder and Manager of 2ndQuadrant Italia
•Data Architect, Business critical environments
•Data warehousing
• Co-Founder Italian PostgreSQL Users Group
• Co-Founder PostgreSQL Europe
• PostgreSQL Contributor and Advocate
giovedì 4 ottobre 12
![Page 4: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/4.jpg)
INGRES
Database
French Painter
Now
19th century
giovedì 4 ottobre 12
![Page 5: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/5.jpg)
BARTOLINI
Myself
Italian Sculptor(same family tree)
Now, here
19th century
giovedì 4 ottobre 12
![Page 6: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/6.jpg)
1799PARIS
BARTOLINIINGRES
2012PARIS
BARTOLINIPOSTGRES
giovedì 4 ottobre 12
![Page 7: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/7.jpg)
DISCLAIMERThis talk assumes you are familiar with disaster
recovery concepts and PostgreSQL implementation of Point In Time Recovery
giovedì 4 ottobre 12
![Page 8: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/8.jpg)
BE AWAREIn 2ndQuadrant, all these concepts usually fit in a 2 day workshop on Disaster Recovery and a 1 day
workshop on Barman alone
giovedì 4 ottobre 12
![Page 9: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/9.jpg)
MENU D'AUJOURD'HUI
• Business continuity / Disaster recovery for databases
•Disaster recovery with Barman for PostgreSQL
giovedì 4 ottobre 12
![Page 10: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/10.jpg)
PART IBusiness continuity / Disaster recovery for databases
giovedì 4 ottobre 12
![Page 11: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/11.jpg)
BUSINESS CONTINUITYactivity performed by an organization to ensure that critical business functions will be available to customers, suppliers,
regulators, and other entities that must have access to those functions - Wikipedia
giovedì 4 ottobre 12
![Page 12: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/12.jpg)
INFORMATION TECHNOLOGY
• Business continuity
• High availability
• Disaster recovery
giovedì 4 ottobre 12
![Page 13: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/13.jpg)
LAW REQUIREMENTSIn Italy, the “Codice dell’Amministrazione Digitale” defines business continuity requirements for public
administrations
giovedì 4 ottobre 12
![Page 14: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/14.jpg)
DISASTER(touch wood)
system/hardware failuresaccidental errors
disaster
giovedì 4 ottobre 12
![Page 15: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/15.jpg)
REACT TO A DISASTERRecover systems, data and infrastructures
giovedì 4 ottobre 12
![Page 16: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/16.jpg)
TOO LATE!Do not wait for a disaster to happen
giovedì 4 ottobre 12
![Page 17: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/17.jpg)
PLAN FOR DISASTERS“Disasters” will happen. Be prepared.
giovedì 4 ottobre 12
![Page 18: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/18.jpg)
“Plans are worthless, but planning is everything. There is a very great distinction
because when you are planning for an emergency you must start with this one thing: the very definition
of "emergency" is that it is unexpected, therefore it is not going to happen the way you are
planning.”- Dwight D. Eisenhower
giovedì 4 ottobre 12
![Page 19: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/19.jpg)
REGULAR CRASH TESTS
giovedì 4 ottobre 12
![Page 20: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/20.jpg)
DATABASEDISASTER RECOVERY
Let’s just focus on databases!
giovedì 4 ottobre 12
![Page 21: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/21.jpg)
REQUIREMENTS
• Automated backups
• Notifications (anomalies)
• Frequency of backups
• Retention policies
• Data protection
• Availability for recovery
giovedì 4 ottobre 12
![Page 22: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/22.jpg)
POSTGRES BACKUP
• Hot backup
•MVCC
• Logical Backup
• pg_dump
• Physical Backup
• Full backup (base backup)
•Differential backup (WAL)
giovedì 4 ottobre 12
![Page 23: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/23.jpg)
TRADITIONAL DRWITH POSTGRESQL
• PostgreSQL primitives for DR are robust and reliable
• High level skills
•DBA
• Sysadmins
• Custom scripts
• Hard to integrate in:
• Backup solutions
•Disaster Recovery plans
• Hard to test!
giovedì 4 ottobre 12
![Page 24: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/24.jpg)
EXISTING TOOLS
•Omni-PITR
•WAL centric
•WALmgr
•WAL centric
• pg-rman
• Server centric
•WAL-E
• EC2 centric, but ...
• good
• came later
giovedì 4 ottobre 12
![Page 25: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/25.jpg)
NONE FOR DRNone of them was a pure disaster recovery solution.
We wanted something similar to Oracle’s RMAN.
giovedì 4 ottobre 12
![Page 26: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/26.jpg)
FILLING A HOLEThe lack of a DR solution is a barrier towards the adoption
of PostgreSQL from Oracle users’ point of view.
giovedì 4 ottobre 12
![Page 27: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/27.jpg)
DESIDERATA
• Hot, Full, Differential and incremental backups
•Multiple servers
• Remote backup & recovery
• Backup catalogues
• Retention policies
• Archival and compression
•WAL segments
• Periodical backups
• Automation
• Integration
• Usability
giovedì 4 ottobre 12
![Page 29: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/29.jpg)
PART IIDisaster recovery with Barman for PostgreSQL
giovedì 4 ottobre 12
![Page 30: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/30.jpg)
BARMAN
• GNU GPL 3
• Hosted on Sourceforge.net
• Python 2.6/2.7
• PostgreSQL 8.4, 9.0, 9.1, 9.2
• PyPI package
• RPM package
•Debian package (soon)
•Designed, developed, maintained by 2ndQuadrant
giovedì 4 ottobre 12
![Page 31: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/31.jpg)
Postgres Postgres Postgres
Barman
LAN, centralised architecture
Barman
LAN, hybrid architecture
tape
giovedì 4 ottobre 12
![Page 32: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/32.jpg)
Postgres
Barman
Continuous archiving(WAL shipping via SSH)
SSH commandsSQL commands
giovedì 4 ottobre 12
![Page 33: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/33.jpg)
secure channel
Postgres Barman
WAL cron
Barman’sWAL archive
giovedì 4 ottobre 12
![Page 34: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/34.jpg)
Postgres
Full backup - Sat 1, 4AM
Full backup - Sat 8, 4AM
Full backup - Sat 15, 4AM
Full backup - Sat 22, 4AM
Barman
Periodical backup (weekly)Differential backupBackup catalogue
giovedì 4 ottobre 12
![Page 35: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/35.jpg)
CONVENTION OVER CONFIGURATION
global/per server optionsdefault directory layout
giovedì 4 ottobre 12
![Page 36: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/36.jpg)
CONFIGURATION FILE
[barman]barman_home = /srv/barmanbarman_user = barmanlog_file = /var/log/barman/barman.loglog_level = NOTICEcompression = gzip
[production]description = Production PostgreSQLssh_command = ssh pg.2ndQuadrant.itconninfo = host=pg.2ndQuadrant.it user=postgrescompression = bzip2
giovedì 4 ottobre 12
![Page 37: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/37.jpg)
CONVENTIONAL DIRECTORIES FOR BARMAN
• barman_home (/srv/barman)
• server directory (/srv/barman/production)
• base directory (/srv/barman/production/base)
•WAL directory (/srv/barman/production/wals)
• incoming directory (/srv/barman/production/incoming)
giovedì 4 ottobre 12
![Page 38: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/38.jpg)
MULTI-SERVER CONFIGURATION
[barman]; General configuration; …[server_one]; Configuration for Server 1; …[server_two]; Configuration for Server 2; …[server_X]; …
giovedì 4 ottobre 12
![Page 39: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/39.jpg)
GLOBAL COMMANDS
• List of managed servers
• barman list-server
• Maintenance operations
• barman cron
giovedì 4 ottobre 12
![Page 40: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/40.jpg)
SERVER COMMANDS
• Information and diagnostics
• barman status
• barman check
• barman show-server
• barman list-backup
• Backup control
• Recovery control
giovedì 4 ottobre 12
![Page 41: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/41.jpg)
giovedì 4 ottobre 12
![Page 42: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/42.jpg)
BACKUP CONTROL
• barman backup
• barman show-backup
• barman list-files
• standalone, data, wal, full
• barman delete
giovedì 4 ottobre 12
![Page 43: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/43.jpg)
giovedì 4 ottobre 12
![Page 44: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/44.jpg)
SHOW BACKUP
• General
• Server name, Postgres version, status, ...
• Base backup
• Start/End time, first/last WAL, disk usage, ...
• WAL
•Number of associated files
• disk usage
• Context
• Previous/Next backup
giovedì 4 ottobre 12
![Page 45: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/45.jpg)
giovedì 4 ottobre 12
![Page 46: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/46.jpg)
RECOVERY CONTROL
• Recovery target (full / point in time)
• Local recovery
• barman recover
• Remote recovery
• barman recover --remote-ssh-command
giovedì 4 ottobre 12
![Page 47: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/47.jpg)
ADVANCED RECOVERY
• Point In Time Recovery
• --target-time = TIME
• --target-xid = XID
• Relocation of tablespaces
• --tablespace NAME:LOCATION [...]
giovedì 4 ottobre 12
![Page 48: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/48.jpg)
COMMON USE CASES
• Accidental errors recovery
•Disaster recovery
• Sandbox server (BI, staging, ...)
giovedì 4 ottobre 12
![Page 49: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/49.jpg)
giovedì 4 ottobre 12
![Page 50: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/50.jpg)
SPONSOR A FEATURE!
• Retention policies
• Sandbox recovery
• Replication protocol support (client / server)
• Incremental backup
• reduce backup time and size
giovedì 4 ottobre 12
![Page 51: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/51.jpg)
RETENTION POLICY CONFIGURATION
; Base backup retention policyretention_policy = 'redundancy 3'retention_policy = 'recovery window of 30 days'
; WAL retention policywal_retention_policy = 'base' ;wal_retention_policy = 'recovery window of 14 days'
giovedì 4 ottobre 12
![Page 52: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/52.jpg)
OUR COMMITMENT
• Keep it open source
• Reinvest money from sale of DR turnkey solutions in R&D
• Support and maintain RPM/Debian packages
• Accept sponsorships for new features development
giovedì 4 ottobre 12
![Page 53: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/53.jpg)
CONCLUSIONS
• Hides complexity of PITR / Keeps unaltered PITR strenghts
•Not invasive
• Fosters migrations from Oracle
• “Standard de facto” for PostgreSQL Disaster Recovery
• Advice: plan for DR (if you have not done it yet)
giovedì 4 ottobre 12
![Page 55: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/55.jpg)
MERCI BEAUCOUP!
giovedì 4 ottobre 12
![Page 56: giovedì 4 ottobre 12 - PostgreSQL Sessions · • Disaster recovery with Barman for PostgreSQL giovedì 4 ottobre 12. PART I Business continuity / Disaster recovery for databases](https://reader031.vdocument.in/reader031/viewer/2022021900/5b59ca897f8b9a6c4f8da0df/html5/thumbnails/56.jpg)
LICENSE
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
Copyright (c) 2012 - 2ndQuadrant.it
giovedì 4 ottobre 12