The Orchestrator data bus is extremely powerful, but it is not persistent. If the Orchestrator runbook server were to reboot or the services were to crash, all data about executing runbooks would be lost. Read this whitepaper about a recommended solution for this issue — utilizing a small backend SQL database table or set of tables.
This whitepaper covers:
- Passing data efficiently between runbooks.
- The difficulties of managing a runbook without a persistent data store.
- Re-running and troubleshooting runbooks.
- Conducting manual intervention.