Rescanning SoBR "skipping"

[LittleNickey]

When rescanning a local Scale-out Repository the status is "Success" but when viewing the result of each extent it will say:
Extent 1: skipped 12
Extent 2: skipped 3
Extent 3: No backups found
Extent 4: skipped 6

First of all, I presume that "No backups found" means no NEW/Changed backups were found.
Second, what does skipped mean in this case, and how can I see what has been skipped? Is there additional logs I can check for more information?

And before you ask, I have disabled all the backup jobs before running the rescan and still it says "skipped".

[foggy]

I assume that it skips the backups it is already aware of: existing jobs -> info about backups is already stored in the database -> nothing new to add.

[chris.childerhose]

What @foggy said is true. If you need to check logs look in here - C:\ProgramData\Veeam

[LittleNickey]

Thank you both. Any suggestion on which log file to look in?

[veremin]

c:\ProgramData\Veeam\Backup\Utils\DatabaseResynchronizer\Job.DatabaseResynchronizer.log - general rescan log
c:\ProgramData\Veeam\Backup\Utils\DatabaseResynchronizer\Task.DatabaseResynchronizer.{extent_Name}.log - extent rescan log (most likely, you will find needed information here)

Thanks!

[LittleNickey]

Thank you @veremin, you were correct. Very helpful!

It seems to be skipping with this log message: "[BackupImmutability] Skip immutability operation. Extent doesn't support linux immutability."

The repository is a Windows repo, and I'm not aware (and can't find any settings configured for it either) that it should be set as immutable. Does it throw this message anyway, just because it is a Linux server stored to that extent? Or where would I see this configured? Is it a job setting?

[veremin]

You can reach our support team for further clarification, but don't you have a Hardened Linux repository as one of Performance extents? Thanks!

[LittleNickey]

@veremin No such repo in this SoBR, but we have another SoBR with S3 storage with immutable support.

[veremin]

Looks unexpected, so you might proceed with opening the support ticket. Thanks!