Read XProtect archive retention as a cumulative timeline

Bottom line: Treat XProtect archive retention values as positions on one recording-age timeline when planning a recording tier followed by archive stages.

Source fact: documented behavior

The Storage and archiving topic is the primary reference for this XProtect 2026 R1 discussion.

Milestone says the next archive’s retention period must be longer than that of the current archive or recording database. The archive value includes all retention stated earlier in the process. Archiving must occur more frequently than the retention period to avoid losing data before transfer. The topic also says an archive can begin overwriting old recordings when its retention time or size limit is reached.

What the source does not establish

This 2026 R1 storage topic describes configuration behavior, not an organization’s required retention or proof of available footage. Cumulative time settings do not establish sufficient capacity, completed transfers or continuous, playable recordings. Keep those acceptance questions separate from interpreting the fields.

Applicability questions

• What total recording age must remain retrievable for each camera class?
• Which recording and archive stages are actually attached to those devices?
• What retention and size limits apply at every stage?
• How often does each transfer run relative to its source stage’s retention period?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends making the timeline explicit before entering or approving values. Use one representative recording timestamp as the origin and draw the recording database followed by every archive.

1. Write the intended end age beneath each tier. Label later values as cumulative endpoints and have a second reviewer reconcile them with the operational retention requirement. Avoid approving a design from a list of tier durations without that shared origin.
2. Add each archive schedule to the same drawing. Ask whether a recording can wait for its next scheduled transfer and still remain within the source stage’s age limit. Review size limits and available capacity alongside the timing decision.
3. Pilot the proposed chain with disposable recordings and approved test settings. Record when each sample is captured, becomes eligible for transfer, appears in the next archive and remains retrievable. Investigate differences before extending the design to other camera groups.

Verification and evidence

Keep the timeline, device-to-storage assignments, configured age and size limits, archive schedules and dated transfer observations. Retain retrieved samples near each transition and the final required boundary, with enough context for another administrator to repeat the check.

Have the recording owner approve the interpretation and measured result separately. Recheck after adding an archive or changing a schedule or limit. These are DSE acceptance recommendations, not a claim of achieved retention or a substitute for testing the oldest available recording.

Official references

• Storage and archiving — Milestone Systems; XProtect 2026 R1.

Source review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.