Scheduled Backup Freezes & Still Shows the Backup Set Executing More Than 16 Hours Later

[kenrwilson]

Installed an evaluation version of Retrospect 6.5 on Windows NT Workstation 4.0, Service Pack 6. Using the Activity Monitor under Executing tab, a scheduled backup is still showing the execution of a backup set 16 hours later, but the backup set is not actually executing.

 

Checked the Operations Log to see where the execution of the Backup Set stopped, but this backup set (for this day) does not appear in the log at all. So, tried to view the Session Contents for this backup set, but an error dialog box appeared that said:

 

Can't continue Backup Set B, error -843(resource is in use by another operation)

 

It appears that this schedule backup set has locked up, while attempting to execute. The client computer that Backup Set B backs up, is still running, and shows an error dialog box that says:

 

"8/13/2003 2:56 PM: Script "Backup Set B Rout..." (MICRON_PC): Drive C(C:), Execution incomplete

 

The MICRON_PC is the computer that has main Retrospect backup software installed. Tried to access the client's C: drive from the MICRON_PC computer and found that I had to enter a password to access the client's C: drive. After entering the password, the Backup Set showing as Executing in the Activity Monitor disappeared and an error message appeared in the Activity Monitor Events tab, which states:

 

Can't reserve backup client Kens-notebk; error -519(network communication failed).

 

Why does the error occur only after successful login of the client shared volume?

 

Why does Retrospect not have a way of dealing with network security for accessing client volumes automatically?

 

Is there a way to change network security so this client volume access problem will not occur?

 

[paleolith]

Error 519 is most often a network hardware problem. For example, just a couple of days ago I traced a 519 to a bad 10BT cable. Replaced the cable and all is hunky-dory.

 

But what you describe sounds more like software. I had a similar (though not identical) problem a few months ago. After going around in circles for about a month, I finally cleaned up the client computer: reformatted the HD and reinstalled EVERYTHING, and reloaded documents from backups. Also upgraded Win98 to XP for good measure. ;-) Completely fixed the problem, with NO hardware changes. For more details, find my thread in the Clients and Networking forum.

 

So a 519 isn't necessarily hardware, as Dantz would have you believe. And it's more than a bit annoying that they won't update their KB despite clear reports that it's incomplete.

 

But the software problem may be nothing more specific than classic Windows Rot.

 

Edward