What the evaluation and Horcrux 5 include
| Access | Backup Location capability |
|---|---|
| Limited evaluation | One local Primary location, with manual backups for the evaluation account. |
| Horcrux 5 purchase | Additional complete local locations, SFTP and Amazon S3 locations, automatic backups, and the option to make any supported location Primary. |
The full purchase and discounted upgrade unlock the same features permanently. Visit Pricing for eligibility and prices.
Choose locations that fail differently
| Location | Use it for | Important details |
|---|---|---|
| Local Folder | Internal storage, an external drive, or a mounted network folder. | The folder must be available when Horcrux writes to or reads from it. The included Primary is local. |
| SFTP Server | A server or NAS reachable over encrypted SFTP. | Setup shows the server’s host-key fingerprint for confirmation. Horcrux remembers that identity and refuses a later connection if it changes unexpectedly. |
| Amazon S3 | A customer-owned AWS bucket and optional folder. | Use credentials restricted to the chosen bucket and folder. Horcrux targets Amazon S3 rather than arbitrary S3-compatible services. |
Remote passwords and access keys stay in Apple Keychain. Backup Locations receive saved messages, backup history, and portable recovery information, but not email credentials, local search indexes, Jobs, or logs.
For example, an external drive protects against internal-disk failure, while an off-site SFTP or S3 location can also protect against loss of the Mac and nearby storage. Horcrux does not replace a provider’s own access controls, versioning, or billing safeguards.
Add or reuse a Backup Location
The first account setup asks for at least one Backup Location. Its first local location becomes Primary. To add another later, open Manage Account → Backup Locations → Add Backup Location.
- Choose a location under Recent Backup Locations, or set up a new Local Folder, SFTP Server, or Amazon S3 location.
- Complete the connection check. Horcrux inspects the selected folder, server, or bucket before saving the account binding or writing new data.
- If an older backup needs current storage organization or integrity information, complete the resumable preparation step.
- Let the initial copy finish. Its progress and result appear in Jobs.
A saved location profile can be reused by more than one account. Each account remains isolated in its own backup folder, and the credentials for the email accounts never become part of that shared location.
Primary is the preferred copy, not the only usable copy
Every account has exactly one enabled Primary Backup Location. Horcrux tries it first when browsing, restoring, exporting, migrating, or building a message-content index. In Horcrux 5, Primary can be local, SFTP, or Amazon S3.
| Control | What it does |
|---|---|
| Keep Updated | Includes an additional location in future backup runs. Primary always stays enabled. |
| Make Primary | Copies and verifies the current backup at that location before switching the preferred read role. The former Primary remains a complete location. |
| Copy Now | Brings one additional enabled location up to date without downloading the email account again. |
| Change | Moves a local Backup Location after copying the current backup to the new folder. |
| Remove | Stops using the location for this account. Existing files are not deleted, and a profile still used by another account remains available. |
A Primary location cannot be disabled or removed until another enabled, complete location becomes Primary.
One backup run publishes one revision everywhere
A location records the revision as complete only after its saved mail, backup records, and completion information can be read back. The new revision becomes available after at least one location completes it. A failure elsewhere produces its own Job and a location that can be caught up later.
- If one location succeeds and another fails, the successful copy remains valid and the account can use the new revision.
- If no location completes, Horcrux keeps the previous committed revision visible and preserves reusable pending work.
- Copy Now can publish the current revision to a lagging location without deliberately downloading all the mail again.
- Automatic Backup History cleanup waits until Horcrux can prove it will not remove the last healthy copy.
Horcrux can read across locations automatically
Primary is tried first. If it is unavailable, incomplete, or missing a requested saved message, Horcrux tries enabled local additional locations and then remote additional locations. After an operation finds a working location, it keeps using that location until it fails, then continues through the remaining candidates.
This fallback applies when Browse opens a message, Migration reads a saved backup, Horcrux restores or exports mail, and content search reads message bodies. The catalog in the Horcrux Library supplies message and mailbox information; the selected Backup Location supplies the durable message bytes.
Horcrux records the location it used in the interface or Job log. Remote fallback can be slower and can use metered or billable bandwidth.
Recover Missing Messages checks every location before the provider
If verification finds that a committed backup is missing saved message files, open Manage Account → Maintenance and choose Recover Missing Messages.
- Horcrux checks the configured Backup Locations for each missing message, starting with Primary and preferring local copies before remote ones.
- When another location has the message, Horcrux verifies its recorded size and SHA-256 integrity value before accepting it.
- Only messages that no valid Backup Location can supply are requested again from the original email account.
- Horcrux rebuilds the affected indexes, verifies the repaired backup, and records how many messages came from Backup Locations or the original provider.
This order matters when a message has already disappeared from the live email account: another complete location may still hold the exact saved copy. If neither another location nor the provider can supply valid bytes, Horcrux reports the individual failure instead of hiding it.
An existing location can rebuild local working data
There is no separate “import existing backup” command. Add or reuse the Backup Location normally. Horcrux inspects it before attaching it and follows conservative account-matching rules.
- Backups for other accounts at the same location are ignored and left untouched.
- A completed revision must match the exact account and pass its immutable backup-record checks.
- If the local catalog is empty, Horcrux rebuilds it from the newest valid matching location.
- If the catalog already has history, a newer same-account history can replace it transactionally; an older location is brought up to date normally.
- Pending catalog work in the Horcrux Library is protected and is not replaced by an attached location.
If Horcrux finds same-account files but cannot verify a complete compatible revision, it refuses to attach the location. Repair that copy or choose another location.
Horcrux 5 ownership does not expire
Local, SFTP, and Amazon S3 Backup Locations remain available permanently after the first successful one-time or annual-supporter payment. Existing files stay on storage you control and remain available for browsing, verification, export, migration, and recovery.
- Canceling an annual-supporter plan ends Priority Support after its paid period but never removes purchased features.
- A future paid major-version upgrade does not revoke features purchased with Horcrux 5.
- Horcrux does not silently delete, reassign, or lock away an existing Backup Location.