Search the Community
Showing results for tags 'iMac'.
Found 3 results
Hey all. Wondering if anyone has any thoughts about this... Within the last month or so, Retrospect (v12.5.0 (111)) on my iMac (OS 10.11.3) has suddenly stopped working. It's as if the server side just can't start up. I'll launch the application, I'll get a "Connecting," all the various things will populate in the interface, then wham, it's back to "Connecting" again. Even worse, when I went to write this I checked and now I can't connect at all to the server. To note: the server and the Desktop client tools are running on the same iMac. I've run the Retrospect Engine Installer.pkg but that hasn't seemed to help. Activity monitor says that the following are running... RetrospectInstantScan RetrospectEngine Retrospect Client retroclient Yet, I can't get the application to connect with the Server. I've added and removed the server within the application a couple of times. Sometimes as the local iMac's IP, sometime as the local loopback (127.0.0.1). Still nada. Any suggestions would be greatly appreciated! Thanks in advance. cheers cproot
cooterbrown posted a topic in Device and Hardware Compatibility-Mac OS XHey, Recently began going through old dvd's of work. Quickly discovered whole series of disks that are not recognized by my Superdrive. I came to the conclusion that these are disks that were probably archived with Retrospect at the time. Some version or 6 and/or prior. I have DVD-R's from 2005 I can read fine - but have a feeling they were stand-alone instances where I just burned files onto the DVD itself as opposed to using Retrospect. Is this a common occurance? Is there a workaround? Any thoughts? Thanks!
I've just updated all my hardware, including a new MacPro, a new iMac, each with a Promise Technology Pegasus 2 RAID. I am trying to backup to a HP LTO-6 autoloader connected via an ATTO ThunderLink. Setup was fairly easy. I had to update firmware in the ATTO ThunderLink in order to recognize the HP autoloader in Retrospect. Initial backup of terabytes of data is a beast. Initial run and a subsequent attempt have ultimately failed with Retrospect throwing a communication error. After the first failure, I noticed that the Thunderbolt bus seemed to be deaf. There was no activity on the Pegasus drive, and when I double clicked the Pegasus from the Mac desktop, it opened a blank Finder window but the drive was not accessed (no activity on drive's LEDs) and the window never drew. The communications error occurred about 12 hours into the backup, after over 4TB of data had been saved to tape. A simple attempt to reboot the Mac locked up on the spinning beach ball, so I was forced to hold down the power key to shut down the Mac. Everything came back normally, and I restarted Retrospect and resumed the backup. Again, this time after about 18 hours, Retrospect has sent me an email indicating a communication error. Retrospect never crashed or became unresponsive in either incident, but reported the communication error via email both times. Unfortunately, I am on a two week vacation out of state and cannot restart the backup until early next month. Is there a known problem with Thunderbolt? FWIW - my current config is with the Pegasus drive attached directly to the iMac, and the ThunderLink daisy chained off the Pegasus. My next step will be to experiment with chaining order, or to home run each device to a separate Thunderbolt port on the iMac.