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

[Technogod]

I've run repository rescan. Same symptom. This is a backup copy job of a VAW backup that is failing.

[veremin]

What is your support ticket ID for this issue?

[Technogod]

Case # 02298832

[Technogod]

I deleted and recreated the backup copy job. This fixed the problem. You can close the case. I removed the backup so B&R could start fresh. I was rebooting the server multiple times troubleshooting another issue which may have caused the problem.

[veremin]

Sometimes such workarounds including job re-creation or execution of active full backup give only a temporary solution, not fixing the underlying root cause. So, I'd recommend you monitoring infrastructure closely and re-opening the ticket in case the issue comes back. Thanks.

[danswartz]

Before I get Support roped in here, I think I found either a bug in B&R or some kind of corrupted DB? I have daily, weekly and monthly backup jobs. For the last 2 weeks or so, when the jobs run per the schedule, I get a failure email saying that a datastore is unavailable and that a vbm file is not synchronized with the backup repository. Here's the problem: if I look in the backup console at the 'last 24 hours' view, it shows all N VMs backed up successfully (e.g. no failure listed). I have tried repeatedly to resynchronize the repo (with no issues/errors), yet these emails keep coming. Even weirder: if I run the job manually, I don't get the error email? I'd be happy to open a case if needed, but if someone has an easy idea, I'd rather go that route. Thanks!

[danswartz]

I'm not sure I'm having the same issue here (I have other oddities as I mentioned.) I guess I will open a case

[danswartz]

Well, this seems to be similar after all. e.g. something corrupted with the jobs themselves. I disabled the daily backup job and created a new one from scratch. Scheduled it to run a bit ago, and... no spurious failure message. Rescheduled for a few minutes later, and the subsequent incremental also worked okay. I'm going to let it go overnight, and if that works also, I guess I have to delete and re-create the weekly and monthly backup jobs.

[danswartz]

Well, highly annoyed. STILL getting the errors. And the job it is complaining about no longer exists! I deleted it! Something is corrupted apparently. Case 03605464 opened.

[veremin]

Seems like there stalled references inside product database. It's indeed recommended to reach support team to have them removed. Thanks!

[danswartz]

For sure. It's odd that if I set a different scheduled time for the job to run, it does with no issues (for example: I set it to run at 3:15AM), but I still get the odd failure email with a start time of 3:00AM (the old time) and for a job that no longer exists...

[Alvin]

Hi Caleone,

Can you share the links that can solve the issue?

[HannesK]

Hello,
and welcome to the forums. @Alvin : I suggest to contact support. The thread is already some years old...

Best regards,
Hannes

[AlexLaforge]

Hi, The links they sent you would be VERY helpful to us here : thank you !

[Backup_Guy]

Can you share the links they gave you?

[HannesK]

guys... I have no idea what link you are asking for...the cases above cannot be compared with each other actually. Please contact support to see how to fix it.

[spider32]

Still encountering this error every now and then. Support says it may be a storage issue itself or communication issue.

We're using Scale out repo so if rescan does not work, you can read the backup log (job_name.Backup) and find out which SOBR is having issue and rename the .vbm file. This will regenerate a new vbm file.

[Andreas Neufert]

Question, did you use the same folder oder folders for 2 Repositories (or Extents) or 2 different Backup & Replication servers?
This situation could lead into the same issue.

[spider32]

We have several folders for our SOBR and a single BNR server. Only one of the folders showed the error.