Jump to content

DavidHertzberg

Members
  • Content count

    1,243
  • Joined

  • Last visited

  • Days Won

    41

Posts posted by DavidHertzberg


  1. khudson should definitely look at the "–625 (not enough memory)" section on page 526 of the Retrospect Windows 11 User's Guide.  Since the Forum he/she has posted in implies that he/she is running a Server version of Retrospect, I would definitely recommend reducing the number of execution units as suggested in the last paragraph of that section—even if he/she is actually running in only 1 execution unit.

     

    Being a Retrospect Mac administrator, I'm a bit out of my depth on some of the issues here.  However I've also gained a certain amount of experience using Advanced Search for these Forums, which is accessed by clicking the gear icon at the extreme right of the same top line that says "IPS Community" on the left.  To find posts mentioning the -625 error, type "-625" including the quotes (apostrophes also work) in the Find Words box.  To find posts discussing any version of Retrospect Windows, select "Windows Products—Retrospect" in the Find in Forum dropdown.

     

    This thread may be of interest, especially post #5 by Mayoff.  The last paragraph of that post says "Retrospect is a 32 bit program, so it can't use more then 2 GB of physical RAM.", which seems a bit obsolete in 2017.   However, because I don't know if a 32-bit version of Retrospect Windows is automatically installed on a "backup server" running on a 32-bit machine with a 32-bit version of Windows, I also did an Advanced Search on "32-bit" (including the quotes).  This thread may be of interest.

     

    khudson should also look at this Knowledge Base article.  Although that article was last updated in March 2015, the second paragraph under "Further Tips" may still be applicable if he/she does in fact have a 32-bit version of the Retrospect "backup server" installed.  But the first and third paragraphs may also be helpful.

     

    In any case, the World Computer Manufacturers Association is highly in favor of khudson buying a new server (insert appropriate smiley here).


  2. toshy, this is a little late, but I just found this post while trying to solve someone else's problem in another thread.  Although the thread linked to is about someone's -519 errors (which would probably be changed to -530 errors by the #6080 fix in Retrospect Mac 13), the post stimulated my little gray cells—because it suggested a possible cause for your problem with getting a -530 error on only some of the disks on a client.  Try unchecking the "Put hard drives to sleep when possible" checkbox in System Preferences->Energy Saver on your problematic client.


  3. jweisbin might also want to look at this post and the following posts in that thread.  I found that thread by doing an Advanced Search for ChronoSync in the Retrospect Mac Forums.  Of course that thread is talking about a -519 error (which would probably be changed to a -530 error by the #6080 fix in Retrospect Mac 13), not a -505 error, and it is in the "Retrospect 8 for Macintosh" forum—and Retrospect Mac 8 was very buggy.

     

    In post #15 in that same thread, Daniels says "I would try backing it up when it is not use with all programs closed ...."  He/she then says in that same post  "I have experienced this issue especially with Adobe and OS automatic updates, as they are using the network card to download thus preventing Retrospect from connecting to the client."  That especially agrees with what I said about Adobe in post #2 in this thread.

     

    Also, in post #12 in that thread, twickland mentions unchecking the "Put hard drives to sleep when possible" checkbox in System Preferences->Energy Saver.


  4. jweisbin started a thread with the above Topic Title in the "Windows Products—Retrospect -> Professional" forum.  It says he/she is using "Retrospect 14.0 running on a Mac server (OS X 10.9.5 server)".  In the second paragraph of the OP he/she mentions "another backup client running - ChronoAgent"; in the last paragraph of my post #2 I note that ChronoAgent/ChronoSync seems only to be available for macOS and iOS.  IMHO he/she should have started the thread in this Forum, because it looks as if the client machine with the problem must also be running macOS.

     

    Anyway the error message belongs to Retrospect error -505.  I used the Forums' Advanced Search feature to find threads concerning error -505, and they almost all seem to be about Mac or Linux clients.  I've already given jweisbin the benefits of my experience with that error, as well as a guess as to what might be causing that error for him/her, in post #2 in that thread.  If anyone has any further guidance to offer, please post it in that thread.  

     

    P.S.: jweisbin has now posted that he started the thread linked-to in the first paragraph of this post in the wrong forum.  He/she has requested that the thread be moved, but IMHO that is unlikely to get done with Mayoff being so busy these days.  So—again—if any of you Retrospect Mac administrators have any guidance to offer on -505 errors, please post it in that thread.


  5. The "backup client reserved" message has Retrospect error number -505.

     

    I encountered error -505 last fall while backing up my MacBook Pro, and fixed it as described in this post.  The problem, as described in the next-to-last paragraph of the quote of my previous post at the top of that post, was that Adobe Flash Player Install Manager.app was repeatedly trying to update my MBP even though the latest version of Adobe Flash Player was already installed.  Deleting Adobe Flash Player Install Manager.app eliminated the -505 error, enabling my MBP to be backed up.

     

    Just so you don't get confused by that post, the two tests referred to in the last sentence of my first paragraph below the quote were: [a] running my "Sun.-Fri. Backup"  script for the MBP after it had been put to sleep by the timer, and ["bee"] running the same script after I had awakened the MBP.  Test [a] continued to get a -519 error (which would be changed to a -530 error by the #6080 fix in Retrospect Mac 13—which I never installed) after I deleted Adobe Flash Player Install Manager.app.  That is because Wake-on-LAN doesn't work at all—as noted in this later post in the same thread—for my MBP client, and Retrospect Support's QA team has confirmed the same result.  Test ["bee"] ran OK after I deleted Adobe Flash Player Install Manager.app, which is what I want to draw attention to in this thread.
     
    Getting back to jweisbin's -505 problem, my experience last fall indicates a -505 error may be caused by another piece of client software monopolizing the communications facilities that are used by the Retrospect Client.  In his/her case, I assume that Client software is running on a Windows machine—unless jweisbin mistakenly started this thread in the wrong Forum.  Therefore the other piece of client machine software must be named something other than Adobe Flash Player Install Manager.app, even if it is Adobe software that serves the same function.  
     
    However it may be software from another manufacturer, such as ChronoAgent from Econ Technologies, Inc..  I've taken a bit of a look at some pages for ChronoSync, which seems to be in some respects the "backup server" equivalent that "supports optimized file transfers with other Macs using ChronoAgent".  Is it possible that, per this page, jweisbin has a ChronoSync synchronization schedule that conflicts with his/her Retrospect backup script for the client machine that is getting the -505 error?  What would happen if he/she changed the sequence in which the client machine that gets the -505 error gets backed up versus the "other similar machines which don't have this issue"?
     
    BTW, this page indicates that downloads for ChronoSynC and ChronoAgent are available only for macOS and iOS.  So I think that my assumption in the second sentence of the fourth paragraph in this post is wrong; jweisbin did mistakenly start this thread in the wrong Forum.  I have started a thread with the same topic title in the "Retrospect 9 or higher for M acintosh" Forum, asking Retrospect Mac administrators who can shed light on the -505 error to post in this thread.

     


  6. Hi.

     

    I actually found the solution to the problem on the forum here http://goo.gl/gMkIUr  (I couldn't find it using the forum search but Google found it)

     

    ....

     

     

    I found that post with the solution, among other posts concerning the -645 error, using the Advanced Search (click the gear icon at the top right of the page) facility for the Forums.  I specified "-645" in the Find Words box—including the quotes—and "Windows Products—Retrospect" without the quotes (it's in a dropdown) in the Find in Forum box.

     

    As I keep reminding people on these Forums, if you want to find posts discussing a particular Retrospect error you have to put that error number in quotes (apostrophes also work) in the Find Words box in Advanced Search.  Include the leading minus sign inside the quotes; otherwise your results will include posts that merely happen to have the numeric part of that error number somewhere in a line.  IME you'll get some of those posts anyway, so use the search feature of your chosen Web browser to search each returned thread for the specified error number including the leading minus sign—but without the surrounding quotes/apostrophes because your browser search will think they're part of the search string.


  7. It's possible that mcmeini is confused by the two different possible ways of calculating storage capacity, as described in this post.  It's early in the morning for me, but it appears that at least the Retrospect Mac version of the Dashboard uses the "disk drive vendor" way in the Backups pane daily totals, but uses the "computer people" way in the Storage pane totals.  That would mean that mcmeini doesn't have as much available space on his/her external HDD as he/she thinks.

     

    This post was sponsored by the World Disk Drive Vendors Association, which would like mcmeini to purchase an additional external HDD (insert appropriate smiley here).  It could instead have been sponsored by Retrospect Inc., who would no doubt like mcmeini to upgrade to Retrospect Windows 12 (insert appropriate smiley here) so he/she could take advantage of the improved Backup Set grooming described in the first bulleted item here or the second bulleted item here.

     

    P.S.: It was too early in the morning for me; I got the "ways" reversed during my walk from my Mac Pro "backup server" to the MacBook Pro from which I post—so I have now corrected the second sentence in the first paragraph.  However my general point is unchanged; Retrospect uses the "disk drive vendor" calculation way—which gives a higher number of TBs—in some places, but uses the "computer people" calculation way—which gives a lower number of TBs—in other places.  mcmeini should beware of this.


  8. If you think this is an enhancement that should be made by Retrospect Inc., you will have to submit it as a Support Case.  For English speakers, that is done by going here http://www.retrospect.com/en/support/contact, and filling out the form (sorry, I don't know what the equivalent addresses are for non-English speakers, but they can figure it out from their appropriate Retrospect website address).  IMHO this is quite reasonable; obliging you to fill out the form provides Retrospect Inc. with useful details about your Retrospect installation that they would otherwise have to query you for.

     

    As a result, Retrospect Inc. will pay no attention to your post in this forum.  On 12 December 2016, in response to a letter I snail-mailed to Mayoff,  I received an e-mail through a Mayoff account that was signed by JG Heithcock, CEO, Retrospect, Inc. http://www.retrospect.com/en/about#exec.  In it he says "From reading your letter, I think the main issue is that you view the forums as a good place to talk to us, Retrospect, Inc. But we view the audience of the forums as restricted to our customers [my emphasis]. The one caveat we have made on that is for feature requests, largely as we would like to see if other customers also agree on the desirability and feature set for these requests."

     

    That means that the only audience for "Retrospect bug reports" in this forum will be other administrators of Retrospect.  Nevertheless, by posting in this forum you are providing a useful service to us fellow administrator peasants.  Thank you.

     

    Please be aware that the "description of your issue" in the Support Case form is IME limited to about 2000 characters by the Support Case software.  If you go over that limit your "description" will be broken up into a "description" plus one or more "additional notes".  The same is true for any additional notes you may later post yourself.  I suggest that, to avoid the appearance of choppiness in your Support Case, you create your case in a post in this forum and then copy it paragraph-by-paragraph to your Support Case. 

     

    Note that, despite the new dialogs in the Retrospect Inc. Support Case system urging you to sign up for Annual Support and Maintenance, Mayoff has verbally assured me that you don't need to be signed up for ASM to report a bug—only to get personal assistance with coping with it.

     

    If this post sounds formulaic, that's because I intend it to be.  I intend to post it in every enhancement-request thread that appears in this forum, unless the OP indicates that he/she has or will open a Support Case for the enhancement that the thread requests.  Of course, Mayoff could take 5 minutes of his time to post a slightly-more-polite version of this post as a  "sticky thread" that will always appear at the top of the forum.  I don't intend to hold my breath until that happens (insert appropriate smiley here).


  9. If you think this is an enhancement that should be made by Retrospect Inc., you will have to submit it as a Support Case.  For English speakers, that is done by going here http://www.retrospect.com/en/support/contact, and filling out the form (sorry, I don't know what the equivalent addresses are for non-English speakers, but they can figure it out from their appropriate Retrospect website address).  IMHO this is quite reasonable; obliging you to fill out the form provides Retrospect Inc. with useful details about your Retrospect installation that they would otherwise have to query you for.

     

    As a result, Retrospect Inc. will pay no attention to your post in this forum.  On 12 December 2016, in response to a letter I snail-mailed to Mayoff,  I received an e-mail through a Mayoff account that was signed by JG Heithcock, CEO, Retrospect, Inc. http://www.retrospect.com/en/about#exec.  In it he says "From reading your letter, I think the main issue is that you view the forums as a good place to talk to us, Retrospect, Inc. But we view the audience of the forums as restricted to our customers [my emphasis]. The one caveat we have made on that is for feature requests, largely as we would like to see if other customers also agree on the desirability and feature set for these requests."

     

    That means that the only audience for enhancement requests in this forum will be other administrators of Retrospect.  Nevertheless, by posting in this forum you are providing a useful service to us fellow administrator peasants.  Thank you.

     

    Please be aware that the "description of your issue" in the Support Case form is IME limited to about 2000 characters by the Support Case software.  If you go over that limit your "description" will be broken up into a "description" plus one or more "additional notes".  The same is true for any additional notes you may later post yourself.  I suggest that, to avoid the appearance of choppiness in your Support Case, you create your case in a post in this forum and then copy it paragraph-by-paragraph to your Support Case. 

     

    Note that, despite the new dialogs in the Retrospect Inc. Support Case system urging you to sign up for Annual Support and Maintenance, Mayoff has verbally assured me that you don't need to be signed up for ASM to report a bug—only to get personal assistance with coping with it.

     

    If this post sounds formulaic, that's because I intend it to be.  I intend to post it in every enhancement-requesting thread that appears in this forum, unless the OP indicates that he/she has or will open a Support Case for the enhancement that the thread requests.  Of course, Mayoff could take 5 minutes of his time to post a slightly-more-polite version of this post as a  "sticky thread" that will always appear at the top of the forum.  I don't intend to hold my breath until that happens (insert appropriate smiley here).


  10. Upon doing a browser search of the Retrospect Windows 12 User Guide for "Instant Scan", I found that page 572—under the heading "Instant Scan Technology"—says "Starting from Retrospect 8.1.0 (266) for Windows and Retrospect 10.1.0 (221) for Mac, Instant Scan is only used for scheduled script activity, and not any activity manually started by clicking a Run button."

     

    So, along with the enhancement jhg proposed in post #1 in this thread, Retrospect could—and probably should in any case—be enhanced to include the file name and backup date and backup Source of the file that produced the error in that error message.  The administrator, reading the enhanced message, could manually Run a Normal Backup for the Source onto the same Backup Set.  That, although it might backup some extra files if the Backup Set were not still in use, would result in a new backup of the file that produced the error.  This assumes, of course, that the Source containing the problematic file is still available; otherwise the administrator would have to do—possibly with help from a further-enhanced error message that accessed the Snapshot for the Source—the alternate-Source search discussed in the third sentence of the last paragraph in post #5.

     

    Therefore my next post in this thread will be my boilerplate instructions for creating a Support Case for an enhancement to Retrospect.  jhg can use these instructions to create the Support Case, by copying portions of posts in this thread into the "description of your issue".


  11. Some followup to my post #18 in this thread:

     

    First, this page by the maker of Vipre describes how to open a port for Retrospect on a client; see the section "Firewall application and Port Exceptions".

     

    Second, it's apparent that Dave...'s use of portqry.exe, described in post #13 in this thread, didn't detect the problem with port 497 not being open on his client because of the Vipre firewall.  Looking at this Microsoft page, it's not clear to me whether portqry.exe really works to detect open ports on the machine the command is run from—even though a lot of examples on that page use -n 127.0.0.1 as a parameter.  It looks as if Dave... should have used portqry -local instead, and looked for port 497 in the list of ports returned.

     

    P.S.: Of course Dave... could theoretically also have used portqry.exe from his "backup server" to see if port 497 was open on his client machine, thusly

       portqry.exe -n clientmachineIPaddress -e 497 -p BOTH

    But that would assume that he knew the actual 4-octet IP address value for what I've denoted as clientmachineIPaddress.  Judging from what Dave... wrote in post #15, it looks as if that client IP address varied over time.  AFAIK, a way to make that client IP address static would be to do what I suggested in the second paragraph of post #16.

     

    P.P.S.: I have submitted the contents of this post as a no-reply-needed Support Case, just to let Retrospect Inc. T. S. know what the outcome was in case they encounter the same Vipre problem again.


  12. Congrats, Dave....  IMHO what you want to do on a permanent basis is to open port 497 for both TCP and UDP on both PCs.  However this review implies that may be difficult to do using Vipre, because it says that Vipre has its own firewall distinct from Windows Firewall; see the  "Firewall: Good News, Bad News" section.  It might be best to permanently disable the Vipre firewall and to use Windows Firewall, which I presume can be manipulated to open port 497.  BTW, the PC Mag review rated Vipre at only 3 out of five "stars", and it didn't speak highly of Vipre's firewall.

     

    It turns out paragraph 5 in this Retrospect Knowledge Base article, which I linked to in post #7 in this thread, talks about firewall software on the client and backup computer—and says port 497 must be open for TCP and UDP.  I did mention that paragraph in post #7, and mentioned port 497 explicitly from post #12 onward.  

     

    Now that I've read the PC Mag review a bit more closely, it says "Vipre defines permissions for its own processes and a few essential Windows processes. For others, it allows all outbound traffic and blocks all unsolicited inbound traffic."  If you ran your portqry.exe tests with the Vipre firewall enabled, it sounds as if the tests didn't detect that the Vipre firewall was blocking inbound Retrospect multicast traffic.  However I now see in the fourth paragraph of the PC Mag review section I referenced that you can enable Vipre's firewall prompting, but I'm not sure how well that prompting would interact with the Retrospect "backup server" and Client apps.  Therefore I stand by my suggestion in the first paragraph of this post to use Windows Firewall instead, if you insist on having firewall software within your LAN rather than relying on your Internet-facing router to do that job.  I welcome comments on this from any malware expert on the Forums.


  13. First, I have now radically revised my second paragraph in post #14 in this thread, because I was wrong about what the IP address 127.0.0.1 means (see the P.S. of that post for an explanation of why I made the error).

     

    Second, given Dave...'s post #15, my only suggestion would be to give his Client PC a static IP address—see this section of the applicable Wikipedia article.  That is the advice the now-departed (from Retrospect Inc., not AFAIK from life) Alan of Retrospect T.S. gave me nearly two years ago, when I started using Retrospect Mac 12 after five years away from Retrospect Mac 6.1. I gave my two clients the static IP addresses 192.168.1.202 and 192.168.1.203 (which are higher than any DHCP-assigned IP addresses I am likely to have on my LAN), using the internal "website" GUI on my Adaptec Internet-facing (and only) router—which I accessed using the IP address 192.168.1.1.  Alan's advice solved the problem I was having getting my scripts to access my clients; it may do the same for Dave....

     

    Note that purposely assigning Client machines a static IP address is not mentioned in either the Retrospect Mac or the Retrospect Windows User's Guide.  This used not to be necessary for Retrospect Mac 6.1 and previous versions, which I used for 15 years from 1995 to 2010  (my "backup server" machine died of old age in 2010).  My gut feeling is that some change to either accepted standards for IP addressing and/or the underlying Retrospect multicast code occurred in or after early 2009 (when Retrospect Mac 8—a Retrospect Mac 7 was never released, which became the foundation for Retrospect Windows 8 and following versions, was released).

     

    P.S.: When I telephoned Retrospect Tech Support in mid-2015 and spoke to Alan, it is likely that I was getting a -530 error for my MacBook Pro client.  I remember that my script couldn't find the client when running via a schedule, although the script could find the client when submitted manually after I did a Sources->select client->Locate (the Retrospect Mac semi-equivalent of Configure -> Clients -> Properties).  Although I can no longer remember the error number, giving my MacBook Pro a static IP of 192.168.1.202 fixed the problem.


  14. Ok, let's go back to Dave...'s post #6 in this thread.  It sounds to me as if, from his "backup server", Retrospect can't see his client at all.  

     

    I see now that what he's done is to first check if port 497 is open for TCP and UDP on the client.  I have essentially no experience with the Windows command line, but—based on the top part of this article and my long-ago experience with the Unix command line—it looked to me originally as if what Dave... did was to check from his client whether port 497 is open on his server.  That's because I forgot that 127.0.0.1 is in most cases the IP address for localhost (see my P.S. below).

     

    The "Working with Clients" section in the Networked Clients" chapter Retrospect Windows 12 User's Guide, on page 293, says "Retrospect uses port 497 for both TCP and UCP communications. To successfully find and access Retrospect clients, your firewall needs to be set to allow communication over port 497 for both TCP and UDP on all Retrospect clients as well as on the Retrospect backup server."

     

    If port 497 turns out in fact to be open for both TCP and UDP on his client, we then need to go back further in this thread to posts #3 through #5—which were made in 2015.  Dave... should do what Scillonian advised in post #4.  That was to Forget the Client on the Server and Add it again; Forget is covered on page 302 of the UG, while Add of a single client is covered on pages 293 through 295 of the UG.  Once he has done that, Dave... should follow the procedure in the "Testing Network Addresses" section on pages 295 through 297 of the UG, using the known LAN address of the client machine.  Note that page 297 says "If there is no TCP/IP response from the specified address, Retrospect reports error –530"; sound familiar? 

     

    When the Client had been Forgotten, Added, and its address tests OK, Dave... should re-add the newly-re-established client to the appropriate scripts.

     

    P.S.: Radically revised the second paragraph, because I originally erroneously thought that 127.0.0.1 was the IP address for the "backup server"—whereas it's the IP address for localhost (meaning the computer on which the command is being run).  What confused me is that, using Retrospect Mac where I run the Retrospect Console app on the same computer as the "backup server" Retrospect Engine (see the third paragraph in this post, if you want to understand that; the sixth paragraph in the same post briefly explains why that superior app separation can't be implemented for Retrospect Windows), the (for me, one-and only) "backup server" address in the Console defaults to 127.0.0.1.  Sorry.


  15. The third paragraph of this post makes it even clearer why I think Dave...'s -530 problem may be caused by some kind of automated updating being done on his client machine.  In the cases I've encountered, that was being being done when the client machine was first booted or awakened from sleep.  That explained why, when I booted the client machine at least 15 minutes before the Backup script was scheduled to run, it ran OK.  It also explained why, when the script had bombed with a -530 error, I could later see the client machine by doing a Clients->select client->Locate (the Retrospect Mac Console equivalent of Configure-> Clients->select client->Properties->Refresh, I think)—after which the script would run when I manually submitted it.  However I can imagine some app, such as a really zealous anti-virus/anti-malware app, that would continually do automated updating.

     

    All this assumes that, as Dave... reported in post #6 in this thread, he started getting a -530 error while he was still running Retrospect Windows 7.7.341.  It also assumes that, even if he is not part of his installation's IT team, he has enough knowledge of its inter-machine communications setup to be sure that no firewall software (such as the Windows firewall) or hardware (such as a router that can block ports within his LAN) has been recently installed/modified in such a way that port 497 is now blocked for TCP and/or UDP.


  16. It's the automatic updating of anti-virus/anti-malware signatures that I'm talking about, not the software. This post amplifies on the first linked-to post in the second paragraph of post #9 in this thread; the -530 problem on my MacBook Pro over a year ago mysteriously disappeared after a major update to my copy of Firefox.  The only non-occult explanation I could come up with is that, prior to the major update, Firefox was doing some kind of automatic updating of files—possibly relating to Adblock Plus.

     

    IMHO Dave... should also look into automatically-repeated updating notices for Adobe Reader, coming from the Windows equivalent of Adobe Flash Player Install Manager.app.  As this post recounts, deleting that install app got rid of automatically-repeating notices which had caused -535 errors and a later -505 error on my MacBook Pro in the past.


  17. First, when Dave... says "Tech support are also investigating ... ", does he mean Retrospect Inc. Tech Support or his own installation's Tech Support?

     

    Second, IMHO Dave... should read again the sixth paragraph of this post.  I don't run anti-virus/anti-malware software, but the -530 situation he is describing sounds similar to the one I had for four months over a year ago—a situation that eventually seemed to be related to a "conceptual bug" bug involving the Firefox browser doing automated updating.  In addition I had a -530 situation for two weeks a year ago, described in the second paragraph of this post, that definitely was a "conceptual bug" caused by Microsoft AutoUpdate on the old Mac G4 I backup once a week; I solved that situation by trashing Microsoft AutoUpdate.

     

    I'm not suggesting that Dave... disable the anti-virus/anti-malware software on his client machine, even though a known feature of such software is to do automated updating.  However, assuming he is booting the client machine shortly before his Backup script is scheduled to run, I suggest that he setup a "sacrificial script" per the fourth paragraph of this post—substituting Selectors for Rules because he is running Retrospect Windows.  He may need to schedule that "sacrificial script" more than 10 minutes before his Backup script, depending on how long the automated updating takes for his anti-virus/anti-malware software.


  18. Dave... should read this post.  It is about a -530 error problem using Retrospect Mac, but AFAIK that portion of Retrospect is the same in either flavor.  As you will see from the second paragraph, I have unfortunately become something of an expert on -530 errors on Retrospect Mac.

     

    Dave... should then read this Knowledge Base article, and make sure he doesn't have any of the "impossible to communicate with" problems.  In particular, he should follow the procedure in paragraph 4 of that article: Go to Configure > Clients. Select the Client and click Properties, then click Refresh.  If he gets an error message, then he should follow the procedure in paragraph 5 of that article.  If the client still fails the connection test, then he should follow the procedures in paragraphs 1 through 3.

     

    If the procedure in paragraph 4 still fails, then Dave... should re-do what Scillonian says in post #4 of this thread.  I guess one question would be now, as it was then, did Dave... do anything between 3 May 2017 and now equivalent to the "wholesale software reinstallation" he did in 2015?


  19. I don't think there is any way to know which file it is from just reading the log, so you can't just rename it.

     

    I would try to recreate/rebuild the catalog file (not just repair it). The next backup should backup the file in question.

     

    Lennart Thelander, you are of course correct; the error message in post #1 doesn't show a file name.  However "20120623-10775.CR2" in the second line of the error message looks as if it starts with a date.  I suggest jhg, if it's feasible, check the Source disk(s) backed up onto that Backup Set for files created or modified on that date or just earlier, and then trivially rename them—possibly by appending "20120623".  I haven't used Windows for about 13 years, so I'll leave the technicalities to jhg.

     

    In addition, Lennart Thelander, back in 2013 you suggested that cgtyoder repeatedly Repair his/her Catalog File rather than Rebuild it to fix a similar error.  At that time you were using Retrospect Windows; has something in the intervening years made you change your recommendation?

     

    I'm not sure I understand why this would slow things down.  As it currently operates, Retrospect has to scan the source directory and build a in-memory representation of the state of each file. That model is then matched to the catalog to see which files have changed and need to be backed up.  All the verify has to do is set a flag on the file in the catalog so that next time a backup is run that file is considered "changed".

     

     

    The process you are describing, jhg, is the way Retrospect used to operate before Retrospect Windows 8.  Then the Instant Scan option was added; the most-complete description of that I am aware of is in the second paragraph of this review article (which happens to be for Retrospect Mac 10, but—excepting the GUI—that's the same "under the hood/bonnet" as Retrospect Windows 8).  If your Source drive—client or local—is using Instant Scan, a separate Retrospect process will have pre-determined which files and folders have been added or changed since the last backup, so Retrospect itself doesn't have to do any matching against the Catalog File before backing them up.  Instant Scan saves me about 8 minutes on my daily Normal (No Media Action) backup of a single pitiful 700K-file SSD; as the last sentence in the linked-to article's second paragraph says, it is a "really big deal" for administrators with either large networks or large amounts of data to back up.

     

    Doing what jhg suggests would IMHO require a Retrospect Verify run to, if it finds an error of the type shown in post #1, at least disable Instant Scan for the Source disk from which the inconsistency resulted.  That, in combination with the enhancement jhg suggested, should cause the problematic file to be backed up again in the next Backup run.  However there is the possibility that the particular Source disk no longer exists on the LAN ("Joe left in 2013, and we junked his machine/drive"), in which case Retrospect would have to do complicated—perhaps impossible—things with the Snapshot in order to re-backup the same file from another machine/disk that contains it.  Even if that possibility didn't materialize, the administrator would be not happy about having to (assuming he/she read the "backup server" message about Instant Scan having been disabled) manually re-establish Instant Scan for the affected Source drive after the problematic file has been re-backed-up.


  20. As far as forcing Retrospect to backup the file again, how about trivially renaming the file?  According to Ash7 in this thread, that would cause Retrospect to back it up again.  Then jhg could rename the file back to its original name, which would cause Retrospect to back the file up a second time.

     

    IMHO the feature jhg is proposing would require Retrospect to scan the entire Catalog File for each Source drive backup, looking for the "failed on verify" mark.  That would effectively negate the use of Instant Scan, thus slowing down backups.  I don't think many administrators who use Retrospect to backup multiple Source drives within a limited time window would want to make that tradeoff.


  21. For the record, iCompute began another thread on his problem (whose description starts in post #7 in this thread) on the "Windows Products—Professional" forum.  My explanation for what he is seeing is at the beginning of the third paragraph in post #10 of that thread.  The best description of how to get around the problem is in iCompute's own post #15 in that thread, although it is prefigured slightly less clearly (at least for non-Retrospect-Windows administrators like me) in the second paragraph of ProFromGrover's post #11 in that thread.  My clarification for Retrospect Windows administrators of why iCompute would not have previously encountered the same problem in Retrospect Mac is in the third and fourth paragraphs of post #18 in that thread


  22. Since it would not be my place to file a Support Case for this problem, I just phoned Retrospect Inc. Support and spoke to Mayoff.  He says there is no part of Retrospect that uses SMB V1.  In his opinion, bcslaam must have messed up something else when he/she disabled SMB V1 on his/her Windows Pro 10 computer.  Did you—bcslaam—disable it on your "backup server" machine, your client machines, or both?  Did you disable port 445 on internal software firewalls and/or routers, and possibly mistakenly disable port 497 along with it?  (The last sentence is my thought, not Mayoff's; I wanted to keep the phonecall as short as possible because I know Mayoff is busy handling calls from administrators who are entitled to at least 30 days of ASM, so I didn't ask for suggestions from him.)


  23. As I said in the second sentence of the first paragraph of post #2 in this thread, I am not a Windows user.  Therefore I cannot advise bcslaam on any solutions for problems he/she is having trying to run with SMB V1 disabled on his Windows 10 Pro machines.  If any Retrospect administrator can give him/her answers, I'm sure he/she would appreciate it.

     

    However, from the Ars Technica article and its comments I linked to in post #2, it seems as if the easier solution for bcslaam is to simply block the SMB V1 port(s?) on every Internet-facing router on his/her LAN—see the fourth paragraph in post #4.  He/she should then conduct a mandatory meeting of every staff member at his installation, for a briefing on how to recognize a "phishing" e-mail and avoid opening its payload.  No doubt some malware developer (from North Korea?) will eventually figure out a way of downloading an attack over the more modern versions of SMB, so IMHO the ports for those versions too (if there are any such ports) should be blocked on every Internet-facing router.

     

    It turns out I made an incorrect extrapolation from Retrospect Mac to Retrospect Windows in my third paragraph of post #4, which I've now fixed.  Under the "Uninstalling a Client and Its Software" section on page 305 of the Retrospect Windows 12 User's Guide, the "Windows" sub-section says to use Add/Remove Programs from Settings->Control Panel—so there evidently is no Retrospect Client Uninstaller app for Windows.   However the "Mac OS X" section directly below that says to choose Uninstall from the Retrospect Client Installer app; I extrapolated from my Retrospect Mac experience that is the equivalent of that.

     

    Directly below that, starting at the bottom of page 305 in the UG, is the "Advanced Networking" section and its "Access Methods" sub-section.  The "Multicast" sub-sub-section in that sub-section describes Retrospect's default method of accessing client computers.  That method uses Retrospect's proprietary Piton protocol over TCP/IP, which sounds to me as if it doesn't depend on any version of Samba (SMB) since it communicates over Retrospect-Inc.-reserved well-known port 497 instead of port 445.   If bcslaam has internal routers in his/her LAN, he/she will have to read the "Subnet Broadcast" sub-sub-section directly below that on page 306 and configure his /her Live Network window accordingly; however that access method also uses the Piton protocol.


  24. As the topic says. Given the latest WannaCry attacks I have disabled smb v1 in Windows 10pro 1607, but now v12 clients wont install on other machine.

     

    ....

     

    ....

     

     

    I presume that, when bcslaam says "now v12 clients wont install on other machine", he/she means when SMB V1 is disabled the Client software won't install on other machines using one of the procedures described in the "Updating Clients from the Backup Computer" section on pages 302 through 304 of the Retrospect Windows 12 User's Guide.

     

    However let me point out that at the bottom of page 304 there is a section "Updating Clients from the Client Computer".  That in turn links to the section "Installing Clients" on pages 289 through 292.  Assuming bcslaam wants to install Client software on one Windows 10 machine at a time, he/she can use the procedure in the sub-section "Installing Windows Clients for Individual Log In" on page 290.  That procedure does not require any inter-machine communication during installation, so presumably disabling SMB V1 wouldn't stop it from working.  The procedure refers to a Retrospect CD, but he/she can substitute for that a USB thumb drive containing the Retrospect Client software downloaded from here.

     

    I personally use the procedure described in the sub-section "Installing the Client Software on Mac OS Computers" to install Client software on my MacBook Pro, using a USB thumb drive.  If there is already older Client software on that machine, I first have to run the Uninstall app that is downloaded together with the Installer app.  I do not have a Windows computer, but it turns out the Windows equivalent of running the Uninstall app is running Add/Remove Programs from Settings->Control Panel.  Presumably the downloading from the Retrospect Inc. site does not involve SMB V1, but only HTTPS.

     

    I realize the procedure described in the second and third paragraphs of this post will be a "pain in the butt" if bcslaam has multiple client machines, especially if the machines are in different physical locations.  Therefore I suggest that he/she consider blocking the SMB V1 port (port 445) at the Internet router, so he can go back to using the procedures described in the first paragraph.  However he should first make sure that no machine on his LAN is infected with WannaCry, since that malware can spread itself via SMB V1 to other machines on the LAN from one infected machine.

     

    P.S.: Corrected third paragraph per third paragraph in post #6 in this thread.

×