Choose Where QCBM Receiver Stores Backups: PC, External Drive, or NAS
Each QCBM Receiver site connection needs a Windows-accessible destination folder for verified Recovery Packages. You can store them on the Receiver PC, an attached external drive, or network/NAS storage.
The best destination is not simply the largest disk. It must remain available and writable to the Receiver background service whenever unattended downloads run.
Option 1: Store Backups on the Receiver PC
A local internal drive is usually the simplest destination because it is available whenever Windows and the Receiver service are running. Use a dedicated folder with enough capacity for your expected Recovery Package size and retention period.
A local PC copy protects you from losing the hosting account's backup copy, but it is still on the same physical computer as Receiver. Consider an additional storage strategy if hardware failure of that computer is a concern.
Option 2: Use an External Drive
An attached USB or other external drive can provide inexpensive capacity and separation from the computer's internal disk. Keep it connected and mounted whenever Receiver is expected to download backups.
A drive-letter or device change can make the saved destination unavailable. After reconnecting or replacing a drive, confirm Receiver can still write to the configured destination before relying on scheduled collection.
Option 3: Use Network or NAS Storage
Receiver supports a Windows-accessible network/NAS folder. The important requirement is that the Windows background service can reach and write to the path without depending on an interactive desktop session.
Use stable network access and permissions appropriate for the service environment. If the NAS sleeps, changes address, or requires credentials unavailable to the service, unattended downloads can fail even though you can browse the share manually while logged in.
Receiver Tests the Destination
When a site connection is saved, Receiver requires a destination and performs a write test. This catches obvious path and permission problems before the connection is used.
That test cannot guarantee a removable drive or NAS will remain online later. Review Receiver status if a previously working destination becomes unavailable.
Configure Local Retention Separately
Receiver 1.0.10 can apply local retention rules to verified backups that it manages for the site connection. Available limits include:
- remove managed backups older than a chosen number of days;
- keep no more than the newest chosen number of backups; and
- cap QCBMR-managed backup storage at a chosen number of gigabytes.
Enabled limits work together against the oldest eligible managed backups. Receiver preserves the newest successfully verified local backup. These rules apply only to Receiver-managed verified backups; they are not a license to delete unrelated files that happen to be in the same folder.
Do Not Confuse Local and Hosting Retention
Receiver local retention and QCBM's hosting-side retention are independent. Changing one does not silently change the other. Decide how long you want a hosting copy and how many local copies you need, then configure each policy deliberately.
The optional Delete hosting copy after Receiver verifies the download setting is also separate. Use it only when you intentionally want Receiver verification to become the trigger for removing that server copy.
Test the Real Storage Path
After pairing, allow at least one real Recovery Package to download and verify. Confirm the final file exists in the expected folder and remains accessible after the Receiver desktop window is closed. For external or network storage, also test after a Windows restart.
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.