The database (mariadb) is affected by the restoration of windows
I use INNODB tables:
We are facing the following problem when Windows forces a point restore:
The database (mariadb) is affected by the restoration of windows, the client ends up losing data. Other banks like SQLSERVER do not have this problem. I would like to know if it is possible to perform some configuration to prevent the bank from being affected by possible point restoration of windows.
Answer Answered by Vladislav Vaintroub in this comment.
So I tried the system restore. Yes, the innodb tables will go back to the past point. first there is an "Undo" in the UI, it seems like it would create a volume shadow copy before doing system restore. You can explore the content with "System Restore Explorer", and I found the pre-system-restore .ibd files there.
Second point is that the user has to regularly do backups, himself of the database, if the data is valuable, rather than not play with Windows System restore. And store them on network location, in the cloud, or somewhere outside of the box, for the case of emergency.
I bet the developers for SQLServer and Postgres did exactly as much as we for system restore, namely nothing. On some arbitrary reason, this questionable tool decided to handle .IBD files specially, so the options are "complain to Microsoft" , or "tell your customers not to use it, to create database outside of system disk, to do their own emergency backups" etc.
