NUS Server does not restore notification state

[Basprog]

Enabling or disabling notification on Client does always lead to an update of local database of Server by writing to its flash memory. Particularly NUS requires enabling of notification on each reconnection. Up to me flash memory of NUS Server's IC will fully degrade after about a dozen thousand of reconnections following this way. If I don't enable notification on NUS Client by skipping a call of ble_nus_c_tx_notif_enable() relying on everything was previously restored from database cache, NUS Server isn't able to send data. What is the reason to store anything on flash while it'll not be used (restored) when required?

[Basprog]

Dear Edvin, if you (and spec) say that Server should store notification state then correct, I observe it's not (re)stored. I'm using SDK 15.2.0 and SD 6.1.0.

[Edvin]

Hello, 

Can you please check my colleagues reply in this ticket, and see if you can use any of those functions to restore the value of the notification/cccd?

Best regards,

Edvin

[Basprog]

Dear Edvin, what reply/ticket do you mean? I don't see any replies here other than yours.

[Edvin]

I am sorry. I missed the link. I meant to link to this ticket:

https://devzone.nordicsemi.com/f/nordic-q-a/30249/getting-cccd-persistence-upon-bonded-peer-connection

[Basprog]

Dear Edvin, could you kindly be more precise on answers? The ticket you referred to doesn't mention exact instructions, just a couple of ways (functions) which mean about nothing for me.

sd_ble_gatts_sys_attr_get(SYS_ATTR_FLAG_SYS_SRVCS | SYS_ATTR_FLAG_USR_SRVCS) returns following array of data: 0xCACD000100020010. How should I interpret it?