I have avoided this issue as follows: via an Automator workflow, each changed database is copied to another directory on my HD. Is this true of Time Machine? Time Machine is hell-bent on backing up every hour, so do I need to close DTPro every hour to keep the database safe? Sorry to jump in here, but I think this is a related issue: I’ve picked up (from posts in other threads) that copying a DTP database while it’s open is a Bad Thing and could damage the database. DEVONthink 2 has a different database structure than did DEVONthink 1.x. No, Time Machine won’t have to recopy the entire DT Pro/Office 2 database package every time new content is added. That’s insurance against loss of everything - including the Time Machine backups - from theft or fire. Periodically, I copy Backup Archive archives of my databases to DVD and store the DVDs offsite. If I were to need to resort to a backup of my main database (which has happened only once in about four years, and then because I was testing a hack, which bollixed the database), my first choice would be the Backup Archive backup. I store the compressed and dated file produced by Backup Archive on an external drive. When I come back, the database has been verified, optimized and has current internal and external backups. I’ll take a break and invoke Scripts > Export > Backup Archive. Note: When I’ve done important changes to a database, usually several hours of work, I don’t wait for a scheduled backup. On the other hand, as sjk noted, I don’t continue working on a database during a Time Machine backup, nor is my ModBook always connected to the external drive for Time Machine backups, so I don’t consistently do hourly backups. I’ve tested a couple of Time Machine backup recoveries and they have been fine. I don’t bother to close DEVONthink when a Time Machine backup is made. Some backup methods have ways to reduce that risk I’m not sure about Time Machine. I think the risk is in making inconsistent backups (of any data, not just DEVONthink dbs) without realizing it until problems occur when they’re restored. But if a backup is relatively small the window of vulnerability to problems is smaller, too. For example, backing up DEVONthink-*.dtMeta files while any are being modified is a bad idea. Otherwise the backup might contain an incompatible mix of old and new data. Since a DEVONthink database is constructed from multiple files/folders you’d like to ensure they’ve all been backed up before making any changes. Probably not necessary to close it, but I wouldn’t want to be updating it during any backup. So do I need to close DTPro every hour to keep the database safe? It might damage the backup of a database, but I don’t see how it could harm the original. I’ve picked up (from posts in other threads) that copying a DTP database while it’s open is a Bad Thing and could damage the database
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |