Jump to content

x509

Members
  • Content count

    151
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by x509

  1. I just changed the various Windows date values for a range of photo files, to correct for the camera clock being set for the wrong time zone. Retrospect did not back up the actual files again, since the contents (photo RAW files) were not changed. But did Retrospect back up the new Windows file date values? x509
  2. I made some mistakes in setting up a grooming job, and Retrospect can't find the dataset member in question (my fault, apparently), so I tried to cancel the job from the window below, but the job isn't cancelled. Even if I shut down and restart Retrospect, the job remains active. I seem to be unable to locate the missing member, even when I click through to the location of that member. Is there anything I can do to make Retrospect forget about this job. Is there a file that I can delete, that Retrospect will then regenerate? EDIT: I sort of killed the job by clicking on the Choices option to indicate a missing member. That solved the immediate issue, but I will have to try again, when I have time, to see if I can still groom this dataset. x509
  3. That's what I had to do. x509
  4. 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
  5. Nigel, Thank you for doing all these tests. I got dragged into this morass only when scripts that apparently had been working, stopped working. So I was in "break-fix" mode, or just trying to solve the problems of broken scripts, so I could move things along. I appreciate all your testing here. I'm going to download this thread so I can save it in my folder of "informal" Retrospect documentation. x509
  6. Nigel, Why you say that drive letter will be mandatory? So far it isn't. I'm running Retrospect 15.61. Now that I think about it, the way Windows networking works, Windows Explorer doesn't actually know about drive letters on networked systems. Or, maybe I should say, drive letters on networked systems aren't exposed in Explorer. I sure hope that Retrospect isn't going to screw all this up in a future release. What I do compulsively, you might say, is that I have a uniform usage of drive letters, as I explained in an earlier post, plus the use of Storage Groups. In my DATA storage group, I have the D drives from all systems. About your comment about total lack of consistency in Windows itself, I agree. Compared to the dark old days of DOS, Windows has enforced a lot of uniformity in the interface, even though there are many annoying inconsistencies. There is no question that Apple does a better job in the interface area. However, for my iPhone/iPad, Apple makes these strange changes from one iOS release to the next, and I'm forced to do Google searches. x509
  7. Nigel, Thanks for this reply. I can only comment that it's not exactly great software design to vary from standard Windows practice in specifying a path. There are several different SAVE AS dialogs in Windows, I'm not sure why, but the key point is that none of them require a trailing backslash. In my scripts, I have not found it necessary to include a drive letter, but maybe that's because I use Source Groups in Volumes. I have four systems, and another being added next week, and it would greatly complicate matters if I had to specify fully qualified paths in the scripts, e.g. \\APOLLO\DATA or \\DELOS\DEL-DATA or \\APHRODITE\APH-DATA. (APOLLO is the Retrospect host system.) All my systems are organized the same way: C - Windows and Programs, related settings. NO user data. D - User data, other than music, photos, videos. E - Music, photos, videos F - software downloads (only two systems) x509
  8. Yes, ironic, but these days the Brussels bureaucrats are looking pretty good in comparison with the state of privacy affairs on this side of the pond.
  9. 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.
  10. Lennart, I can't thank you enough for this seemingly simple suggestion. Once I changed the dataset preferences to storage optimized grooming, I got this result: All the 50 GB files are gone, and so are all the folders in $Recycle Bin. Your suggestions together have enabled me to recover over 1 TB of wasted storage. x509
  11. Yes, I forgot to mention grooming a dataset with selectors. I'm having a real issue with Retrospect ignoring a some folders that were explicitly excluded, and this grooming has allowed me to recover about 1 TB of wasted space on my 6 TB (5.45 TB in Windows) backup drive. See this thread, particularly the last few posts. x509
  12. Lennart, Sorry for being so very late in replying. My backup dataset MEDIA has been filling up rapidly with these 50 GB files and my backup drive was dangerously close to being 100% full, so I thought the first thing I needed to do was groom that dataset. I used this Selector with the Groom job: Before running the groom job, I ran a Find Files operation on the MEDIA dataset. Here is the result. There are over 20 of these crazy 50 GB files backed up: After running the Groom Media job, there were still some 50 GB files left. This is the backup log for that grooming job: Unfortunately, some of the 50 GB files remain: I tried several different variations on the Selector, but I couldn't get the rest of these 50 GB files deleted. Also, I noticed after running the groom job that there were a lot of $Recycle Bin folders backed up, like this: I tried all sorts of Selector conditions to get these folders groomed out, but nothing worked. Here is but one example: All this is very frustrating, because I'm both trying to recover wasted space on my backup drive AND work out Selector conditions for the broken backup script. Do you have any suggestions, outside of buying a biggger backup drive? x509
  13. David, I meant the ability to transfer backup files from one dataset to another backup dataset, in the interest of eliminating redundant file backups and simplifying the number of old datasets to store and maintain. x509
  14. David, I didn't just file a support case. I have written to one of the senior execs, several times. I got replies each time, including one (from Robin Mayoff) that is absolute BS that just completely underscores your point about poor documentation in recent releases. I'm still a bit underwater and I have another business trip soon, so i may not get to posting my list of issues until around May 15. But trust me i have "found my voice" with Retrospect. Sorry to dribble all this out. x509
  15. I know it's just about two months since David's post (and unlike ihlo, I find David's posts very helpful), but I ultimately decided not to downgrade. I discovered that I needed to prune out spurious 50 GB files from one dataset, and I also think I will use the transfer datasets features of V15. I'm writing this very late reply because I feel that I owed David a courtesy of a reply and as a way of expressing my appreciation to him. As for being very late with this reply, I'll just say that "life has been happening" for me, with all kinds of situations that delayed this response. If something doesn't kill you, it makes you stronger, or so I would like to think. x509
  16. Nigel, I tested out your suggestion in Windows 10 Explorer. The trailing backslash is not necessary for Windows to understand that I am referring to a directory and not to a filename. Same is when I do a "Save As" with different applications such as Microsoft Word or Adobe Lightroom. It's a damn selector bug, methinks. x509
  17. I have several backup scripts that use the same resource (source drive) and which are scheduled to start exactly one minute apart. I want to confirm that that approach works just fine on R15.61 on a Windows 10 Pro machine.. The practical impact is to "batch process" all the scripts together, and minimize total execution time. x509 PS: I've been away from this forum for a long time, for reasons that I don't want to explain but are "understandable." I will try to do several catch-up posts in the next few days to document all my issues with scripts and selectors.
  18. 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
  19. 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
  20. No explicit changes in Retrospect. Desktop APO and Laptop are running Windows 1809. Desktop APH (older system) still running Windows 1803.
  21. 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.
  22. 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.
  23. 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.
  24. 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
  25. 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
×