My ideal solution is to have everything backed up "in the cloud" plus have a backup at home. So far I've got the home backup happening - every machine uses 'attic' to back up onto my NAS. I'm still figuring out what the "in the cloud" side looks like.
One thing you can do is keep copies of important documents elsewhere - like Dropbox, a USB drive in a safe deposit box, etc. It all depends on what technologies you trust and how much you trust them.
For OCR, I can't say I've had much trouble with it. Mayan breaks the PDFs into pages, then feeds each page to tesseract. All of that happens in a worker process and I haven't found that it has a significant impact on the use of Mayan. The OCR section for the document will be incomplete for a while though.
[0] http://mayan.readthedocs.io/en/v2.1.4/topics/backups.html
For the OCR, my issue is that if I import several documents Mayan will feed them all to tesseract in parallel. Then I have two available cores, but 40 tesseract workers and the system comes down because it runs out of RAM and CPU. How did you set up your OCR?
Maybe something changed at some point to limit the active workers to the number of cores.
[0] http://mayan.readthedocs.io/en/stable/topics/deploying.html
OCR is going to be CPU bound, so the solution seems obvious.
- backups. I plan on using it to go paperless and keep tax returns etc. I can't afford to lose that info, but I can't come up with a robust enough backup plan. How are you doing it?
- concurrency. It runs on a 8 years old home server, and when I scan multiple pages documents, the ocr slows down to a crawl. Have you run into this?