Difference between revisions of "Maintenance Schedule"
From RCampus Wiki
m |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
==RCampus Maintenance Schedule== | ==RCampus Maintenance Schedule== | ||
We are committed to providing a secure and unparalleled experience to our user community with continuous maintenance and optimization of RCampus. To ensure minimal disruption to our users' critical work, we schedule these maintenance activities during low-traffic windows. | We are committed to providing a secure and unparalleled experience to our user community with continuous maintenance and optimization of RCampus. To ensure minimal disruption to our users' critical work, we schedule these maintenance activities during low-traffic windows. | ||
| − | |||
===System/Server Maintenance:=== | ===System/Server Maintenance:=== | ||
| Line 12: | Line 11: | ||
*Duration: 30 minutes per hourly window, with a maximum of two updates in a single evening. | *Duration: 30 minutes per hourly window, with a maximum of two updates in a single evening. | ||
*Scope: We update shared database systems during this time which may temporarily impact data delivery to users. However, the application remains available. | *Scope: We update shared database systems during this time which may temporarily impact data delivery to users. However, the application remains available. | ||
| − | |||
===Application Updates:=== | ===Application Updates:=== | ||
'''Friday nights between 8:00 PM and 10:00 PM PST:''' | '''Friday nights between 8:00 PM and 10:00 PM PST:''' | ||
*Frequency: Typically once a quarter. | *Frequency: Typically once a quarter. | ||
| − | + | *Duration: 15 minutes to 2 hours. | |
===Urgent Updates:=== | ===Urgent Updates:=== | ||
*These updates are reserved for critical security and functionality patches requiring (semi) immediate attention. We aim to schedule them during nighttime low-traffic hours unless urgency dictates otherwise. | *These updates are reserved for critical security and functionality patches requiring (semi) immediate attention. We aim to schedule them during nighttime low-traffic hours unless urgency dictates otherwise. | ||
| − | |||
===Important Note:=== | ===Important Note:=== | ||
*Prior to performing Application and Urgent Updates, a notification is displayed at least 60 minutes in advance. This affords our users ample time to save their work and exit the platform. | *Prior to performing Application and Urgent Updates, a notification is displayed at least 60 minutes in advance. This affords our users ample time to save their work and exit the platform. | ||
Latest revision as of 00:17, 12 October 2023
Contents
RCampus Maintenance Schedule
We are committed to providing a secure and unparalleled experience to our user community with continuous maintenance and optimization of RCampus. To ensure minimal disruption to our users' critical work, we schedule these maintenance activities during low-traffic windows.
System/Server Maintenance:
Friday and Saturday nights at 9:00 PM PST:
- Frequency: Every week.
- Duration: Typically less than 3 minutes.
- Scope: Each night, we update half of our nodes while the other half continue their operations seamlessly.
Friday nights starting at 11:00 PM and 12:00 AM PST:
- Frequency: As needed, typically once a month.
- Duration: 30 minutes per hourly window, with a maximum of two updates in a single evening.
- Scope: We update shared database systems during this time which may temporarily impact data delivery to users. However, the application remains available.
Application Updates:
Friday nights between 8:00 PM and 10:00 PM PST:
- Frequency: Typically once a quarter.
- Duration: 15 minutes to 2 hours.
Urgent Updates:
- These updates are reserved for critical security and functionality patches requiring (semi) immediate attention. We aim to schedule them during nighttime low-traffic hours unless urgency dictates otherwise.
Important Note:
- Prior to performing Application and Urgent Updates, a notification is displayed at least 60 minutes in advance. This affords our users ample time to save their work and exit the platform.
