Jump to content

Search the Community

Showing results for tags 'yosemite'.

  • 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 6 results

  1. We have had to upgrade the failed drives on our Mac Pro OSX Server from 10.7.5 to 10.10.5 An opportunity to update for this OSX Servers compatibility too .. it is 5 years+ old. Anyway ... Retrospect will no longer see our Overland 200-S Tape Deck. I checked the compatibility with the ATTO SAS R680 for OSX Yosemite and installed the latest drivers. [see attached images] The Mac sees the ATTO Card [see attached images] Retrospect v 9.0.2 does not. I checked the compatibility for Retrospect v9.0.2 and it said OSX 10.6.8 an up? I assume that information was updated with each OSX version? [see attached images] I can see the Overland alive an AOK too. [see attached images] Any idea's welcome ... I am unsure it is an ATTO or OVERLAND issue. Thank you, James R
  2. Hi all, In my workplace, we're currently using Retrospect 11.5.3 to backup all of our systems. We're considering making the jump to RS 12, but I'm concerned by some of the weird quirks I've encountered in 11.5.3 (such as: scheduled backups not running - engine needs a reset, backup clients not found - sources need to be relocated, reserved backup clients - client system needs a reboot, among some others....) and would like to get an idea of whether I should expect things to be better or worse in version 12. So before we go any further in consideration, I'd like to ask forum users about their experience with Retrospect 12. Any input as to what issues I might expect, or expect to be resolved, what works, what doesn't, and anything relating to 11 vs. 12 overall would be greatly appreciated. Thanks, Jeff
  3. Hello, this note is a reminder to the community to use .metadata_never_index at the root of your backup drive to stop Spotlight from competing with Retrospect for access to the same drive. After searching the Knowledge base and the user forums, I didn't actually find this information - although the topic is so basic it is probably present and I missed it. In case it is useful to other searchers, I am providing this note because this morning I spent a fair amount of time trying to debug what appeared to be an 11.5.3 performance problem in Retrospect which turned out to be caused by the MacOS Spotlight feature. This is not a Retrospect problem, however it would be a useful Retrospect default option to automatically create a .metadata_never_index file in the directory containing the Media when you create disk Media in Retrospect. Symptom: Retrospect server reported performance drops to a surprisingly low <100MB/min in Details section of "Activity Pane" on a running script. Alternately, cumulative reported performance in the log file less than 500 MB/min. Environment: Retrospect Server and client running on the same MacBook Pro Retina 15. Yosemite 10.10.1. 16 GB RAM. Backup volume is a new volume (fresh erase), first Media write of Retrospect backup (new catalog). Catalog stored on backup volume. Source drive was an SSD. Backup drive was a WD 750 GB drive. Possible Cause: a new volume with significant MacOS Spotlight activity competing with Retrospect for access to the same drive. Solution: disable Spotlight indexing on the backup volume (this is the normal preference as such spotlight indexing provide no value to a backup volume) Methods to disable Spotlight on a backup volume -- System Preferences/Spotlight/Private is the most discussed approach, but I found it unreliable - perhaps because I was changing volumes. -- most reliable method: from a terminal window (Applications/Utilities/terminal) create any file (can be empty) named .metadata_never_index at the volume or drive root level. ----- the command I used was ---------- sudo cat /dev/null > /Volumes/<yourBackupDrive>/.metadata_never_index ---------------- if sudo has permission issues you can enable root access (dsenableroot & dsenableroot -d to disable) to briefly sidestep the permissions. ---------- although it is probably not necessary, after creating the file I rebooted to be sure that Spotlight noticed the .metadata_never_index file. In my particular case, I was using a WD7500AYYS 750GB drive over FW800 via the MacBookProRetina Thunderbolt adapter. Using Drive Genius 4 "Speed" testing, disk access dropped to a reported 10.25 MB/sec when Spotlight was indexing the new Retrospect data. After executing sudo cat /dev/null > /Volumes/<yourBackupDrive>/.metadata_never_index the reported speeds from Drive Genius went to 47 MB/sec. Log file reported that backup performance improved from 349.4 MB/min to 1,386 MB/minute. Verify operation 4,374 MB/minute (SSD source drive, WD 750 GB destination drive) If I see other performance problems which indicate some other cause, I'll update this post, however the problem is repeatable (erase backup volume) and the solution is repeatable, so I think this is the root cause. best regards, parker9635
  4. I just bought a Mini with Mac OS X 10.10 on it, and wanted to back up the disk image before I blew it away, and retro barfed on me: *File "/Volumes/MacOSX/usr/share/terminfo/68/h-100bw": can't read, error -1100 ( invalid handle) *File "/Volumes/MacOSX/usr/share/terminfo/68/h100": can't read, error -1100 ( invalid handle) *File "/Volumes/MacOSX/usr/share/terminfo/68/h100bw": can't read, error -1100 ( invalid handle) *File "/Volumes/MacOSX/usr/share/terminfo/68/h19": can't read, error -1100 ( invalid handle) *File "/Volumes/MacOSX/usr/share/terminfo/68/h19-a": can't read, error -1100 ( invalid handle) *File "/Volumes/MacOSX/usr/share/terminfo/68/h19-b": can't read, error -1100 ( invalid handle) I got 98000 of these errors. Is there something in the 10.10 filesystems that retro 10.5 can't deal with? I see "full support" for 10.10 appearing in retro 11. Is this the problem that requires increased supprt?
  5. Client computer updated to Yosemite. Retrospect Client 10.5 was running on mavericks. Retrospect will not turn on when clicking "on" in client control panel. Uninstalled 10.5 client and installed 11.5.2 client and still cannot turn on retrospect client. I choose "on" but never changes to "on"
  6. Console and Server run on same machine. Wiped drive and clean install of OS (10.10) Fresh install of Retrospect 11.5.1 Entered License code Quit Restored entire contents of /Library/Application Support/Retrospect Restored ~/Library/Preferences/com.retrospect plist When the console is launched, all Rules, Catalogs, Media Sets, the whole shebang is missing. Not sure if this is a Yosemite problem or a restore problem.
  • Create New...