Jump to content

Assertion failure at "Mem.cpp-993"


rjhfandclf

Recommended Posts

I have just encountered this problem - which causes Retrospect (v. 7.6.111 + 7.6.1.101 fixes) to crash on back-up.

 

I understand it is related to a failure to groom correctly. I am backing-up to a 200Gb external hard drive, which has been progressively filling up. It is now full and contains 865 files in the back-up set, although the grooming is set to keep (and only shows as present) the last five back-ups.

 

I have tried rebuilding the catalogue - which solves nothing. Before I try to repair the file backup set or anything else, I would appreciate guidance, please.

 

How can I i) resolve the present problem, and ii) prevent it from re-occurring ad lib?

 

Thanks!

Link to comment
Share on other sites

Before I try to repair the file backup set or anything else,

 

You mention grooming which is not a feature of file backup sets.

 

I have tried rebuilding the catalogue

Since you seem to be trying to rebuild a file backup set, then you are using the wrong catalog rebuild options for a Disk Backup Set.

 

 

Link to comment
Share on other sites

I'm sorry but I don't understand how this reply in intended to help me. Can we please go back to my original query:

 

I understand it is related to a failure to groom correctly [ref KB 7947]. I am backing-up to a 200Gb external hard drive, which has been progressively filling up. It is now full and contains 865 files in the back-up set, although the [color:blue]grooming is set to keep (and only shows as present) the last five back-ups.[/color]

 

How can I i) resolve the present problem, and ii) prevent it from re-occurring ad lib?

 

Grooming is a normal part of the back-up set-up, is it not?

 

So what are you telling me to do to repair this problem?

 

Thank you.

 

Link to comment
Share on other sites

 

OK - thanks; it was the correct repair route to follow that I was seeking advice for.

 

However, after 3 hours rebuilding from the disk, I have tried again to run back-up and to groom out the excess files, but the disk remains full and fails via the same error message: Assertion failure at "Mem.cpp-993".

 

The problem still seems to be that the grooming only restricts the back-up snapshots and does not reduce the mounting files via the sessions.

 

What should I try/do next to correct this problem please?

 

Link to comment
Share on other sites

 

OK - I have now done that - renamed Retrospect as 'old'; re-registered the product on the PC, then completed a full catalogue rebuild from the disk, but it is still exactly the same - as soon as I try to do anything (back-up or groom separately) I get the same error notice and the program closes.

 

I still have the correct 5 snapshots listed. but also the same 865 .rdb disk backup set files on the backup disk.

 

Also the re-cataloguing covered 300,000 files in 180Gb - but my C drive only contains 60Gb in used space (don't know how many files).

 

Incidentally the program sends a "assert_log.utx" error report to EMC.

 

 

Link to comment
Share on other sites

OK - I have now done that - renamed Retrospect as 'old'; re-registered the product on the PC, then completed a full catalogue rebuild from the disk, but it is still exactly the same - as soon as I try to do anything (back-up or groom separately) I get the same error notice and the program closes.

 

 

Since the above action, I have had major problems with continual BSODs with IRQL messages. I have rolled back the PC by one day. This does not reverse all the Retrospect changes, so I feel now that the only thing I can do is to uninstall and re-install Retrospect, and clean out the back-up disk and start from scratch again.

 

If you can see any easier way of resolving this, I will be pleased to hear.

 

 

Link to comment
Share on other sites

Well since the test you suggested above is the only alteration/update I have made to the PC in 24 hours and since reversing it cures the Blue Screen issue, I calculate that it must be responsible for creating some sort of conflict.

 

Anyway, I assume from the brevity of your response that you cannot contribute further to resolving this failure of Retrospect to groom my disk properly, so I guess I am left with the blunt option of deleting everything and starting from scratch.

 

It certainly doesn't seem very satisfactory.

Link to comment
Share on other sites

Marc - Thanks for the comment ... and yes, it was set to 'on' (I had never even thought about it - so that is really helpful, thanks!).

 

I have corrected this anyway, but I am not entirely sure whether you are saying this may be causing the problems with my original query (of the failure to groom) or the later one of the crashing system.

 

Your clarification will be much appreciated. I will then try another back-up with groom!

 

Thanks - Robin

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...