Comments - The database (mariadb) is affected by the restoration of windows
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Disclaimer : I'm not familiar with system restore, and never used that
Sounds like someone else had this problem before https://superuser.com/questions/1259835/exclude-some-files-from-windows-system-restore, and his registry key fixes were *not* helpful either (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot)
That same person complained in https://jira.mariadb.org/browse/MDEV-14099 , which I closed, before actual understanding what happened. Yet anyway, MariaDB would not be a place to complain about that, and Innodb won't be changing .ibd extension which it had been using for 25 years.
If anything, it helps to store data not on system partition, or to do data directory backup before system restore, or to disable system restore.
It might help to complain to Microsoft to do something different about IBD file extension rather than remove it.
https://docs.microsoft.com/pt-br/windows/win32/sr/monitored-file-extensions?redirectedfrom=MSDN
it looks like the extension: IBD is monitored by the windows restore point.
Vladislav Vaintroub, thanks for responding. Windows does not always allow the user to back up before a point restoration, he can simply force a point restoration, so it is not possible to perform a backup. Other databases like SQLSERVER and POSTGRE do not present the problem. Once in MariaDB or MySql the data is lost, returning the data to the date of the restore point.
In this topic, a user faces the same problem: https://social.technet.microsoft.com/Forums/pt-BR/016d8e9b-9ae7-461c-822a-c47859a76c1d/restaurao-do-windows-apaga-dados-de-uma-base-mysql?forum=winvistapt
it seems that the solution has to do with: innodb_file_per_table=0
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.