Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by jhg

  1. I configured a daily email report to be sent at 7:00 AM, as shown in the attached screenshot.

    However, it appears that the email is sent only if the full Retrospect application is open at the requested time.  I would have expected that the email would be generated by a small background process, such as retrorun.exe instead of the full app.

    If this it is intended that the email status requires the full app to be running, then I would like to submit a feature request that the task of sending the status email be moved to retrorun so that the main app does not have to be running.


  2. If I start Job A which uses BackupSet-1 and then attempt to start Job B, which also writes to BackupSet-1, Retrospect complains that the backup set is in use and refuses to queue the job to wait for the backup set to become available.

    However, if I edit Job B and add a one-time schedule entry to start 1 minute from now, while Job A is still running, Retrospect dutifully queues Job B and runs it when Job A finishes.

    This is probably a feature request.  In the first situation, where I attempt to run a job for which a resource is currently in use, I would like for Retrospect to queue the job just the way it does when the job is started by the scheduler instead of manually.

  3. Windows 10 Pro x64 build 1803 with all current updates applied, Retrospect

    Every time Retrospect starts based on a schedule task it produces the following Windows Event Log entries:

    1/3/2019 2:00:04 AM Retrospect version - Automatically launched at 1/3/2019 2:00 AM
    1/3/2019 2:00:16 AM Execution terminated unexpectedly, possibly due to a power failure or system crash.
    1/3/2019 2:07:06 AM Script "JHG" completed successfully
    1/3/2019 2:07:06 AM Normal backup using JHG at 1/3/2019 2:00 AM (Execution unit 1)
            1/3/2019 2:00:16 AM: Finished scanning backup set data files
        To Backup Set HD Set 012...
        ... [uninteresting message content deleted]
        1/3/2019 2:01:08 AM: Comparing Backups on STORAGE (D:)
        1/3/2019 2:01:27 AM: Execution completed successfully

    I believe that Retrospect logs the error (2nd message) because it believes a previous invocation of the script failed, which did happen over a week ago. 

    I think Retrospect is failing to clear some indicator of a previous failure when a backup is successful.

  4. 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.

    • Like 1

  5. 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?

    • Like 1

  6. As far as forcing Retrospect to backup the file again, how about trivially renaming the file?  According to Ash7 in this thread, that would cause Retrospect to back it up again.  Then jhg could rename the file back to its original name, which would cause Retrospect to back the file up a second time.


    IMHO the feature jhg is proposing would require Retrospect to scan the entire Catalog File for each Source drive backup, looking for the "failed on verify" mark.  That would effectively negate the use of Instant Scan, thus slowing down backups.  I don't think many administrators who use Retrospect to backup multiple Source drives within a limited time window would want to make that tradeoff.


    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".

  7. 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?

  8. 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? 

  9. 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?

    • Like 1

  10. 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.



    • Like 1

  11. 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?

    • Like 1

  12. 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.

    • Like 1

  13. 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.

  14. 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?

    • Like 2

  15. 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?

  16. I am using Retrospect 7.7.620


    I have an archive backup of a folder with about 800GB of image files. A large fraction of the images consist of a camera-raw file (.cr2) plus a "sidecar" .xmp file.


    There is one folder that I need to recover. If I examine the contents of the archive snapshot, the folder looks normal with matching .cr2 and .xmp files.




    I tried restoring this folder, and it restored only the .xmp files.


    If I use Restore/Find Files, it does not show the .cr2 files, although .cr2 files are included for other folders.




    Where are the missing files and how do I get them back?


    Update: I decided to go ahead and upgrade to Retrospect 8 (been planning to do it anyway) but I get the same results. The snapshot claims the files are there but the restore capability claims they're not.


    Update2: Never Mind :-) I figured out the problem. "Find Files" does not use the snapshot and will restore all archived copies. More importantly, if files were moved they will be restored to their original location, not where the snapshot says they currently reside. Doing a restore through the "Restore" option with "Advanced" will use the snapshot and do what I need.

  17. Starting about a week ago, I've been seeing a new dialog popping up in the background. The title is "Interactive Services Detection" and the text is


    A program running on this computer is trying to display a message


    See the attached image


    When I click "View the message" it just displays the Retrospect Monitor on a blank desktop. There seems to be one of these every time a scheduled task starts, and I assume something's changed in Win7 that's now trapping the background activity and popping up this new dialog.


    Suggestions on how to avoid this?



  18. I use an eSata drive dock to backup to disk using Retrospect. My usual method is to do a full backup on one HD and then store that in the safe. Subsequent incrementals accumulate on another HD for a week and then another full backup is run, cycling through HDs. I recently had one of the backup disks get corrupted (filesystem only, the disk shows no SMART problems). I was able to recover all the Retrospect backup files to another disk. I decided to run a Media Verify and here's what happened:


    1) It verified the full backup which was not no the failed disk.

    2) Then it asked for the second disk, at which point I inserted the new disk containing the copy of the failed disk.

    3) It verified a couple of files and then asked for the first disk again.

    4) It spent 15 minutes apparently re-verifying files it had already looked at, then asked for the second disk again.

    5) Repeat steps 3-4 for every individual RDB file on the second disk, swapping disks each time.


    It sounds like it's verifying each snapshot, and thus re-verifying files that didn't change from one snapshot to the next.


    Why can't it just verify all of disk 1, then all of disk 2?