I've got some strange behaviour of one ScaleOut Repository.
At a customer we've got two Synology NAS devices which are rotated on a weekly manner. Each NAS is configured with its own IP address and hostname and added as single repository. Then i created a ScaleOut Repository and added these two extents. That worked fine.
Now the customer shuts down a NAS (because of the weekly rotation) and Veeam BR doesn't get it, that there is only one NAS active in the ScaleOut Repository:
Code: Select all
Error: Cannot proceed with the job: existing backup meta file 'Daily.vbm' on repository 'NAS-ScaleOut' is not synchronized with the DB. To resolve this, run repository rescan.
I can see clearly in the Veeam logs that there happens a automatic rescan (host discovery) every few hours, and Veeam does recognize that one of the two NAS devices is not active / online. So i assume Veeam should know which extent is active and should be able to use the extent which is online. But the job fails.
- Is this a behaviour by design?
- Is it necessary to activate maintenance mode manually?
- Is it necessary to do a scripted rescan before the backup job runs, and Veeam gets it that the online extent should be used?
I don't want to manually rescan that as an admin, nether do i want to delegate this to the customer.
I want to ask first the community before i open a support case. Perhaps someone out there had the same issues and a possible solution for it.
Thanks for your help!