Customers who have a valid S-user ID can subscribe to the Change Log document below to receive an email notification whenever updates or changes (unless such change is a reduction in duration of the applicable windows) are made to the Maintenance and Major Upgrade Windows.
Maintenance Windows in the Cloud
DOWNLOAD: https://tlniurl.com/2vAbpB
The table below lists the Maintenance and Major Upgrade windows for cloud services provided by a third party. It provides the start times and maximum scheduled downtime duration for the following regions:
OpenText reserves one extended maintenance window (4 hrs) per calendar quarter. This window and other upcoming scheduled maintenance, current status and incidents are published under status.opentext.com
OpenText reserves one extended maintenance window (4 hrs) per calendar quarter. This window and other upcoming scheduled maintenance, current status and incidents are published under status.opentext.com
A maintenance window is a period of time designated to perform regular maintenance activities on monitored entities. You can perform the tasks related to a maintenance window in the Administration console in Oracle Management Cloud.
A maintenance window can be scheduled to run immediately or in the future, and to run indefinitely or stop after a specific duration. It can be created on an as-needed basis, or scheduled to run at regular intervals. Notifications, such as emails and webhooks, are suppressed during the maintenance window. However, Oracle Management Cloud continues to monitor entities and display entity status, while indicating that the entity is currently under maintenance. Also, events are generated during the maintenance window, but event notifications are suppressed.
The availability percentage of an entity changes based on the maintenance window created for the entity. When creating a maintenance window, you can determine whether the maintenance window duration should be included in the availability calculation of entities.
Note that the Type field on the Create Maintenance Window page cannot be edited. Only notifications can be suppressed in the maintenance window, and the Notification Suppression option is selected by default in the Type field.
You can search for a maintenance window or an entity for which a maintenance window has been created. A drop-down list and a Search field are displayed on each of the tabs on the Maintenance Windows page.
The reason I'm hesitating between RDS and Cloud SQL is that I couldn't find that if I set a Cloud SQL instance to high availability with read replicas how will the scheduled maintenances happen. After reading SO and documentation for quite a few hours now I believe that even in case of a HA instance you can experience outages due to scheduled maintenance, so you cannot set any settings / policies to have virtually 100% uptime unlike in AWS RDS where you can set different maintenance windows for replicas.
When scheduled maintenance occurs, the operations are first performed on the read replica(s) and then on the master instance. Cloud SQL attempts to keep one of them running at all time, but this is not guaranteed, is subject to change and you shouldn't rely on it.
High availability equates to multi-az sql instance. So when you set this option you get a primary instance running in a zone and secondary in another zone. So when maintenance window kicks in the cloud sql should automatically fail over to the other availability zone and your app / users shouldn't be affected. However there are some reported incidents where Cloud SQL caused a downtime (see edit notes below).
With this option enabled, any ServiceNow change requests that list Affected CIs will create entries in the servicenow_maintenance_windows catalog when the change request enters the Implementation state. The catalog entries will be of the form:
At the end of the change window, when the change request in ServiceNow moves out of the Implementation state, all Moogsoft Cloud servicenow_maintenance_windows catalog entries matching the change are identified and deleted.
Navigate to Correlate & Automate > Data Catalog and make sure that the servicenow_maintenance_windows catalog has been created. This will be the case if the ServiceNow Moogsoft Cloud application has processed a change request entering Implementation.
Cloud storage devices subject to maintenance and administrative tasks may need to be temporarily shut down, thereby causing an outage to cloud service consumers and IT resources that require access to the devices and the data they host (Figure 4.31).
Figure 4.31 The maintenance task carried out by a cloud resource administrator causes an outage for the cloud storage device. Resultantly, the cloud storage device becomes unavailable to cloud service consumers.
Prior to a cloud storage device undergoing a maintenance outage, its data can be temporarily moved to a duplicate, secondary cloud storage device. Cloud service consumers are automatically and transparently redirected to the secondary cloud storage device and are unaware that the primary cloud storage device has been taken offline.
Figure 4.36 When it is confirmed that the maintenance task on the primary storage device has been completed, the primary storage is brought back online. Live storage migration subsequently restores the LUN data from the secondary storage device to the primary storage device.
On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.
Maintenance Tasks are processes that run on a schedule in order to optimize the repository. With AEM as a Cloud Service, the need for customers to configure the operational properties of maintenance tasks is minimal. Customers can focus their resources on application-level concerns, leaving the infrastructure operations to Adobe.
In previous versions of AEM, you could configure maintenance tasks by using the Maintenance Card (Tools > Operations > Maintenance). For AEM as a Cloud Service, the Maintenance Card is no longer available so configurations should be committed to source control and deployed by using the Cloud Manager. Adobe manages those maintenance tasks which have settings that are not configurable by customers (for example, Datastore Garbage Collection, Audit Log Purge, Version Purge). Other maintenance tasks can be configured by customers, as described in the table below.
Must be done in git. Override the out-of-the-box Maintenance window configuration node under /libs by creating properties under the the folder /apps/settings/granite/operations/maintenance/granite_weekly or granite_daily.
See the Maintenance Window table below for additional configuration details. Enable the maintenance task by adding another node under the node above. Name it granite_TaskPurgeTask, with attribute sling:resourceType set to granite/operations/components/maintenance/task and attribute granite.maintenance.name set to TaskPurge. Configure the OSGI properties, see com.adobe.granite.taskmanagement.impl.purge.TaskPurgeMaintenanceTask for the list of properties.
Must be done in git. Override the out-of-the-box Maintenance window configuration node under /libs by creating properties under the the folder /apps/settings/granite/operations/maintenance/granite_weekly or granite_daily. See the Maintenance Window table below for additional configuration details.
Enable the maintenance task by adding another node under the node above (name it granite_WorkflowPurgeTask) with the appropriate properties. Configure the OSGI properties see AEM 6.5 Maintenance Task documentation.
A previous client of mine regularly scheduled a two-hour maintenance window each week, so they could perform upgrades and data adjustments, while allowing them to keep operating normally the rest of the time.
The problem is that the maintenance window is, by itself, a major hit to availability. A two-hour maintenance window means that the greatest availability you can offer to your customers is 98.8%. By definition, you will not be able to operate greater than 98.8% of the time.
By comparison to other online applications, 98.8% is a horrible statistic. For example, the Amazon S3 service guarantees 99.99% service availability (and has an even higher data integrity SLA). This guarantee amounts to a maximum of 61 seconds of downtime each week. In order for Amazon S3 to make this SLA consistently, Amazon can never plan to have any downtime for any maintenance, ever. Any outage at all will cause them to fail their contracted SLA.
Yes, 99.99% is a high level of availability to guarantee, and not every company needs that level for their business to thrive. But even at a lower percentage of availability, there is little room for planned maintenance windows:
Your Atlassian Cloud site is unavailable due to scheduled maintenance.Please refer to our page describing Maintenance Windows for more information.Please check Atlassian Status for any known issues.If you have any further questions, please contact our support team.
However, I'm not seeing any scheduled maintenance for today on our status page. Can you confirm when you received this message and if there is any feature/product that is not working as expected for you?
As with any cloud product that is being updated, scheduled maintenances are required to implement new changes or fix bugs with the Application. This is not different for Atlassian products, so I'm afraid you can not avoid scheduled maintenances for your Atlassian Cloud products. 2ff7e9595c
Comentarios