Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


jhg last won the day on August 31

jhg had the most liked content!

Community Reputation

8 Neutral

About jhg

  • Rank
    Frequent Poster

Recent Profile Visitors

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

  1. I have some fairly complex selectors, and editing these via the UI is somewhat cumbersome. Is there a way to export the selectors in a text format that can be edited and rearranged in a simple text editor, and then reimported? I tried the "export" function, which produces a .rxx (Retrospect Exported Selectors) file. The format is binary and doesn't start with a known file type signature.
  2. Retrospect on Windows 7x64 Pro When displaying a backed up file's properties I noticed that the Created/Modified/Accessed times are all UTC but the BackedUp time is local, with no indication that different timezones are being used. The file is on a local disk, no NAS or other systems involved. See attached screenshot.
  3. That would just add a second volume, which I want to avoid.
  4. I have an archive backupset on an HD, and the HD has filled up. The HD contains only the Retrospect backupset and nothing else. I'd rather not add a second disk so I copied the contents of the full disk to a new, larger disk and then set the volume name and volume serial number on the new disk to match the old one. However, Retrospect does not recognize the hard disk as belonging to that backup set. What else do I need to change on the new drive so Retrospect will recognize it?
  5. I'm not sure I understand why this would slow things down. As it currently operates, Retrospect has to scan the source directory and build a in-memory representation of the state of each file. That model is then matched to the catalog to see which files have changed and need to be backed up. All the verify has to do is set a flag on the file in the catalog so that next time a backup is run that file is considered "changed".
  6. Retrospect 11.5 on Win7x64 Pro. I ran a verify which found an error on one file Backup Set format inconsistency: 5 at 459,277,423,255 [*] Xca::ArxExec: FASIG_TAIL's nodeid=63,453; expecting fileno=63,443 for 20120623-10775.CR2 I then ran a backup, expecting the file to be re-backed up, but it does not appear in the session contents. IMHO a file that fails on verify should be marked in the catalog to be re-backed up the next time a backup is run. How do I force Retrospect to backup the file again?
  7. In the log: The description for Event ID 1 from source Retrospect cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Execution terminated unexpectedly, possibly due to a power failure or system crash. The specified resource type cannot be found in the image file Here's a screenshot of the Event Viewer: However, Retrospect DID NOT terminate unexpectedly, I launched it manually at exactly the time this event was logged. What does this error mean?
  8. I have an archive set containing about 1.7 GB, residing on an external hard disk connected via USB3. Since this is a long-term archive I run a verify every couple of months. Yesterday I got the error below in the log. + Executing Verify at 5/2/2017 9:44 PM To Backup Set HD Photo 3... [*] TPCVol::GetInfo: UGetVolumeInformation failed, H:\, osErr 55, error -1102 Backup Set format inconsistency: 5 at 470,609,027,046 [*] Xca::ArxExec: FASIG_TAIL's nodeid=64,271; expecting fileno=64,267 for 20120707-11493.CR2 5/3/2017 1:16:40 AM: 1 execution errors Remaining: 5 files, zero KB Completed: 157144 files, 1,707.9 GB Performance: 8619.4 MB/minute Duration: 03:32:20 (00:09:26 idle/loading/preparing) Does this indicate a hardware problem on the disk?
  9. That's exactly what I was looking for. In this case "ugly" is beautiful as it's nicely formatted and easily parseable in Perl. The UI to do the export is a little wonky, I wouldn't have thought to look for File/Export while in what looks like a dialog. But then I realize the UI is a sort of Mac/Windows hybrid given the original provenance of Retrospect (I know, I first used it on my SE30 and was delighted when it became available for Windows). I was greatly relieved that it let me select multiple sessions for the export. This will do exactly what I need. Thanks.
  10. I want to extract a listing of the contents of a snapshot, in order to write a Perl script to compare two snapshots I have three archives of a large collection of images. The latest archive may be missing some files that would appear on the previous archives, and I would like to recover those files if there are any, before discarding the earlier archives to free up some space. To do this I was hoping I could extract a list of files contained in a backup set snapshot, listing the full path, size and last mod time, into a text file that I could then process with a Perl script. Is this possible? If not, does Retrospect provide a way to compare two snapshots and list the differences?
  11. The "Download Microsoft Windows ADK image" link in the "Prepare for Disaster Recovery" dialog links to the Windows 10 ADK download. Is it possible to download the ADK for Windows 7? I have not been able to find it -- everything leads to Win10 or Windows 8.1 versions.
  12. jhg

    Archive size > original files?

    FYI, I deleted the backup set and reran with compression turned off. Now the backup set is the same size as the source files. Thus the 35% increase in size was due entirely to Retrospect's poor performance on compressing incompressible data. I'm running Retrospect, and this is a rather serious problem that should be corrected if it hasn't been already addresses in version 10.5.
  13. I created an archive of a large photo directory (mostly consisting of ~20-30MB raw files) and find that, while the on-disk size is just under 1.2TB (where 1TB = 10244) the resulting backup is about 1.7TB. Is this to be expected? I have software compression enabled based on the fact that gzip can still compress the raw files a few percent. Is it possible Retrospect's compression is causing that much expansion?
  14. This is parallel to my other question about Verify Media MD5 errors I have an HD archive set that gets two MD5 errors when I run Verify Media. However, if I restore the two files in question (to a different location) and then compare them to the originals, they are identical. What would cause Retrospect to report an MD5 error when the files are in fact identical (as confirmed by various methods including WinMerge and Cygwin "cmp" command). The two files were originally archived to the HD in 2012 and 2014. Have there been any changes to the MD5 algorithm used by Retrospect that could account for this?