Veeam is constantly waking up our NAS

[Earthrise]

Hello folks,

i have a problem with Veeam v10 that didn't exist with v9.5. Veeam is rescanning our repositories every 15 minutes, therefore our NAS is waking up constantly. How can i turn off this annoying "feature"?!

Edit: I've looked through the old logs under "C:\ProgramData\Veeam\Backup\ResourceScan" and it seems that v9.5 did a rescan every 22 hours. Now it's every 15 minutes and it drives me nuts!

[Gostev]

Hello, actually periodic repository rescan has always been done every 15 min, because resource scheduler needs this information to be fairly up-to-date (and in 22 hours, situation can change quite dramatically). So, no changes with v10 there. Perhaps there was some other change in your environment, or NAS firmware update, or something. As for the logs, I think you're looking at some other resource rescan process... 22 hours seems quite a weird number too, and not what we would normally use by default in any functionality. Thanks!

[Earthrise]

What you are saying is simply not true! Our NAS was not waking up every 15 minutes until we installed Veeam v10! If i stop the Veeam Backup Service, the NAS is not waking up anymore. Here the Logs ("Task.Repository.log") from 9.5:

Code: Select all

[09.02.2020 10:31:18] <06> Info     [ResourceScanner] Scan for resource <name of nas> will be started by schedule
[09.02.2020 10:31:18] <06> Info     [ResourceScanner] Scan is started for resource <name of nas>
[09.02.2020 10:31:18] <06> Info     [RepositoryResource, Id: {0}, Name: {1}] Info about repository has been refreshed from DB.
[09.02.2020 10:31:18] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[09.02.2020 10:31:18] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[09.02.2020 10:31:18] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[09.02.2020 10:31:18] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[09.02.2020 10:31:18] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[09.02.2020 10:31:21] <06> Info     Physical host volume was not found for path '\\<name of nas>\<foldername>' on host '<name of backup server>'.
[09.02.2020 10:31:21] <06> Info     Resetting storage availability bit RepositoryUnavailable for repository c5b468ff-99de-4900-aeb4-a3310043047d
[09.02.2020 10:31:21] <06> Info     [ResourceScanner] Update resource <name of nas> result: av. Available, options <RepositoryAuxData><FreeSpace>4723448782848</FreeSpace><Capacity>5497558138880</Capacity></RepositoryAuxData>
[09.02.2020 10:31:21] <06> Info     Prev result was Available, options <RepositoryAuxData><FreeSpace>4950359498752</FreeSpace><Capacity>5497558138880</Capacity></RepositoryAuxData>
[09.02.2020 10:31:21] <06> Info     [ResourceScanner] Scan is finished for resource <name of nas>
[10.02.2020 08:31:24] <06> Info     [ResourceScanner] Scan for resource <name of nas> will be started by schedule
[10.02.2020 08:31:24] <06> Info     [ResourceScanner] Scan is started for resource <name of nas>
[10.02.2020 08:31:24] <06> Info     [RepositoryResource, Id: {0}, Name: {1}] Info about repository has been refreshed from DB.
[10.02.2020 08:31:24] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[10.02.2020 08:31:24] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[10.02.2020 08:31:24] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[10.02.2020 08:31:24] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[10.02.2020 08:31:24] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[10.02.2020 08:31:27] <06> Info     Physical host volume was not found for path '\\<name of nas>\<foldername>' on host '<name of backup server>'.
[10.02.2020 08:31:27] <06> Info     Resetting storage availability bit RepositoryUnavailable for repository c5b468ff-99de-4900-aeb4-a3310043047d
[10.02.2020 08:31:27] <06> Info     [ResourceScanner] Update resource <name of nas> result: av. Available, options <RepositoryAuxData><FreeSpace>4717356298240</FreeSpace><Capacity>5497558138880</Capacity></RepositoryAuxData>
[10.02.2020 08:31:27] <06> Info     Prev result was Available, options <RepositoryAuxData><FreeSpace>4723448782848</FreeSpace><Capacity>5497558138880</Capacity></RepositoryAuxData>
[10.02.2020 08:31:27] <06> Info     [ResourceScanner] Scan is finished for resource <name of nas>
[11.02.2020 06:31:30] <06> Info     [ResourceScanner] Scan for resource <name of nas> will be started by schedule
[11.02.2020 06:31:30] <06> Info     [ResourceScanner] Scan is started for resource <name of nas>
[11.02.2020 06:31:30] <06> Info     [RepositoryResource, Id: {0}, Name: {1}] Info about repository has been refreshed from DB.
[11.02.2020 06:31:30] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[11.02.2020 06:31:30] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[11.02.2020 06:31:30] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[11.02.2020 06:31:30] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[11.02.2020 06:31:30] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[11.02.2020 06:31:33] <06> Info     Physical host volume was not found for path '\\<name of nas>\<foldername>' on host '<name of backup server>'.
[11.02.2020 06:31:33] <06> Info     Resetting storage availability bit RepositoryUnavailable for repository c5b468ff-99de-4900-aeb4-a3310043047d
[11.02.2020 06:31:33] <06> Info     [ResourceScanner] Update resource <name of nas> result: av. Available, options <RepositoryAuxData><FreeSpace>4710274330624</FreeSpace><Capacity>5497558138880</Capacity></RepositoryAuxData>
[11.02.2020 06:31:33] <06> Info     Prev result was Available, options <RepositoryAuxData><FreeSpace>4717356298240</FreeSpace><Capacity>5497558138880</Capacity></RepositoryAuxData>
[11.02.2020 06:31:33] <06> Info     [ResourceScanner] Scan is finished for resource <name of nas>
[12.02.2020 04:31:36] <06> Info     [ResourceScanner] Scan for resource <name of nas> will be started by schedule
[12.02.2020 04:31:36] <06> Info     [ResourceScanner] Scan is started for resource <name of nas>
[12.02.2020 04:31:36] <06> Info     [RepositoryResource, Id: {0}, Name: {1}] Info about repository has been refreshed from DB.
[12.02.2020 04:31:36] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[12.02.2020 04:31:36] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[12.02.2020 04:31:36] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[12.02.2020 04:31:36] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[12.02.2020 04:31:36] <06> Info     Received from cache. Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[12.02.2020 04:31:39] <06> Info     Physical host volume was not found for path '\\<name of nas>\<foldername>' on host '<name of backup server>'.
[12.02.2020 04:31:39] <06> Info     Resetting storage availability bit RepositoryUnavailable for repository c5b468ff-99de-4900-aeb4-a3310043047d
[12.02.2020 04:31:39] <06> Info     [ResourceScanner] Update resource <name of nas> result: av. Available, options <RepositoryAuxData><FreeSpace>4702767927296</FreeSpace><Capacity>5497558138880</Capacity></RepositoryAuxData>
[12.02.2020 04:31:39] <06> Info     Prev result was Available, options <RepositoryAuxData><FreeSpace>4710274330624</FreeSpace><Capacity>5497558138880</Capacity></RepositoryAuxData>
[12.02.2020 04:31:39] <06> Info     [ResourceScanner] Scan is finished for resource <name of nas>

And here the very same log from v10, same server, same nas:

Code: Select all

[23.04.2020 19:05:58] <14> Info     [ResourceScanner] Scan for resource <name of nas> will be started by schedule
[23.04.2020 19:05:58] <14> Info     [ResourceScanner] Scan is started for resource <name of nas>
[23.04.2020 19:05:58] <14> Info     [RepositoryResource, Id: c5b468ff-99de-4900-aeb4-a3310043047d, Name: <name of nas>] Info about repository has been refreshed from DB.
[23.04.2020 19:05:58] <14> Info     Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:05:58] <14> Info     [CProxyRpcInvoker] RpcInvoker [51405321] has been created. Host: [<name of backup server>:6162], Identity: []
[23.04.2020 19:05:58] <14> Info     [CProxyRpcInvoker] RpcInvoker [51405321] was disposed
[23.04.2020 19:05:58] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:05:58] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:05:58] <14> Info     [CProxyRpcInvoker] RpcInvoker [48716837] has been created. Host: [<name of backup server>:6160], Identity: []
[23.04.2020 19:05:58] <14> Info     [CProxyRpcInvoker] RpcInvoker [48716837] was disposed
[23.04.2020 19:05:58] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:05:58] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:05:58] <14> Info     [CProxyRpcInvoker] RpcInvoker [18937041] has been created. Host: [<name of backup server>:6160], Identity: []
[23.04.2020 19:05:58] <14> Info     Physical host volume was not found for path '\\<name of nas>\<foldername>' on host '<name of backup server>'.
[23.04.2020 19:06:01] <14> Info     [CProxyRpcInvoker] RpcInvoker [18937041] was disposed
[23.04.2020 19:06:01] <14> Info     Resetting storage availability bit RepositoryUnavailable for repository c5b468ff-99de-4900-aeb4-a3310043047d
[23.04.2020 19:06:01] <14> Info     [ResourceScanner] Scan is finished for resource <name of nas>
[23.04.2020 19:21:01] <14> Info     [ResourceScanner] Scan for resource <name of nas> will be started by schedule
[23.04.2020 19:21:01] <14> Info     [ResourceScanner] Scan is started for resource <name of nas>
[23.04.2020 19:21:01] <14> Info     [RepositoryResource, Id: c5b468ff-99de-4900-aeb4-a3310043047d, Name: <name of nas>] Info about repository has been refreshed from DB.
[23.04.2020 19:21:01] <14> Info     Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:21:01] <14> Info     [CProxyRpcInvoker] RpcInvoker [25983967] has been created. Host: [<name of backup server>:6162], Identity: []
[23.04.2020 19:21:01] <14> Info     [CProxyRpcInvoker] RpcInvoker [25983967] was disposed
[23.04.2020 19:21:01] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:21:01] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:21:01] <14> Info     [CProxyRpcInvoker] RpcInvoker [41518173] has been created. Host: [<name of backup server>:6160], Identity: []
[23.04.2020 19:21:01] <14> Info     [CProxyRpcInvoker] RpcInvoker [41518173] was disposed
[23.04.2020 19:21:01] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:21:01] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:21:01] <14> Info     [CProxyRpcInvoker] RpcInvoker [49580594] has been created. Host: [<name of backup server>:6160], Identity: []
[23.04.2020 19:21:01] <14> Info     Physical host volume was not found for path '\\<name of nas>\<foldername>' on host '<name of backup server>'.
[23.04.2020 19:21:03] <14> Info     [CProxyRpcInvoker] RpcInvoker [49580594] was disposed
[23.04.2020 19:21:03] <14> Info     Resetting storage availability bit RepositoryUnavailable for repository c5b468ff-99de-4900-aeb4-a3310043047d
[23.04.2020 19:21:03] <14> Info     [ResourceScanner] Scan is finished for resource <name of nas>
[23.04.2020 19:36:03] <14> Info     [ResourceScanner] Scan for resource <name of nas> will be started by schedule
[23.04.2020 19:36:03] <14> Info     [ResourceScanner] Scan is started for resource <name of nas>
[23.04.2020 19:36:03] <14> Info     [RepositoryResource, Id: c5b468ff-99de-4900-aeb4-a3310043047d, Name: <name of nas>] Info about repository has been refreshed from DB.
[23.04.2020 19:36:03] <14> Info     Resolved by NTLM strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:36:03] <14> Info     [CProxyRpcInvoker] RpcInvoker [31982423] has been created. Host: [<name of backup server>:6162], Identity: []
[23.04.2020 19:36:03] <14> Info     [CProxyRpcInvoker] RpcInvoker [31982423] was disposed
[23.04.2020 19:36:03] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:36:03] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:36:03] <14> Info     [CProxyRpcInvoker] RpcInvoker [4770767] has been created. Host: [<name of backup server>:6160], Identity: []
[23.04.2020 19:36:03] <14> Info     [CProxyRpcInvoker] RpcInvoker [4770767] was disposed
[23.04.2020 19:36:03] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:36:03] <14> Info     Received from cache. Resolved by NTLM preferred strategy ip addresses and host names: <backup server ip> <name of backup server>
[23.04.2020 19:36:03] <14> Info     [CProxyRpcInvoker] RpcInvoker [22581391] has been created. Host: [<name of backup server>:6160], Identity: []
[23.04.2020 19:36:03] <14> Info     Physical host volume was not found for path '\\<name of nas>\<foldername>' on host '<name of backup server>'.
[23.04.2020 19:36:06] <14> Info     [CProxyRpcInvoker] RpcInvoker [22581391] was disposed
[23.04.2020 19:36:06] <14> Info     Resetting storage availability bit RepositoryUnavailable for repository c5b468ff-99de-4900-aeb4-a3310043047d
[23.04.2020 19:36:06] <14> Info     [ResourceScanner] Scan is finished for resource <name of nas>

I've checked this on at least three customer systems as well and they all show the same behaviour -> v9.5 every 22 hours, v10 every 15 minutes. I still want to know how to change this *** back!

[foggy]

You can alter the default repository rescan period value via registry.

[Earthrise]

I know about this Registry Value, but it alters the normal infrastructure rescan. This scan happens every 4 hours, i can see this in the logs and im fine with that. The scan from the logs above is something else. I even monitored the network traffic from a 9.5 backup server to nas and i can confirm that v9.5 is clearly NOT scanning the nas every 15 minutes, while v10 clearly is. Please change this back or give me another reg key i can set.

Edit: oh wait, you meant the RescanExtentStatusSec value right? I'll try that, thank you!

[Earthrise]

Worked like a charm, thank you very much!

[Gostev]

What you are saying is simply not true!

I double checked with the devs, they reviewed the 9.5 code and confirmed it's true: version 9.5 also rescanned repository every 15 minutes. However, there seem to be an issue in v10 that this rescan is not stopping when the job scheduler has no pending tasks. They will be looking at this issue closer.

[Earthrise]

Hey, thanks for the reply. I can only say that the NAS boxes we have in use on multiple networks as backup repositories did not wake up very often before we installed v10. I don't have a number, but less than once per hour for sure. With v10 they get woken up every 15 minutes, which is confirmed by the mentioned logs and the corresponding network traffic. If i look at the "Task.Repository.log" on all our Veeam installs, it's pretty much like the example i posted: one scan per 22 hours for v9.5, though if v9.5 scanned every 15 minutes too, then i guess it only did it while a backup job was already started and therefore it was not logged in the "Task.Repository.log"? Anyway, it would be great if this will get fixed, since i don't know if setting the "RescanExtentStatusSec" Value has negative side effects for our installs. For now it works as expected though.

[TiBor]

The log of my NAS device shows that Veeam B&R servers are accessing smb shares every 15 minutes. Veeam support says this behavior is caused by backup copy jobs (Case # 04235114). Unfortunately, this behavior prevents NAS devices from entering power save mode.

- This behavior is acceptable to check if there are new restore points for copying at smb shares on a source backup repository. But this behavior shouldn't occur when all backup copy jobs have a specified schedule and, for example, are only allowed to work at night. Then there is no need to scan the source backup repository for new restore points all day long. So please stop doing that and allow the device to go to sleep.

- This behavior doesn't make any sense AT ALL for smb shares of backup repositories that are only being used as target for backup copy jobs. There is no reason to access a target share all day long every 15 minutes, but it prevents the device to enter power save mode for nothing.

Could you fix that please? Thanks.

[foggy]

Hi Timo, thanks for the detailed feedback. As you can see in the thread above, there's a known issue in the latest Veeam B&R version causing this behavior which is going to be addressed further down the road. Also, please consider extending the rescan period with the help of the mentioned registry value as a temporary workaround. Thanks!