Jump to content

Search the Community

Showing results for tags 'case-sensitive'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. Retro 10.2.0 (221) running on Mac OS X 10.8.x I would like to have a Mac OS X volume that is case sensitive, and back it up with Retrospect. I generally test before I rely on them, and I have found that case-sensitive restores do not work on local volumes, nor with a "new" client. If I have 3 files "FILE", "file" and "File" on a case sensitive volume, they are restored correctly on a Mac OS X 10.5 client running on a PPC machine. (client v 6.3.029), but that is the ONLY way I can get it to work correctly. On local volumes (local to the machine running the Retro engine) they come out as "FILE", "File-1" and "file-2". I get the same result on several variations of local volumes that are formatted as HFS case-sensitive. I have also tried this on a Mac OS X client running 10.6.8, and Retro client 10.2.0 (221). I formatted an external Firewire drive case-sensitive, journalled. I got the File-1, file-2 result. Obviously, this would not be acceptable where many files depend on case differences. Is case sensitivity supported? I am squeamish about relying on my 10.5 PPC system for something I need, and if I start doing this, it will be "production" for me. Thanks,....