Recently I had to return my OOTBI node. Therefore, I will show you how to remove a Repository from Veeam Backup and Replication. These are some similar guides on this topic “Fix broken Repository Path in Veeam Scale-Out Backup Repository“, and “how to fix missing path and delete a Veeam Backup Repository“. A repository in Veeam Backup & Replication acts as a managed storage target that stores backup files, backup chains, metadata, restore points, and other backup data generated by backup, replication, and copy jobs.

You can configure repositories on local storage, network-attached storage (NAS), deduplication appliances, hardened Linux servers, or object storage platforms. These repositories store and manage protected workloads as the primary backup location.

Please see how to setup DS923+ Synology NAS as a Backup Repository for VBR, and how to setup iSCSI Target and Storage LUN on Synology DS923+ for VBR.

Repository Rescan

Before removing a repository from Veeam Backup & Replication, perform a repository rescan or configuration database resynchronization to validate its current state. This step becomes particularly important when the storage target is unexpectedly disconnected, or no longer reachable.

This process allows Veeam to validate the current state of the repository, synchronize backup metadata, and update internal inventory records within the configuration database. The rescan operation helps identify unavailable backup chains, stale metadata references, and unresolved repository dependencies that may still exist within backup jobs, scale-out backup repositories (SOBR), capacity tier mappings, or background maintenance tasks.

By refreshing repository state information before removal, the likelihood of residual configuration inconsistencies, orphaned backup references, or job-related errors appearing later within the backup infrastructure.

In environments using object storage, hardened repositories, or SOBR capacity/archive tiers. This synchronization step becomes even more important, because Veeam maintains metadata indexes and block mapping information locally within its configuration database.

Updating this information before deleting the repository helps ensure a cleaner infrastructure removal and enables more predictable backup management operations afterward.

Please see Can’t Sign In: Domain Unavailable 169.254 IP Address Issue, how to automatically resolve errors associated with failed dependencies, and How to clean packages lying around in Linux.

Perform Rescan Operation

To proceed, navigate to Backup Infrastructure and select Backup Repositories. Next, click Rescan on the affected repository. As shown below, the repository appears as unavailable in this example. I intentionally configured this state in my lab environment because I already removed the underlying server.

If your repository is unexpectedly showing as unavailable. First perform proper troubleshooting and due diligence to identify the root cause. Before proceeding with removal or cleanup operations in Veeam Backup & Replication.

Note: To re-emphasize, a rescan is not always strictly mandatory before removing a repository. But recommended as discussed due to being disconnected unexpectedly etc. As you can see below, the rescan is in progress.

Please see “The web application “Administration Portal” cannot be enabled because one or more software dependencies are not met, and how to fix The trust relationship between this workstation and the primary domain failed.

Rescan Status “Failed to Rescan Repository”

During the rescan, Veeam gathers (enumerates) information about the backups currently available in the repository and updates the inventory accordingly.

The warning and failed synchronization messages shows that Veeam was trying to reconcile the object storage repository entry that is unavailable. This is the reason I perform this rescan to reveal this stale state.

Under the Inventory section, click on the warning entry to review the rescan results. As shown below, the rescan operation failed because the OOTBI repository is no longer reachable. In my case, I expect this behavior because I have already intentionally removed the underlying server from the lab environment.

Since I know the repository is permanently unavailable, I can safely proceed with its removal. However, Veeam Backup & Replication will not allow you to delete a repository. Especially when there are active jobs, backup copy jobs, SOBR extents, or other backup components still reference it.

Therefore, you must remove or update any existing dependencies in the corresponding job settings before you can cleanly delete the repository from the backup infrastructure.

If you wish to attempt the removal as shown below, it will fail due to the references.

We are already aware that this will happen. So click to confirm object storage repository removal.

Please see Remove Microsoft Exchange Server: Using ADSIEdit Tool, NSlookup Displays Error: UnKnown Default Server, and how to Update Global Address List: Fixing the “Not Recognized” Error.

Reveal Dependency to unavailable Repository

As you can see below, there are references pointing to this storage. When you click on Yes, it will fail.

As you can see, one of my DC backup is tied to this storage. This job is no longer needed, and I have the option to delete or edit the job and specify a new repository for the VMs.

Please see Hub Transport Server: Resolving ‘Failed to Reach Running Status’, how to enable Virtualization in Windows: Fixing VirtualBox’s 32-bit Option, and Domain Name System Protocol: Client Registration Issue.

Delete Repository in VBR

When the above is done, please proceed to delete the repository once again.

As you can see, we have successfully deleted the backup repository from my backup infrastructure. By the way, here is a guide on “Object First OOTBI Appliance Unboxing and Quick Setup“.

Note: After the repository is removed. Check for warning to confirm Veeam no longer tries to rescan or synchronize this repository. Also verify that the repository no longer appears under the backup infrastructure tree. And that no backup jobs report missing targets as performed above.

If any backups remain in the configuration database as unavailable. Remove only the broken references through Remove from Configuration. This depends solely on whether you want to keep the files or delete the records

I hope you found this guide very useful on how to remove a Repository from Veeam BAcckup and Replication. Please feel to leave a comment below.