I have noticed several failures of backups of the Mail Database with Retrospect 5 (workgroup). These failures always seem to happen when the file changes between the time of the initial scan of files and the time of the actual backup of the particular file (eg the database).
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. As for how the file changes, I suppose it changes because some new mail arrived or something. The time between the start of the scan/backup and the actual file backup can be seconds or minutes, so that "lag" would be a big factor in whether people see this phenomenon. I hope this helps some. Paul On 7/11/02 10:08 AM, "Paul Berkowitz" <[EMAIL PROTECTED]> wrote: > On 7/11/02 3:58 AM, "Thomas Schierle" <[EMAIL PROTECTED]> wrote: > >> On 2002-07-11 02:16 +0200, Paul Berkowitz wrote: >> >>> Actually, Retrospect is completely foolproof (I'm referring to myself). I've >>> been using it for months now. It's set to run a backup "script" at 2:30 AM >>> every night. (I'd make it 3:00 or 3:30 except there's some Unix stuff that >>> apparently runs then.) More than a few times I've still been scripting when >>> 2:30 arrives. usually I catch Retrospect and defer for an hour or until >>> quit. But sometimes I miss it and it just runs. All it does is give a little >>> "boop" when it meets the open Database file (and any open app) and skip it >>> with an error logged. No big deal. it won't do the backup if the file is >>> open. Very safe. But it also doesn't terminate. It just moves on to the next >>> file. Very smart. >> >> (Entourage 2001 (4011), OS 9.2.2, Retrospect 4.0) >> >> actually Retrospect *does* backup my open Entourage Database. >> Looks to me like E'rage doesn't use OS level locking mechanisms, >> but that's just an uneducated guess. >> >> Somebody @MS care to comment? >> > Sorry. I guess the times when I've found an error have been not when it was > simply open but when I've been active in it - and perhaps only in particular > types of ways. It has happened several times, but I have no idea what the > circumstances might have been. And perhaps most of those were back when I > was still using the "Preview" beta version which I used for an awfully long > time. -- 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/>
