Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by DavidHertzberg

  1. Thank you, iCompute, for clarifying the existence of the Retrospect Windows "Retrospect Dashboard" stand-alone view-only app and its differences from the Dashboard panel in the "backup server" Activity Monitor.  


    DovidBenAvraham has now updated the Wikipedia article accordingly.  He has also updated the article to state that the "Console for iPhone" app mentioned as an item in its "Retrospect Macintosh 9" section has not been updated since 2014, even though there is still a "Retrospect for iOS" appendix in both the Windows and Mac User's Guides.  My guess is that either there were technical problems in keeping the iOS app up to date, or the iOS app still works un-updated, and/or the rise of Android phones made an iOS-only phone app into a niche product whose generalization would have been too expensive—so Retrospect Inc. may have simply abandoned it.


    I will create a Support Case requesting updating of the Retrospect Windows User's Guide to include the "Retrospect Dashboard" app.  In that Support Case I will also ask Retrospect Inc. to test whether the Retrospect for iOS app still works either for Retrospect Windows and/or for Retrospect Mac (being an old fuddy-duddy I don't have any kind of cell phone, so I can't check it for Retrospect Mac myself).

  2. So how does one run the Dashboard without having launched the Retrospect app, and then running the Dashboard from within that app?  I don't have a Windows machine, so I don't know about the programs group, but is there actually a separate  app or Windows service named "Dashboard"—not "Retrospect Launcher"—shown there?  If so that would be wonderful news, and I'm sure DovidBenAvraham would want to revise the Wikipedia article to include that information.  However that news seems to have escaped the Retrospect Inc. committee that, per Mayoff, writes all the User's Guides and most of the Knowledge Base articles.


    And yes, I am sure that I am downloading the Retrospect Windows 12 User's Guide when I refer to a UG on this forum.  Even I am not stupid enough to look in the Retrospect Mac UG when I have a question about Retrospect Windows (although a few months ago In the "Retrospect 9 or higher for Macintosh" forum I actually did intentionally look in the Retrospect Windows 11 UG, because its greater length includes discussions of facilities that are in the Retrospect Macintosh app but left out of its UG).  It's just that my fingers are stupid, and tend to type the number 14 instead of 12 because I now have Retrospect Macintosh 14 installed.  I've now fixed the two such mistakes my fingers made in this thread.


    IMHO ProFromGrover is misunderstanding what the Relaunch button in RDP (still known in the Retrospect Windows UG as Terminal Services) does for the Retrospect app.  Every mention of the word "relaunch" in the Retrospect Windows 12 UG after the "What's New" chapter—except for the mention on page 383 that refers to manually relaunching Outlook—puts it into a phrase similar to "exit [my emphasis] and relaunch Retrospect".  That includes mentions on pages 67, 264, 436, and 509.  If you have exited Retrospect the program can never be in use, because you just killed it by exiting.  That is why you don't get the message that the Retrospect program is in use.


    P.S.: ProFromGrover has taken irate exception to what I wrote in the third paragraph.  At the time I wrote it, I did not yet believe that there is a "Retrospect Dashboard" program that is separate and distinct from the "Retrospect" program—given that to this day there is no indication in the Retrospect Windows UG of the existence of the "Retrospect Dashboard" program.  In post #11 (where he refers to what turns out to be the "Retrospect Dashboard" program as owning the "service", and erroneously reasons that it must do so because like the Retrospect Launcher it does not show a Taskbar icon), and even IMHO in post #13, ProFromGrover did not make it clear that he was referring to a separate program rather than the Dashboard in the Activity Monitor of the Retrospect program.  So that's why I thought he was misunderstanding the Relaunch button in RDP.  Fortunately iCompute—having learned a fair amount about Retrospect Windows during the nearly 2 weeks since he wrote post #1—has explained in post #15 that there are two programs with different functioning of the Relaunch button.

  3. DovidBenAvraham updates the Wikipedia article basically from the information in Retrospect User's Guides, although wherever possible he tries to cite a second-party review as a reference to avoid being accused of violating a WP rule by using too many primary sources.  He does, however, look at relevant Forums posts.


    The only mention of the Dashboard in the Retrospect Windows 12 User's Guide is in the "High-level Dashboard" section of the Fundamentals chapter on pages 31-32.  There it says "Launch Retrospect Activity Monitor from the Windows Start menu or Start screen."  On page 242 it says " ... click Activity Monitor from Retrospect’s navigation bar ...."  That IMHO means that the Retrospect Dashboard can only be viewed within an execution of the "Retrospect backup server".  AFAIK the "backup server" runs as an ordinary Windows program, with the accesses allowed by the user account it is run in—per page 419 of the Retrospect Windows 12 UG.  


    As described on page 420 of that UG, you can Enable Retrospect Launcher service [my bolding], which "registers the launcher application as a service so it is always running. This allows the auto-launch preference described below ....".  My understanding is the Retrospect Launcher is a Windows service; my further understanding is that Windows services cannot display a GUI (I don't have any Windows programming documentation, but some of you may).  I'm dead sure that, if it could display a GUI, the Retrospect Inc. engineers would have built a capability to display the Dashboard into the Launcher.


    So I think what I wrote in my post #10 is correct, and when ProFromGrover wrote "it owns the service" in the second substantial paragraph of his post #11 he didn't mean Windows service—i.e. the Launcher.


    ​Please, anyone, feel free to correct me if you have better information.  I'm trying to make this thread a definitive resource for any "new Windows user [who] wants advice" about Retrospect Windows, especially if—like iCompute—the new Windows user is coming from Retrospect Mac.


    P.S.: A little Googling goes a long way.  My further understanding in the third sentence of the second paragraph appears to be correct; a Windows service, such as the Retrospect Launcher, cannot display a GUI.

  4. Let's go back to iCompute's OP.  His problem seems to be that on Windows he can't see what Retrospect is now doing, or has done, unless he either starts the Retrospect app on his "backup server" machine or finds that the app is already running.  If the app was not running before, he can simply exit the app when he is finished looking.  However if the app was running before, he must take care not to exit it after he is finished looking and/or executing immediate operations—lest he stop any script or immediate operation that is running.


    To understand where iCompute is coming from, those readers who have only used Retrospect Windows should look at the second bulleted item—starting with "Powerful new engine"—under the first paragraph of this section of the old Wikipedia article.  The last sentence in that item means that a Retrospect Mac administrator can start or quit the Retrospect Console app without affecting the continuing operation of the Retrospect Engine app—which is the app that actually runs scripts or immediate operations.  The Retrospect Mac Console app does what the Retrospect Activity Monitor does in Retrospect Windows, but the Console is a separate user-space app. 


    Unfortunately, as described in the second through fourth sentences in the second paragraph (the one after the bulleted items) of this section of the old WP article,  Retrospect Windows (running on Windows Vista or beyond) can't separate the Console function from the Engine function; they both must be part of the same user-space app.  So while running Retrospect Windows it seems that iCompute must—to be safe—first look at the Taskbar system tray for the account that might have Retrospect running on the "backup server" machine; and Retrospect must have been installed on that account with the Startup Preferences option to show a Retrospect icon in the system tray when Retrospect is not running.  Having done so, iCompute need only remember whether he started Retrospect from the system tray icon or whether Retrospect was already shown on the Taskbar.  If the latter, he must take care not to exit the Retrospect app when he finishes looking.  The alternative to the second and third sentences in this paragraph is for iCompute to have first checked Services and Tasks, presumably in the Processes tab of Task Manager, which he may only be able to do if he is signed in to an administrator account (not being a user of modern Windows, I don't know about such things).


    If iCompute has physical access to the "backup server" machine, he can do all this from its keyboard.  Otherwise he can remotely use Windows RDP (renamed from Terminal Services, which is how it is still referred to in the Retrospect Windows 12 User's Guide).  Either way he must be able to logon to the account that might be running Retrospect.  If there is a problem with this because the account is not an administrator account, he may have to bypass UAC as described by ProFromGrover in the post linked to from post #6 in this thread.  iCompute might have a third alternative for monitoring and running/stopping scripts, which is Retrospect for iOS, but that app has not been updated in the Apple App Store since 2014 (although it is still described in an appendix on page 578 of the Retrospect Windows 12 UG).


    I don't know whether Retrospect Windows has a method of closing the Retrospect Activity Monitor while leaving the Retrospect app running, which might cut down on the RAM used.  


    Please remember that I don't use either modern Windows or Retrospect Windows.  If I am wrong in this post, please correct me.  I have, however, looked at this and subsequent posts in the thread linked to by ProFromGrover in post #6 of this thread, as well as at the posts preceding the one he linked to.


    P.S.: Corrected fourth paragraph; Retrospect for iOS is still available in the Apple App Store, although it has not been updated since 2014 (I couldn't find it when I checked the App Store app on my MacBook Pro, but that app may only show App Store apps for Macs).

  5. When you said your disk is full, you were referring to your "2-disk 5-TB USB-attached media set".  However I'm beginning to wonder if you have enough space on your catalog-storage volume, which probably has a folder whose hierarchical name is root-volume/Library/Application Support/Retrospect/Catalogs.  If you don't, implement what I said in paragraph 3 and the P.S. of post #2 in this thread, but put the new catalog on another drive that has enough space.


    OTOH even if you have enough space on your catalog-storage volume, I would suggest you purchase a new 4TB USB3 portable external hard drive—they're slightly over $100 on NewEgg.com tonight, initialize it with a different name, and copy the "Retrospect" folder and everything underneath it on your Offsite 3 TB drive to the newly-purchased drive.  Then do what I suggested in paragraph 3 in post #2, but when Retrospect asks for your second Member (assuming that second Member was on your Offsite 3 TB drive), give it the newly-purchased drive instead of the original Offsite 3 TB.  Then do what I said in the P.S. of post #2.  Finally, when the catalog has been recreated and everything is OK, wipe your Offsite 3 TB disk and figure out something else to do with it; do you have grandchildren or nephews you could give it to?

  6. For a start, you can read Chapter 9 "Disaster Recovery" on pages 329-350 of the Retrospect Windows 12 User's Guide.


    There are now 3 Disaster Recovery video Tutorials.  I think the one you probably want is this one, entitled "Prepare for Disaster Recovery—Flash Media".  However, if you are old school, you may want this one, entitled "Using the Disaster Recovery Boot CD".  If you are positively archaic, you may want this one, entitled "Disaster Recovery Preparation in Retrospect 8 for Windows"—which may correspond to what's in the UG.

  7. I've been polluting my mind further.  iCompute would do well to pollute his mind by using his web browser to search the Retrospect Windows 12 User's Guide using the phrases "auto-launch" and "system tray".  However he can first get a general idea of what's going on by reading post #2—by JoTraGo—in the thread linked to by ProFromGrover in post #6 of this thread.


    If you are logged in as a non-administrator on the "Retrospect server" PC, it looks as if the procedure in the long post by ProFromGrover in the thread linked to by him in post #6 in this thread is also necessary.  But, as someone unfamiliar with modern Windows, I don't understand auto-launch precisely.


    P.S.: DovidBenAvraham has now added a link to a Knowledge Base article outlining the general idea at the end of the first paragraph of this section of the Wikipedia article.


    P.P.S.: DovidBenAvraham has now added another sentence to the second paragraph of this section of the old Wikipedia article, mentioning the capability of setting up the Retrospect Windows "backup server" so that it can be used remotely via RDP—as described in the post linked to in the second sentence of post #4 in this thread.  That capability is mentioned on pages 67-68, 419, and 434-436 (all of which refer to RDP/RDS as Terminal Services—which AFAIK is obsolete Windows terminology) of the Retrospect Windows 12 UG, so Retrospect Inc. apparently doesn't consider it a kludgey workaround.


    P.P.P.S: I've totally rewritten the second paragraph in this post; I didn't understand what I was talking about.  I've also rewritten the first paragraph in post #4 in this thread, because what I thought was a kludge dreamed up by an administrator turns out to be a kludge dreamed up by Retrospect Inc..


    P.P.P.P.S.: ProFromGrover, would you be kind enough to explain under what circumstances the solution you linked to in post #6 of this thread—which you say in post #6 of the linked-to thread goes against security standards in some installations—is necessary?

  8. As I said at the beginning of post #2 in this thread, as an exclusively Retrospect Mac administrator I can't really contribute much to this discussion.  However I have now done a bit more searching.


    First, it turns out that there are at least two "Resources" Knowledge Base articles on this subject: this one and this one.  I suggest checking that whole Resources section of the Knowledge Base, skipping the articles that start with a numbered error code; you may see another article that is applicable—in which case please post it in this forum thread.


    Second, wading into the morass of the Retrospect Windows 12 User's Guide, it seems to me that there are two areas where this subject is covered.  The first area is the "Using Retrospect" and "Using Windows 8 ..." sections of the Getting Started chapter; these are on pages 15-23.  The second area is the "Retrospect Preferences" section of the Management chapter—especially the "Schedule Preferences" and "Security Preferences" and "Startup Preferences" sub-sections; these are on pages 416-420.  It may be helpful to search through these pages with "launch" in your web browser's search bar.


    All I can say in conclusion is "Better you than me, buddy" ;).

  9. iCompute might consider doing what is described in this post.  To access the running Retrospect "backup server" app, which includes what we Retrospect Mac users know as the Console, he would then have to do what is described in this post.  That workaround is IMHO kludgey,  but it's on page 434-436 of the Retrospect Windows 12 User's Guide.


    If any Retrospect Windows administrator has a less-kludgey solution, please post it here.


    P.S.: With more knowledge, I have corrected the second sentence in the first paragraph of this post; retrorun.exe is not the "backup server" program itself, but is the launcher that runs as a Windows service to launch the "backup server" program when a scheduled script is due to be run.  I've also changed the third sentence in that paragraph, because using Terminal Services turns out to be SOP.

  10. I come to sympathize, but I can't really help.  My "backup servers" have always been Macs, although I had a Windows 95 client from 2001 to 2004.  


    IMHO to understand why there are major differences between the Retrospect Mac and Retrospect Windows GUIs, you need to read the first paragraph of this section of the Wikipedia article.  I do not dare to comment in these forums on the contents of that paragraph, but if you click on the footnotes for that paragraph and follow their references you'll gain an understanding as to why the Retrospect Windows GUI went its own way.


    In this same section of the WP article,  the  Knowledge Base article linked to at the end of the first paragraph explains why you are finding that Retrospect Windows stops cold if you log off.  The article details ways around this, but I don't know modern Windows well enough to understand—much less explain—them.  One approach to finding such a way is to use the Advanced Search capability of these forums, which you can access by clicking the gear icon on the far right of the top line that says "IPS Community" on the left.  For best results, I recommend putting any multi-word search term inside quotes.  Another approach, if you either are in the pre-sales process for Retrospect Windows 12 or have purchased it within the last 30 days, is to contact Retrospect Tech Support.  Retrospect Inc. should darn well create a Knowledge Base article or video Tutorial to explain how to handle this problem, but AFAIK it hasn't done so.


    The last paragraph in this section of the old version of the WP article linked to in the preceding paragraph of this post contains DovidBenAvraham's speculation as to why the Retrospect Windows 12 User's Guide is over 600 pages long.  It also contains his speculation as to why Retrospect Windows 8 and above kept what he considers to be the pre-Retrospect-Mac-8 GUI and terminology.  Some of that GUI, such as non-resizable dialog boxes, may have been adapted to the limitations of Windows; we'll only know for sure if someone tries out a copy of Retrospect Mac 5 or 6.

  11. i need to upgrade to Retro 13 so I can see if this is fixed. I have installed Retro 14-Windows at one of my clients. I may have an opportunity to try it there.

    (No good deed goes unpunished - once you get it working reliably, no one ever upgrades again. ;-> )



    I'm getting a bit confused as to which Retrospect versions you are referring to.  I suspect you mean you need to upgrade to Retrospect Mac 13—which is one major release behind the latest—in order to see if this is fixed, and that you have installed Retrospect Windows 12—there won't be a Retrospect Windows 14 for two more major releases—at one of your clients.

  12. toshy, a further thought:


    In your scripts that get the -530 error when backing up the two non-startup disks on one client, what is the sequence in which the disks are supposed to be backed up—and in which the disks are backed up when you run one of the scripts manually?  Is it the startup disk first, followed by the internal disk and the other external disk?  Or is the startup disk last, preceded by the internal disk and the other external disk?


    If so, I wonder whether you are getting some variant of the software-caused -530 error I described in the sixth paragraph of post #4 in this thread.  This would be a "conceptual bug" involving automated updating of other software on the affected client machine overlapping with Retrospect script execution.  Think about whether you have recently installed additional software on the affected client machine.

  13. Using the Advanced Search capabilities for the Forums, and specifying "-1119" including the quotes, I found several threads that deal with this error.  As far as I understand the threads, the error seems to be caused by folders and/or files whose names were duplicated by Windows in the process of upgrading.


    The most recent applicable thread is here.  The OP was doing a Duplicate.  Post #2 describes how he solved the problem, and the first paragraph of post #3 contains an explanation by the very-knowledgeable Scillonian of what in Windows caused the folder name duplication.


    The only other useful thread is here.  The OP was doing a Restore.  Posts #2 and #4 contain an explanation by Mayoff on what in Windows caused the the file name duplication.  Posts #3 and #5 describe how the OP solved the problem.


    Ah yes, Windows is a lovely operating system.  I used it professionally (as an applications programmer supported by systems programmers, and mostly Windows 95) from 1999 to 2004.  I can't say I miss it much.


    Nevertheless, Retrospect Inc. should IMHO create a Knowledge Base article under here describing what Retrospect error -1119 really means.  To get them to do that, MingoPapa, you're going to have to create a Support Case for a documentation bug.  This dyspeptic post by me describes why and how to do that.  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.

    • Like 1

  14. A more-careful search using the Forums' Advanced Search feature revealed this thread.  It turns out that Retrospect Mac as late as version 12.5 could not see Avid ISIS volumes, but Retrospect Windows 10.5 could recognize them as network shares (although the OP in that thread said they were not supposed to be network shares)—which meant they had to be mounted by "... 'Volumes Database', ... click 'My Network...' then 'Advanced...' and enter the location of the share in the //<servername>/<sharename> or //<server.ip.address>/<sharename> format" per post #2 in this thread.  


    Post #3—by Mayoff—in the thread linked to in the first sentence of the preceding paragraph says that Retrospect Inc. was planning to add Avid ISIS support in the next release of Retrospect Mac (which would have been Retrospect Mac 13).  The "What's New" chapter in the Retrospect Mac 14 User's Guide, which is identical to the one in the Retrospect Windows 12 UG, implies that that plan slipped by one major release—which is BTW confirmed by the Retrospect Windows 12 Release Notes.  My educated guess is that, if you use the Avid utility referred to in the last paragraph of the KB article linked to in the first sentence of post #2 in this thread, you probably don't need to setup a network share for an Avid ISIS device in either Retrospect Windows or Retrospect Mac.  However my further educated guess is that you have to run the Avid utility on the "backup server" machine itself, so that the Retrospect Engine and Console can see the Avid ISIS device in order to incorporate it in scripts.


    Again, I bow to any further enlightenment from more-knowledgeable administrators.

  15. Retrospect Windows 11 added a number of features that were documented in the "What's New" chapter of the Retrospect Windows 11 User's Guide.  These include Performance-Optimized Grooming—which has tradeoffs vs. Storage-Optimized Grooming, "Seeding" for Cloud Backup, and Large Scale Recovery from Cloud Backup.


    Unfortunately the documentation for those features has disappeared from the Retrospect Windows 12 User's Guide, because the "What's New" chapter was entirely replaced without its prior contents having been moved to later chapters in the UG.  The documentation for basic adding/using/throttling Cloud Backup has also disappeared from the Retrospect Windows 12 User's Guide; however that documentation was incorporated at the end of several Knowledge Base articles grouped under here, and was also duplicated stand-alone into this Knowledge Base article.


    These features are still available in Retrospect Windows 12, but you'll have to follow the links in the preceding paragraphs to learn about them.

  16. Retrospect Mac 13 added a number of features that were documented in the "What's New" chapter of the Retrospect Mac 13 User's Guide.  These include Performance-Optimized Grooming—which has tradeoffs vs. Storage-Optimized Grooming, "Seeding" for Cloud Backup, and Large Scale Recovery from Cloud Backup.


    Unfortunately the documentation for those features has disappeared from the Retrospect Mac 14 User's Guide, because the "What's New" chapter was entirely replaced without its prior contents having been moved to later chapters in the UG.  The documentation for basic adding/using/throttling Cloud Backup has also disappeared from the Retrospect Macintosh 14 User's Guide; however that documentation was incorporated at the end of several Knowledge Base articles grouped under here, and was also duplicated stand-alone into this Knowledge Base article.


    These features are still available in Retrospect Mac 14, but you'll have to follow the links in the preceding paragraphs to learn about them.

  17. As to what Avid support does, see this Knowledge Base article.  It's not clear whether "the file system where Retrospect is running" means the file system of the Retrospect "backup server" itself, or whether it can also be the file system of a client that the "backup server" can see.  I'd appreciate it if someone who has past experience using Retrospect with Avid can enlighten us; I'm not sure whether what Retrospect Windows 12 can do with Avid is actually an improvement on what was available with previous versions.


    As to running an Archive script in Retrospect Windows 12 onto an LTFS Backup Set, Craigo5000 won't be able to do it; you can only Duplicate.  Read this post (and preceding posts in the same thread—which Craigo5000 started in October 2015) and follow the link to that Knowledge Base article in it (I don't want to repeat myself).

  18. Oops, according to this Knowledge Base article the LTFS support is only for Copy/Duplicate; it does not support Backup or Archive scripts.  I'm not sure this is actually an improvement on what was available previously in Retrospect for LTFS—see the last paragraph.   And JoTraGo discusses what was available previously in post #2 in this very thread.  The link to the Retrospect Blog article in my second sentence of this post is actually from post #4; JoTraGo meant to include that link as well in post #2, but it "didn't come through".

  19. See the section "Recreating a Catalog" starting on page 478 of the Retrospect Windows 12 User's Guide.  It says there "Retrospect can recreate a Catalog by reading the Backup Set media. Recreating may take a long time, depending on the amount of data in the Backup Set."  IMHO that means Retrospect is actually reading the data, so that—per any error messages in the log—should tell you if the files are OK.  However, I bow to anyone who actually knows more about this.


    P.S.: Changed Retrospect Windows 14 to Retrospect Windows 12 in first sentence; I'm a Retrospect Mac user, although the page number shown is the correct one for the Windows UG.

    • Like 1

  20. A second thought, toshy:  Down at the very bottom of the "What's New" for Retrospect Mac 14, the Other Enhancements say "Network Connectivity – Retrospect 12 for Windows and Retrospect 14 for Mac include clients that are more resilient to network hiccups and outages."


    When I was running tests for -530 Bug 1 at the request of Retrospect Support, they provided me with a trial version of Retrospect Mac 13.5—13.5.0(317)—a late build that contained networking bug fixes that Support wanted me to test on my problem.  I suspect that these were the same fixes that are incorporated in Retrospect Mac 14 as the Network Connectivity enhancement.  The trial client release didn't fix my -530 problem, but the fixes might work for your problem.  One easy test would be to upgrade the Client software on your problematic machine to the Retrospect Mac 14 Client, doing the usual Console-Client-Console dance for dropping and adding a client.  Another approach would be to start a Support Case—which I have been informed by Mayoff can be done for a bug even if you don't have Annual Support and Maintenance, and ask Support for a trial of the 13.5.0(317) release.


    P.S.: I would also suggest setting up "sacrificial script" versions of your two Backup scripts, as linked to in the last paragraph of post #4.  If you schedule these 10 minutes ahead of the real Backup scripts, they may fix your problem even if the Engine is not shut down between the operation of each script.  That would be consistent with the phenomenon you report in your second substantial paragraph of post #5.


    P.P.S.: toshy, you should have made post #5 in place of post #1.  If you don't give us all the information you can in your OP, we have to drag it out of you post by post.  Either that, or we have to make a WAG which—as in my post #4—may turn out to be wrong because of lack of information.  In the case of post #4, it took a lot of effort for me to write it.  It's not totally wasted effort, because it will help others if I can have an as-clear-as-possible explanation of -530 Bug 1 and -530 Bug 2 to link to.  However, I think my aggression at the end of the first paragraph of post #4 was justified, considering how little information you supplied in post #1.

  21. Sorry, toshy, but the aggression in my first paragraph was because I have trouble believing the situation you describe more fully in the first substantial paragraph in post #5 of this thread.  I suggest that you look again carefully at this Knowledge Base article.  The only thing I can imagine is that your two scripts backup the startup disk on that client first, and that the client then goes to sleep before the internal disk and another disk can be backed up.  However there may be some weirdness such that the client is accessible through the external SSD but not through the internal and external spinny disks.  I have no personal experience with any kind of SSDs.  Please post your screenshot in this thread.


    As for your second substantial paragraph in post #5, that corresponds more closely to my -530 experiences as described in post #4—in which I failed to mention that in both my separate -530 problems the script would also run perfectly if triggered manually after failing when run automatically via its schedule.  I'm wondering whether the Retrospect Engine is finding your problematic client "difficult to communicate with" even when the Engine has been running for a while before trying to backup that client.  I didn't say that my -530 Bug 1 is the only bug the Engine has, nor do I rule out other varieties of what I called -530 Bug 2.  Please post your other screenshot in this thread.