Jump to content

Search the Community

Showing results for tags 'retrospect 10'.

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

  1. Currently running Retrospect 10.5.0 on Snow Leopard Machine: Processor Speed: 2.66 GHz Number Of Processors: 2 Total Number Of Cores: 4 L2 Cache (per processor): 4 MB Memory: 13 GB HDD Capacity: 496 GB Available: 396.91 GB Have been using Retrospect 10 to rebuild catalogues that were previously being used within version 6. The rebuilds have been going fine but lately I have been getting an error of: '!Not enough application memory'. Nothing in my opinion has changed from when we started rebuilding catalogs and in my opinion I would think that the machine being used has plenty of system memory. Has anyone else come across this error on rebuild/repair? Surely there should be an easy solution to this that I'm just missing, or isit simply a bug? Any info would be great. Thanks
  2. We have three OS X servers set to be backed up every night. Intermittently, the backup script fails to complete with the following error message at the bottom. UAllowSystemSleepAgain: IOPMAssertionRelease failed, err = -536870199 Does anyone have any clue as to what the error message is trying to say? The servers are not set to sleep or to shutdown in any manner. The only power saving feature is to turn off the display after 10min. Thanks for your time, Mac
  3. I am getting the error "Scanning Incomplete -516 Illegal Request". Any suggestions. I tried some of the suggestions in the link below and about nuked a critical file installation file. http://forums.retrospect.com/index.php?/topic/150083-trouble-reading-files-error-516-illegal-request/ How do you fix this issue? It just creeped up this last week. Nothing has changed on the client machine. So I don't know???
  4. This has happened on several backups lately. Retrospect 10.5 is backing up both the computer it's installed on (iMac 2006 model running OS 10.7.5) and a Mac laptop. The media sets are all kept on a 4TB Drobo, connected to the iMac. The backups for iMac run at 1am, and the backups for the laptop run at 2am. So I'm not there to watch them run. Checking in the morning, I found that the iMac backup failed due to "error -1101 ( file/directory not found)" I selected the media set, and clicked verify. The response window said that "An error has occurred," and no verify operation ensued. Then I looked at the Summary window. It reported that the set contained no members. I didn't really know what to do at that point, so I quit the application and worked on getting to a place where I could call tech support. A few hours later, I sat down at the computer again, and lo and behold, there was a member in the media set! I quickly selected the script to do the backup into that set, and it ran with no errors, completing in just about six minutes. Does anyone have a clue how a media set manages to "lose" a member, what I can do to recover from it, and/or how does the media set later "find" that member, with no intervention by me? Thanks, everyone, for whatever insight you may be able to provide. Elaine Poe elaine@natca.net
  5. I've been trying Retrospect 10 for Mac for a few days and I've had lots of problems with a Windows client. Error -519 almost instantly (dropped connection). Searching for the error online gave me no results. I've tried everything (updating drivers, checking for network problems), but no result. The last thing I tried was uninstalling Avast! completely and my problems were gone. Note that disabling the shields isn't enough, mb the local proxy is always active? So, if you have -519 errors, check your antivirus software, especially with network shields etc. It might save you some time I replaced Avast with Avira and everything is running smooth now!
  6. I have a 2012 Mac Pro Server (3.2GHz Quad Core Intel Xeon, 16GB RAM) running Mountain Lion Server 10.8.4 and Retrospect 10.1.0 (221). It's connected to a G-Tech G-Speed ES Pro 12TB (9TB RAID 5) connected via mini SAS to an ATTO ExpressSAS R680 and a Overland NEO 200s connected via fibre channel. I have been running Daily, Weekly and Monthly backups for the last 6+ months to LTO5 tape with no issues. Ran a couple simple and small test restores to a local second hard drive on the Mac Pro and that went fine. Now I've run into an issue that required me to re-format the external RAID and restore from tape backup. Should be easy using the previous weeks full weekly backup along with the daily incremental backups should put me very close to where I need to be. Unfortunately I can't for the life of me get Retrospect 10 to restore the data without going non-responsive most of the way through. I have had to force quit Retrospect multiple times and re-boot the server to restart it. I have 3.8TB to restore and the best I can get is about 3TB before it locks up. I have tried multiple times to "Restore only missing files" but the progress details show the entire 3.8 TB remaining. The entire restore should take roughly 8 hours but it never finishes. Retrospect support has helped with a few things but unfortunately I still need help and their support is closed on the weekends, unfortunately I don't have that luxury. Thanks in advance to any help I can get.
  7. I am running Retrospect (and have been since 6.1) on an Xserve 3,1 running Mac OS X Server 10.6.8 with 12Gigs of RAM, 24TB of Active Storage backup disk space and a Quantum Scalar 50 LTO-4 Two Drive Fibre Channel tape library connected via a QLogic 5602 FC Switch with Zoning enabled. I have Advanced Tape Support as part of my licensing. I upgraded Retrospect on this Xserve about 2 weeks ago from 9.0.2 (107) Multi Server/Unlimited Clients to 10.0.1 (105) Multi Server/Unlimited clients. Everything appeared to be OK during the upgrade. Everything remained intact. After the upgrade I immediately started to notice the following day a change in the way Retro 10 scans files and accounts for them. Background: I have a staged backup system in place so that, using Carbon Copy Cloner, I clone two source disks from two different Xserve with the same aforementioned specs. I clone to sync, removing any data on the destination which does not exist on the source. One source has about 5.3 TB and the other about 100GB. They are cloned every 4 hours onto one 12TB Active Storage LUN. From here I use a Retrospect backup to Tape script to perform one Full backup of the 12TB backup disk over the weekend and then incrementals nightly during the week. A new Media set is started during the Full weekend and Skip to New Member is used for incrementals since the tapes are removed offsite daily the following morning. This system has worked flawlessly for several years over several versions of Retrospect and countless Restores have been successfully performed both during DR drills and real emergencies. After upgrading to version 10 I noticed that Retrospect was 'seeing' about 128GB of data during a newly instituted Full backup over the weekend. The Tape Media set showed 128GB in size for the Full backup. Normally the full 5.4 TB was scanned and backed up at the start of a Full backup to a new Media set and then the incrementals averaged about 20GB during the nightly backups during the week. So essentially Retrospect was missing 99% of the data. I even created a new script to make sure that it was not a corrupted script caused by the upgrade to 10. Same results. Retrospect was scanning about 128 GB for the Full backup and 24k or so for the following incrementals. I noticed in the Logs for each backup a mention of the new Instant Scan process. Searching the documentation for 10 and then Forum topics related to Instant Scan (ISA), none of which seemed to mention my specific issue, I decided to disable the ISA process. Once I did that Retrospect performed as expected, 'seeing' all of the data on the source volume (5.4TB total) and backing up all of the data to tape during the Full backup and any changes during the incremental. Am I missing something? Is what I described the proper functionality with the new ISA process? This seems to affect all scripts. I have another Disk to Disk script with the same symptoms when ISA is enabled. Keeping ISA disabled for now. Thanks for any insights...
  • Create New...