Jump to content

Windows Client 8.1 not respecting Privacy

Recommended Posts

I'm running a Retrospect 10.1.0 (221) Server on a 10.6.8 Mac to back up a Windows XP client running Client 8.1.0 (266). One folder kept throwing errors due to the activity in it (anti-virus folder), so I decided to add that folder to the list of folders not to back up. It was added under the Client Privacy tab. But I'm still getting errors from that folder because Retrospect is apparently still trying to back it up.


There are currently two folders listed under the Privacy tab. A folder previously added under Retrospect Client 7.5 and the new folder. The old folder has backslashes for the path delimiters. The new one has forward slashes.


Any suggestions?

  • Like 7
Link to comment
Share on other sites

If you can't get the forward slashes changed to back slashes (Solidus and Reverse Solidus to give them their typographic names) there is a configuration file called RETCLIENT.DAT that can be edited. On Windows XP this file should be in the "C:\Documents and Settings\All Users\Application Data\Retrospect" folder. The file is a plain text file and can be edited with the Windows Notepad text editor (notepad.exe).


The file contains two entries for each folder to be made private. The first specifies the folder in long file name format and the second in 8.3 compatible file name format as in the example below:

I:\Images\Lightroom Catalogs\Main Lightroom 4 Catalog\Main Lightroom 4 Catalog Previews.lrdata
To be on the safe side make a backup copy of the file before you edit it.
Link to comment
Share on other sites

  • 4 weeks later...

Thank you both for your reponses.


Lennart, the client does not allow typing path names.


Scillon, the RETCLIENT.DAT was not within the Documents and Settings folder. I eventually found in it C:\Windows\. This may have changed for client 8.1. I made the change and tonight's backup should let me know if it fixes the problem.


Thanks again.

Link to comment
Share on other sites

  • 4 weeks later...

Thank you, Robin. The option to allow client privacy was already on.


Scillon's suggestion fixed the problem, but not immediately. The first backup after editing the file still exhibited the problem. But after restarting the client computer the privacy setting was finally recognized.

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.

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.


  • Create New...