Jump to content

thinkjim

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thinkjim

  • Rank
    Occasional forum poster
  1. thinkjim

    I am getting tired...

    Well I've been using 7.5.387 on 4 windows 2000 servers and I've had problems with memory leaks on two of them. The leak occurs only when retrospect is running a backup, using performance monitor you see the paged/non paged pools spike up, and whilst most of the memory is released some is not. If I don't use retrospect there isn't a leak, and I can backup using windows backup without losing memory. Closing / Reopening retrospect doesn't seem to release the memory. The gradual loss of memory means the server has to be rebooted every 2-3 weeks when running retrospect. I was able to solve this problem on one of the servers by completely reinstalling retrospect and also applying the exchange 2000 post sp3 hotfixes, but I still have this issue on the second server If anyone has any ideas?
  2. thinkjim

    Bad backup set header errors

    P.S. I posted the problem on this forum some weeks ago and got no reply. I think it would probably help if EMC had some tech's working on their forums! all you seem to find here are problems and no solutions.
  3. thinkjim

    Bad backup set header errors

    I am using retrospect 7.5 and am unable to get it to backup to single files at all. I have tried this on two servers, and it fails to both local disks and attached storage media. We get a 'Bad Backup Set header' error in the log files. I have to say I'm thinking of switching to Backupexec because Retrospect is so shockingly bug ridden. This is just one of many problems we've had.
  4. Hi, Having trouble with Retrospect since upgrading to version 7.5. I have created a script to backup to a single file on a USB drive and the execution finishes as incomplete with error -641 (chunk checksum didn't match), an error saying Bad Backup Set header found, or Retrospect Crashes with Assertion Failure at "elm.cpp993". I have also tried: 1. Backing up data to a single file on the local disk, c: (not the external usb drive) 2. Test backup of a text file to a single backup file on the local disk (backing up different data) 3. Deleting / Recreating Backup file etc. Retrospect seems to backup perfectly normally my external LTO Tape drive. any ideas?
  5. thinkjim

    Buffer Overrun

    I understand this has been fixed with the the new update, which is version 7.5.387. will give this a shot.
  6. thinkjim

    Buffer Overrun

    Hi I know this may have been posted already in a different thread, but I wonder if the error is for different reasons. I've just installed retrospect 7.5.370 (driver update and hotfix 7.5.11.100) and it crashed during the second script execution (backup to file) with the error: " Microsoft Visual C++ Runtime Library Buffer overrun detected! Program: ...Files\Retrospect\Retrospect7.5\retrospect.exe A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated. " The only difference I can see to the other thread is that the cause is reported in assert_log as user32.dll. I've posted a copy of this log at the bottom of the page. Part of the reason for upgrade was that we were having a problem with retrospect 7.0 leaking memory. Is this just a known fault, is there a solution? thanks in advance ------ assert_log: OS: Windows 2000 version 5.0 (build 2195), Service Pack 4, (32 bit) Application: C:\Program Files\Retrospect\Retrospect 7.5\retrospect.exe, version 7.5.370 Driver Update and Hot Fix version 7.5.11.100 Module Fn (symbol or seg:offset in DLL) Args USER32.dll 0001:0004741b 20deac4 0 0 Retrospect detected a failure: This report documents an unusual condition detected by Retrospects internal integrity checking. This might be caused by a software bug, but can also be the result of an incompatibility, hardware malfunction, damaged system software, or other problems. Details on possible causes can be found on the EMC Retrospect website: http://www.emcdantz.com/support For further assistance, call us at (888) 777-5664 or (925) 600-5304. Please be prepared to provide us a brief description of the steps that led to this failure along with the assert log. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX OS: Windows 2000 version 5.0 (build 2195), Service Pack 4, (32 bit) Application: C:\Program Files\Retrospect\Retrospect 7.5\retrospect.exe, version 7.5.370 Driver Update and Hot Fix version 7.5.11.100 Module Fn (symbol or seg:offset in DLL) Args USER32.dll 0001:0004741b 20deac4 0 0 c54 Retrospect detected a failure: This report documents an unusual condition detected by Retrospects internal integrity checking. This might be caused by a software bug, but can also be the result of an incompatibility, hardware malfunction, damaged system software, or other problems. Details on possible causes can be found on the EMC Retrospect website: http://www.emcdantz.com/support
×