How automatic updates are scheduled for installation
Suggest changes
PDFs
All eligible nodes within the same cluster are grouped together for automatic updates. The timeframe in which the eligible nodes are scheduled for automatic update varies based upon the priority level of the update and the percentage of systems in your environment that require the update.
For example, if 10% or less of your total systems are eligible for a non-priority update, the update is scheduled for all eligible systems within 1 week. However, if 76% or more of your total systems are eligible for a non-priority update, then the update is staggered across the eligible systems over the course of 8 weeks. This staggered installation helps to mitigate risks to your overall environment if there is an issue with an update that needs to be remedied.
The percentage of your total systems scheduled for automatic updates by week are as follows:
For critical updates
| % of systems requiring update | % of updates that occur week 1 | % of updates that occur week 2 |
|---|---|---|
50% or less |
100% |
|
50-100% |
30% |
70% |
For high priority updates
| % of systems requiring update | % of updates that occur by week | |||
|---|---|---|---|---|
week 1 |
week 2 |
week 3 |
week 4 |
|
25% or less |
100% |
|||
26-50% |
30% |
70% |
||
50-100% |
10% |
20% |
30% |
40% |
For normal priority updates
| % of systems requiring update | % of updates that occur by week | |||||||
|---|---|---|---|---|---|---|---|---|
week 1 |
week 2 |
week 3 |
week 4 |
week 5 |
week 6 |
week 7 |
week 8 |
|
10% or less |
100% |
|||||||
11-20% |
30% |
70% |
||||||
21-50% |
10% |
20% |
30% |
40% |
||||
51-75% |
5% |
10% |
15% |
20% |
20% |
30% |
||
76-100% |
5% |
5% |
10% |
10% |
15% |
15% |
20% |
20% |