Create a Local or Server-Path QCBM Export Destination

A Local / Server Path destination copies the canonical QCBM Recovery Package to another filesystem path that the Joomla server can access. The target can be another local disk, a mounted storage volume, or another server path exposed to PHP, but it should be independent enough from Managed Private Storage to provide a meaningful second copy.

Off-site export destinations require Pro, Max, or All Access. Pro includes one active destination; Max and All Access can manage multiple destinations.

Choose a Suitable Destination Path

Before adding the destination, choose a path that:

  • is writable by the PHP/Joomla process;
  • has enough capacity for the Recovery Packages you plan to retain;
  • is not the same managed Backup Set storage location;
  • is preferably outside the public website document root;
  • stays mounted/available whenever scheduled or automatic exports may run.

A mount that disappears intermittently can pass setup today and fail later during an automated export, so monitor the underlying storage as well as QCBM.

Add the Destination

  1. Open Components > QC Backup Manager > Settings.
  2. Find Export Destinations.
  3. Click Add New.
  4. Enter a clear Destination name.
  5. Choose Local / server path as the destination type.
  6. Enter the Local/server path, for example /home/account/qcbm-exports.
  7. Choose whether the destination should be enabled/published and whether it should be the default.
  8. Save the destination.

QCBM Validates the Path When You Save

A Local / Server Path destination cannot be saved without a destination path. QCBM resolves the configured path and validates/prepares it before accepting an enabled destination.

If the target cannot be prepared safely or does not meet the local export-path requirements, QCBM returns an error instead of saving an apparently active destination that cannot receive backups.

Understand Enabled and Default

An enabled/published destination is eligible for export actions when its provider configuration is valid. The default destination is the primary target used by Export to Default and by current automatic Profile export.

QCBM maintains one default destination. Pro can enable one off-site destination at a time; Max and All Access can enable multiple and still designate one default.

Test the Destination

  1. Return to the Export Destinations table after saving.
  2. Run the destination's Test action.
  3. Confirm QCBM reports Local destination is writable and ready.

The test creates a small timestamped text file in the export path, confirms it exists and is readable, and removes it. A passing test proves basic write/read/delete access at that moment; it does not prove there will always be enough disk capacity for a large Recovery Package.

Run a Real Backup Export

After the test passes, use a complete verified Backup Set in Backups > Backup History and export it to the destination. QCBM copies the canonical Recovery Package to the configured path and records/validates the export separately from the local Backup Set.

Confirm the copied Recovery Package exists on the intended storage volume and is included in whatever independent protection strategy you use for that volume.

Avoid a False “Off-Site” Copy

A different folder on the same physical disk as the production website protects against accidental deletion from Managed Private Storage but does not protect against disk failure, server loss, ransomware at the same host, or account-level compromise.

For disaster recovery, prefer a genuinely separate mounted device, backup server, NAS, or another supported remote/cloud destination.

If the Destination Later Fails

Re-run the Test and check filesystem permissions, mount availability, free space, path changes, and hosting restrictions. A destination can become unusable after it was originally saved if the underlying server environment changes.

A failed export does not automatically invalidate the local verified Backup Set; preserve the local package while correcting the destination.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.