Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


x509 last won the day on December 11

x509 had the most liked content!

Community Reputation

22 Excellent

About x509

  • Rank

Recent Profile Visitors

591 profile views
  1. So I thought I would do one more run of my scripts before I submitted the bug report, and now the VSS errors are gone?!🤐 Windows issue? Retrospect? I have no idea, but I don't have the time to chase down this ephemeral issue.
  2. David, I don't use OneDrive nor Hyper V. In any case, I never had this problem until the 16.6 upgrade. Later today (so I don't forget), I'm going to file a support case with all the relevant backup logs attached.
  3. x509


    Agree. I have a selector named "_Always Exclude." The leading underscore means that this selector will be at top of the Selectors list. This selector contains entries like, "~*.* for MS Office temp files, *.bak, my \temp directory, etc. Works fine.
  4. After doing the upgrade, I got a 3050 error for my Outlook PST file and the Adobe Lightroom LRCAT file. Outlook was active at the time, and until this latest upgrade, I have never had any issues backing up Outlook. So I shut down Outlook and reran the relevant backup script and this time Outlook was backed up. But still no backup for Lightroom, which is odd because Lightroom was not running at the time. I even inspected the folder where I have my LRCAT file, and I didn't see the LOCK file that Adobe creates when Lightroom is active. Is this a bug in 16.6, or some weird Windows issue? Or some Adobe Lightroom bug? (No way, Adobe never, ever has any bugs. 😉 ) I haven't yet tried to reboot my system and repeat the Lightroom backup.
  5. So I solved the problem. First I uninstalled the old Retrospect client, using Revo Uninstaller. That utility does a much better job than the normal Windows feature to completely clean out files and registry entries. Then I did an install of the new client (using Revo to track the install.) I did not have to remove the client from Retrospect. After the client install, all my backup scripts worked properly for this client.
  6. One of my clients stopped backing up and I just examined that system. The backup computer doesn't detect this client, The Retrospect client says that it is OFF, but there is no apparent way to turn it on. Specifically the ON/OFF line shown on p. 303 of the Retrospect 16 UG simply does not appear in the main window for this client. I clicked on ALL the client tabs, but I could find no way to turn the client back on. I don't know if it's just my client system, but the Retrospect client seems extremely slow to respond. Every time I clicked on a tab, I got a Windows spinning blue circle for about 15-30 seconds. There is no way to open Retrospect Client Preferences, as described at the top of p. 303. I suspect that this section was not updated for Windows 10 (and maybe not properly tested?). What do I have to do here? x509
  7. x509

    Grooming Policy Too Simplistic

    David and everyone else, I followed David's suggestion and set the Grooming policy for my PROGRAMS dataset to 6, wanting to be very, very conservative about keeping the ability to do restores from not just the last few days. And I selected Storage-Optimized because I'm almost out of space on my backup drive. Anyway, before the backup, PROGRAMS was 1156 GB, over 20% of my 5.45 (net) TB backup drive. The grooming operation removed 675 GB from this backup set. so now I'm done to a net 481 GB for this backup set and I have lots more free space on the backup drive. Part of my "backup hygiene" is that I use a new backup drive each year, starting Jan. 1. So this grooming operation means I won't be running out of space before year-end. Amazing.
  8. x509

    Grooming Policy Too Simplistic

    Retrospect response to my feature request: You can view a listing of what file are backed up on specific days by going to Reports>Session contents. You can browse the session for a specific backup to view a listing of every file copied from that disk on that day. Please let us know if you have any additional questions.
  9. x509

    Grooming Policy Too Simplistic

    DavidHertzberg, Thanks for the compliment. I never thought that anything I do could be a "shining example" for the stalwarts of this group. I already have a separate backup script for the PROGRAMS drive. (I have standard partition/naming assignments for all systems in my LAN. Using the Volumes option, all the various systems' C drives are in the PROGRAMS group, and this group is the target for the PROGRAMS script. It never occurred to me to take the approach you describe, but it does make sense. I like your suggestions and will implement them as soon as I get a chance. Being cautious, I might retain 3 or 4 backups of each file. I keep a copy of all my current year datasets on a USB drive that I plug in periodically to back up those datasets. I didn't think to do a dataset transfer. Instead I use the Goodsync utility to sync the datasets between my G backup drive and the USB drive. That way, I avoid having to groom the USB drive. x509
  10. x509

    Grooming Policy Too Simplistic

    So I just submitted that feature request. I'll post updates if/when Retrospect responds. x509
  11. x509

    Grooming Policy Too Simplistic

    It's about 12 hours after I wrote the last post, just above, and I think I left out an important point. I don't keep any user data on my PROGRAMS drive. There is the Windows ProgramData and the \users\phil set of subdirectories, which keep program config and status data. And some of that data does change frequently. However, these data files are pretty small, usually well under 1 MB. Right now, as I write this post, a script is backing up the PROGRAMS drive. On one system, there is 13, 262 files and 4.6 GB of backup. On another system, 10, 533 files and 6.6 GB. Again, this isn't real user data. I think all these files represent true "transient data," where I would need only the latest version or maybe 2 versions for restore purposes. This is the kind of datathat needs better grooming capabilities.
  12. x509

    Scripts intact after drive replacement

    To be clear, are you running Retrospect 7.6? It's a very old version. I'm running Retrospect 16. Last year, when I was still running Retrospect 15, I had the problem you described with scripts reporting missing volumes. Which version of Windows 10? NOTE: Edited for clarity two hours after original posting.
  13. x509

    Grooming Policy Too Simplistic

    When I back up my Windows 10 partition, which also contains all program installs, I get an enormous number of files in the various Windows directories and subdirectories that get backed up into my PROGRAMS dataset. I back up daily, yet sometimes there are several GB of such changed files. These aren't files I downloaded, and they have really long, obscure names. I'm reluctant to simply exclude the directories that contain these files, since they may be critical to restoring a functional Windows installation. (Been there, done that with a restore approach that didn't include all critical files. That restore failed.) So up to now, my "solution" has been to shrug my shoulders and buy a bigger backup drive. As a single-LAN user, I back up my system and all clients to a separate backup drive installed in my system. I get a new drive each year. For years, I was fine with a 4 TB drive. For 2018, with increasing photo file volumes, I got a 6 TB drive. Even with pruning and then transferring older "Monthly Transaction Data" into my regular DATA dataset, that 6 TB drive is barely enough. The Monthly Transaction Data is files I create and modify on a daily or near-daily basis. That's not what I'm concerned about with this "transient data" issue. So to deal with this issue for now, for 2020, I just bought an 8 TB drive. With likely photo file growth, I will probably need a 10 TB drive by 2021 or 2022. If I could manage all this transient data, I would certainly have a smaller PROGRAMS dataset. Perhaps enough to get by with one size smaller backup drive. EDIT: Spell checker made "LAN" into "land." Fixed with edit. 11-24 x509
  14. x509

    Grooming Policy Too Simplistic

    True enough, but there is no report that identifies those files that have been backed up N times in the last N days/weeks, as in a list that includes file name, directory, file size and dates of recent backups. And it would be even nicer if I could just check a box and Retrospect would automagically groom out these file and even add an exclude item to my backup script. Yeah, I'm smoking the good stuff now. I know that when I back up my PROGRAMS drive, which is Windows and installed programs, I'm backing up some daily or weekly updates for my security software and probably other utilities, and also a HUGE number of Windows files with really cryptic names. But it's too much work to track down these files to determine which are transient. It's "easier" to spend a few bucks on a larger backup drive.
  15. x509

    Unable to bypass frozen Dashboard

    What he said. I had problems with the Console in Retrospect 15, and apparently those issues weren't fixed (properly) even as recently as 16.50. The only practical solution was to do what mbennett wrote. The downside is that I need to start Retrospect manually so sometimes backups go later at night that I would prefer. But at least I get my backups (and occasional restores) done without incident.