I found that IBD extension of mariaDB InnoDB data files is included in "monitored files" of Windows System Restore (https://msdn.microsoft.com/en-us/library/windows/desktop/aa378870%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396).
This means that if the data folder is inside a disk volume with System Restore enabled there is the serious hazard of silent data loss in case of System Restore and there is no way to avoid this.
If System Restore starts (consider that this can starts automatically from a simple power loss) all "monitored" files are rolledback included IBD file of MariaDB databases. After the Windows restore MariaDB service starts normally but all its data is rolledback at restore point due to IBD file restore!
I tried to find a solution configuring Windows Restore, if I exclude MariaDB folder from the restore using FilesNotToSnapshot (https://msdn.microsoft.com/en-us/library/windows/desktop/bb891959(v=vs.85).aspx) the restore process simply delete IBD files instead of restoring them. *Seems that there is not way to do not touch IBD files during System Restore. *The only solution is to change the file extension.
I think this is a serious problem and I spent a lot of time to understand what was the cause of some huge (many days!) rollback of my users after power loss.
The only solution for me now is to disable the Windows System restore.
I wonder if MariaDB can optionally use a different extension for IBD files.