Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 04/07/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
    That's the information I was looking for... So *if* you are only backing up one volume *and* that volume is backing up/verifying successfully *and* you can restore from the backup *and* you get the un-named volume error *and* Retrospect carries on regardless -- I'd just ignore it. If the error is causing other problems, eg killing the script while there are still other machines to process, re-arrange things so the erring machine is the last to be done. If the error is truly killing the system, eg popping a dialog that must be dismissed before continuing, I'd look into script triggers and a GUI-targetted AppleScript to automatically dismiss the dialog so RS can continue. Some things are easier to work round than to fix 😉
  3. 1 point
    As to how the crashing bug report will be treated, read the fifth paragraph in this 2017 post. I have never had ASM, but Tech Support responds to my bug reports; for one bug I was given a test release with enhanced logging—although I didn't get personalized help.
  4. 1 point
    Dashboard actually got me excited- a more friendly user interface! But it is dog-slow (okay - I LOVE dogs, but this thing is a Basset Hound in Greyhound race.) It often hangs, gobbles resources, hangs again when trying to simply scroll, and ultimately gives little useful information. It's everything short of what we've come to expect from Retrospect - a lean, efficient, business-like and functional application. When Retrospect is invoked by a scheduled script, dashboard is the only option that comes up when you want to monitor the program itself - and the fact that there is no escape from dashboard only adds to the frustration. I get that it is well-intended - but it was executed poorly and ends up detracting from the program. I'm in the trial period (Windows 16.5) and likely will invest in Retrospect based on the last ten years of functionality and reliability with 7.7. The dashboard is the single biggest negative in my pluses and minuses column as I decide on making the purchase. Just my opinion here, but instead of the dashboard, might I suggest this approach: Develop a user interface that finally leaves the '90's behind. It would probably meet dashboard's intent with more digital elegance. Add a tray monitor - something we can mouse over and see the basics, or open and get more detail. Perhaps that goes to knowing your customers. Face it - this is a techie's software that requires a greater learning curve than the prettier faces like Cloudberry. I could be mistaken, but I suspect most Retrospect users (certainly me) would appreciate a backup solution that provides ease of both interface and access - and a tray monitor would be a simple, performance-oriented way to do just that.
  5. 1 point
    We have solved the problem. The cause seems most likely to have been Retrospect's new automatic client update feature. In any case, at some point the client software on the affected machines became corrupted or was actually deleted. In the cases we tested, if the client was removed from the sources list and we attempted to re-add it, the process failed due to an incorrect public/private keypair. We decided to just go ahead and reinstall the client software locally on all our "invisible" Windows clients, which solved the problem; we did not need to delete any client configuration files, so these must have been OK.
  6. 1 point
    Kidziti, You raise a whole bunch of points in your post. Retrospect, or any other product in its class, is not just a point-in-time purchase. You also need to "invest" in learning the product (non-trivial) and doing configuration and tuning. You also want to be sure that your investment is protected long-term because of the financial strength of the vendor. I don't know much about Storcentric (or its competition) but I will observe that backup is a relatively mature market category. One could argue that web-based backup is a different market segment than more traditional premises-based backup, but I will leave that argument to others. And what is Storecentric's strategy in purchasing Retrosepct and Drobo, as opposed to any of their direct competitors, I simply don't know. That is an issue for Storcentric of course, but it's also the kind of issue that is catnip for product management types like me. However, on the more narrow decision to purchase an ASM. I have found that I can get quite good support for my issues, even though I have not purchased an ASM. of course, when release 17 comes out, then I will have to pony up for the upgrade. More generally you have to decide if Retrospect, as it exists today, meets your needs better than the competition. Salespeople are supposed to "SWAT," Sell What's Available Today. I would ignore the statement about a new release next March, because the reality of software development is that March can easily become May or July or September. And unless you know what is in that release, you don't know how important that release is for you with capabilities that you need now, but are not in the current release. Whatever you do, DO NOT buy shares in Storcentric. There is not much information on the website, certainly not who/what is funding this acquisition strategy. https://storcentric.com/
  7. 1 point
    kidziti and everyone else, I had a telephone chat with the head of North America Sales for Retrospect "Inc." this morning (his time), in which I suggested just that. My suggestion, which he seems to like, is to simply actively market the Web-based Management Console in its no-extra-cost view-only form. You can get a brief view of the Retrospect 16.1 version of this facility in the first of these four interconnected videos. You can skip the second video (unless you want to learn how to sign up for the Management Console), and view the third video to see how to integrate the Management Console with a running Engine. The fourth video, which is designed for "Partners" (consulting organizations) shows additional two-way features available with the Add-On—which is US$49 for the Desktop Edition. The Retrospect 16.5 Add-On version of the Management Console moves the list of "backup servers" to a column on the left-hand side of the Dashboard window. Its Granular Remote Management also adds Activities and Sources and Backup Sets panels that the administrator can drill down to, as well as Scripts Management displays and the ability—for individual "backup servers"—to create and edit scripts and create destinations. Here's a 43-minute webinar that demonstrates the Retrospect Windows 16.5 version of Granular Remote Management—with a GUI resembling Retrospect Mac. At minute 27 the head of Retrospect Tech Support recommends leaving Retrospect running all the time—using the Management Console. At minute 29 he says they're moving towards having Retrospect run as a service with an HTML-based GUI. Is Server column also in the non-Add-On Web Dashboard? As the first of the four interconnected videos linked atop this post once stated, the Dashboard in the Management Console is basically an enhanced version of the non-Web-based Dashboard that kidziti and other Retrospect Windows administrators simultaneously love and hate. That non-Web-based Dashboard is a poorly-implemented feature of Retrospect Windows. It was implemented in Retrospect Windows 8 because a Retrospect-Mac-like Console proved to be impossible, but had glaring bugs that weren't supposedly fixed until 4 years later in Retrospect Windows 12.5. See this 2017 Forums post by me, which quotes the applicable 12.5.0.177 Release Notes but also quotes a reply from Retrospect Tech Support. Also read the remainder of that 2017 post's thread.
  8. 1 point
    Earlier this year, I tried to restore my "production" system, following the directions in the V15 manual. That system is Windows 10 Pro 64. The V15 manual states on p. 99 (my highlights) So I blithely assumed that I could do a Restore of my C : partition, after it somehow got hosed. Wrong!! I ended up reformatting that partition, doing a fresh install of Windows, and then re-installing all the programs and doing all the config settings. So I was pretty frustrated about the experience. When I wrote a letter a few months ago to Retrospect management about a bunch of issues, I included this issue. I got a detailed response to all my issues from Robin Mayoff, which I do appreciate. However, it was very frustrating to read the following. When you perform a restore of a Windows operating system with Retrospect, it is very important to perform this restore while booted from a Retrospect Disaster Recovery disk. It is not possible to restore a modern version of the Windows registry or Windows system while booted from the C disk. This is probably why you got some errors and ended up needing to reinstall programs. Had I known this point, I could have saved myself several days of work. Why am I posting this now, months after the fact? I can't fully explain why, but "stuff" happened. Still I thought this point is important enough so that the next person with this problem might find this post and save themselves a lot of trouble. As the expression goes, I am "paying it forward" in appreciation for all the help I get in this forum.
  9. 1 point
    I don't have exactly the same experience... however, I do have a caution to share: Microsoft OneDrive has a similar feature. Last I checked, it's not exactly compatible with ANY backup software, in the following sense: Backups work fine However, when you go to restore, it restores the EMPTY local folder(s) Which causes the cloud copies to get cleared out Which means you lose all of your cloud files Unfortunately, I can't place the details on this with a quick google search ...
  10. 1 point
    Interesting. I just finished discovering a specific set of bugs in Retrospect, and challenges in our router(s) and local network apps, that directly lead to the above anomalies in finding and/or connecting to clients. (Yes, all of the following has been submitted as a bug report.) I'm running a more Windows-centric network, with a little OSx tossed in, so my tools are a bit different. Tools: WireShark: shows packets actually traveling. Most useful is a filter of udp.port==497 || tcp.port==497 tcpdump (command line in linux and/or osx) - monitoring port 497 TCPview (from SysInternals, now owned by Microsoft) - sort on port. Look at what is listening to 497 and on what IP address(es) (command line) ipconfig and also "route print" In Retrospect: go into Clients -> choose a client-> access tab -> Interface -> Configure Interfaces ... and see what default interface IP address is. Things to watch for: Are UDP broadcast packets being received by clients? (eg 192.168.x.255, port 497) For multicast, are packets getting to clients? (eg 224.0.0.0/4 -- Retrospect uses 224.1.0.38 UDP port 497) Are clients responding to those packets (UDP broadcast or multicast) (initially to UDP port 497 on the backup system) If crossing subnets, is TTL set high enough to reach the client? What could possibly go wrong? Heh. Here are anomalies I've seen: Often, some app will create virtual interfaces. This includes npcap (for Wireshark etc), VMware, TAP-Windows (comes with Windows?), etc... This has led to: On some of my clients, some virtual interfaces have APIPA addresses (169.254.*) -- which makes it obvious when retrospect chooses the wrong interface to listen on! (Workaround: I uninstalled the TAP-Windows adapter as I don't need it. And I temporarily disabled npcap on the one workstation where that got in the way.) On my retrospect backup desktop, retrospect chose one of the VMware virtual adapters as the default adapter! This even though the real gig adapter has higher priority etc etc. (Workaround: create another adapter in Retrospect) The result in either case: I can't see the clients, even though ping works. I have a network security system. It regularly scans all ports on all subnets. Some (but not all) clients get confused by this, with the retroclient app hung up on an IP connection in CLOSE_WAIT status. The result: the client is never available for backups. Yet it is visible to subnet or multicast. We switched to a pfSense firewall/router. I just discovered that multicast forwarding is badly broken.(Workaround: manually installed pimd.) Similarly, UDP broadcast is often blocked by firewalls. Make sure the packets are getting through! Having fixed and/or worked around ALL of the above, and rebooted everything... I can now reliably use either multicast or subnet broadcast to connect with clients.
  11. 1 point
    It is 100% true, but it would have been more clear if the backup set name was within single or double quotes, such as: from Backup Set "Drives C D and V"
  12. 1 point
    Tags. If you set your scripts to use tags to determine what to back up, you only have to set a new/replaced client's tags once and it will be picked up by all appropriate scripts. And as David said, you shouldn't get a full backup unless that's part of the script's definition -- "Match only files in same location/path" may be the culprit here.
  13. 1 point
    You're right about Server Editions, Nigel Smith, but the OP says he licensed the Desktop Edition. As for the "soak the (presumed) rich installation" policy, which was instituted by Dantz before it was acquired by EMC, IMHO the recent failure of that "value pricing" policy in general is what led to the StorCentric acquisition. It appears business customers no longer needed to license Server Editions, because they were now using Linux machines as their servers. Retrospect Inc. put a yellow-colored note into the Windows 15.1 Release Notes saying "Linux Client: In a future update, Linux clients running on server-level Linux distributions will be treated as server clients". However, as I cautiously mentioned elsewhere on these Forums, the opinion of experts I solicited on the Ars Technica Linux forum was that it would be impracticable to distinguish server-level Linux distributions—which shot down extending the "soak the (presumed) rich installation" policy. I have never questioned Windows administrators' need for the Dissimilar Hardware Restore Add-On, just its different "value pricing" levels in the Online Store.
  14. 1 point
    Joriz. First I suggest you read this April 2019 thread—the whole thread all the way through the final post. The OP in that thread discovered that he was backing up a lot more data than he thought he was. He also found the data was mostly pre-compressed, so that what really mattered was the native capacity and speed. Second, the OP in that thread also found that the tape library was never cleaning its heads—so he was getting un-recoverable errors after only a fraction of a particular tape was used. Your "backup server" machine is quite old; are you sure whoever was responsible for it before didn't just cable-up a new tape library without finding out how to set up head cleaning? That's one reason why Nigel Smith asked the make/model question. See pages 50-52 of the Retrospect Mac 16 User's Guide for instructions on how to set up cleaning for libraries and drives. Third, you write "a manual file transfer of the same source is utilizing the 1Gbit network card". That sounds as if there might be more than one network card on either your "backup server" and/or your SMB-attached source machine—which brings up another set of questions. After you've looked into those questions, I would suggest you phone U. S. Retrospect Technical Support at (925) 476-1030; the people on these Forums are just volunteers like me‬. If your organization installed Retrospect Mac 16 within the past 30-45 days, you are entitled to free personalized support. Because it sounds as if your native language is not English, and because you posted so early in the morning even compared to New York time, it seems that you may be located in Europe. I've heard that European Retrospect Tech Support is handled by a contractor, whose personnel don't know that much about Retrospect (probably especially about Retrospect Mac). May I suggest you put your Location in your Forums profile?
  15. 1 point
    Sounds like you've got problems with the library/drive. What make/model is it? I try to use Retrospect Client on the source servers rather than SMB-mounting them onto the Retrospect server since I find it generally works better -- an interrupted/resumed SMB session is usually handled fine during, say, a Finder copy but can be death to a backup. Otherwise, try the usual troubleshooting: how fast is a Retrospect Server to tape backup (i.e. eliminating SMB from the problem); how fast is a backup of SMB-mounted share to a disk directly attached to the Retro Server (i.e. eliminating the tape drive), and so on. For best speed you may want to look at a disk-to-disk-to-tape setup... As to overwriting tapes -- we don't do that here but, IIRC, that's what the "Recycle Media Set" media action (in the "Schedule" pane of the script definition) is for. Or have you tried that and found it doesn't work?
  16. 1 point
    We are working closely with Apple and are testing each internal build as they come out. We will put out an official statement when we get closer to the release. I think we have a few more weeks before Apple posts it. Like all Apple systems, we will make sure it works with Retrospect.
  17. 1 point
    Lennart_T, I am shocked that you of all people would say such a thing (see the second and third paragraphs) about the UG. Since I'm sure you're just as tired as I am of dealing with the lack of UG updating, I suggest you write (which I've done) to Rod Harrison—the Chief Technology Officer of Drobo who probably now has some influence at Retrospect "Inc". If you want to impress him with a Swedish-stamped "snail-mail": Drobo Attn.: Mr. Rod Harrison, CTO 1289 Anvilwood Ave. Sunnyvale, CA 94089 USA However, if you are willing to enroll in LinkedIn—which I am not because of delete-finger tiredness—you should be able to get an e-mail address for Harrison there. P.S.: What Lennart_T and I said about the User's Guide not being updated is still valid; Nigel Smith's post below goes beyond what the UG says.
  18. 1 point
    Oh my, x509, it appears you're back to the same situation I responded to here in a post last fall. My first suggestion would be to follow whichever of the alternatives is appropriate from the first paragraph of that post. My second suggestion would be to update your Support Case on the problem, but this time tell Support to tell Engineering that you'll go to Rod Harrison—CTO of Drobo and probably by virtue of that position now de-facto StorCentric "enforcer" at Retrospect formerly-Inc. Engineering—if you don't get some work-around in Retrospect Windows 16.5 (which I hear is due out around 20 September). A snail-mail address for Harrison is : Drobo Attn.: Mr. Rod Harrison, CTO 1289 Anvilwood Ave. Sunnyvale, CA 94089 However, if you are willing to enroll in LinkedIn—which I am not because of delete-finger tiredness—you should be able to get an e-mail address for Harrison there. My third suggestion would be to "go with the flow", and setup the Web-based Management Console per this Knowledge Base article. Of course I haven't had to do that because, as a Retrospect Mac administrator, I've had a perfectly-adequate non-Web-based Console since I upgraded to Retrospect Mac 12 (from Retrospect Mac 6.1 on a "backup server" machine that died in 2010) in 2015. P.S.: In response to x509's post below, I'd think "royally pissed" would be expressed by the following emoji:
  19. 1 point
    Replying months later to Lennart_T's post, I finally (never mind why!) got around to doing a grooming operation. It was a success. Here is the selector I used in the groom job: Note that the S-1 ... folder never should have been backed up. The System Volume folder was explicit.y excluded in my universal "Always Exclude" selector. Just in case the System Volume exclusion didn't work, I also excluded files matching pattern 32{* and *{380* that are either 12 GB or 50 GB in size. Before the groom operation I did a Find Files operation on the Media dataset, to identify files and folder to groom out. AFter the groom operation, I did another Find Files operation to confirm that all those files were in fact groomed out, except for an S-1* folder inside the $RecycleBin, which should never have been backed up. (But I'll clean that up.) The groom operation recovered 345 GB and 15479 files. After I get some more experience with this grooming selector, I will incorporate it into the backup script. x509
  20. 1 point
    launchd still thinks it should load InstantScan, even if you've turned it off. Try the following in Terminal to stop launchd from trying to load retroisa now, and turn if off for the future: sudo launchctl unload /Library/LaunchDaemons/com.retrospect.retroisa.plist sudo defaults write /Library/LaunchDaemons/com.retrospect.retroisa Disabled -bool true Then check to see if it's worked: sudo launchctl list | grep -i retro ...and, with any luck, you'll see just retroclient and updater listed and not retroisa. How are you choosing those folders -- are they "Favo(u)rites", or are you using rules?
  21. 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!
  22. 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
  23. 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
  24. 1 point
    FYI: You can delete the snapshots one by one. But it takes lots of time and Retrospect is "not responding" for a looong time for each snapshot.
  25. 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".
×