← Knowledge Base

Knowledge Base

Configuring a Copy

Updated November 7, 2026

In Hiberden, a copy is not something you create by hand. It is the result of three things lining up: a destination that exists, a policy that binds that destination as a required copy, and an archive written under that policy. This article walks that chain from start to finish.

Step 1: Add a destination

Destinations live in a shared pool. You set one up once, and any project's policy can bind to it.

The Add-destination dropdown offers four kinds:

  • Local folder: a folder on a disk in or plugged into this computer, for example D:\Archives or /mnt/archives. A share path such as \\nas\archives saved as Local folder is refused, with a pointer to NAS. See Local folder and NAS.
  • NAS: any network share this computer can reach: a UNC path (\\nas\archives) or mapped drive on Windows, or the folder where the share is mounted on a Mac or Linux, such as /Volumes/archives or /mnt/nas/archives.
  • Cloud (S3): an S3-compatible bucket in your own account. You supply the endpoint, region, bucket, storage class, and access keys; the keys are never stored in the catalog. On Windows they are kept in Credential Manager and on a Mac in your login Keychain; on Linux, Hiberden keeps them in owner-only files under ~/.hiberden/keys. Storage class defaults to STANDARD and takes any class that can be read back right away (the app suggests STANDARD, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, and GLACIER_IR); verification reads the stored archive back immediately after write, so GLACIER and DEEP_ARCHIVE are refused when you save. See Cloud (S3-Compatible).
  • Tape (LTO): binds to the connected tape drive, so there is no path to enter. Archives are written to the connected tape drive. See Tape (LTO-9 / LTFS).

Step 2: Save & test runs a real probe

When you press Save & test, Hiberden actually exercises the destination. Nothing is assumed:

  • Cloud (S3) performs a real bucket check against your endpoint with your credentials.
  • Local folder and NAS write a small marker file to the path, read it back, and delete it. If the share is unreachable or read-only, the test fails here instead of during your first archive.
  • Tape (LTO) checks that a tape drive is attached and passes when one is listed; it does not load or mount a cartridge. For real tape, use an IBM LTO drive on Windows. A tape copy is written after the save, from a disk or NAS copy of the archive, so a policy with tape needs one of those too. A tape copy the desktop app writes is checked by reading it back as it is written; after that, Hiberden 2.0 checks it again only when you restore from it, which re-hashes every byte.

Each destination shows a status badge: Testing… while the probe runs, then ● Connected or ● Connection failed. A destination you have not probed yet shows Not tested, and one missing required fields shows Not configured. The test is there to surface problems early, before your first archive depends on the destination; it is not a gate, and a policy can bind a destination whose badge still reads Not tested.

If the tape test fails with no drive on the system, the message is: "No tape drive detected. Turn on the virtual tape drive (or connect an LTO drive)." The virtual tape drive lets you exercise the tape workflow with no hardware attached.

A destination that exists is not yet protecting anything. That is the next step.

Step 3: Assign a policy and bind the destination into it

Protection is defined by the project's policy. Each binding in the policy points at one destination and means: every archive in this project must have a verified copy there. The number of destinations bound is how many times the policy stores each archive.

A new project starts without a policy, and until one is assigned its archives show a "Needs setup" badge. Under Settings > Policies, create a policy if the project does not have one yet (the one-click starter policies are created without bindings, ready for this step) and assign it to the project. Then add the destination as a binding and save. Bindings are add-only in the editor: adding one only increases protection. To require fewer copies, create a new policy and assign it to the project instead. See Policies and Required Copies.

Step 4: Archive, and the copy exists

From now on, every archive you add to that project with Add archive is written to the bound destinations (for tape, the first tape destination), with each copy tracked separately; a destination you have disabled or retired is skipped, and Add archive says why. With more than one tape destination, write the others with Write to tape in the archive's details. An archive added with Find archives… arrives with only the copy that was found (see Local Folder and NAS). After writing each copy, Hiberden reads that copy back from where it was written and re-hashes it against the recorded SHA-256 before it counts as Verified. Only then does it contribute to the archive's coverage badge, such as "Covered 2/2".

If you bind a new destination into a policy that already has archives behind it, those archives now require a copy they do not yet have, so their badges show "At risk" with the fraction of verified copies until every bound destination holds a verified copy. See Reading coverage status.

Turning off, retiring or deleting a destination

Each destination's row in Settings > Destinations has three ways to stop using it.

  • Enabled: switch it off and the destination takes no new copies; switch it on again to write there. While it is off, Add archive leaves it unticked with the reason beside it, an archive's details offer no Write to tape or Add copy here for it, and Fill missing copies passes it by. The policy still requires that copy, so an archive missing it stays short of its required copies until you enable the destination or give the project a policy without it.
  • Retire…: Hiberden stops writing to the location and marks every copy stored there Destination retired. Nothing on the disk, share, bucket or tape is touched, and the copy records stay in the catalog, so you still know where the bytes are. A location in a policy that a project uses cannot be retired: give those projects a policy without it first. Once retired, the destination is no longer offered when you assign a destination to a policy.
  • Delete…: shown only for a destination that holds no copies, is in no policy, has no unfinished work, and is not the catalog backup location. Hiberden forgets the location and its finished activity, and for a cloud destination removes its access keys from this computer. Nothing on the storage is touched. A destination that holds copies or is in a policy keeps Retire… instead.

Where to go next