Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Lennart_T last won the day on January 25

Lennart_T had the most liked content!

Community Reputation

147 Excellent

About Lennart_T

  • Rank
    Retrospect Veteran

Profile Information

  • Gender
  • Location
    Helsingborg, Sweden

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. "Source Speed: The speed of the source volume is the single most important factor in determining streaming tape capacity. Each time the buffer in the drive runs out of data to copy, an "underrun" occurs and unused tape streams on by, wasting raw tape capacity. The more underruns, the greater the reduction in capacity." https://www.retrospect.com/au/support/kb/tape_capacity_faq For an offsite backup, you really should perform a disk-to-disk-to-tape backup (as already suggested).
  2. Lennart_T

    unistall engine

    Neither can I, when I look in my own folder. It seems as Retrospect needs to update its user guide.
  3. Lennart_T

    unistall engine

  4. Lennart_T

    Unknown Windows error 343 after SSD upgrade

    Since there are different methods of accessing the filesystem at program level, it might be that Retrospect uses another method than other programs. (Where the other method(s) does not cause an error, while Retrospect's method does.) The errors does indicate a problem reading the disk. ("can't read, error -1001" "MapError" "can't read data, BackupRead failed") What if you try Clonezilla to clone the disk to another disk? Perhaps the old SSD. Or try another piece of (backup)software that copies all files from the disk.
  5. Lennart_T

    Unknown Windows error 343 after SSD upgrade

    Your new SSD could be broken. Yes, it happens. You could try to run CHKDSK.
  6. I do not know if Retrospect will see it as a new volume, but it normally recognizes the files on the volume by the FILE metadata and not backup them again.
  7. I say "YES". A proper "verify media" should detect such errors.
  8. Yes, it could but not likely by itself. It looks like you have a hard disk problem, since some files can't be read properly. Test the hard drive, including a surface scan. Page 459, "Verifying Backup Set Media" http://download.retrospect.com/docs/win/v16/user_guide/Retrospect_Win_User_Guide-EN.pdf Maybe you can. Page 454 in the above user guide: "Recreating a Catalog"
  9. Not necessarily. It is just the last link in a long chain of things that can go wrong. See it as the messenger, if you wish. Too bad the catalog file isn't a simple text file. That way you could have opened it in Notepad (for instance) and see if you could make changes and save. By the way, do you have more than one version of Retrospect installed? Both could be running and one could be locking the catalog file from the other. Maybe you have anti-virus software installed that interferes with Retrospect.
  10. Here is my theory, for what it is worth: When copying from the old G to the new G, you got some incorrect permissions copied as well. Copying to C and back corrected these permissions, by forcing the default C-drive permissions onto the folder (or file).
  11. Yes, indeed. Hopefully(?) it was this bad drive that caused all your problems.
  12. It appears the Microsoft (nowadays?) calls it "finding bad sectors". https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk The command is: chkdsk /r
  13. Did that coincide with a Windows Update? ...and with the Retrospect problems starting? Did you do a surface scan also? If not, please do.
  14. I still think something has gone wrong with the permissions. Does Retrospect run as the logged in user, or as another user (set up in Retrospect's Preferences)? If you run (for instance) Notepad or MS Word as the same user as Retrospect is running, can you create and edit a document in the same folder as where the catalog file is?