Skip to main content
Answer

SOBR rescan with S3 is very long

  • October 5, 2021
  • 7 comments
  • 647 views

Hello to all,

On my Veeam Cloud Connect server I have a SOBR with 2 extents and S3 storage from Wasabi.
1 of the 2 extens was recently added but no offload to the S3 was happening.
I probably shouldn't have, but I removed the S3 from the sobr then put it back.
I ran a rescan and since then I have the "Configuration Database Resynchronize" job running for almost 63 hours ....

There are 15TB of backups on the S3 storage.

Is it normal that it takes so long? What can I do?

Thanks

Best answer by JMeixner

OK, perhaps the limit of concurrent tasks it set too low on the SOBR or extent for this process?

7 comments

JMeixner
Forum|alt.badge.img+16
  • On the path to Greatness
  • October 5, 2021

The rescan has to read all the backups on your extend. So, it depends on your internet connection...


  • Author
  • New Here
  • October 5, 2021

Thanks @JMeixner this is a dedicated server in a datacenter (ovh).

3gb/sec.

 


BertrandFR
Forum|alt.badge.img+7
  • Influencer
  • October 5, 2021

more verbosity in logs for the rescan? C:\programDATA\Veeam\Utils

Healthcheck the mssql DB?


  • Author
  • New Here
  • October 5, 2021

Thanks @BertrandFR  I think I have to open a ticket :-(

Since yesterday 15PM, every second:

[05.10.2021 12:31:29] <24> Error                  [AP] (Client) error: Agent process does not exist: 147116
[05.10.2021 12:32:28] <12> Warning      [AgentServiceManager] Agent process does not exist: 211758
[05.10.2021 12:32:28] <12> Error                  [AP] (Client) error: Agent process does not exist: 211758
[05.10.2021 12:32:29] <25> Warning      [AgentServiceManager] Agent process does not exist: 161217
[05.10.2021 12:32:29] <25> Error                  [AP] (Client) error: Agent process does not exist: 161217
[05.10.2021 12:32:30] <24> Warning      [AgentServiceManager] Agent process does not exist: 147116
[05.10.2021 12:32:30] <24> Error                  [AP] (Client) error: Agent process does not exist: 147116


JMeixner
Forum|alt.badge.img+16
  • On the path to Greatness
  • Answer
  • October 5, 2021

OK, perhaps the limit of concurrent tasks it set too low on the SOBR or extent for this process?


BertrandFR
Forum|alt.badge.img+7
  • Influencer
  • October 5, 2021

Indeed that seems tricky! Have you try to reboot you vbr or restart service “Veeam Backup Service”? :upside_down:


wolff.mateus
Forum|alt.badge.img+11
  • Veeam Vanguard
  • October 5, 2021

I have some Blob Azure together with local storage in a SOBR and the rescam is takes a loooong time to run.

So, I think that is normal.