Jump to content

Ongoing Error messages


Recommended Posts

Client - MacBook Pro running Tiger (10.4.11) and latest version of Client

 

Here is the log

 

+ Normal backup using Barry at 3/13/2008 9:25 AM

To backup set Barry…

 

- 3/13/2008 9:25:19 AM: Copying Users on Barry…

3/13/2008 9:25:19 AM: Connected to Barry

Trouble reading files, error 519 (network communication failed).

3/13/2008 9:53:55 AM: Execution incomplete.

Remaining: 344655 files, 217.8 GB

Completed: 6764 files, 3.8 GB

Performance: 259.2 MB/minute

Duration: 00:28:36 (00:13:55 idle/loading/preparing)

 

+ Normal backup using Barry at 3/13/2008 9:54 AM

To backup set Barry…

 

- 3/13/2008 9:54:12 AM: Copying Users on Barry…

3/13/2008 9:54:12 AM: Connected to Barry

Trouble reading files, error 540 (trouble creating service).

3/13/2008 11:12:36 AM: Execution incomplete.

Remaining: 277837 files, 198.6 GB

Completed: 66979 files, 19.9 GB

Performance: 298.5 MB/minute

Duration: 01:18:24 (00:10:13 idle/loading/preparing)

 

+ Normal backup using Barry at 3/13/2008 11:30 AM

To backup set Barry…

 

- 3/13/2008 11:30:06 AM: Copying Users on Barry…

3/13/2008 11:30:06 AM: Connected to Barry

Scanning incomplete, error -43 (file/folder not found)

 

One note about the client - there are no other network issues - it has full access to servers and the Net. Even if the only running application is the Finder, I still get 519 errors.

 

This product is becoming unusable and totally unreliable, and EMC/Insignia hasn't done anything about the client side in almost 2 years while continually updating the Windows version (as recently as 1 month ago for the server product). According to their own website, here is the Mac version update record:

 

Retrospect 6.1.138 Installer 2007-12-06

Retrospect Client for Macintosh 6.1.130 2006-05-04

 

My server and all clients are running the latest version, but errors occur on a regular basis

Link to comment
Share on other sites

Let me state again - this Mac has no other network related issues at all

 

> On Mac OS-Based Computers

 

> 1. Check for software conflicts. Firewall software,

> virus checking or file encryption utilities may cause

> problems. Restart the client Macintosh and try to back

> up again.

 

N/A

 

> 2. Ensure there are no unnecessary activities such as

> disk optimization, screen savers, or memory-intensive

> or processing-intensive applications running on the

> client during the backup. Also, verify there is not an

> energy saver that turns off the client computer during

> the backup.

 

Given that the issue happens when nothing else is running, I can’t understand how this is THE problem. When other processor intensive apps are running and being used, I can understand that RR doesn’t have the resources allocated to perform the task, and unlike the earlier OS 9 version, I can’t set the client to have priority over other user processes.

 

> 3. Change the time of the script execution or rearrange

> the backup order of the clients. Backing up the client

> computer at a different time may access the computer

> when it is not busy. If backups work at other times,

> review what is happening at the original time on your

> network or on this client.

 

Manual backup - Running the script immediately

 

> 4. Run Disk First Aid, which checks for directory

> corruption in the disk. Also run Repair Disk (boot the

> machine using the original OS install CD, go to the

> Disk Utility and choose the First Aid tab) which check

> for bad sectors on the drive which could cause hangs or

> backup failures. Be sure not to run tests that will

> erase data. Pay attention to warnings.

 

Done

 

> 5. Connect the machine to a different port on the hub.

> Swap ports and cables with a nearby client that is not

> experiencing network trouble or producing errors.

 

Haven’t tried yet

 

> 6. Try a third-party ethernet card. This can sometimes

> help isolate the problem to a problematic interface.

> Check with the manufacturer or vendor of the client's

> ethernet card or interface and find out whether you

> have the most recent drivers, and whether the drivers

> are compatible with your system software.

 

Built-in Ethernet on MB Pro

 

> 7. Try new hub, switch, connectors, and a network

> cable.

 

Give me a break -again - this Mac works flawlessly on all network activities

 

> 8. Disconnect all external SCSI peripherals from the

> client computer and try backing up the internal hard

> drive. SCSI problems can cause network disconnections

> or hangs.

 

SCSI???

Not on a MB Pro

Not on any Macs in my environment since switching to OS X years ago

 

> 9. Install a copy of the Retrospect application on a

> different computer. Try a backup from this new computer

> to see if the original backup computer was causing the

> problem.

 

Huh? Why would this be, when it works for 99% of the other machines?

 

> 10. Reinstall the networking software and drivers and

> trash any network-related preferences. Try a clean

> installation of system software.

 

So, the fault is elsewhere, not with the RR client?

 

> 11. Try defragmenting the hard disk. Never defragment

> without a good backup!

 

Why?

 

> 12. Try to back up through a direct connection between

> the host and client computer. A crossover ethernet

> cable between the backup computer and a problem client

> allows you to do this.

 

Not a reasonable option

 

Again, I am incredulous. I realize you’re trying to help, and you didn’t write this document (I assume!)

Link to comment
Share on other sites

Client - MacBook Pro running Tiger (10.4.11) and latest version of Client

 

- Retrospect is running on what machine?

- What version of the RDU is loading along with 6.1.138 ?

 

 

> 12. Try to back up through a direct connection between

> the host and client computer.

 

Not a reasonable option

 

Why? A Macbook Pro weighs 5.4 lbs (for the 15") or 6.8 lbs (for the 17") and is pretty easy to carry. A test with a straight connection that fails in the same way points a pretty strong finger at software and against most "environment" causes.

 

Of course, a successful backup might suggest networking hardware after all...

 

 

Dave

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...