Synology backup repository recovery

A Synology Active Backup for Business repository needs its backup data and catalog metadata preserved together.

Active Backup for Business stores deduplicated backup data with package metadata that tracks devices, versions and restore points. A moved shared folder, package reinstall, storage-pool failure or incomplete replication can leave data present but not relinkable.

Understand the symptom

Repository recovery depends on catalog-to-chunk consistency, not just visible backup folders.

WHY

What is happening

The catalog maps protected machines, restore points, deduplicated chunks and task identities. Recovery must match repository generation, package version, volume state and any replicated copy. A folder-level copy that omits metadata or snapshots may retain chunks without enough structure to assemble a restore point.

What you may see

Symptoms that change the recovery path.

01

Relink cannot find a valid repository

The selected folder lacks expected metadata or belongs to another repository generation.

02

Tasks appear without versions

Catalog entries and stored chunks no longer align.

03

Restore portal fails to browse

The package cannot resolve backup indexes or metadata.

04

Problem followed pool repair or migration

Some package data, shared-folder content or permissions may be from different points.

Protect the source

Actions that can make the situation worse.

01

Package reinstall can initialize new metadata

A new database may overwrite or obscure the previous catalog.

02

Cleanup can delete unreferenced-looking chunks

Broken catalog references do not mean the underlying chunks are disposable.

03

NAS rebuilds alter source storage

RAID or SHR repair can overwrite metadata and stress remaining disks.

Do this now

Safe steps before evaluation.

01

Stop backup and retention tasks

Pause new jobs, cleanup, relink loops and package upgrades.

02

Preserve the complete NAS state

Keep all member disks by bay and image or snapshot the repository volume when possible.

03

Collect package context

Save DSM and package versions, task exports, logs, repository path, permissions and recent changes.

04

Retain every alternate copy

Protect snapshots, Hyper Backup, replicated folders and offsite copies from automatic retention.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Repository inventory

NEPFOSYS maps package metadata, indexes, chunk data, tasks and alternate copies.

02

Protected relink or reconstruction

Compatible DSM and package states are tested without changing the source repository.

03

Restore-point validation

Priority machines, dates and files are assembled and checked on ordinary storage.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can Active Backup data be restored from the shared folder alone?

The repository also depends on catalog and package metadata. A complete preserved repository has a much better chance of producing valid restore points.

Should I reinstall Active Backup for Business?

Not before preserving package and repository state. Reinstallation can create new metadata or change compatibility.

Can snapshots help?

Yes, if they capture a consistent repository and package state. Preserve multiple snapshots rather than rolling the only volume back first.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case