How do I reconnect Hyper Backup to an existing .hbk backup without starting a new archive?

QUICK ANSWER

Use Relink to existing task when the original repository and destination are compatible. Relinking associates a task with existing backup history; it does not turn an unrelated folder into a valid archive.

Applies to: Hyper Backup data-backup repositories; source and destination versions must support the existing backup format.

Work through these checks

  1. Preserve the complete repository and its original directory name. Record the old task’s destination type and keep encryption passwords or key files safely available. Do not edit individual files inside the .hbk archive.
  2. Ensure the old task will no longer write to that repository. One repository should be linked to only one task. Check that the new NAS can reach the original destination using the intended account.
  3. In Hyper Backup, choose + > Data backup task, select the matching destination type, then Relink to existing task. Select the existing repository and follow the wizard without choosing a new empty archive.
  4. Review the source folders, application selections, schedule and retention policy before allowing a new backup. If the repository does not appear or the format is rejected, retain it and collect the exact message.

Confirm the result

Browse an older version, restore a small file to a separate location, then run and verify the next backup. Keep the earlier recovery copy until these checks succeed.

Before going further: Do not rename the archive, downgrade Hyper Backup or delete an unrecognised repository. Encryption keys cannot be replaced by a DSM login password.

If you need help

Include these details in your ticket: Old/new Hyper Backup versions, destination type, repository visibility and the exact relink error.

Updated 261107

Please Wait!

Please wait... it will take a second!