Verify of client stops

[vac]

Hello everybody,

 

I have a environment of two Windows 2003 servers. One fileserver and one terminalserver, both on the latest Microsoft patchlevel. We are using Retrospect 7.6, Retrospect is installed on the fileserver with a external Tandberg Data Storageloader 1U sttached (SCSI), the terminalserver is backuped using the Retrospect client 7.6.

After several months/years without any problems I got now the following error:

 

After finishing the backup, the verify process starts. Then suddenly, the data throughput drops to 0,0MB/min and the verify process does not continue. If I make nothing, the job will run endless and will never finish.

The curious thing is: the verify process stops at different files. For example job a) stops at some windows internal files, I cancel this job and start job and this fails for example on some user data files.

the last message within the backup protocoll was for example (translated)

File "C:\Documents and Settings\%USERNAME%\local settings\Application Data\Mozilla\Firefox\Profiles\m7efrya0.default\Cache\B841FE5Ad01": could not be read, Error -1101 (File/Directory not found)

 

There are no additional error messages in the eventlog on the fileserver or the terminalserver.

We made no changes to this systems, except Windows updates. What did we tried:

 

- rebooting both servers

- deactivated antivirus software

- reinstalled and readded the client on the terminalserver

- updated network drivers

- changed network cables

- changed scsi cables

- changed scsi terminator

- changed order within the backup source groups

- try to add the volumes of the client to retrospect instead the whole client

 

Any ideas how to resolve this issue?

 

best regards

[Lennart_T]

You may have a corrupt disk directory. Try running CHKDSK.

[Daniels]

You may also want to skip the cache files since I have never found any reason to back them up.

[vac]

Hi Daniels, hi Lennart,

 

thank you both for the reply and suggestions.

 

@Lennart: will try that

 

@Daniels: those cache files were just an example. You're right, there's no need for them, but the verify also stops on other, more important, files. I can exclude the mentioned files, but this won't help me with the rest.

 

Anyway, I will try a chkdsk on this machine and we'll see if this solve my problem.

 

If someone have more ideas, let me know.

 

best regards

Edited August 10, 2010 by Guest

[Daniels]

Do you know if the computer goes to sleep or is restarted at a certain time? If the communication between the client and server is lost it could just stop the backup and be waiting for the computer to respond. I have seen it happen where it just keeps retrying and never proceeds onto the next client.

[vac]

Hi,

 

because this server is a terminalserver it runs 24/7. it was never restarted during a backup or something like that.

 

best regards

[vac]

UPDATE: I tried a CHKDSK yesterday on the mentioned terminal server, sadly without any success. Oh wait, the first backup after the reboot runs fine, I started later the day another backup to verify that my problem is solved. Guess what... this backup actually has a throughput 0,0MB/min and hangs.

 

Some more solutions?

 

best regards

[johnnymacgo]

It could be happening due to a corrupt Retrospect configXX.dat file. Try creating a brand new one on the backup server and see if the backup then works. I had a very similar problem like this backing up a remote client and it ended up being a corrupt configXX.dat file.

 

Johnny Mac

[vac]

Update: I solved my problem moving the problematical server to the end of my volume list. During the problem he was at the top of the volume list, after moving it to the end the problem was gone.

 

best regards