Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by haggis999

  1. I am nearing the completion of transferring three snapshots from an existing backup set to a new backup set. Each one of the snapshots has generated a lot of 'Backup Set format inconsistency' errors (1008 errors so far). Needless to say, neither the Retrospect Professional 7.0 online help nor the User's Guide contains anything about such errors... Can anyone please explain what such errors mean, what might have caused them and how they could be eradicated? When I created the new Backup Set, I was prevented from entering a name longer than 20 characters. This limitation does not appear to be documented and I am puzzled as to how I managed to name a couple of older backup sets with 21 character names. Has this limitation only been applied in a recent update to Version 7? I'm currently on 7.0.326. David ======sample of error messages======== Backup Set format inconsistency (10 at 3260425) Backup Set format inconsistency (10 at 3261498) Backup Set format inconsistency (10 at 3261512) Backup Set format inconsistency (10 at 3261526) Backup Set format inconsistency (10 at 3261537) Backup Set format inconsistency (10 at 3261538) Backup Set format inconsistency (10 at 3280957) Backup Set format inconsistency (10 at 3281021) etc, etc
  2. I have progressive backups going back about 12 months for the C: drive on my PC. The most important folder on my C: drive is My Documents. At present, I store a lot of preview jpeg files for an Extensis Portfolio media database in this folder but they take up a lot of room and I may soon choose to transfer these files to my much larger H: disk, which is dedicated to digital images. The H: drive backups are currently contained in separate snapshots within the same backup set. I'm using Retrospect Professional 7.0. My objective is to keep going with my progressive C: drive backups (without the Portfolio files) and change my H: drive backup (now including the Portfolio files) to a simple Duplicate process. I have two questions, 1. If I 'Forget' the H: drive snapshots in my backup set will the existing H: drive data be erased from the backup set? 2. How do I delete the existing backups of my Portfolio files (all contained in a subfolder of My Documents) from my backup set without erasing any other historical data for My Documents in the same snapshots? David
  3. I have just changed the grooming policy on one of my backup sets from 'Groom to Retrospect defined policy' to 'Groom to remove backups older than 3'. After clicking on the Action button, I got the message 'Retrospect will retrieve older snapshots to make sure that they don't get groomed out'. My presumption is that this refers to snapshots that I deliberately chose to 'Forget' in previous attempts to reduce the size of my backup set. Why is Retrospect retrieving such unwanted snapshots? How do I ensure that selected snapshots are permanently deleted from a backup set? I'm using Retrospect Professional 7.0. David
  4. Robin, I understand your point about tape or optical backups. I am only raising the question in connection with disk-based backups. The deletion of individual files or folders would indeed affect the restore process, but I can't quite see why such deletions could not be logged by Retrospect. This log could then be used to bypass the attempted restore of the missing files. I'm not sure why you mentioned that "Retrospect uses an archiving methodology, retaining older versions for restore in the future". The word 'archiving' has no specialised technical meaning that I am aware of, and simply means to place records in a store. Obviously I am aware that Retrospect stores several historical versions of each file, since that has been the focus of the grooming discussion in this thread. Have I missed the point of your comment in some way? David
  5. Robin, As the resident guru, can you address my original question. In other words, can you please explain why Retrospect does not offer a facility to selectively delete files and folders from a backup set? David
  6. Success, at last! Grooming to keep only the last 3 backups of each source worked this time without any confusing errors. The catalogue rebuild solved the problem, though offered no clue as to why it was corrupted in the first place. My backup set reduced to 191GB, which was enough to allow me to run a new backup. I guess the lesson must be that whenever Retrospect starts to behave oddly, just rebuild the catalogue. Thanks to everyone for the assistance provided.
  7. The grooming can't have been a linear process. It took 'only' one hour eight minutes. However, it only deleted 8 files. This reduced the backup set size from 236GB to 233GB, a fairly trivial reduction, so the next step is to try a more aggressive grooming option. David
  8. Well, my catalogue rebuild has just completed (it's not quick!). I've now initiated a 'Groom to Retrospect defined policy' to see if that gets me anywhere in terms of space saving. If not, I'll try once again to do grooming with the option set to keep the last three backups of each source (the process that previously failed with a disk full error). By the way, contrary to my earlier speculation, I have not fully rebuilt the catalogue from the disk before, so I'm hoping that this laborious process will eventually prove worthwhile. The grooming looks like it will be an even lengthier exercise. After 19 mins it's only done 52 segments (whatever they are) out of 473. I think my PC will be left to run all night ... David
  9. Do you mean the Repair Catalog facility? If so, I think I've already tried that but I'll do it again just in case.
  10. Robin, I have unearthed some Windows environment variable settings within the System Properties dialogue box of the Control Panel that associate TEMP with a folder on my C: drive. Is that the setting you mean? The specific external 300GB hard disk containing my backup data on which I was running my grooming session had just over 2GB free. Note that my backup set contains thousands of files, but two of them are very large. One file is 8GB and another is 21GB. Could this be relevant? Unfortunately, I'm still no further forward after posting my plea for help three days ago and I'm still unable to make any new backups. An urgent response would be much appreciated. My panic levels are rising! David
  11. Robin, I can't see anything in Retrospect Preferences about default temp directories. Where is this setting? Also, I don't understand your reference to a 'destination' drive. That implies that data is being transferred somewhere. I just want it deleted! David
  12. I've got 4.2GB free on my C: drive. How do I calculate how much is required? David
  13. My grooming process has just failed with an error -1115 (disk full). So the grooming process fills up my disk instead of creating more space on the disk - the reverse of what I want. Aaaaargh!!!!!! I'm lost. Where do I go from here? David
  14. Michael, I have just noticed that, while 'forgetting' snapshots in a backup set automatically initiates grooming activity (even if it then fails with a 2249 error, as previously mentioned), changing grooming options does not. In the latter case, you have to initiate grooming manually by clicking on the Action button (confusingly labelled 'Prepare media for next backup', which to me implies disk formatting) and then selecting the Groom option. It's not exactly an intuitive interface for the new user. As a further confusion, the KB link you provided suggests that using the Action button is required even in the case of snapshot delection. No mention there of it being automatically initiated, as I experienced. I have now started the grooming process to action the previous change of grooming option. It looks like it's going to run for a very long time, encouraging me to believe that some space is being freed up at last! David
  15. Michael, Thanks for the info about Version 7.5. Are you saying that the errors I am getting with Version 7.0 are caused by a bug in the software? Are the errors real or are the messages misleading? You were mistaken in describing your KB link as providing a method for grooming files. It only tells me how to delete snapshots, not specific files. I find the inability to delete selected files and folders a rather strange and frustrating limitation of Retrospect. As deleting snapshots so far has gained me no space, I tried changing my grooming options to keep only the last 3 backups of each source (it was originally set to 'Groom to Retrospect defined policy'). This change then set in motion an unwanted process to retrieve all the snapshots I had already deleted!! At the end of this process Windows Explorer told me that the backup folder contained exactly the same number of files as before, with the same folder size. I'm beginning to find Retrospect a little difficult to understand ... David
  16. You say that Retrospect will only save each file once. By that, I assume you mean each file of a given name of a given saved date in a given folder. As I understand it, if there have been several versions of the file in that folder over a period of time, then Retrospect saves each version within the limits of the current grooming policy. However, my situation relates to a large number of digital images that have been significantly reorganised over the past six months. Most of these files have not been changed, but they have all been put into more than one variation of folder structure. Does Retrospect still hold just one copy of the unaltered files in such circumstances, regardless of folder location? David
  17. I use a couple of 300GB external hard disks for storing my Retrospect Professional 7.0 backups and these disks are now both nearly full. I need to create more space for new backups by deleting some redundant large files and folders from previous snapshots. How do I do this? My suspicions are that only complete snapshots can be deleted from a backup set, though I don't understand why and my attempts to do so have all failed with error -2249 (could not find session). I really would appreciate some urgent guidance as I am currently unable to run any more backups due to lack of disk space. David
  18. Quote: The items in the manual that you mentioned are for cases where SCSI communication problems are causing trouble backing up to tape. Your errors are likely just some minor disk corruption. Nothing too serious. In fact, I suspect the files would restore properly as is. Nate The only possible conclusion an average user like myself could reach when reading the error messages I quoted is that the backup did not work for those specific files. There is not much room for ambiguity in a phrase such as 'Execution Error'. I see nothing "minor" in that. The code already has a means of highlighting minor issues: it calls them Warnings rather than Errors. This was an error. In what way is that not "serious"? Backup is a binary process. Either it works or it doesn't. There is no room for shades of grey. On that basis, I think that it is unacceptable for Dantz to completely ignore such errors and their possible solutions in the User Guide. The whole point of a backup program is to provide peace of mind. Every single error message generated by RP7 should be properly covered by the manual - WITHOUT ANY EXCEPTION!
  19. Nate, I've not yet played with the restore facilities of RP7 as I'm just taking one step at a time during the trial period to avoid any mistakes. However, is this 'alternative restore method' a matter of selective restore versus 'standard' full restore, or does the standard method also allow selective restores?
  20. Quote: It looks like the fix for this has not made it in v7.0.326. This problem could turn a simple restore into a complicated process. As someone who is evaluating the trial version of RP7, I am concerned that a problem raised last April and long accepted to be a genuine bug is still not fixed. I don't like the idea that a restore might be complicated. I want my chosen backup product to make restores easy. The product appears to have moved from V7.0.300 (or perhaps even earlier) to V7.0.326 in that time, i.e. at least 26 updates in 8 months and yet this bug is still there! Can someone from Dantz please assure me that it will be fixed very soon.
  21. Quote: ........ While not as thorough, this is much quicker than scandisk and defrag. You may still choose to scandisk before extracting the files. I did, but no problems were reported (and I frankly didn't expect any). I went through the scandisk (actually, it seems to be called chkdisk in Win 2k) and defrag process before reading your post. Like you, no errors were found but the problem does now appear to have gone away. It was certainly a time consuming business that took several hours, but I guess the defragging may have some minor benefits.
  22. Your first suggestion didn't work for me. After selecting Ignore ID for the relevant drive, RP7 refused to acknowledge that any CD was in this drive. However, your second suggestion to copy the i386 folder did the trick. Can I now erase this 300MB folder from my hard drive?
  23. Nate, At first, I didn't understand your explanation because there is no "Files chosen" button on my version of RP7. I eventually realised that you probably meant the Preview button, which causes a scan of the selected source and then leads to the dialogue box that allows individual file selection/deselection via check boxes. I guess that I didn't stumble across this facility earlier because it was easy to miss and was not a required step when making a backup. My experience with other packages at work, such as ArcServe, let me to expect that source selection would combine the process of 'volume' selection and file selection in the same checkbox list, something which is a far more intuitive process than Dantz has chosen. Thanks for your help.
  24. Thanks for the advice Nate. I'll certainly give that method a try. I eventually found a very brief reference to this sort of error in the RP7 User Guide (the index wasn't much use in tracking it down), but it just seems to blame my SCSI bus as the "usual" cause. Since I have been using the SCSI drives on my Dell Precision Workstation without any obvious problem for several years, it seems unlikely that my SCSI bus is configured incorrectly or has a hardware failure of some kind. Dantz offers no guidance on other possible causes of this error or any advice on how to resolve the problem. It seems strange that such little help is provided on how to handle important error messages.
  25. Thanks for those workarounds. Your help is much appreciated. However, can anyone explain why this problem arose in the first place? It looks like a bug and I'm surprised that software at version 7 should fail in such a basic fashion. Simply reading a file from a CD is not exactly rocket science, is it?
  • Create New...