Hi,
Error: Cannot proceed with the job: existing backup meta file 'xxxx.vbm' on repository 'xxxx' is not synchronized with the DB. To resolve this, run repository rescan.
I'm getting this error several times, on different servers running Veeam Backup Agent for Windows.
They are all managed through Veeam service provider console and the backup target is on a Azure Blob immutable repository.
The jobs can run fine for a couple of weeks, and then suddenly fails with that error.
I cannot seem to find a way to rescan the repository to fix this.
I have opened a case # 07234204
The solution given for this problem is to create a new backup policy and assign it to the server.
Case closed.
Unfortunately, this is happening again, for yet another server.
I'm really not happy with the given solution, since this is using twice the amount of storage space, and all the trouble of keeping the jobs in order to be able to restore anything.
This also brings on extra costs, which I cannot charge backup to the end customer.
I have once again opened a new Case #07304198
Hopefully I will get a better solution, as making new backup policies every time something goes wrong, doesn't make it a reliable product.
-
- Service Provider
- Posts: 13
- Liked: 1 time
- Joined: Jun 18, 2013 6:53 pm
- Contact:
-
- Product Manager
- Posts: 10110
- Liked: 2696 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Repository rescan for agent managed by Cloudconnect
Hi Kurt
Our Agent does an automatic rescan at the start of a backup job session. But it seems that it doesn't solve the issue.
07234204 + 07304198: Let me review both cases.
Best,
Fabian
Our Agent does an automatic rescan at the start of a backup job session. But it seems that it doesn't solve the issue.
07234204 + 07304198: Let me review both cases.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Product Manager
- Posts: 10110
- Liked: 2696 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Repository rescan for agent managed by Cloudconnect
Hi Kurt
Can you please confirm with me the build number of your VCC server and Veeam Agent?
There is a reg key to solve this issue (VCC v12.1 and later/Agent v6.1 and later).
And VCC v12.1.2 and Agent v6.1.2 has bug fix to prevent the issue from happening at all.
I will inform your case engineer about the reg key and the fix in our most recent version.
Best,
Fabian
Can you please confirm with me the build number of your VCC server and Veeam Agent?
There is a reg key to solve this issue (VCC v12.1 and later/Agent v6.1 and later).
And VCC v12.1.2 and Agent v6.1.2 has bug fix to prevent the issue from happening at all.
I will inform your case engineer about the reg key and the fix in our most recent version.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 70
- Liked: 32 times
- Joined: Jul 13, 2018 3:33 pm
- Full Name: Derek M. Loseke
- Location: Omaha, NE, US
- Contact:
Re: Repository rescan for agent managed by Cloudconnect
Was this issue resolved? I'm getting the same error on two different machines that have the agent managed by the SPC and is backing up directly to Wasabi. I also have an agent that is backing up to a local NAS, also managed by the SPC that is getting a similar error.
Derek M. Loseke, Senior Systems Engineer | Veeam Legend 2022-2024 | VMSP/VMTSP | VCP6-DCV | VSP/VTSP | CCNA | https://technotesanddadjokes.com | @dloseke
-
- Product Manager
- Posts: 10110
- Liked: 2696 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Repository rescan for agent managed by Cloudconnect
Hello Derek,
Unfortunately, I cannot confirm the specifics of your issue or determine if it is related to known bugs through a forum topic. As mentioned, the issue described by Kurt should be resolved in v12.1.2.
If you are running the latest version and are still experiencing a similar issue, I recommend opening a support case so our customer support team can assist you in resolving it. Please share the case number with us.
Best regards,
Fabian
Unfortunately, I cannot confirm the specifics of your issue or determine if it is related to known bugs through a forum topic. As mentioned, the issue described by Kurt should be resolved in v12.1.2.
If you are running the latest version and are still experiencing a similar issue, I recommend opening a support case so our customer support team can assist you in resolving it. Please share the case number with us.
Best regards,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 42 guests