RADARPRINT GUIDE

Archive retention and access policy

Separate document retention, held job cleanup and backup scope.

In this guide

Three distinct data areas

Held jobs contain output awaiting release, job records describe operations, and archives hold retained document content. Deleting one does not necessarily delete the others. Build your organizational policy around this distinction.

Establishing a policy

  1. Identify which operation types will be archived and verify license scope.
  2. Agree retention needs by document type with the responsible teams.
  3. Restrict who can search and open document content.
  4. Monitor archive growth and disk capacity.
  5. Test the interaction between cleanup and backups.

Before deleting

Confirm scope and recovery options before removing production documents in bulk. Removing a document from the application does not mean it is absent from older backups. Backup retention belongs in the same policy.

Sharing support data

Start an archive investigation with job identifiers, timestamps, document type and anonymized errors. Make export of real documents subject to your authorization process. This is technical planning guidance; the responsible teams determine organization-specific retention periods.