Jump to content

x509

Members
  • Content count

    136
  • Joined

  • Last visited

  • Days Won

    6

x509 last won the day on November 20 2018

x509 had the most liked content!

Community Reputation

18 Good

About x509

  • Rank
    Newbie

Recent Profile Visitors

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

  1. As far as I can tell from a quick inspection of each volume, the only file/folder that is backed up, but should not be, is the System Volume Information folder, and only on the systems running Windows 10 1809. I guess I should report that as a bug to Retrospect. To reply to your second question, I have had an ongoing exchange with Retrospect support about file/folder selector conditions that are part of my Include selector, but that don't in fact automatically select new files to back up. I'm still sorting through all that, and I will both submit to Retrospect and do some postings here when I have successfully gotten all folders properly backed up. In this case, it appears that some selector conditiions are not being implemented correctly. As an example, I have top-level folders 2018 and 2018. The selector "path matches \2018" does not automatically select files or subfolders to back up. Change matches to matches pattern and suddenly files in folder 2018 do get backed up, so it seems. I still want to run some more tests. In a different script, I have my normal include selector, plus a few specific folder excludes, as well as the exclude AlwaysExcluded selector. Once I finish these tests, I may need to adjust those folder excludes. x509
  2. Ooops. I didn't document well enough. All my scripts have an "include" selector and an "exclude" selector, which is always AlwaysExclude. Here is the MEDIA script: The source here is the Media drive (always Drive E:) on all three currently active systems: Also I need to add that I back up to 4 different Windows volumes, C-F. This system, APO, and DELOS contain all four volumes. System APHRODITE contains only volumes C-E. The unwanted System Volume Information folder is backed up only on systems APO and DELOS, which are Windows 1809. The unwanted folder backups started on Feb. 12. I didn't make any explicit changes on that date, but Microsoft updates version 1809 frequently in the background or overnight. This folder is not backed up on system APHRODITE, which is Windows 1803. x509
  3. No explicit changes in Retrospect. Desktop APO and Laptop are running Windows 1809. Desktop APH (older system) still running Windows 1803.
  4. DavidHertzberg, I used the Operating System and Application selector as a source for ideas for my AlwaysExcluded selector. My frustration here is that the AlwaysExcluded selector has been set-it-and-forget-it for several years now, and works as expected in all my scripts except this one MEDIA script starting about a week ago. I have not made any changes to the backup script or to the selector that selects files for backup or to this AlwaysExcluded selector. Here is the full selector. The last four lines are application-specific.
  5. Lennart, Thanks for the link. In the latest version (1809) of Windows 10, this System Information Volume is not displayed even though I have selected the View option for Hidden Items But that's OK. I don't want to ever back up this folder.
  6. I'm running Retrospect 15.6.1 on a Windows 10 Pro 64 system. I use Always Excluded Selector for all the different types of files that I want to exclude from any backup script. Here is the relevant part. The issue here is with the name System Volume Information folder. I use this Always Excluded selector for 7 different backup scripts for 5 different backup sets covering Windows 4 drives C-F. For 7 days now, my MEDIA script does back up a 50 GB file contained in the System Volume Information folder. None of the other scripts back up this folder. I can't figure out how to stop my MEDIA script from backing up this folder. It appears that every day, there is a different 50 GB backed up. I thought something might be wrong with the drive, so I reformatted the drive, and then ran the MEDIA script on the now empty drive. Windows never displays this System Volume Information folder. If you use a cmd window, the system shows this directory as empty even though it does contain files. However, the Session Report for the most recent MEDIA script does show files in this folder. So what can I do to stop MEDIA script from including files in this System Volume Information folder? It's a big waste of time and disk space. Again, No other script backs up this folder on Drive C, D, or F, and no other Always Excluded files are backed up by this script or any other script. I believe I can do selective grooming to recover the 350 GB wasted on these files, but that's not a real answer. Very frustrated at this point. In a few days, I will post how apparent bugs in Selector Include definitions have caused a bunch of my scripts to stop working properly when I upgraded from Retrospect 12 to 15.6. x509
  7. Guys, Is it safe for me to downgrade from V15.61 back to the last release of V12? Will all my backups done by V15 still work in V12? If it is safe for me to do that downgrade, I will ask Retrospect for a refund of my 15.6 upgrade. I've been "silent" for a while now, because I have been spending a lot of time trying to deal with a script that broke in V15, and then I had a failed system partition restore on my main system, so i had to spend days (actually evenings and weekends) just reloading all my apps and doing all the necessary configurations. The last straw was when I think I discovered that a backup script that involved several volumes was backing up only one of the subvolumes, but if I did an immediate backup, everything worked fine. I need to do more tests when I get back home from this business trip and then document all these issues. This new problem is in addition to a different script that worked fine in V12 but broke completely in V15.6. I have spent way too many hours just doing what amounts for free quality testing for Retrospect, plus all the time I had to spend reinstalling Windows and apps after that failed Restore operation. So I am royally p---ed. As soon as I get home, I want to finish that testing and then write an email with a multi-page Word doc to Brian Dunagan, Chief Operating Officer. I will include a list of all my support cases and the poor quality of those responses. At this point, I have no confidence in support for their ability to deal with bugs or complex configuration issues. I will also include pages of documentation, including screen shots, about the problems with backup scripts. Thing about backup software is that it needs to do both backups and restores properly and without a lot of hassle. That is fundamental. My recent issues with Retrospect are that it is doing neither. Features like the Dashboard are secondary, in my opinion. I have been using Retrospect for over 10 years now, and I have never had issues like I have been with V15.6 x509.
  8. When I couldn't get my existing Windows 10 Pro install to boot, I had no choice but to do a Retrospect volume restore. (Windows geek warning: my problem was that the BCD Store got corrupted, so the boot manager got confused.) Summarizing the problem the restore failed with lots of 1017 errors. I need to know what to do diffrently so next time I have this issue I can do a successful restore. So I followed the instructions in the manual: I did a fresh install of Windows (after wiping the disk clean). Then i installed just Retrospect 15.6, and did the volume restore, including system state. After the restore my system did boot up OK, but there were lots and lots of problems. Most programs would either not start or start and then stall. Even re-installing a few programs didn't help. The search/command box on the bottom left of the main window didn't work. That means I couldn't open up a CMD window, which in itself is a serious issue. Most desktop shortcut icons didn't display their graphic. I could post the error messages from this install but I can easily summarize by saying that I got 120 error messages. Most were for 1017 errors. Most were for specific C:\Program Files folders. But one error message included "and 52 others" so I don't really know which folders were affected. So I tried doing just a Files and Folders restore, just the latest version of files.. Here is just one issue: Whereas the volume restore was 79 GB, doing the Files and Folders resulted in a total of 85 GB files that either didn't need to be restored or did need to be restored. After this restore, most desktop icons displayed correctly. But the search/command box still didn't work, nor did some programs and Windows control panel items like some Administrative Tools would not run. So i'm stuck doing a completely fresh install, but I want to be smarter about this in the future. I went to the website knowledge base and found this explanation, but I couldn't get the Preferences to run. So once I create my new windows install and install Retrospect, how do I set the configuration? if it matters, my user account is administator status. Also if I have to restore a windows partition on a client system, do these same considerations apply? Retrospect 6.5 and later includes an option to configure Retrospect to run under a specific user account. This should allow a backup of a mapped volume without needing to modify the launcher service. Go to Configure>Preferences>Security. Configure Retrospect to run as a specific user. Note: Users in a Domain should enter the domain name in the "log on to" field of the security preferences. If you are in a workgroup environment, enter the local computer name into the "log on to" field. You should also go to Configure>Volumes. Get properties on the network volume and configure it for automatic login.
  9. I screwed up the BCD Store (used in multi-booting Windows OSes), and it could be that the easiest way to fix that BCD Store is to restore my C volume to 12-16, including system state. My OS is Windows 10 Pro 64, installed on a GPT/UEFI volume. There are apparently other ways to fix the BCD Store, which involve booting from a Windows 10 install disk and then doing some kind of advanced repair. So is it wise to take the "easy way out" and just do the C volume restore? x509
  10. x509

    Backups "freeze" part way with no error

    Fair, but ouch! I thought about this for a while, but if I wanted to enable concurrent backups, I wouldl have to completely restructure all my scripts as well as my source groups, and every time I redo my scripts, I find an issue a few days later. I can live with the lack of concurrence on my four main backup scripts, because I know they work. Still, it's good to know that I can run a grooming operation, even more than one, at the same time I'm doing backups. 🙄 x509
  11. David, I am actually familiar with pcap, but it's not exactly easy to use. If the problem occurred more frequently, I might need to debug the problem, but even for my personal use (where I am the "IT guy" at home), I have a list of issues to address. Of course if this LAN client goes dark more often, then I will need to investigate. I appreciate the help, still.
  12. x509

    Backups "freeze" part way with no error

    James, So "it's a feature, not a bug." So I just tried to run immediately some backup scripts that all work on different backup sets. I deliberately selected different Execution Units. Here is what I got: DELOS and APHRODITE are two LAN clients. The currently active script will back up from these clients. Is that why scripts Software Library and DATA are waiting? If so, major bummer. With some exceptions, all my backup scripts back up different files from both the server (this system) and the LAN clients.
  13. Lennart, Thanks, but Little Snitch runs on on MacOS, and all my systems, including the problem client, are running Windows 10. The problem hasn't occurred for several days now, and i'm still dealing with other Retrospect issues. Once I get them fixed, I am NOT going to pay for another upgrade unless there is a specific feature I need.
  14. x509

    Backups "freeze" part way with no error

    This new "feature" would be nice, if it actually worked. But it doesn't. 😖 Yes, I can now assign different execution units to different backup scripts, but I still can't run two different backup scripts at the same time. And product management "reluctant" to tell Support about a new feature? In all my 30+ years of doing software product management, I was never reluctant to announce a new features, nor were my colleagues. So I'm going to guess, and I'm going out on a limb here, is that the multi-execution feature somehow "escaped" from the Programming group, who probably didn't communicate it to other parts of the company, including Quality Assurance and Support. Draw your own conclusions, and feel free to disagree with mine. x509
  15. x509

    Backups "freeze" part way with no error

    If "Sally" is in sales, "she" is probably in the office only for the "annual sales meeting" and meetings with major customers. And if "she" is like most of the sales people I have known, she is not exactly "IT intuitive." LOL! So Sally and all her fellow sales people can benefit greatly from Remote Backup. By the way, Sally may travel across time zones, especially when she is visiting the home office.
×