Way back when my server was up, then down, then back and such I was "living in the cache." This means that OneNote was letting me edit my notebooks while in "offline" mode and would keep track of my changes while the server was gone. I wrote a little about what this means and how we test it back in January. This gives me great flexibility to keep working and upload my changes when the server comes back.
But that configuration is not without its own risks. Had my hard drive with my cache completely died, or my cache gotten deleted or otherwise corrupted, I would have lost some of my work. This could also happen if I choose to delete the cache. I figured I would publish the list and add the "safety net" OneNote employs to help with this.
First, the list:
Items 3-5 are certainly nice to have, but I'm willing to live with the risk of losing that level of detail in the event of a hardware failure or crash corruption on my end. It would take only a few seconds for me to reconstruct the information if it were to disappear. 1 and 2 are more important. Looking at 1, I lose any information that exists only in the cache (changes I haven't been able to send to the server since the server is not there while I'm offline). If I'm not comfortable with this risk, the "safety net" I mentioned earlier can help me. OneNote makes backups for me automatically to files outside of the cache. You can see them in File \ Open Backup. This backup gets run once per day by default, but you can control that by clicking Tools | Options | Backup:
If I'm really worried, I can set the backup to happen every minute. And I can obviously click the button to force a backup whenever I want. This operation will take all the changes that exist only in OneNote's cache and apply them to the .ONE files on my machine. Fortunately for me, despite losing three hard drives at once, my drive that holds my cache (and the cache itself) have survived unscathed.
Questions, comments, concerns and criticisms always welcome, John