Jump to content

mwilliamson

Members
  • Content count

    31
  • Joined

  • Last visited

Everything posted by mwilliamson

  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
  16. mwilliamson

    What on earth is going on at Dantz/EMC?

    I just think they need to decide if they really want Retrospect to be an "Enterprise" backup solution. MAC's have a very small if any part in most enterprises. Last time I checked nearly all web servers, database servers, file servers, Active Directory servers, (need I go on), run on Windows or UNIX. As we speak they are losing their share of the "Enterprise" backup market because 7.7 just plain doesn't work yet. But I guess that's not important as long as you have a good backup of the "Creative Guy"'s MAC.
  17. mwilliamson

    Slow matching under 7.7?

    Hi guys, you may have seen me in another thread. http://forums.dantz.com/showtopic.php?tid/32765 I am having all of the same problems as well as a lot of "assert" errors and crashes. The recent update to 7.7.208 hasn't really fixed anything.
  18. mwilliamson

    HeapValidate error on client backup

    Yes, the support team has confirmed it is happening on both 32 and 64-bit systems.
  19. mwilliamson

    HeapValidate error on client backup

    Hi all, below is the thread I have been posting on. The is the same memory error everyone who has large backup jobs is seeing. It almost seems worse after the update from 7.7.203 to 7.7.208. I have been sending my assert and operations logs to EMC support but still no fix for this particular issue. I am completely unable to rebuild a large catalog file and twice have had to blow away my backup sets and start over. http://forums.dantz.com/showtopic.php?tid/32765 -Matt
  20. mwilliamson

    7.7.203 memory leak?

    Windows Server 2003 Std SP2 4GB of RAM I just checked this morning and had another crash over the weekend. - 1/31/2010 9:19:41 AM: Copying Local Disk (C:) on ad2 TMemory::freeSpace: HeapValidate failed TMemory::freeSpace: HeapValidate failed TMemory: heap 85 4,255 K virtual 13 183.0 M commit 183.0 M purgeable 0 zero K Pool:pools, users 3 11 max allowed mem 614.0 M max block size 8,192 K total mem blocks 2 16.0 M used mem blocks 2 16.0 M file count, size 1 8,192 K requested 98 10.8 M purgeable 0 zero K avail vm size 1,498,349,568 B TMemory::mhalloc: VirtualAlloc(256.0 M, MEM_RESERVE) failed, error 8 TMemory::freeSpace: HeapValidate failed TMemory::freeSpace: HeapValidate failed TMemory: heap 86 4,257 K virtual 13 183.0 M commit 183.0 M purgeable 0 zero K Pool:pools, users 3 11 max allowed mem 614.0 M max block size 8,192 K total mem blocks 2 16.0 M used mem blocks 2 16.0 M file count, size 1 8,192 K requested 99 10.8 M purgeable 0 zero K avail vm size 1,498,349,568 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 1/31/2010 at 9:29:12 AM
  21. mwilliamson

    7.7.203 memory leak?

    Here is the error I am getting when I try to recreate a catalog file... + Executing Recatalog at 1/27/2010 11:12 AM (Execution unit 3) To Backup Set Office_Servers... TMemory::freeSpace: HeapValidate failed TMemory::freeSpace: HeapValidate failed TMemory: heap 95 2,524 K virtual 19 104.5 M commit 104.5 M purgeable 0 zero K Pool:pools, users 4 65 max allowed mem 614.0 M max block size 8,192 K total mem blocks 6 48.0 M used mem blocks 6 48.0 M file count, size 5 40.0 M requested 114 33.7 M purgeable 0 zero K avail vm size 893,784,064 B TMemory::mhalloc: VirtualAlloc(268.0 M, MEM_RESERVE) failed, error 8 TMemory::freeSpace: HeapValidate failed TMemory::freeSpace: HeapValidate failed TMemory: heap 96 2,525 K virtual 19 104.5 M commit 104.5 M purgeable 0 zero K Pool:pools, users 4 65 max allowed mem 614.0 M max block size 8,192 K total mem blocks 10 80.0 M used mem blocks 10 80.0 M file count, size 9 72.0 M requested 115 33.7 M purgeable 0 zero K avail vm size 893,784,064 B TMemory::mhalloc: VirtualAlloc(268.0 M, MEM_RESERVE) failed, error 8 Backup Set format inconsistency (6 at 987720527) 1/27/2010 1:37:40 PM: Execution incomplete Completed: 1892990 files, 383.7 GB Performance: 2769.7 MB/minute Duration: 02:23:49 (00:01:58 idle/loading/preparing)
  22. mwilliamson

    7.7.203 memory leak?

    Unfortunately nothing was appended to the assert log. In fact the jobs running at the time have no log information. The operations log indicates the following error prior to the crash but I'm not sure it's related. I already have an open case...C4232123. TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398 TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398 TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398 TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398 TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398 TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398 TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398 TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398 TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398 TVol::GetInfo: UGetVolumeInformation failed, Y:\, osErr 1398, error -1001 MapError: unknown Windows error 1,398
  23. mwilliamson

    7.7.203 memory leak?

    Just another update. Retrospect crashed again with two jobs running (about 6 hours in). -Matt
  24. mwilliamson

    7.7.203 memory leak?

    I have installed the patch. On my first shot the backup ran about 48hour before crashing with the following errors in the operations logs. After restart on my my backup set catalog files was corrupt. I was unable to rebuild as I would continue to get the TMemory HeapAlloc errors. I would up having to delete the entire backup set start over. I restarted the script and it's now been running about 6 hours. Only time will tell if this patch resolved the problem. So far, there is no indication that it has. -Matt
  25. mwilliamson

    7.7.203 memory leak?

    The problem with me rolling back is I don't believe the backups I've done on 7.7 will be readable. I have had some complete so do have some snapshots I want to keep. Were you able to recreate a catalog file in 7.6 using 7.7 backup set files? I can't believe EMC is not going to address this. I am seriously considering another backup product at this point. Retrospect is only more cost effective if it works. -Matt
×