Planned maintenance windows and notifications

Prerequisites and authority

Assign an operator and an authorized technical owner. Data-replacing recovery and updates require a maintenance window, preserved recovery point and known target.

Plan a maintenance window

Define the work, affected components, expected impact, start/end estimate, responsible operator and recovery plan. Distinguish management-only interruption from customer internet interruption; do not promise either without understanding the network.

1. Review backup and rollback/recovery readiness.
2. Identify payments, imports and scheduled jobs that could overlap.
3. Notify customers through supported channels and manual notices.
4. Restrict normal changes/writes as required by the procedure.
5. Perform the planned work and keep a timeline.
6. Verify end-to-end service before announcing completion.
7. Update users if the window extends or impact changes.

Use the actual supported Telegram/in-app mechanism where present. An in-app notice alone may not reach customers who are offline. Manual notices at the site or through the organization's established communication channel may be necessary. This guide does not assume an automated scheduled broadcast feature.

A useful notice includes affected site/services, local date/time, likely access effect and the contact/recheck plan. Do not include credentials or private infrastructure details.

Before stopping services, understand active sessions and expiry behavior. After restart, review backlog processing, router reconciliation, provider events and customer access. Closing the maintenance ticket requires those checks, not just the process restart.

Related guides

Related guides: Health checks, background services and workers, Back up BryanNet and validate backups, Restore BryanNet safely, Product updates, compatibility and rollback, Daily weekly and monthly operator checklists.