Jump to content

rmwilliams23

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rmwilliams23

  • Rank
    Newbie
  1. I am currently in the middle of rebuilding a number of catalogues for use within the newest retrospect. The system used is a tape based system and now within a certain media set retrospect seems to have skipped over tape 17 of this showing 0GB used. I have continued on with the rebuild but now seem to have no way in going back to tape 17 for it to repair the catalogue and rebuild everything on that tape. My question simply, Is there a way around this other than starting the media set rebuild again? Is there a way to jump back to this individual tape and repair it correctly. Thanks
  2. I am currently going through a rebuild from a number of tapes and unfortunately Restrospect seems to be getting stuck when it comes to a certain file. Is there any way of just skipping this single file on rebuild or can I only skip to the next tape to continue the rebuild? Thanks Mac:Lion Retrospect:10.5.0
  3. I was running 16 threads so yes 8 would probably solve it too but to be honest putting it to 1 thread hasn't slowed and rebuild down one bit. As quick as ever so I will persist with it and hope won't be anymore errors.
  4. Ok think I've solved the problem. Seems to be running smoothly now but we shall see. If anyone else gets this problem here's how to fix it. It had nothing to do with system memory but seems that there were too many activities within Retrospect running at once which was giving the '!not enough application memory' error message on rebuild. Luckily there is an option within general preferences that allows you to choose how many activities can run at any one time. The number in the activity threads box had defaulted to 16 so I simply changed this to 1 and now it seems to be running without any problem at all. I have also attached an image so everyone can see where this is. Thanks
  5. I am indeed running 10.5.0 and I did a reboot yes. The rebuild files shouldn't be corrupt as I've previously rebuilt this set on the system but it got lost. So in theory if I update the machine to Yosemite and install the latest version that could very well fix the issue?
  6. Just ran system monitor whilst Rerstrospect was trying to rebuild and the activity monitor said that it never dropped below 13GB of free memory at any time. Should I therefore rule out a system memory problem? The issue still says not enough application memory so that is maybe leading me in the direction of it being a bug/software problem. If anyone could get back to me on this with maybe the same problem that would be great!
  7. 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
×