Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
Kelverions Best Practice Guide- Using a Persistent Data Store
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.
ITPro Today
April 4, 2015
1 Min Read
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.
Download now!
About the Author
You May Also Like
.png?width=700&auto=webp&quality=80&disable=upscale)