Managing Server Updates Print

  • devopsinfrastructure, devops, database, backup, security, guide, howto, solution
  • 0

Keeping systems current.

WHY IT MATTERS MOST

Known vulnerabilities are published and scanned for within hours.

WHAT TO UPDATE

The operating system Installed packages The runtime and its extensions The web server and database

WHAT TO AUTOMATE

Security updates, where the risk of an unattended update is lower than the risk of delay.

WHAT NOT TO AUTOMATE

Major version upgrades.

WHAT TO SCHEDULE

Regular review of what needs updating.

WHAT TO DO BEFORE A SIGNIFICANT UPDATE

Take a backup Read the change notes Test on a copy, where possible Have a way to revert

WHAT TO CHECK AFTERWARDS

The application works Services restarted The log is clean

WHAT TO WATCH FOR

Services not restarting after an update Configuration files replaced by new defaults

THAT SECOND ONE

A common cause of a working server stopping after an update.

WHAT TO NEVER DO

Leave a system unpatched because updating seems risky.

WHAT TO PLAN

Replacement of systems reaching end of support.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot