Jump to content

Search the Community

Showing results for tags 'communication error'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. 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.
×