Purge a Protected Item and Keep Its Audit History

This article explains how to permanently remove only the protected recovery object after confirmation while retaining the historical audit record of the original event and purge action.

What you need to know

  • Basic includes Local storage and the first active Workspace. Pro adds FTP/SFTP, multiple Workspaces, advanced permissions, and background continuation. Max/All Access adds Google Drive, OneDrive, Private Connections, Recovery Vault management, and bulk operations.
  • A plan gate decides whether a feature exists at the current Effective tier. Joomla access and QCSB permission rules separately decide whether a particular user may use that feature.
  • Recovery protection is a safety boundary for destructive operations and is separate from Max/All Access Recovery Vault management. QCSB may create protected copies even when the current user cannot open the management UI.
  • Delete, replace/overwrite, and destructive move are blocked when the required protected copy cannot be created and verified.
  • QCSB records durable audit events for important actions and results, but 1.01.08 intentionally does not expose a standalone Administrator Activity Log tab.

How to do it

  1. Open the Recovery Vault and verify you selected the correct protected item.
  2. Click Purge and confirm the permanent-deletion warning.
  3. QCSB removes the protected Recovery object and marks the Recovery item purged.
  4. The purge cannot be undone through the Recovery Vault, so download/restore first if the protected content may still be needed.
  5. Audit history remains after purge so the historical destructive/recovery action is not erased.

Verify the result

  • The Recovery item/state matches the action you performed.
  • A restored/downloaded item matches the expected content and destination.
  • Purge/cleanup does not erase the historical audit trail.

Important limits and mistakes to avoid

  • Do not bypass failed recovery protection to force a destructive action. The block is intentional safety behavior.

Troubleshooting

  • If a destructive action is blocked because recovery protection failed, repair recovery storage/capacity first; do not bypass the protection boundary.

Community Discussion

For practical QCSB workflows and discussion with other Joomla site owners, visit the QC Storage Bridge Community. For private support, bug reports, account-specific entitlement issues, or feature requests, use the QuantaCade support system.