About two weeks ago, one of my SQL servers had to be rebooted. When it came back up, both drives had lost their .vmdk files(the flat files were still there, but the configuration file was missing). I was able to get them recreated, but one drive(the one with all the data on it, naturally) had to be moved to a separate datastore, as it was too big to recreate on the one I was using. So I recreated the vmdk files, copied the file from the second datastore back to where the flat files were and edited the configuration file to point it to the correct flat file. But the machine still would not boot with that drive attached, so I ended up copying the flat file to the other datastore and running it from there. Everything seemed well and good after that.
Two days ago, the server was rebooted again. When it came back up, everything on the data drive had reverted to the date that I made the change(6/19). Eventually we figured out that for some reason the server had still been writing to the original file, and when we added it back to the server all the data from the past two weeks was there(I'm still not sure why it booted up with the drive attached this time, but that's a whole other issue). I went back in today to look at the files on the datastore, and the flat file is still saying it was last modified yesterday(when we got it back up and running).
So the question is, are we going to lose everything up until yesterday the next time this server gets rebooted, or is it normal for the modified date on the flat file not to change? And does anyone have any idea why it was writing to the old file(I did change the settings on the VM to point the drive to the location on the new datastore).