Case history:Client 7.7.100 on RedHat AS5 found to crash Windows Retrospect Server 7.7.341

[pcg-cornell]

[support ticket #1111227]

Client Version 7.7.100 installed on RedHat AS 5

Server version 7.7.341 x64 installed on Windows Server 2003, Dell 2950 quad core

Retrospect was crashing on linux backups - on the server side it just

says "RS quit unexpectedly - possibly due to power outage."

on the client side in /var/log/retrospectclient.log

" ConnReadData: Connection with xxx.xxx.xxx.123:2757 was reset"

in /var/log/retropds.log there were errors:

volScan: Can't open directory "/users/xxxxx/üÃÃÆ¥Ã" and similarly named directories.

These file names came from files originally named in Chinese pictograms.

After some noodling around and testing we found that Retrospect on the server was crashing when these "can't open" errors were thrown on the client. We edited the script to exclude the nasty files but (evidently) the catalog operation doesn't exclude accessing the files, just the backup. We then hid the files by tar/zip of the drectories.

btw: New scripts or changes made to scripts were lost when Retrospect server crashed...

Is there a way to save things that would keep this from happening? A file->exit did save the changes.

Since this was a .5 tb partition it took several days re-running the script until we ferreted out all the wierd file names - (only 4 dirs but 2 were near the end)

 

[Mayoff]

That version of RH has never been tested with Retrospect and is not officially supported by us.

[Antti]

Old post, but we have similar trouble with RHEL5. According to this: http://retrospect.co...-client-support it seems to be a supported client. I filled the support form and will post the outcome of the case here.