Jump to content

mwilliamson

Members
  • Content count

    31
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mwilliamson

  • Rank
    Newbie
  1. mwilliamson

    Retrospect Crashes

    I just wanted to chime in. I too have experienced these same issues since 7.7 came out. I have plenty of free space on C: more than 15GB for each execution unit and is it still crashes. When I run only two execution units it might run for a day or two or even a week but eventually crashes. When I run any more than two execution units it crashes overnight everytime. I am on 32-bin Win 2003 Std. Are any of you running 64-bit? Does it alleviate the issue at all? I read older posts related to 7.6 saying this problem went away on 64-bit installs.
  2. Hi Pete. I've been in the same boat since 7.7 came out. I upgraded immediately because I'm backing up some Win7 machines. Sometimes it will go a few days on 2 execution units but always eventually crashes with the tmemory or other error. It's odd because I also often notice it crashes while backing up a domain controller. We have 4 and quite often the crashes occur when it's backing up one of them. I have tried uninstalling and reinstalling the client but it hasn't helped. I also have a case open with support but they don't ever do anything but ask for the logs and then I never hear back from them. Per their suggestion I have recreated my config file and rebuilt the server with a larger O/S partition. Nothing has fixed the tmemory errors. If I run on 1 execution unit it seems okay but for me that's not enough to back all my stuff up. Am wondering what direction this product will take under Iomega's direction. -Matt
  3. mwilliamson

    ok - so who has tried 7.7 build 325?

    No dice. It just crashed again with the TMemory assertion error. I am now going to try deleting and recreating the config file. Unfortunately I will have to recreate all of my scripts and catalog files. If that doesn't work I guess I'll have to completely rebuild the server with a larger OS partition. I really need to be able to run more than 2 execution units.
  4. mwilliamson

    ok - so who has tried 7.7 build 325?

    Yes, I did reboot the server after changing the variable. I have now tried changing the location of the Temp directory for the logged in domain account. I restarted the jobs and we'll see how it goes.
  5. mwilliamson

    ok - so who has tried 7.7 build 325?

    Just got in this morning and checked out Retrospect. Even after moving the default Windows temp folder to a different disk I am still getting the TMemory assert crash when I use more than two execution units.
  6. mwilliamson

    ok - so who has tried 7.7 build 325?

    I changed the default temp directory from C:\WINDOWS\TEMP to G:\WINDOWS\TEMP and restarted Retrospect. I then started some jobs. I don't see any files populating there. I only see files in C:\Documents and Settings\Administrator.\Local Settings\Temp\1 They are called RetroMapper_XXXX.tmp, there appears to be one for each execution unit and they are all 8,192KB. Are these the cache files? If so why so small and why would you need 10-15GB of free space for each execution unit?
  7. mwilliamson

    ok - so who has tried 7.7 build 325?

    I have 17GB of free space on my C: drive. Oddly, I never had issues running 4 execution units on v7.6. Is there a way to tell it to cache on a difference disk?
  8. mwilliamson

    ok - so who has tried 7.7 build 325?

    It is 32-bit Windows 2003 Server Std. SP2 w/4GB of RAM.
  9. mwilliamson

    ok - so who has tried 7.7 build 325?

    I was excited to see the update. I installed it, bumped my execution units back up to 4, and started 4 jobs. I ran for a couple of hours and then.... TMemory: heap 120 4,652 K virtual 20 241.5 M commit 233.5 M purgeable 0 zero K Pool:pools, users 7 17 max allowed mem 614.0 M max block size 8,192 K total mem blocks 6 48.0 M used mem blocks 4 32.0 M file count, size 0 zero K requested 140 186.1 M purgeable 0 zero K avail vm size 1,170,460,672 B TMemory::mhalloc: VirtualAlloc(256.0 M, MEM_RESERVE) failed, error 8 TMemory: heap 121 4,654 K virtual 20 241.5 M commit 241.5 M purgeable 0 zero K Pool:pools, users 7 17 max allowed mem 614.0 M max block size 8,192 K total mem blocks 6 48.0 M used mem blocks 4 32.0 M file count, size 0 zero K requested 141 194.1 M purgeable 0 zero K avail vm size 1,170,460,672 B TMemory::mhalloc: VirtualAlloc(256.0 M, MEM_RESERVE) failed, error 8 TMemory::SetSize: priority 2 failed from 128.0 M to 256.0 M Assert occurred on 3/29/2010 at 3:31:39 PM Still seeing the TMemory "assert" crash.
  10. mwilliamson

    7.7.203 memory leak?

    Any response Robin? I have a ticket open and last communicated with K. Dukes....he never responded back after I sent him several sets of error logs. This was a month ago and he said he was escalating it. Thx.
  11. mwilliamson

    Slow matching under 7.7?

    Am also hoping the "tmemory" crashes will also be remedied. I still can only use 2 execution units. If I use any more the system inevitably crashes after several hours. On 7.6 I had no trouble running 4 execution units for several days at a time without crashes.
  12. mwilliamson

    Slow matching under 7.7?

    I have given this info. to you before and also to the support team. I am running 32-bit Windows 2003 Server SP2 with 4GB of RAM. Retrospect version is 7.7.208 with Driver Update and Hot Fix version 7.7.1.102.
  13. mwilliamson

    Slow matching under 7.7?

    Hi all, I am seeing the problem and its taking all the fun out of using Retrospect. It seems I am about the last hold-out on this forum for rolling back to 7.6. It seems they know about all the bug problems but are hiding it. My sales rep...for a hardware vendor that shall remain nameless, did some research posing as a potential customer. The Retrospect sales rep. would not say anything about the buggy latest release and when pressed said he hadn't heard of any problems. My rep also confirmed with their Symantec Contact that BE quotes and sales have risen sharply over the last few months. So, to EMC/Iomega...please keep working on fixing this. I am holding out but can't for much longer. And yes, I have an ASM, and no, it hasn't done me any good.
  14. mwilliamson

    Windows 7 (MSDN Official) and invalid Public / Private Key

    When I've seen that error I just "forgot" the client from the list, uninstalled the client, reinstalled the client, and readded the client....and it seems to work. I was backing up Windows 7 for a while on RS7.6....am now on RS7.7 and can't backup much of anything. If you are using the Documents and Settings selector be sure to add "or path matches pattern C:\Users" to the spec.
  15. mwilliamson

    Slow matching under 7.7?

    I feel your pain Rich. I have 40 servers and many of them have files numbering in the millions. Backups are taking 2-3 days and thats "if" they complete before I get the TMemory error and assert crash. I have broken up source groups, recreated catalog files, and tried everything else in my power and RS is still not getting it done. I can't believe they can't fix this issue. They have the code for version 7.6 (where this didn't happen). I am being forced to get quotes for BackupExec, Data Protector, and CommVault because we can't go on much longer this way. My company stands to lose money and I stand to lose my job if this keeps up. -Matt
×