Previous chapters emphasized the importance of storing backups in a remote offsite location in case of catastrophic site loss. Often, this is handled manually by exporting the backup mount or its contents using software or hardware-level filesystem synchronization features.
Beginning with Barman 2.6, it's possible to configure a server to act merely as an offsite storage location for Barman backup data. This can be done on a per-server basis in case it's necessary to follow certain distribution criteria. Not every enterprise has access to sophisticated or expensive distributed SAN snapshots and scripting is sometimes temperamental. Why not use Barman?
This recipe will explain how to configure a passive server that acts merely as an offsite backup holding area.
