Schedule Drupal updates for your lowest-traffic overnight or weekend slot, often between 2 a.m. and 4 a.m. local time.
Staff that slot around Wednesdays, because Drupal releases land then. A maintenance window is a planned period when a site can show a maintenance or read-only message during updates. A quiet window limits lost visits, failed checkouts, and support tickets.
Table of Contents
- Plan around Wednesday releases
- Confirm your own quiet hours
- How do you run the update window?
- Can overnight work be automated?
Plan around Wednesday releases
Drupal core schedules bugfix releases for the first Wednesday of each month and security releases for the third Wednesday, according to the Drupal Association in the current Drupal core release schedule. Keep staff or on-call cover ready on those Wednesdays.
Contributed projects have a security-release window every Wednesday, while Drupal core has a monthly security window usually on the third Wednesday, according to the Drupal Security Team in the current release timing guidance. That pattern supports a weekly patch review, with extra cover for core Wednesdays.
Confirm your own quiet hours
There is no universal low-traffic slot. Audience, time zone, and weekday demand change the answer, so check day-and-hour reports in Google Analytics before fixing a schedule. Weekend and early-morning periods are commonly quietest. IT operations teams schedule unavoidable server work overnight or on weekends when demand is low, according to Computerworld reporting on uptime practices.
Ohio University follows the same idea and restricts disruptive work to low-impact windows, including Tuesday and Thursday 6 p.m. to midnight and Wednesday 2 to 7 a.m. A Drupal agency guide from Pedalo also recommends 4 a.m. for bandwidth-heavy backup tasks.
How do you run the update window?
Drupal's manual core-update procedure directs administrators to enable maintenance mode at Administration > Configuration > Development > Maintenance mode before changing code and running database updates, according to Drupal Association documentation in the manual update procedure. Use that order every time.
- Enable maintenance mode and warn editors about the freeze
- Back up files and database, then change code
- Run database updates, check logs, then disable maintenance mode
Can overnight work be automated?
Yes. The Drupal Maintenance Windows module automatically places a site into maintenance or read-only mode during scheduled infrastructure or integration work, according to the Drupal Association project page. That avoids manual switching at inconvenient hours.
Read-only mode suits content freezes when browsing can continue. Full maintenance mode suits core updates and database changes. Test the schedule, message text, and permissions before using either overnight, and confirm the quiet slot in your own analytics reports as described by Elad Levy in the analytics heatmap method.
