> I tend to leave Lightroom running in the background for days sometimes, allowing my Windows 7 Pro 64-bit system to sleep.
In all honesty, I would recommend against that. When you are not using LR, formally exiting the app will better ensure the integrity of the database.
It would be best to avoid using a backup app while Lightroom is open and relying on Lightroom backing up the catalog. Using a BU app while Lr is open can lead to corruption as mentioned above.
You're correct, and I appreciate the answer, but it doesn't really get to the bottom of the issue of 'why?'. However, I will be a bit more conscious of not leaving it open.
Although you're correct about the LR catalog, changing the backup app (CrashPlan) to no longer backup the catalog defeats at least part of my purpose. As would making it a manual backup. The best backups are those done without any further action needed on my part.
However, I did read a bit more about CrashPlan, and have changed it to not backup currently open files. It will check every hour and see if the file has been updated but is no longer open, and then back it up. This should fix the Volsnap and VSS errors on Win 7.
The question remains as to whether it will keep the LR catalog message from occurring. I am assuming that it's related to backups, but cannot say for sure at this point. I'll leave it open (against ManiacJoe's rec) and see if this still occurs.
Trusting the windows "sleep" functionality to get all your unsaved data to disk places way too much trust in a subsystem that is not bug free.
LR consumes a large amount of system resources. If you are not actively using LR, your computer will respond better by having those resources available to programs that actually need the resources. Plus, by exiting the app, you are ensured that the database edits get written to disk.