QCSB Frontend Design: Recovery and Transfers

This article shows how to customize the frontend presentation of transfer progress, Recovery Vault elements, status states, and operation feedback without changing their security behavior.

What you need to know

  • QCSB uses durable jobs but follows an immediate-first model: the request attempts ordinary work immediately, and only unfinished work remains for continuation.
  • Pro/Max/All Access can use the 5-minute Transfer Continuation task. The worker rechecks the original user’s current authority before contacting a provider.
  • 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.
  • Frontend Design changes the actual QCSB runtime interface. It has seven independently saved sections; the accepted current appearance is the default baseline.

What Recovery and Transfers controls

This section of Frontend Design changes the live QCSB frontend values for recovery and transfers. Save this section independently, then refresh the actual frontend to judge the result in context rather than treating Administrator values as a preview.

Verify the result

  • The durable job reaches the expected terminal state: completed, completed with warnings, failed, or cancelled.
  • Successful items remain successful; failed/retried items report their own sanitized outcome.
  • For a Move, the source is removed only after the destination is verified and the source has required Recovery protection.

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.