A proper database backup is probably the most important component of a true high availability stack. Inadequate backups can lead to or even compound data loss by providing a false sense of security in the face of a catastrophe.
In the chapter where we explained architecture, we provided a recipe that explained the 3-2-1 backup rule. This is a good start but is more of a design and resource allocation consideration. Truly managing PostgreSQL backups means having the right software, configuring it optimally, and testing both the backup and recovery procedures.
We've written this chapter to apply the architecture lessons we learned at the beginning of this book, and expand upon it with a solid foundation by focusing on the Barman backup software. In our experience, this is the most reliable approach for constructing a fully integrated high availability stack...