On 7/11/02 1:17 PM, "Pam Lefkowitz" <[EMAIL PROTECTED]> wrote:
> The solution is to close Entourage during backups. Retro will get the datase > in its entirety, compare it to make sure the data grabbed is the data that > was written to your backup media and then you can go back to work. This is > why we recommend backing up at times when machines aren't in use. I always shut down all applications before running a Retrospect backup. I have not yet seen any errors in the Retrospect logs about Entourage v.X DB files changing or not being backed up. But I am still wondering about that MS Database Daemon - and whether it is necessary to shut it down before doing a backup. From earlier messages in this thread, and from messages sent to MacFixit, it appears that the Daemon keeps the DB file open and that this might be causing problems for some people. It's not hard to see why it is necessary to kill the Daemon when doing a restore/replacement of the DB. It's less clear why the Daemon, or an open DB file, would be causing problems when the DB file is copied to a backup. Palm Desktop (formerly Claris Organizer) has something similar to the MS Database Daemon. It is a process launched by the Instant Palm Desktop extension. Like the Daemon, this process runs at all times and manages reminders. But instead of keeping the entire Palm DB open, it uses a separate file containing only the data it needs. Maybe this is a safer approach. -- Julian Vrieslander <[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
