Routine maintenance is easier to manage when the work has a defined objective and a recovery plan. List the operating system packages, application components or configuration changes involved, and decide whether the task can restart services or require a full reboot. Use the application owner to confirm a suitable maintenance window.
Recommended workflow
- Define the expected result, likely interruption, named decision maker and conditions that would trigger a rollback.
- Pause conflicting jobs where appropriate, apply the planned changes and record any deviation from the original steps.
- Complete a documented set of service checks, notify affected stakeholders of the result and retain the maintenance record.
Take a usable backup and check that you know how to restore it before starting. A snapshot or backup created immediately before the work still needs a realistic recovery path. Record important version numbers and configuration values, and keep console access available if an SSH session becomes unavailable.
After the change, test the application from outside the server and inspect the relevant logs. Confirm database access, background jobs and email delivery where those functions are part of the workload. If a separate Weeby managed service is involved, agree the request scope and available engineering time in the ticket before the work begins. Additional application development or unrelated administration may require a separate quote.
