Jump to content


Popular Content

Showing content with the highest reputation since 04/25/2019 in all areas

  1. 2 points
    As promised. The Test Client: "NIG-PC" -- Windows 10 VM, Retrospect 15.6.0, with C drive and external E drive. Both drives had "Test_Data" and "Test_Data2" directories, each with a couple of text files inside. Server: Windows Server 2016, Retrospect Multi Server Premium v15.6.1.104 Client was added by Direct IP with "Volumes" tab "Client Sources" set to "Client Desktop" -- both C and E drives were visible A new disk-based Backup Set called "Filter_Test" was created A new filter called "Filter_Test" was created, initially blank and then edited as per the following screenshots After the filter was edited, an Immediate Backup was created: Source -- "NIG-PC"; Destination -- "Filter_Test"; Selecting -- "Filter_Test". The Preview button was clicked and, once the results generated, the screenshot taken. The Immediate Backup was then cancelled to clear any cached Preview and to force a re-scan for the next test The Results "Windows folder path exactly matches \Test_Data\" -- no drive letter, so nothing is matched: "Windows folder path exactly matches E:\Test_Data" -- no trailing backslash, so nothing is matched: "Windows folder path exactly matches E:\Test_Data\" -- drive letter and trailing slash included, matches only with "Test_Data" on E and not E:\Test_Data2 or C:\Test_Data: So, what about "matches pattern"? We know from the filter dialog tip that "* matches any or no characters and ? matches any single character", but x509 had no special characters in his filter yet still got matches. Let's see what we can find out, starting with a filter similar to x509's... "Windows folder path matches pattern \Test_Data" -- matches Test_Data and Test_Data2 on both drives: "Windows folder path matches pattern \Test_Data\" -- matches Test_Data only on both drives: "Windows folder path matches pattern E:\Test" -- matches Test_Data and Test_Data2 only on the E drive: "Windows folder path matches pattern st_Data" -- matches Test_Data and Test_Data2 on both drives: Conclusion Exact folder matching requires a full path, including the drive letter, and a terminating backslash, i.e. "E:\Test_Data\". The "matches pattern" condition includes invisible "*"s, both prefix and postfix, i.e. if you enter "st_Data" it is actually "*st_Data*". That may be what you want, e.g. the same folder name at different levels of the directory structure across multiple drives on a client, but could also greatly widen the matches beyond what was expected. As always, the more explicit you are the closer the filter results will match your wishes. Vagueness on "includes" can massively increase backup resource requirements, vagueness on "excludes" can result in important data being missed. So test, test, test -- and be careful out there! Note Yes this was all done with "includes" whilst x509 was having trouble with "excludes" -- that's simply because I think it is much easier to see none, one or two ticked boxes amongst a column of unticked in a fuzzy screenshot than to spot the gaps in a line of selected items. But the conclusions above also apply to "excludes", and it's simple enough to verify for yourself if you doubt it. Hope that helps someone!
  2. 1 point
    By default, Retrospect Client will bind to the first available active IP address. In a dual-NIC setup (e.g. network card and wireless in a laptop) that "first available" can vary. So you'll need to tell the client which IP to bind to -- see this page for details. Obviously, only works for static IPs. Luckily it sounds like that's what you are using. That might be enough to get you going. Otherwise, could you re-post the problem but refer to machines as "clients" for the ones you want to back up and "server" for the one doing the RS backup? Like David, I'm getting a bit confused as to what's what!
  3. 1 point
    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
  4. 1 point
    David, I had to laugh when I read your suggestion. One of the HARDEST MOUNTAINS YOU WILL EVER CLIMB is to try to convince the management of a small software company to hire a good tech writer to create and maintain their documentation. They see this as a straight money losing proposition. I've tried with different companies over the years, and if there is a convincing argument I've yet to find it. They never think the subsequent decrease in support costs and increase in customer satisfaction will make up the difference. As with most companies, Retrospect's manuals fall into the category of "informative but not instructional". They tell you what the program can do, but not how to use the program to achieve the results you want. It's better than nothing, and you've got to appreciate the volume of the docs, but it's sometimes a treasure hunt to find what you're actually looking for. It is quite expensive to do it right. If you want to see somebody who does it right, and is much bigger than Retrospect, take a look at Fortinet. Just Google "Fortinet Cookbooks" and get on the Fortinet Youtube channel. It's phenomenal. Mark
  5. 0 points
    rfajman and others, As to ProactiveAI, you have to read the Knowledge Base article I linked to in my preceding post in conjunction with pages 236-251 in the Retrospect Windows 15 User's Guide. The "AI" was added to the end of "Proactive" to signify the adoption of a new decision-tree algorithm for determining the priorities of "client" backups. IMHO It really doesn't constitute artificial intelligence, unless you count the use of linear regression along with a decision tree as rising to that level. OTOH it's evidently better than the preceding algorithm, on which Dantz/EMC's patent seems to have expired in 2016. The fact that you have to go through this instructional mess is yet another example of the IMHO gross stupidity/laziness of a policy adopted by Retrospect Inc.'s august Documentation Committee in 2015. Prior to that year, Retrospect Inc.'s policy was to describe new features of a major version fairly comprehensively in the "What's New" chapter of the UG for that version. The descriptions in that "What's New" chapter would then, for the next version of the UG, be incorporated in appropriate sections of follow-on chapters in the UG—allowing the"What's New" chapter to be overwritten with fairly comprehensive descriptions of the next set of new features. Starting in 2015 the august Documentation Committee adopted a policy of only overwriting the "What's New" chapter without incorporating its previous contents in follow-on chapters. The Committee relied instead on individual engineers to create KB articles containing the previous feature descriptions. For some new features, such as the one facilitating moving Members of Backup/Media Sets to larger disks, the engineer(s) couldn't be bothered to create a short KB article. So how to use those features, especially for Retrospect Windows, is locked forever in the minds of Retrospect Inc. engineers—and maybe harassed Retrospect Tech Support people. Starting in March 2018 the "What's New" chapter in the UGs became merely marketing blurbs, useless for administrators trying to learn how to use new features. I created Support Case #59820, stating the problem plainly on 20 March 2018. I was told by a senior Tech Support engineer that, sometime this side of the indefinite future, Retrospect Inc. intends to do a comprehensive rewrite of the UGs. I think it's time for us administrator users to each inscribe the letters "TUIT" on a round piece of paper, and snail-mail it to : Retrospect, Inc. Attn.: August Documentation Committee 1547 Palos Verdes Mall, Suite 155 Walnut Creek, CA 94597 United States That will communicate to the August Documentation Committee a notice that now is the time to "get around to it".