The idea behind this spreadsheet is to describe the environments in our architecture sufficiently so that we can track where the backups originate and how many there should be. Once we have a definitive number, it may be apparent that it's too much to manage with a series of ad hoc scripts and scheduled backup or WAL archival maintenance events.
This example spreadsheet represents part of our architecture in the introduction:
When we say Cluster Name, we really mean the primary focus of the data itself. If the application stack is a stock trading system, we might call it Trading. If it's a complex game engine based on many ...
