Manage Maintenance Window configuration
Periodic maintenance is a mandatory part of the FPT MongoDB Enterprise service, not an optional feature. It applies security patches, system updates, and optimizations that keep clusters healthy.
What you control is when it happens. The maintenance window is a weekly time slot, set per cluster, during which the platform is allowed to perform that work.
What maintenance does and costs
Maintenance applies required security patches, system updates, and long-term stability optimizations.
During the window, the service may experience:
- Short connection interruptions
- Reduced performance
- Limited availability of some features
These end when maintenance completes.
Do not operate on the cluster during maintenance. That includes configuration changes, system modifications, and starting or stopping services. Doing so can degrade performance and stability or produce unexpected errors. Wait until maintenance completes.
Operating rules
- Runs weekly, per cluster.
- Each cluster has exactly one active maintenance window.
- Duration is 1 hour from the configured start time.
- If you configure nothing, maintenance defaults to 23:00 every Saturday.
Required permissions
| Permission | Action type | Allows |
|---|---|---|
manageDatabase:Configuration | Edit | Modifying cluster configuration, including maintenance and scaling settings |
Set the window at creation
In the additional services step of Create your first database, choose Day of Week and Start Time. The configuration applies from the first operational cycle.
Change the window later
Step 1: Open the Maintenance tab
Log in to FPT Cloud Portal. From the main menu, select Database Platform → All Database. Select the Cluster ID and open the Maintenance tab.
Step 2: Configure
-
Click the Configuration icon — the gear next to Maintenance Window.
-
Set:
Field What to enter Day of Week Monday through Sunday. Start Time When maintenance may begin. Runs for 1 hour from here. -
Click Save.
The new window applies to subsequent maintenance sessions.
You can only change the window while the cluster has no maintenance event already scheduled. If one is pending, the configuration is locked until it completes.
Step 3: View pending maintenance
Scheduled activities appear under Pending Maintenance Event:
| Field | Shows |
|---|---|
| Maintenance Event | Name of the event |
| Type | Type of maintenance |
| Duration (Minute) | Estimated duration |
| Apply At | Scheduled start time |
Review this regularly so operations can be planned around it.
Notifications
The system emails recipients twice before maintenance:
- 7 days before the scheduled time
- 1 day before it begins
Recipients come from the Notification tab's maintenance service settings — see Notification. Telegram does not support the Maintenance service, so maintenance alerts must go to email.
Emergency maintenance
For critical security patches or important system updates, emergency maintenance may run outside your configured window. The maintenance window optimizes timing; it does not guarantee that maintenance never happens at another time, nor that there is zero interruption.
Schedule your window during off-peak hours to minimize impact.
Next steps
- Notification to set maintenance recipients
- Monitoring to watch cluster health around maintenance