Full Storage Not Found - How I resolved this error

Great to hear you solved this and sharing to the community.

Also, to add, SureBackup is worth implementing as it should be able to pick up when the chain has corruption creeping in.

Hey all,

While the OP strategy will work, this happens typically because of some issues within the database; the most common reason is that during retention, something breaks the SQL or VBR (or both) servers mid operation and we end up with a situation in the DB that shouldn’t exist: incremental backups that don’t have a full backup at the start of their chain.

There are a few other situations with such linking problems, but it’s not worth listing them.

The good news is that usually this is a pretty fast fix with a Support Case. Open a case, export logs as per https://veeam.com/kb1832 and use the 1st radio option and select the affected job(s). You can ctrl and/or shift + click to select multiple jobs.

You will also want to add a copy of your Veeam Configuration Database if your org policies allow exporting of that data: https://www.veeam.com/kb1471

Mention that you read on the forums it _might_ be related to issue 377509; your Engineer should be able to find appropriate steps. This is a general fix that can allow retention to clear those invalid links in the DB, but it’s not a panacea for all instances when you might see this, so just be prepared that we may need more research in some cases, but typically this can be solved without losing backups.

But if you’re okay just starting a new Backup Set, then just follow the opening post, Remove from Configuration for the affected backup, and run the job (prepare for an Active Full!)

Hello @bp4JC 

Did you configured Backup job maintenance settings:

https://helpcenter.veeam.com/docs/backup/vsphere/backup_job_advanced_maintenance_vm.html?ver=120

Hello, i have the same error message on one backup jobs and two BCJ but i still have a support case opened. V12 Last CP;

• Only concerned 10% of VMs in the jobs
• Rescan SOBR without success
• Can’t run a new activefull
• one week after upgrade to the new format
• restore test are ok before the error appeared

I will share to the community the solution when I have solved the problem.

When you get a resolution from Support, I recommend sharing their solution here @A.Venturi , if you don’t mind….will help others out who have the issue. 😊

Hello,

My case is still in progress about this, investigation are engaged by R&D.

could you check when it happens? After a backup chain was complete? Does it concerns backup jobs or backup copy jobs maybe both?

What is the status from background retention?

Background Retention - User Guide for VMware vSphere (veeam.com)

Could you check if some errors, is there an orphaned vib when you browse your jobs and sort it by date?

Unfortunately, if you are in the same boat as me. You will probably need to remove orphaned vib by cli, then rescan sobr and forget all unavaiable backups...

I’d suggest you take a look at this with support then or review with a Veeam Partner (assuming you’re an end customer), that’s not a normal error message and could indicate issues within your environment. You don’t want this error when you need to perform a recovery...

yep that’s correct, you get best effort access to support when Veeam Support have spare capacity.

I’d suggest, make a new topic here, detailing your environment, and the problems you’ve got, and then we can get into it properly, it will also help get fresh eyes on your issues vs this old topic.