This is something a lot of people have noticed since upgrading to Retrospect
4.2. Long story short, it's nothing to worry about.

As you guessed, the reason it's happening is that Retrospect 4.2 now makes
more frequent additions to the log file, to aid in troubleshooting if
something goes wrong. Since the log may have been added to during a backup,
Retrospect may find that it is larger when it compares the file than when it
originally copied it.

Retrospect will report ANY difference in name, size, type, creator, creation
date or time, or modification date or time. Nothing escapes its compare
phase, even its own log file. I usually recommend treating execution errors
equally. Keep an eye on what types of errors you're getting, even something
as seemingly innocuous as this one. Retrospect's devotion to detail can come
in very handy when you need to troubleshoot problems.


Matthew Tevenan
Technical Support Specialist
Dantz Development Corporation

> From: Erling Johansen <[EMAIL PROTECTED]>
> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
> Date: Tue, 11 Jan 2000 18:12:42 +0100
> Subject: Operations log entry
> Since upgrading to Retrospect 4.2, I get the following log entry
> each night when backing up our server startup disk:
> Different data size (set: 1,151,362, vol: 1,151,414) for file
> ≥Srv:System Folder:Preferences:Retrospect:Operations Log≤.
> It is logged as an error, written in red, and I have to check it
> out every time I read through the log or backup report.
> I understand that the size of the operation log will change
> during backup. But why is it logged as an execution error?
> -- 
> ejo  <mailto:[EMAIL PROTECTED]>
> --
> ----------------------------------------------------------
> To subscribe:    [EMAIL PROTECTED]
> To unsubscribe:  [EMAIL PROTECTED]
> Archives:        <>
> Problems?:       [EMAIL PROTECTED]

To subscribe:    [EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:        <>
Problems?:       [EMAIL PROTECTED]

Reply via email to