Re-Archiving Android Capture Data

Prev Next

Re-Archiving is a feature designed to retrieve historical data that was not archived due to specific circumstances. This process ensures that all critical data is accounted for, supporting compliance and investigative needs. Re-Archiving is especially useful in addressing gaps caused by delays in application installation, technical issues, or intentional actions to bypass archiving.

Re-Archiving ensures that:

  • No critical data is lost due to archiving gaps.

  • Compliance standards are met, even in challenging scenarios.

  • Administrators have a streamlined way to recover missed data for defined periods.

Types of Re-Archiving

Re-Archiving can be performed in two ways:

  • Manual Re-Archiving: This is a user-initiated process where administrators must request support to recover specific data for selected users and date ranges. The selected date range can span a maximum of six months. For example, if the start date is 02 August 2024, the end date must be within the six-month period, such as 01 February 2025. For more information, see Manual Re-Archiving

  • Automatic Re-Archiving: This is a system-triggered process that automatically addresses data gaps during specific events, such as new installations or re-installations of the Android Capture application. For more information, see Automatic Re-Archiving

Difference Between Manual and Automatic Re-Archiving

Feature

Manual Re-Archiving

Automatic Re-Archiving

Trigger

Admin request

Automatic based on installation/re-installation

Effort

Requires admin to contact support

No admin intervention required

Use Case

Specific recovery for defined date ranges

Proactive recovery to fill gaps

Setup

No prior setup required

Must be enabled during onboarding

Timeline

Up to 24 hours after request

Up to 24 hours post-trigger