Warnings for Endpoint Backup - How to clear/suppress/correct

[axiomcrs]

Using the latest version.

This is what I am seeing: https://i.gyazo.com/f7ef58260b4781f7a72 ... e336f6.png

I need to clear those warnings.

I am looking here: C:\ProgramData\Veeam\Endpoint\Backup_Job_ABCCo-SERVER

At the end I see:
[20.10.2017 00:30:33] <01> Warning You are running low disk space on Recovery Image (D:)
[20.10.2017 00:30:33] Warning <26fc> Cryptocontainer 'VeeamCryptoContainer' does not exist, creating...
[20.10.2017 00:31:07] Warning <26fc> Force backup files list is empty. ( 3 times for this one)
[20.10.2017 00:40:10] <01> Warning Global event notification is not used on current service

I have many endpoints working just fine in this network with no warnings all sending their backup files to the same nas.

Can any of these be suppressed and is it wise to suppress any of these?
I'm not worried about the first 3, but I don't know what to make of the last one. Perhaps I can enable event notification for this one. But where?
Can someone offer some details?

TIA

[Dima P.]

Hi axiomcrs,

Warning You are running low disk space on Recovery Image (D:)

This key should help

Force backup files list is empty. ( 3 times for this one)

From the top of my head, this might be related to inconsistent state of items to backup. In case items in the source are missing - we notify the user. To eliminate such warning open backup job > source objects step. It should resync the number of source items to backup.

Cryptocontainer 'VeeamCryptoContainer' does not exist, creating...

I am not aware of this warning. If resyncing the backup content does not help, please open a support case.

[axiomcrs]

Thanks.

I added the registry key.

I wasn't what you meant by backup-> source step, but I went thru the b/u config and didn't change anything.

I reran the b/u and it was successful w/o warnings.

You didn't mention what the last warning was referring to, any clue?

[Dima P.]

You didn't mention what the last warning was referring to, any clue?

Looks like its related to encryption, but that the only thing I can say based on this warning. If you see the last warning once again please open a support case.