'Backup Repository' is not synchronized with the DB. ERROR

[atike]

Hi All,

Every now and again, probably about once a week I get a failure email through from Veeam saying the following =

"Error: Cannot proceed with the job: existing backup meta file '\\****\veeam_backups\Daily Backup\Daily Backup.vbm' on repository 'Backup Repository 4' is not synchronized with the DB. To resolve this, run repository rescan"

I run the rescan and restart the job and the backup continues to run OK for a few more days and then this will happen again...

Can any one shed some light on why this is happening and how I can fix it please ?


Regards,
Alex

[foggy]

Alex, please contact technical support for logs review, as it is advised to do with all technical issues (right when you click New Topic). Please provide your support case ID number, if you want to keep this thread open. Thanks.

[atike]

I have contacted technical support, and the case ID number is 00827484

[ivoneta]

I'm getting this error frequently as described above, will also log a job.

[veremin]

Hi, Tom, what kind of storage are you using as a backup repository? Is dedupe one by any chance? As I can see from the case, the support team has just provided a hotfix for Alex and now is waiting for his response.

[nebojsa]

I have a similar situation, using NetApp deduplicated CIFS shares as backup repositories, Veeam 8.0.0.917

[foggy]

Please also contact technical support to verify your setup and apply hotfix, if applicable.

[nebojsa]

Is there a chance for this hotfix to make its way to the next patch release? If yes, I can wait for that.

[veremin]

Is there a chance for this hotfix to make its way to the next patch release?

Yes, chance is there. I'd still recommend contacting support team to confirm whether the issue you're experiencing is similar to the described one and whether the hotfix addresses it. Thanks.

[kkuszek]

I am experiencing the same issue on some of my backup jobs using dedupe type right now, but not all of my jobs with dedupe enabled. Sounds like the hotfix needs to make it's rounds

[foggy]

Kurt, have you already contacted support to request the hotfix?

[kkuszek]

I have not yet, I just googled the error and found the thread this morning. I will be reaching out.

[TvT]

Try this.

Rescanning Backup Repositories
Home topic > Administration > Setting Up Backup Infrastructure > Configuring Backup Repositories >

Backup repository rescan may be required, for example, if you have archived backups from a backup repository to tape and deleted backup files on the backup repository or you have copied backups to the backup repository manually and want to work with them in Veeam Backup & Replication.

To rescan a backup repository:

1.Open the Backup Infrastructure view.

2.Select the Backup Repositories node in the inventory pane.

3.Select the necessary backup repository in the working area and click Rescan Repository on the ribbon or right-click the necessary backup repository in working area and select Rescan repository.

[foggy]

Thanks for the tip, however this did not help the OP in the long term, so I'd still recommend to ask for our technical team assistance.

[cliljest]

I'm getting this error on two of my backup jobs. All other backup jobs are successful. I have re-scanned the backup repository and tried the failing jobs again but getting the same results. I am on version 8.0.0.2021. Case #00921717

[veremin]

Are those jobs pointed to dedupe repository? Also, within the existing case you might want to refer to the cases mentioned here to help support engineer find solution faster. Thanks.

[cliljest]

These jobs are not pointed to a dedupe repository. I will mention these cases to the support engineer.

[cliljest]

The case engineer did not think the previous case in this thread would apply because the fix for it was for version 8.0.0.917 and I am on version 8.0.0.2021. He suggested deleting the backup job, re-scanning the repository, creating a new backup job and mapping them back to the original restore points. I did that and it failed. Then I decided to delete the jobs, rescan the repository, create new backup jobs but not map them to the original restore points. The new jobs ran successfully. Still not sure what caused them to get out of sync with the DB though.

[veremin]

What about recoverability of those restore points? Have you checked that?

[theprojectgroup]

I get this error from all my endpoint clients using the B&R repository. (Current version of endpoint, B&R has Update 2, will install Update 3 this night)

[foggy]

Florian, have you contacted technical support already?

[theprojectgroup]

not yet, is there a hotfix?
just installed update 3 and reboot the repository server.

[foggy]

Our engineers will be able to confirm whether you're seeing similar issue and provide the hotfix, if it is available.

[rsargeant]

Hi there,

This is still an on-going problem (even in v9) when you rotate USB disks and choose NOT to use a repository with the Rotated Hard Disk option. The
problem seems to occur when the incorrect .vbm file is present on the plugged in USB disk, probably because the disks haven't be changed at the
correct time (e.g daily on specific days). What is a pity is Veeam doesn't have the option to auto-rescan the DB, because this would then allow the job
to run successfully. We have many clients running Veeam and the only option is to initiate a manual rescan after the failed Backup job. The reason
we prefer not to use the Rotated Hard Disk option is this creates a fresh VBK if the wrong disk is plugged and we loose the roll-back history.

I believe an auto-rescan DB or rescan DB via a PowerShell command would be a useful addition.

Cheers,

Richard.

[foggy]

Richard, could you please describe your scenario in more detail, as I'm not quite sure in how you're rotating disks without the rotated option? Do you have different jobs for different disks that start on specific days only? What do you expect to get on the disk if the wrong job is started when it is plugged in?

[cardendave]

Hi

I sometimes get a error like this: 08/07/2016 20:45:59 :: Error: Cannot proceed with the job: existing backup meta file 'NAS.vbm' on repository 'NAS' is not synchronized with the DB. To resolve this, run repository rescan

When this occurs can we please make it rescan the repository automatically and then try again?

Thanks

Dave

[Vitaliy S.]

Hi Dave,

Thanks for the FR, actually rescan procedure is performed on daily basis and usually you shouldn't see these messages. Can you please tell us what actions do you perform that lead to this message?

Thanks!

[caleone]

Hi all.

Same trouble. Veeam Backup & Replication 9.0, Hyper-V with 3 virtual machines and backup plan job with 2 external USB drives. Problem seems to be that the program isn't rescanning the backup repositories. If I do it manually the job gets successfull for one day, but when I change the USB drive the next day, the job fails. Error message says:"Cannot proceed with the job: extisting backup meta file 'XXXXXX' on repository 'YYYYY' is not synchronized with the DB".

Any suggestions?

Thanks.

[foggy]

Carlos, have you contacted support already with this?

[caleone]

Hi foggy.

Yes I did. And they sent me some links which were really useful. Today I confirm if finally everything is working properly.
All responses were very quick and concise.

Thanks for all.