randeep Posted April 15, 2009 Report Share Posted April 15, 2009 We are using Retrospect7.6.123 version. One time out catalog file got corrupt. Then we repaired catalog files and then started backups. Backups started happening successfully. But again catalog file got corrupt. Can please somebody help me out why is this happening again and again? Its very urgent. I am unable to take my backup. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 15, 2009 Report Share Posted April 15, 2009 How did you repair the catalog? What steps? What type of backup set? What operating system? What path do you use when saving the catalog file? Quote Link to comment Share on other sites More sharing options...
randeep Posted April 24, 2009 Author Report Share Posted April 24, 2009 How did you repair the catalog? What steps? What type of backup set? What operating system? What path do you use when saving the catalog file? Ansr: Went to Tools>Repair catalog, then selected the disk which contained the backupset, then started repairing. It got repaired successfully. Disk type backup set Windows 2003 D:\IT Catalog file We use the above path to sace the catalog file. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 24, 2009 Report Share Posted April 24, 2009 Went to Tools>Repair catalog, then selected the disk which contained the backupset, then started repairing. That is missing a critical step. Which repair type did you pick? Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted April 27, 2009 Report Share Posted April 27, 2009 There would only be two options wouldn't there? Repair existing Catalog file or create a new one. I always create a new one as repairing these things is buggy as hell and often simply wastes a day of my time. I'm repairing another catalog today, my "Friday backup" drive as it managed to corrupt itself again. Once these things corrupt it causes MASSIVE problems as not only are several hours spent rebuilding it, I then need to backup all the servers missed over night during the working day. Retrospect SERIOUSLY need to fix this problem as it's being going on for years and it appears to be thought of as 'acceptable' by EMC engineers!? Rich Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted April 27, 2009 Report Share Posted April 27, 2009 Retrospect SERIOUSLY need to fix this problem as it's being going on for years and it appears to be thought of as 'acceptable' by EMC engineers!? I'm sure the problem can be fixed as soon as you (or any other person) comes up with a step-by-step instruction on how the problem can be reproduced by the EMC engineers on any hardware, not just yours. Quote Link to comment Share on other sites More sharing options...
robvil Posted April 28, 2009 Report Share Posted April 28, 2009 This is not a true statement you give here. This error is not hardware related, but is 100% caused by a bug in retrospect. I get this error every 7/14 days on one of my backup sets when it gets groomed. We have replaced everything except the retrospect software and still see this issue. I personal believe this error should be a top priority fix. This is a reply from tech support when I confronted them with this: "Grooming is not perfect. For some customers it works 100% of the time. For others it works 50% or less. For me, I will sometimes need to do 2 catalog rebuilds before I can finish a really big grooming operation. The larger the backup set, the greater the chance grooming will fail and require a catalog rebuild. For now, all we can do is suggest they try catalog rebuilds between grooming attempts until all needed data is groomed or switch to a strategy of recycle backups along with Snapshot Transfers to new sets. We will be looking at the grooming feature, but I don't expect bug fixes to happen until the next major release at the earliest. " Regards Robert Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted April 28, 2009 Report Share Posted April 28, 2009 (edited) Lennart, I take it from that response that you have never had to rebuild a catalog? The EMC guys on here have had to rebuild their own catalogs, so they must know EXACTLY why it is occuring! (or at least should be able to analyse the problem). Holy cow Robert, nice 'support' response! Rich Edited April 28, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted April 29, 2009 Report Share Posted April 29, 2009 Lennart, I take it from that response that you have never had to rebuild a catalog? Unfortunately, I have to rebuild catalogs every once in a while. As a software engineer, I know it's almost impossible to fix something that isn't reproduceable with a reasonably high probability. So a way to reproduce this problem is what I challenged you to provide. I have one disk backup set now that refuses to rebuild correctly due to a damaged file. (The file was damaged due to failing hardware, not Retrospect's fault.) BUT, there is no way to rebuild successfully, so I have to do a recycle this week. Sigh. Quote Link to comment Share on other sites More sharing options...
robvil Posted April 29, 2009 Report Share Posted April 29, 2009 Lennart, You are correct and yes it can be very hard to track down periodicly bugs. We code our own PoS systems and we do also have bugs. But when a customer is saying to us there is a periodicly fault/bug we do not deny it and we investigate it hard until a resolution a found on our own equitment. It seems as EMC keeps saying it´s hardware related and not there fault dispite many customers have complained about this issue. Robert Quote Link to comment Share on other sites More sharing options...
randeep Posted May 8, 2009 Author Report Share Posted May 8, 2009 I choosed Recreate from Disk option. Quote Link to comment Share on other sites More sharing options...
randeep Posted May 8, 2009 Author Report Share Posted May 8, 2009 Hello Richy, I also used recreate from Disks option, but again catalog file got corrupted after 10-15 days. I don't know why is this happening. Can somebody help me out. We need to resolve this matter urgently and i am unable to find any solution. Quote Link to comment Share on other sites More sharing options...
emulator Posted May 8, 2009 Report Share Posted May 8, 2009 I've found that when trying to do a groom on a VERY large backup set (e.g., 1-2TB), that Retrospect completely crashes (assertion error). I didn't realize that the grooming function was so buggy. Quote Link to comment Share on other sites More sharing options...
dbakerstl Posted May 8, 2009 Report Share Posted May 8, 2009 I dont know if its a best practice, but I tend to break-up my backups into smaller sets if possible. Instead of backing up an entire server in one set organize a couple of sets for that one server, so they are more manageable, and if something where to happen to the catalog, it is much quicker to recover... Quote Link to comment Share on other sites More sharing options...
madasczik Posted May 9, 2009 Report Share Posted May 9, 2009 Corruption???...hmmm....how much data are we talking about here? Quote Link to comment Share on other sites More sharing options...
randeep Posted May 11, 2009 Author Report Share Posted May 11, 2009 600GB Quote Link to comment Share on other sites More sharing options...
randeep Posted May 11, 2009 Author Report Share Posted May 11, 2009 Hello Emulator, As you are facing the same problem as we are facing, have you been able to somehow eliminate this problem with some alternate or some solution? Thanksa and Regards, randeep Singh Quote Link to comment Share on other sites More sharing options...
emulator Posted May 11, 2009 Report Share Posted May 11, 2009 We have to do a recycle backup on these large backup sets once a week. They run over the weekend. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.