Define the usable backup voltage window
An RTC backup interval begins from a charged condition and ends when the available voltage no longer supports the intended backup operation. These endpoints define the useful part of the discharge process. A capacitor can still retain charge after that endpoint, but retained charge is not the same as useful supply voltage for the backed-up circuit.
The starting voltage and minimum usable endpoint therefore belong together. Comparing a reserve described from one starting state with a requirement that assumes another starting state changes the question being answered. Likewise, an endpoint chosen for a different circuit does not automatically describe the interval available to the intended RTC or memory-retention function.
The Eaton discussion treats these voltage terms as part of the backup budget, alongside capacitance and current. This provides a more useful starting point than asking whether a capacitor has a large enough nominal value in isolation. Define the voltage window before comparing reserve descriptions, so the comparison concerns the portion of stored charge that the intended backup function can use rather than the existence of residual charge alone.
Keep capacitance as the charge-reserve coordinate
Capacitance supplies the charge-reserve coordinate of the budget. It describes a different property from the current that leaves the capacitor during backup. A reserve can be larger while the discharge demand is also larger, so neither property should be allowed to stand in for the other when describing the expected backup behavior.
Consider two explanations that both mention a low leakage current. That shared description does not tell you whether they begin with the same reserve or use the same voltage window. Conversely, equal nominal capacitance does not establish an equal usable reserve when the charged starting condition and minimum useful endpoint are different. The budget needs these terms together because they describe different parts of the discharge process.
This makes capacitance a positive engineering question rather than a label to append after a leakage comparison. Establish what reserve is being discussed, then connect it to the defined voltage interval and drain. The resulting description can explain why a capacitor value is relevant without copying an example calculation or presenting a numerical hold time. It also keeps an RTC backup decision distinct from a generic discussion of leakage as a component property.
Include load and leakage in total discharge current
During backup, the application load is not the only current represented in the Eaton budget. The capacitor leakage contributes to the discharge demand as well. The two terms have different origins: one supports the backed-up function, while the other reduces the stored reserve without performing that function. Both matter to the same discharge interval.
This distinction prevents an apparently complete load specification from becoming an incomplete budget. An RTC current description can accurately describe the circuit and still omit a capacitor contribution. Equally, a capacitor leakage entry describes only that contribution; it does not establish what the connected backup circuit draws. Combining the responsibilities makes the current side of the budget explicit.
Load current and capacitor leakage draw from the same stored-charge reserve, even though only the load supports the backup function. Associating both contributions with that reserve avoids presenting either one as the total discharge demand. Omitting a contribution changes the budget without changing the capacitor's nominal label. The relevant comparison therefore keeps both current terms with the same voltage window and starting condition, rather than substituting a leakage ranking for a complete backup scenario.
Retain charge conditioning with the leakage basis
A backup calculation assumes a starting condition, but a capacitor reaches that condition through charging. The Eaton material links the leakage and hold-up discussion to charging-time context. A current description obtained under one conditioning basis should not be detached from that basis and combined with a different assumed charged state.
This is a separate issue from reserve size and discharge demand. Capacitance identifies the reserve coordinate; load and leakage describe how it is depleted. Charging context concerns the state from which that depletion begins and the basis of the leakage description. A proposal that names the first terms but leaves its initial condition implicit can appear more directly comparable with another proposal than it really is.
Retain the charging or conditioning statement alongside the values it qualifies. This lets the reader distinguish a defined backup scenario from a component description assembled from unrelated conditions. It does not require transferring an example duration, a competitive curve or an ageing assumption into the application. The useful outcome is a budget whose starting state, usable window, reserve and drain all refer to the same stated scenario.
Sources and further reading
Qualitative use of the named Eaton RTC and memory-backup material. Numerical examples, competitive curves, lifetime predictions and guaranteed hold times are excluded.