Jump to content

Can't Back Up Registry, Error -1019 ( Not Enough Resources)


Recommended Posts

After at least 10 years of using Retrospect, have recently begun to get "Can't back up registry, error -1019 ( not enough resources)" on every backup.

 

System is an HP4400 XP SP3. Plenty (hundreds of gigs) of unused space on all drives. 3 GB RAM. No other applications running. Can't imagine what resource might be in short supply, and can't find anyone reporting a similar experience.

 

Tried doing a full backup with a new backup set to a fresh external drive, but get "malformed backup set name" no matter what I call it. Separate problem, but cause for increasing concern about V7.7.562.

 

I'm hearing a telltale sound that says a drive is on its way out. Assuming the worst, not sure what good a restore of the system © drive would be without a backup of the registry, and would prefer not to find out the hard way...

 

Anyone?

Link to comment
Share on other sites

After at least 10 years of using Retrospect, have recently begun to get "Can't back up registry, error -1019 ( not enough resources)" on every backup.

What does that mean? Every backup of every source? Or "just" every time you backup a specific source? In the former case, restart the Retrospect server. In the latter case, restart the client.

 

Is there a way to check the consistency of the registry? Such as a CHKDSK, but for the Registry instead od the disk drive.

I'm not a "Windows" man by any means, so I have no clue. Except that the registry sometimes get corrupted.

Link to comment
Share on other sites

What does that mean? Every backup of every source? Or "just" every time you backup a specific source? In the former case, restart the Retrospect server. In the latter case, restart the client.

 

Is there a way to check the consistency of the registry? Such as a CHKDSK, but for the Registry instead od the disk drive.

I'm not a "Windows" man by any means, so I have no clue. Except that the registry sometimes get corrupted.

 

Single system, full incremental backup of multiple disks. No server, no client. The registry is just a collection of data files - it can be corrupt internally, but I don't see why Retrospect would be concerned with that distinct possibility...

Link to comment
Share on other sites

The registry is just a collection of data files - it can be corrupt internally, but I don't see why Retrospect would be concerned with that distinct possibility...

The registry has a tree structure of nodes. What if one data node points back to a previous node, creating an infinite loop? Retrospect scans this tree structure to find (and backup) all nodes.

What if one node in the registry says "I contain a gazillion other nodes"? Retrospect scans this tree structure to find (and backup) all nodes.

Link to comment
Share on other sites

I've encountered that error before, and found this guide (recommended on the old Retrospect website/forum) helpful:

 

http://support.microsoft.com/kb/304101

 

However, I got the error when backing up large files (and/or large numbers of files), not the Registry, so this solution might not be relevant for you. But it could be worth trying if you run out of other ideas.

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