Daniel

I'm sorry, but I still can't create Microsoft SQL Server database snapshots with ImDisk. I'm now using the RAMDisk program from Dataram. It does create a database snapshot. Just FYI.

After every restart of a virtual machine with Debian 12, I get the following message from Logwatch 7.10: --------------------- Systemd Begin ------------------------ Unmatched Entries Expecting device sys-subsystem-net-devices-ens192.device - /sys/subsystem/net/devices/ens192...: 1 Time(s) ---------------------- Systemd End ------------------------- I don't have a subsystem subdirectory under /sys. However, the ens192 interface works great.

OK, thank you.

The fsutils tool, of course, I can use that to test. What commands exactly did you used? If they work for me too, I can ask Microsoft why a database snapshot cannot be created.

Yes. I think only NTFS supports sparse files.

I was able to successfully configure a system so that Microsoft SQL Server uses the ramdisk for databases. These do not have to be persistent, they are created, used for a short time and then deleted again. Unfortunately, a database snapshot cannot be created. The command CREATE DATABASE xx AS SNAPSHOT OF yy shows the following error: Msg 1823, Level 16, State 2, Line 10 A database snapshot cannot be created due to an error during startup. Msg 5119, Level 16, State 1, Line 10 The file "D:\Temp\TestSnapshot.mdf.snapshot"...

Response status code does not indicate success: '403' ('Forbidden')

These files do not come from logrotate, but from samba itself. Some of them are created every minute, but not by every workstation. Unfortunately, I don't know why these are created. This problem has only been present for two weeks, but I haven't changed anything in the Samba configuration in the last time. I just update the software packages regularly. The customer does not notice anything, i.e. he does not have any errors that occur suddenly. I asked for advice on the Samba mailing list but unfortunately...