On 7/11/02 11:16, "Paul Welty" wrote: > I know this because Retrospect reports in the 'execution failures' log > something like "file cannot be backed up---modification date changed". > Presumably, this means it changed during the time mentioned above. > > I guess this is some sort of safety feature of Retrospect.
If Retrospect scans a file and that file changes between the time of the scan and the time of the backup you will see this error. It's not a bad thing. It's a good thing. This means that the file could not be verified and you won't get fooled into thinking that your mail database is safe. You want this. You want to be able to trust the integrity of your backup. Just look at the problems folks are having with FolderSynch lately - no error checking, no comparing, no logs to tell someone their mail database is really 0kb. That's bad. So the error entries in the log don't mean that Retro isn't doing its job. Those entries mean that Retro will not guarantee the integrity of the file because it has changed. 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. Hope this helps, Pam Lefkowitz, ACTC ---- Pam Lefkowitz, Owner Core Computing Technologies, Inc. voice:847/675-3513 Apple Certified Technical Coordinator Apple Consultants Network, Premier member Apple Product Professional Dantz Development Solutions Provider -- 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/>
