M called me over to deal with a frozen Windows VM, which had in turn frozen VirtualBox and eventually the whole machine. The VM was eating 4GB of memory. Tried restarting just the VM but it crashed again, so restarted the whole machine; that took a forced reboot because it wouldn't shut down. When we brought everything back up, there was no temporary nVivo file in the normal temp folder [user]\local\Application Data\temp, but there was a 4MB binary log file. On starting up nVivo again and trying to load the database, it complained that the original was corrupted, but offered to retrieve a cached copy; the binary log file then disappeared and the db was restored, so it looks as though it ran the log file against the original file and reconstructed all today's changes.

Note to Greg: nVivo's looking a bit unstable. We should look at extra backup options to give us more redundancy that we have.