Appears incomplete and very frustrating!

[Mabans]

I have Retrospect 6.1.138 running on my g4 1.3ghz using Leopard Server as an OS. Now here is a peculiar thing that seems to happen seemingly only during Duplicates and not backups (for incremental)

 

When the duplicate is running I get the following error.

 

File “filename†appears incomplete, path: “pathnameâ€.

 

Yet the duplicate happens and there is a new copy dated the previous day (backup happens over night) at the destination drive and fully working.

 

Now when the incremental happens (we are transitioning as well) those errors are not popping up. Anything I should look for or suggestions?

[twickland]

What happens when you try to copy "filename" in Finder?

[Mabans]

I don't get any errors when I copy from the destination (an external harddrive) or the server that is actually hosting the file. Just a straight copy..

[Mabans]

Bump for help? Please?

[Mayoff]

What happens if you duplicate this data to a different disk? What file system is used for your backup disk?

[Mabans]

No errors. Maybe this may be of help but I can't imagine how it would matter but all the same.

 

There are 2 machines involved.

 

Server 1 that houses the data that needs to be backed up on a Leopard server using Mac OS Extended (Journaled)

 

Server 2 is a Leopard server using Mac OS Extended (Journaled) to run Retrospect and back up files to an external Hard drive formatted to Mac OS Extended (not journaled).

 

Any straight copying from computer to computer, drive to drive and network to drive doesn't yield any errors, I even put in a file there that I was certain wasn't going to be accessed (I'm the only one that knows it's there. =P) and that yields the same error as well.

 

I would like it to be error free when we finally put it to full production. I understand it's most likely something on our end just looking for help on other handled this particular issue. Any help or insight would be great.

[Mayoff]

If duplicating the identical data to a different disk does not cause this error, then Retrospect may be having trouble writing to the original disk. This could be caused by a connection issue or a minor disk issue.

[Mabans]

Interesting.. Any reason why I do not recieve these errors when an incremental back up takes place?

[CallMeDave]

Server 1 that houses the data that needs to be backed up

 

Server 2 to run Retrospect and back up files to an external Hard drive

 

OK, how does Retrospect, running on #2, communicate with #1 in order to access files? (hint question: is #1 running Retrospect Client software? If so, what version?)

 

here is a peculiar thing that seems to happen seemingly only during Duplicates and not backups (for incremental)

Any reason why I do not recieve these errors when an incremental back up takes place?

 

You have stated that you get the problem when you Duplicate from #1 to an external Hard drive on #2. We don't know much yet about how you have configured Retrospect to do this, nor do we know anything about the hardware involved.

 

You have further stated that you do not see the problem when you copy files to a Backup Set. We don't know yet what Type of Backup Set you are using, or if it's stored on the same physical Hard drive as the one involved in your Duplicate operations. But note that Duplicate and Backup are different operations in Retrospect. The issue isn't why one operation works (it's supposed to, after all). The question is why the other one does not.

 

Dave

[Mabans]

The duplication operation is woring but still yielding the dupe. I open it and it seems to work just fine. So this isn't a question of why one works and the other doesn't.

 

I am getting those error messages while the duplication is happening but not when the incremental is running..

 

Now that is interesting that you brought up client on the machines being backed up. I do believe we are using older versions, i will check those out.. thanks..

 

Oh BTW the 2nd external hard drive is sitting on a G4 1.33ghz machine running Mac OS X.5. Also the machine that is being copied from are quad Xeon XServes and 1 Dell dual Xeon rack Server.

[CallMeDave]

When the duplicate is running I get the following error.

 

File “filename†appears incomplete, path: “pathnameâ€.

 

- When, exactly, during the Duplicate do you get the error? Is it during the "Copying" phase, or during the "Comparing" phase?

 

The duplication operation is woring but still yielding the dupe...

 

You hope. If Retrospect is reporting a file incomplete error, I'd be very suspicious of the validity of the file.

- Are you doing any sort of low level comparison between the Source file and the file on the Destination, other then just opening it?

 

the 2nd external hard drive

 

Second external drive? Please explain. What is the first external drive? For what is it used? For what is the second external drive being used? All the hardware is there for you to see; out here on the intertubes, we can only work with the descriptions you provide.

 

At this point, with the limited information provided, Robin's test is the most valuable. What happens when you Duplicate the same Source Volume to a completely different physical Destination Volume?

 

this isn't a question of why one works and the other doesn't.

 

Well, yeah, it is. You report that Backup (what you term "incremental") operations work without errors in the Operations Log, while Duplicate operations have very serious errors noted in the Operations Log.