Jump to content

haggis999

Members
  • Posts

    203
  • Joined

  • Last visited

Everything posted by haggis999

  1. Scott, Ah, now I understand! Thanks for clearing the fog. I am so used to thinking of the path as an integral part of the folder name that I misunderstood Amy's post. However, I think that it was stupid of the Retrospect programmers not to have made it crystal clear that references to a folder should not include the path. It is perfectly normal in the Windows world to refer to a folder by including a full or partial path along with the folder name. References to a folder without the path can be highly ambiguous and are normally best avoided. David
  2. Nearly a week with no reply . Surely one of the Retrospect gurus here must know the answer to this basic question?
  3. Hi Amy, I'm all for exactitude when it come to computer software, but in this case I am still none the wiser. Within my exclusion definition, I was (in your own words) "asking it to find the name of the actual folder". Yes, that's exactly what I intended, and to my eyes, that still seems a pretty clear instruction. If I wasn't asking Retrospect to exclude this folder and it's contents, then what was this selector really asking it to do? Why was there no effect at all? Would you please also provide an example of a successful use of the 'Name of folder matches pattern' selector method, as this may help in clarifying what appear to be some very subtle distinctions. David
  4. As an experiment, I ran the Transfer Backup Set again using a slightly different selector definition (but with exactly the same purpose). This time I used: But always exclude files matching Windows path matches pattern C:\Documents and Settings\Administrator\My Documents\Extensis Portfolio\, selecting all enclosed items or matching Windows path matches pattern C:\Documents and Settings\Administrator\My Documents\iView MediaPro\, selecting all enclosed items This time it appears to have worked correctly! However, it is by no means obvious why 'Name of folder matches pattern' should fail while 'Windows path matches pattern' should work. Can anyone explain what was wrong with my first selector definition? Does the use of a trailing backslash in my second version have any significance? Is it just a Retrospect bug? David
  5. I have just run a Transfer Backup Set process in which I set up a couple of 'exclude' conditions, as shown below. The excluded folders contained several GB of files in the source Backup Set. The destination was a newly created Backup Set. But always exclude files matching Name of folder matches pattern C:\Documents and Settings\Administrator\My Documents\Extensis Portfolio, selecting all enclosed items or matching Name of folder matches pattern C:\Documents and Settings\Administrator\My Documents\iView MediaPro, selecting all enclosed items Unfortunately, the result of the transfer was that the new Backup Set was exactly the same size as the original and browsing revealed that it still contained both of the excluded folders and all their contents! Can anyone explain how to make the file selector facility work properly? I'm using Retrospect 7.0 under Windows XP. David
  6. I would like to Duplicate a folder on one of the hard drives on my PC to a DVD-R disk but Retrospect 7.0 does not list my DVD-RW drive as one of the destination options (even though it has been successfully configured and has a blank disk in the drive). Is Duplicate supported on DVD-RW drives? If not, why not? David
  7. An earlier thread on a similar topic suggested uninstalling Nero. I did this but it made no difference. However, after a reboot, Retrospect then let me configure my Plextor drive for DVD-R disks. I did this configuration with an old 4X DVD-R disk, but my normal DVD backups will be using 16X DVD-R disks. Will my configuration still be okay? David
  8. I initiated a custom configuration of my Plextor PX-760A DVD-RW drive in Retrospect 7.0 over half an hour ago but it seemed to be stuck in a loop. The dialogue box said that it was 'Checking disk information' and there was constant hard disk activity but I had this feeling that it was going nowhere, so I killed Retrospect via the Windows XP Task Manager. On reopening the program, Retrospect told me that I didn't have any CD or DVD drives! Help please! David
  9. I have electronically searched both the User's Guide and the online Retrospect Knowledgebase for information about 'Backup Set format inconsistency' errors, but there is nothing to be found. Is there no one here who can explain these error messages?
  10. In each case, the list before and after clicking on Add is identical. The order is different, but the same Snapshots are listed. I've now compared the Snapshot lists in greater depth. In Backup Set #1 (the original), the list includes the following two Snapshots, C: Drive 431 files 17/09/2006 C: Drive 2107 files 19/08/2006 In Backup Set #2 (the clone), the list includes the same two Snapshots but with different file totals! C: Drive 387 files 17/09/2006 C: Drive 1935 files 19/08/2006 There are other Snapshots, but the details are exactly the same in both Backup Sets. I don't understand how such differences have arisen. Any ideas?
  11. I checked the compression settings before posting. Both catalogues are compressed. Both Backup Sets appear to have the same number of Snapshots (and both have the same list when you click the Add button). Both are on identical external disk drives.
  12. Thanks, Amy, your positive response prompted me to look a little harder and now I've found the relevant selection process. It's a lot more tedious than ticking check boxes in a file list, but with care and patience it should do the job. In a roundabout way, this should enable me to effectively delete selected files from a Backup Set, the thing you are clearly told can't be done. Yes, I know you are creating a new Backup Set rather than changing the existing one, but the end result is just the same. I'm surprised that this is not covered in the documentation (or have I missed something?). Thanks again.
  13. Sorry, Amy. I should have updated this thread to say that I have now succeeded in grooming out several unwanted Snapshots (all of which were initially active). I can't be 100% certain, but it is possible that all my previous attempts to Forget'n'Groom were overlapping with a change of grooming policy. The latter change may have taken precedence. If I am right, then I suspect that Retrospect could have been more helpful in telling me what was going on...
  14. I have just used Transfer Backup Set to create a clone of my primary Backup Set. The destination was a brand new Backup Set. It all ran fine with no errors, but I am puzzled as to why the new set (47.7GB) is not exactly the same size on disk as my original set (56.9GB). In contrast, the RBC catalogue file for the new set is nearly three times bigger than the catalogue file for the original! Can anyone make sense of this for me, please?
  15. I have now confirmed that 'forgetting' a Snapshot in a disk-based Backup Set does indeed then trigger a grooming process that permanently erases both the Snapshot and the files it contains. Getting back to my original Q2, Retrospect does not appear to permit the erasing of selected files within a Snapshot but is there any way to selectively transfer the contents of a Snapshot into a new Backup Set?
  16. Actually, I'm still quite confused by the grooming process. The online help tells me that, ""When you forget a Snapshot from a disk Backup Set with grooming enabled, Retrospect deletes the selected Snapshot and its associated files (the Snapshot and files cannot be retrieved later)". However, every time I forget a Snapshot and then initiate grooming via the Action button on the Options tab of the Backup Set Properties box, Retrospect insists on retrieving the Snapshot I have just forgotten! How exactly do I delete a Snapshot and its associated files?
  17. Using 'Repair Catalog' to rebuild the catalogue from the Backup Set has fixed my problem. The 'Verify Media' process has now successfully checked all the files on this Backup Set. However, I would still like to know how I am supposed to move a disk-based Backup Set (ideally in a way that does not require a time-consuming catalogue rebuild).
  18. I have now done another backup, with no significant errors, and a Verify Media process has checked 166548 files and found no problem. Panic is now over. Until the next time....
  19. Amy, OK, there is a certain logic in that, though it would have been more intelligent if the program had said to me "the only way to obtain three versions of each file would be to reinstate Snapshots X, Y and Z which you chose to forget earlier" and then offer a Yes/No option for each such Snapshot. At present, I think you get one Yes/No decision for all such retrievals without any explanation or identification of the affected Snapshots. However, thanks for the explanation. I will now be able to make a more informed decision whenever this situation arises again. Regards, David
  20. I don't fully understand your question. What else could these 'older snapshots' be, other than ones I had deliberately 'forgotten'? Surely Retrospect does not hide, forget or delete snapshots on its own account?
  21. I have created a new Retrospect 7.0 Backup Set on the F: drive in my PC (it's a temporary solution for merging together several Snapshots from external hard disks). Due to finger trouble, I accidentally created my new Retrospect folder as a subfolder of a folder unrelated to backup purposes. I subsequently moved the Retrospect folder to its intended location on the root of the F: drive. The full path of the folder containing the RDB files is now, F:\Retrospect\Dell 670 Backup #1\1-Dell 670 Backup #1\ Previously, it had been, F:\Config.Msi\Retrospect\Dell 670 Backup #1\1-Dell 670 Backup #1\ I then went to Configure/Backup Sets, selected the relevant BS and clicked on Properties. Under the Members tab I clicked on another Properties button and this gave me an opportunity to change the 'Location for the backup data folder'. For some unfathomable reason, Retrospect would not let me choose my top level F:\Retrospect\ folder, but it was happy to accept the simple drive letter F:\. I then ran a backup job to this newly moved BS and it ran without error. Because of previous problems with this BS (reported in other recent posts), I then decided to run a Verify Media test. However, this process generated loads of errors (during an initial Resynchronising process, whatever that might be), as shown in the attached log. As you can see, Retrospect was still using the old path. How do I fix this? I stopped the Resynchronising process. Should I have let it continue? What was the proper way to have changed the location of the Backup Set? BTW, this log refers, in a very illiterate fashion, to reading TO a file! You can WRITE TO a file. You can READ FROM a file. READ TO is just meaningless, but then I'm used to that with Retrospect error messages.... David ===================VERIFY LOG======================== + Executing Verify at 09/02/2007 16:24 To Backup Set Dell 670 Backup #1... Additional error information for Disk Backup Set member "1-Dell 670 Backup #1", Can't read to file F:\Config.Msi\Retrospect\Dell 670 Backup #1\1-Dell 670 Backup #1\AA000000.rdb, error -1101 (file/directory not found) Trouble reading: "1-Dell 670 Backup #1" (0), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-Dell 670 Backup #1", Can't read to file F:\Config.Msi\Retrospect\Dell 670 Backup #1\1-Dell 670 Backup #1\AA000000.rdb, error -1101 (file/directory not found) Trouble reading: "1-Dell 670 Backup #1" (1), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-Dell 670 Backup #1", Can't read to file F:\Config.Msi\Retrospect\Dell 670 Backup #1\1-Dell 670 Backup #1\AA000000.rdb, error -1101 (file/directory not found) Trouble reading: "1-Dell 670 Backup #1" (2), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-Dell 670 Backup #1", Can't read to file F:\Config.Msi\Retrospect\Dell 670 Backup #1\1-Dell 670 Backup #1\AA000000.rdb, error -1101 (file/directory not found) etc, etc
  22. Jelenko, your claim that 'forgetting' a snapshot does not cause any files to be deleted seems to contradict the following statement I have just found in the online help. "When you forget a Snapshot from a disk Backup Set with grooming enabled, Retrospect deletes the selected Snapshot and its associated files (the Snapshot and files cannot be retrieved later)".
  23. Yinqinq, Thanks for the info. My comments are as follows. 1. The KB article about Error 3043 only addresses the situation where a computer is being backed up locally at the same time as it is being backed up over the network. That is not my situation. I am only running a local backup. In addition, the text of the KB article does not seem to relate to the wording of the error message. There is nothing in the text about the 'number of snapshots'. I am still totally in the dark about the meaning of this error and what action I need to take. 2. Thanks for the link. It seems to confirm that I shouldn't worry about these errors. 3. Again, thanks for the link. Error now understood. 4. I am well aware of the time it takes to verify my data. I didn't kill a working process. Retrospect had definitely hung my PC and nothing useful had happened for a long time before I switched off. I will be running the backup again today.... David
  24. I'm not sure why you offered an explanation of the Duplicate process. I didn't actually ask for help on this topic - which appears to be fairly straightforward and has not caused me any problems in the past. Ref Q1: If 'forgetting' a snapshot doesn't cause any files to be deleted then what is the purpose of the 'Forget' process? Ref Q2: I'm not sure that you understood my question. Neither the transfer of snapshots nor any grooming option addresses the problem of discarding my Portfolio files while retaining everything else in the backup set. The Portfolio files are not contained in their own unique snapshots. They are included within snapshots that contain the full contents of my C: drive. My backup set is stored on an external hard disk.
  25. I attach below the log of a backup I ran earlier today on my PC. As usual, the Retrospect Professional 7.0 online help and User's Guide offers little or no assistance in explaining the meaning of error messages and how to fix them. It is very frustrating that a product at version 7 still does not appear to have proper error code documentation . I have the following list of questions. 1. Ref Error 3043 - can anyone tell me how many snapshots the Open File Backup option supports? Presumably, the 1020 and 1111 errors would not have occurred if Open File Backup was working properly. 2. From past discussions here, the 'didn't compare at offset' errors are some form of obscure nonsense that can usually be ignored. The info in the online Help only contains totally irrelevant stuff about the SCSI comms bus. Please advise if I am mistaken and should worry about such errors - in which case, please advise what action is appropriate. 3. I have no idea what the 'different modify date/time' errors mean and what action is required to fix. Please advise. 4. At the final stage of this problematic backup, near the end of the verification process, Retrospect hung up. I killed it with Windows Task Manager and restarted Retrospect but soon hit problems, as it claimed that another Retrospect process was already running (confirmed by seeing two retrospect.exe processes in Task Manager). I tried to reboot the PC but it refused to clear the warning message about waiting for the other Retrospect process to close and I had to do a forced power off. After rebooting, I ran a Verify on the backup set and have added the resulting log to the end of this post. This log tells me that 2582 files were not verified. So what do I do now, apart from tearing out what little remains of my hair? David ================Backup Log================== To Backup Set Dell 670 Backup #1... Can't use Open File Backup option for Local System Disk (C:), error -3043 (the maximum number of Snapshots has been reached) 08/02/2007 16:22:18: Copying Local System Disk (C:) File "C:\Documents and Settings\Administrator\Application Data\Microsoft\Outlook\outcmd.dat": can't read, error -1020 (sharing violation) File "C:\Documents and Settings\Administrator\Local Settings\Temp\~DF7AD4.tmp": can't read, error -1020 (sharing violation) File "C:\Documents and Settings\Administrator\My Documents\MS Outlook\outlook.pst": can't read, error -1111 (locked range conflict) 08/02/2007 16:30:50: Snapshot stored, 91.8 MB 08/02/2007 16:31:06: Comparing Local System Disk (C:) File "C:\Documents and Settings\Administrator\Cookies\index.dat": didn't compare at offset 21,316 in stream "Data" File "C:\Documents and Settings\Administrator\Local Settings\History\History.IE5\index.dat": didn't compare at offset 658 in stream "Data" File "C:\Documents and Settings\Administrator\Local Settings\History\History.IE5\MSHist012007020820070209\index.dat": different modify date/time (set: 08/02/2007 10:31:29, vol: 08/02/2007 12:53:06) File "C:\Program Files\eBay\eBay Toolbar2\eBayDaemon.log": different modify date/time (set: 08/02/2007 16:25:02, vol: 08/02/2007 16:31:01) File "C:\WINDOWS\Prefetch\RTHLPSVC.EXE-32A01DCB.pf": different modify date/time (set: 08/02/2007 16:22:20, vol: 08/02/2007 16:25:47) File "C:\WINDOWS\Prefetch\TASKMGR.EXE-20256C55.pf": different modify date/time (set: 08/02/2007 16:09:41, vol: 08/02/2007 16:30:05) 08/02/2007 16:31:19: 3 execution errors Completed: 29 files, 50.3 MB Performance: 317.4 MB/minute (377.0 copy, 301.6 compare) Duration: 00:09:01 (00:08:41 idle/loading/preparing) ===============Verify Log================= Executing Verify at 08/02/2007 16:43 To Backup Set Dell 670 Backup #1... 2,526 files were not verified 08/02/2007 16:59:29: 1 execution errors Remaining: 2526 files, zero KB Completed: 138923 files, 44.0 GB Performance: 3044.8 MB/minute Duration: 00:15:41 (00:00:55 idle/loading/preparing)
×
×
  • Create New...