If you have VSS enabled in a drive where a live Firebird database is working this is enought to corrupt the database as you described in the examples.
Also, antivirus softwares do this but ussualy only when the database became more than 1gb. We had various problems like yours. We "solved" by performing an obrigatory backup and restore cicly every day and check if all is correct. When we have a problem the system stops, the client call us and we instruct (again) to do not use vss or a external backup program or file copy or antivirus. This reduced our problems and always found a problem related with user configuration. We had only 2 corruptions related to a bad ram and a bad disk. The next step will be detect if an antivirus software is running and tell the user to add an exception to our application. Also we will not run when vss is enabled. Em 15/09/2014 08:32, "Jan Flyborg jan.pers...@gmail.com [firebird-support]" <firebird-support@yahoogroups.com> escreveu: > > > Hi, > > Thanks for this. > > 2014-09-14 1:21 GMT+02:00 fabianoas...@gmail.com [firebird-support] < > firebird-support@yahoogroups.com>: > >> >> >> If Windows has volume shadow copy enabled this always corrupt databases >> in several ways. >> Em 13/09/2014 17:32, "Svein Erling Tysvær >> svein.erling.tysv...@kreftregisteret.no [firebird-support]" < >> firebird-support@yahoogroups.com> escreveu: >> > > Do you mean it would be enough to have the Windows Backup service (or any > other backup program that uses VSS) to corrupt a live database or do you > mean that the backed up files would be corrupted and the error would be > produced when such a backup was read back into production? > > Best Regards > //Jan Flyborg > >
