{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/read-xprotect-archive-retention-as-a-cumulative-timeline/", "item": { "id": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/", "slug": "read-xprotect-archive-retention-as-a-cumulative-timeline", "url": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline.md", "json": "https://update.dsesecurity.com/api/v1/posts/read-xprotect-archive-retention-as-a-cumulative-timeline/" }, "title": "Read XProtect archive retention as a cumulative timeline", "summary": "XProtect archive retention includes earlier retention periods. Map each archive value to the recording timeline and check the transfer schedule before accepting a storage design.", "format": { "slug": "explainer", "name": "Explainer" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-28T23:23:31+00:00", "modified_at": "2026-10-28T23:23:38+00:00", "reviewed_on": "2026-10-28", "reading_minutes": 3, "word_count": 468, "potentially_affected": "XProtect 2026 R1 recording servers using one or more archive stages.", "dse_recommendation": "Draw the recording-to-archive timeline and verify cumulative age limits, schedules and actual retrieval in a controlled test.", "primary_source": { "name": "Milestone Systems — Storage and archiving (XProtect 2026 R1)", "url": "https://doc.milestonesys.com/xprotect/xprotect-management-client/2026r1/en/storage-and-archiving.html", "published_on": null, "authority": "doc.milestonesys.com" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

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

\n

Source fact: documented behavior

\n

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

\n

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.

\n

What the source does not establish

\n

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.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

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

\n

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.

\n
    \n
  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. \n
  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. \n
  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.
    4. \n
\n

Verification and evidence

\n

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.

\n

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.

\n

Official references

\n\n

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

\n", "content_text": "Bottom line: Treat XProtect archive retention values as positions on one recording-age timeline when planning a recording tier followed by archive stages.\nSource fact: documented behavior\nThe Storage and archiving topic is the primary reference for this XProtect 2026 R1 discussion.\nMilestone 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.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nWhat total recording age must remain retrievable for each camera class?\nWhich recording and archive stages are actually attached to those devices?\nWhat retention and size limits apply at every stage?\nHow often does each transfer run relative to its source stage’s retention period?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE 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.\n\nWrite 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.\nAdd 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.\nPilot 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.\n\nVerification and evidence\nKeep 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.\nHave 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.\nOfficial references\n\nStorage and archiving — Milestone Systems; XProtect 2026 R1.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: Treat XProtect archive retention values as positions on one recording-age timeline when planning a recording tier followed by archive stages.\n\n## Source fact: documented behavior\n\nThe [Storage and archiving](https://doc.milestonesys.com/xprotect/xprotect-management-client/2026r1/en/storage-and-archiving.html) topic is the primary reference for this XProtect 2026 R1 discussion.\n\nMilestone 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.\n\n## What the source does not establish\n\nThis 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.\n\n## Applicability questions\n\n- What total recording age must remain retrievable for each camera class?\n\n- Which recording and archive stages are actually attached to those devices?\n\n- What retention and size limits apply at every stage?\n\n- How often does each transfer run relative to its source stage’s retention period?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE 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.\n\n- 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.\n\n- 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.\n\n- 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.\n\n## Verification and evidence\n\nKeep 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.\n\nHave 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.\n\n## Official references\n\n- [Storage and archiving](https://doc.milestonesys.com/xprotect/xprotect-management-client/2026r1/en/storage-and-archiving.html) — Milestone Systems; XProtect 2026 R1.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/", "url": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-28" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Business Continuity", "item": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "ListItem", "position": 3, "name": "Read XProtect archive retention as a cumulative timeline", "item": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/#article", "identifier": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/", "url": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/", "headline": "Read XProtect archive retention as a cumulative timeline", "description": "XProtect archive retention includes earlier retention periods. Map each archive value to the recording timeline and check the transfer schedule…", "abstract": "XProtect archive retention includes earlier retention periods. Map each archive value to the recording timeline and check the transfer schedule before accepting a storage design.", "articleBody": "Bottom line: Treat XProtect archive retention values as positions on one recording-age timeline when planning a recording tier followed by archive stages.\nSource fact: documented behavior\nThe Storage and archiving topic is the primary reference for this XProtect 2026 R1 discussion.\nMilestone 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.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nWhat total recording age must remain retrievable for each camera class?\nWhich recording and archive stages are actually attached to those devices?\nWhat retention and size limits apply at every stage?\nHow often does each transfer run relative to its source stage’s retention period?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE 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.\n\nWrite 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.\nAdd 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.\nPilot 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.\n\nVerification and evidence\nKeep 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.\nHave 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.\nOfficial references\n\nStorage and archiving — Milestone Systems; XProtect 2026 R1.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-28T23:23:31+00:00", "dateModified": "2026-10-28T23:23:38+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/read-xprotect-archive-retention-as-a-cumulative-timeline/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Read XProtect archive retention as a cumulative timeline" }, "articleSection": [ "Business Continuity", "Video Surveillance" ], "keywords": [ "Business Continuity", "Video Surveillance", "Explainer", "Advisory priority" ], "genre": "Explainer", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 468, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Milestone Systems — Storage and archiving (XProtect 2026 R1)", "url": "https://doc.milestonesys.com/xprotect/xprotect-management-client/2026r1/en/storage-and-archiving.html" } } ] } }