Backups with Exported Resources - Zach Leslie, Puppet Labs
2 likes960 views
This document discusses the importance of backups and configuration management. It introduces exported resources in Puppet as a way to share data across nodes. It then provides a brief overview of the Bacula backup software, including its main components and how backups flow through the system. Resources on system failures and a thank you to the speaker are also included.
Backups with Exported Resources - Zach Leslie, Puppet Labs
- 1. Backups! ...and the joys of Exported Resources with Zach Leslie
- 2. Why take backups? Your data is at risk! Fire Co-Workers Solar flares Zombies Security Incidents You
- 3. But I use config management... "I have configuration management, I can just rebuild!" Yes, though... machines fail. systems fail. people fail. And what about the data?
- 4. Exported Resources: what? Exported resources are a way to use local data on a remote system.
- 5. Exported Resources: An example A resource is with local fact data is "exported" to all other nodes. Each node then "realizes" or "collects" these resources using the data from every other node. class profile::ssh { # Declare: @@sshkey { $hostname: type => dsa, key => $sshdsakey, } # Collect: Sshkey <<| |>> }
- 6. Bacula: An ultra-Brief intro Bacula has three distinct moving parts: Director: Coordinates backups, stores status. Labels media, handles all coordination. Storage Daemon: Allocates disk storage for pools that Bacula uses to store backup data. File Daemon (or client): The daemon run on each system that needs to be backed up.
- 7. Bacula Flow
- 8. (demo)
- 9. Resources Richard Cook, "How Complex Systems Fail"