>My desktop support people run backups between 00:00 and 00:05. The system is set to log anyone out who happens to be logged in, forcing a disconnect from all files; the backup system does not backup open files.
>
>I was working late one night and got "kicked out" - I got File read errors, which of course is the same thing you get if the server crashes. Luckily I was not writing to any files.
>
>My LAN people tell me that my choice is to request that I not be disconnected and risk data not being backed up (sometimes files are "invisibly" open and no one knows they are never backed up, or to be disconnected as is our SOP, possibly risking data corruption.
>
>The value of good backups is high. The likelihood of my actually having files open that late is low. My experience is that if I'm not actually writing to files when disconnection occurs there is no data corruption.
>
>Can anyone verify this, especially with documentation?

Without addressing your question, the real answer is for the backup process to notify users that have files open 2 minutes or so before it kills their connections - or, failing that, send a broadcast message to all w/s that may be running and logged in. That lets interactive users shut down gracefully; non-interactive or unattended processes will still get killed ungracefully - but that's no different from what's happening now.