Search the Community
Showing results for tags 'memory'.
The search index is currently processing. Current results may not be complete.
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
Retrospect 8 for Mac is not completing backup and giving the following error. "Can't save catalor, error -108 (not enough memory)" It was working fine and nothing changed, but last 2 weeks it is giving me this error for the weekly full backup. It works on daily backup. Tape library is just fine and have enough empty tapes in it. Mac server 10.4 has 8 GB RAM and nothing else running. Total volumes need to backup 1.2 TB The backup script has 5 shared volumes to backup. It finishes first 3 and then it stops at number 4 generating this error. The total number of files is about 2 millions. As I said, it worked with all of this just fine. But now it is not working for last 2 weekends. Any idea? Thanks
First: Background Chassis: Dell Poweredge T410 Xeon E5620 @ 2.4 GHz 8GB RAM 5TB RAID 5 on a Dell PERC 6/i RAID controller IBM ULTRIUM-HH5 Tape Drive Software Windows Server 2008 R2 Standard x64 Retrospect 7.7.620 -- It all started when I did a standard cleanup on the RAID and it wiped out the entire catalog set. So I dumped that destination, and started over. Ever since I have started having severe issues with the backup process. The screenshot attached says it all. What ends up happening is even on a full reboot, as soon as it tries to backup any client on the network, Memory usage climbs to maximum and the backup either hangs, or fails eventually with the "Not Enough Application Memory" error. On the worst case, Retrospect throws a cpp error and dumps the process. in either case it damages the catalog file belonging to the destination it was accessing, Attempting to rebuild it, fails with the same error... and endless loops ensue. I am honestly at a loss here... I have not backed up the network since the 1st and I am beginning to look at other options. Help?!
I got the following just now: + Executing Rebuild at 4/28/12 (Activity Thread 2) To Backup Set iCompute11 ... SixOneTree:TAddAbstractFile failed objects.nib !Not enough application memory 4/28/12 3:08:39 PM: Execution incomplete Completed: 326998 files, 19.9 GB Performance: 233.3 MB/minute Duration: 01:26:27 This is an 8 GB machine. I have 2 VMs running, and another catalog rebuild running at the same time,and looking in Activity Monitor, there was almost no "free' memory at the time, but the rebuilds (one tape, one disk file set) were not that large - about 400-500K files, 70 GB data - each. (config: Retro 22.214.171.124, Mac Mini, 8 GB memory, VMware fusion on same machine with 2 VMs (one 1 GB and one 2GB config) Mac OS X 10.6.8.) Is this normal? I'll try again. Maybe doing one at a time is a better bet.