Blog ·

Your Servers No Longer Reboot While Your Customers Buy

New in the ISVTEC console: you set, for each server, the only time we may interrupt it. Reboots and planned interventions happen there, nowhere else.

Cyril Bouthors, founder. Managed infrastructure and DevOps since 2003. Book a Call

Tuesday, 9:40 am. A server reboots for a security update. Three minutes later it is back. For the customer paying at that moment, your shop was down.

Do reboots land at random with your current host? Request our free audit, results within 1 business day.

The Update Cannot Wait, the Hour Can

A published flaw is exploited within hours: security updates cannot be postponed. But when the reboot happens should be your call.

Now It Is

In your ISVTEC console, the “Maintenance window” tab sets, for each server, the only time we may interrupt it: days, start, end and your time zone.

  • Security updates reboot your server only inside that window. Outside it, the reboot waits for the next one.
  • Every planned intervention (OS upgrade, migration, failover) is scheduled inside it, and announced on your ticket two business days ahead.
  • No end set means one hour, and the console shows it.
  • Change it whenever you like, in 30 seconds, no ticket needed.

One source of truth: your setting. No more reboots during your traffic peak.

How

In the console, pick a server, then the “Maintenance window” tab, marked “New”. Your current setting is already there.