Monthly DB Maintenance Schedule

Schedule PolicyCopy Anchor Link

• Window: first Saturday of every month
• Start time: 02:00 UTC
• Target duration: up to 2 hours
• Scope: MSSQL, PostgreSQL, MySQL, MongoDB runtime stack and related DB UIs
• Approval model: single-owner approval before execution

Pre-Window ChecklistCopy Anchor Link

• Confirm latest Tier-1 backup run completed successfully.
• Confirm backup timer is active and next run is scheduled.
• Confirm latest restore-validation report is present and target-compliant.
• Record maintenance change record under docs/operations/change-records/.

Execution BaselineCopy Anchor Link

• Apply controlled image/package updates only within approved scope.
• Update one database engine at a time with verification between steps.
• Keep rollback checkpoints available before each stateful component change.
• Run post-change health and connectivity checks for each updated engine/UI.

Post-Window EvidenceCopy Anchor Link

• Save command/output evidence in tmp/backups/evidence/ when applicable.
• Update executed change record with outcomes, deviations, and rollback status.
• Update docs/state/next-steps.mdx for any follow-up remediation.

Initial Scheduled Window ReferenceCopy Anchor Link

• First tracked window after policy finalization: 2026-05-02 02:00 UTC.