Jump to content

x509

Members
  • Content count

    151
  • Joined

  • Last visited

  • Days Won

    7

x509 last won the day on May 3

x509 had the most liked content!

Community Reputation

19 Good

About x509

  • Rank
    Newbie

Recent Profile Visitors

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

  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. That's what I had to do. x509
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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.
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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.
×