Cyberstudy
PDF p.388 In progress

Restarts, Dependencies, and Downtime

Open PDF at p.388 10 flashcards

Summary

PDF p.388

Service and application restarts, as well as downtime, are critical considerations in change management. They directly impact business operations, and the goal is to minimize disruptions by scheduling these events during maintenance windows or off-peak times.

In plain words

Supplementary — not from your PDF

Restarts and downtime affect business operations, so schedule them for maintenance windows or off-peak times and tell stakeholders in advance. Dependencies matter: one service often relies on others, so a restart in one place can affect another and extend the time needed for the change and its backout. Manage the risk with backout plans, post-change monitoring and alternatives.

Detailed explanation

PDF p.388
  • Restarts and Downtime
    • Impact: Directly affect business operations.
    • Scheduling: Minimize disruptions by scheduling during maintenance windows or off-peak times.
    • Communication: Ensure stakeholders are aware of service outages to prepare accordingly.
  • Dependencies
    • Complexity: Services and applications often depend on other software, interfaces, and services.
    • Impact Analysis: A service restart in one area may significantly impact another.
    • Time Considerations: Dependencies can extend the time needed for changes and backout plans.
  • Risk Management
    • Backout Plans: Develop effective plans to handle potential complications.
    • Post-Change Monitoring: Validate system functionality and detect issues quickly.
    • Alternative Solutions: Identify alternatives if risks are too high.

Important terms

taken from the text above
Scheduling
Minimize disruptions by scheduling during maintenance windows or off-peak times.
Impact Analysis
A service restart in one area may significantly impact another.
Time Considerations
Dependencies can extend the time needed for changes and backout plans.
Backout Plans
Develop effective plans to handle potential complications.
Post-Change Monitoring
Validate system functionality and detect issues quickly.
Alternative Solutions
Identify alternatives if risks are too high.

Examples & real-world scenarios

Supplementary — not from your PDF
  • Announcing a planned outage to users.
  • Mapping dependencies before restarting a service.
  • Monitoring after a change to catch issues fast.

Scenario

Restarting a database also takes down three apps that depend on it, surprising users. A dependency analysis beforehand would have revealed the wider impact.

Common mistakes

Supplementary — not from your PDF
  • Ignoring dependencies when planning a restart.
  • Not communicating downtime to stakeholders.

Practical skills

Supplementary — not from your PDF
  • Map dependencies before a change.

What I should remember

Key Points PDF p.388
  • Restarts and Downtime: Schedule to minimize impact.
  • Dependencies: Analyze and manage impacts.
  • Risk Management: Develop backout plans and monitor changes.