Jump to content

DavidHertzberg

Members
  • Content count

    1,120
  • Joined

  • Last visited

  • Days Won

    39

Posts posted by DavidHertzberg


  1. The automatically repeated updating notice, which continued even after I had done the update,  turned out to be from Adobe Flash Player Install Manager.app.  I deleted the install app.  I then reran the same tests early this morning.  I got a -519 error on the first test, but the second test ran fine.

     

    My guess is that, on my MBP, letting the computer go to sleep after 1 hour temporarily disables the Retrospect Client.  This may have something to do with my now having an ATEN CS782DP KVM switch, but I didn't have that switch in February.

     

     

    After disconnecting the ATEN CS782DP KeyboardVideoMouse switch from my MacBook Pro, repeated the same two tests early this morning.  Got exactly the same results: "Sun.-Fri. Backup" script got a -519 error (which would be a -530 error after #6080 fix) with the MBP having gone to sleep after one hour per revised System Preferences->Energy Saver options, but ran fine with the MBP awake.

     

    So—after eliminating oddities such as simultaneous Adobe updater messages—the results for Wake-on-LAN for my MBP seem to be: works fine when a Mac laptop client is put to sleep via a special keyboard combination on the laptop keyboardfails with a -519 error (which would be a -530 error after #6080 fix) when a Mac client automatically goes to sleep per System Preferences->Energy Saver optionsfails with a -519 error (which would be a -530 error after #6080 fix) when a Mac client is put to sleep via the Apple Menu

     

    To me that sounds as if presumably greater OS X involvement in the second and third cases is what causes Wake-on-LAN to fail on my MBP.  That may not apply to other peoples' Mac clients with their own installations of OS X.

     

    P.S.: Just noticed (on 18 September) a bug fix for Retrospect Mac 13.0.1 "Fixed issue where clients not found on network incorrectly reported as error -519 instead of -530 (#6080)"; put in parenthetical note after every mention of -519 in this post—no doubt you should mentally do the same for previous posts in this thread.


  2. Retrospect has for a number of years supported the WebDAV cloud interface.  However the Retrospect Inc. documentation is nearly non-existent, probably because methods of using the WebDAV interface differ so much from service to service.  A few weeks ago someone asked about using box.com in this thread on the Windows Professional forum, so I did a little searching and put together posts #6 and #7 there.  Post #6 may be helpful for services other than box.com.

     

    It does not appear that Amazon Cloud Drive by itself supports WebDAV.  Amazon of course has Amazon AWS, which Retrospect Mac 13 supports, but that—as I'm sure you realize—is more expensive than Amazon Cloud.  If you do a little searching with a web search engine such as Google, you will find add-on products that say they add a WebDAV interface to Amazon Cloud.  Your Mileage May Vary (spelled-out because the second sentence of your OP makes it seem that English is not your native language).

     

    Good luck, and please reply with what you discover.


  3. Received this reply to my case's Additional Notes—which were the contents of my early-morning-15-September post above—from Retrospect Support this morning (15 September):

     

    "Agent Response: 

    We do have open bugs for users getting -559 and 505 errors at random times during backup, but for most users they are not related to Wake on LAN operations.  I will pass your experience onto our engineers so it is included in the bug report for those errors."

     

    I'm going to retry the same tests overnight, but with my ATEN CS782DP KeyboardMouseVideo switch disconnected from my MacBook Pro—to see if that makes any difference.


  4. Last night in my MacBook Pro's System Preferences->Energy  Saver, I changed both Computer Sleep and Display Sleep to 1 hour, and left it running. Early this morning, after verifying by there being no longer any light under the KB that the MBP had gone to sleep, I booted my Mac Pro "backup server".  The scheduled "Sun.-Fri. Backup" got the the following log:

     

    Normal backup using Sun.-Fri. Backup at 9/14/16, 3:36:55 AM

        To Backup Set Media Set White...

       

        9/14/16 3:37:17 AM: Connected to David’s MacBook Pro

        *  Resolved container David’s MacBook Pro to 1 volumes:

        Macintosh HD on David’s MacBook Pro

        -  9/14/16 3:36:55 AM: Copying Macintosh HD on David’s MacBook Pro

        Using Instant Scan

        9/14/16 3:38:17 AM: Found: 626898 files, 150652 folders, 46.6 GB

        9/14/16 3:39:21 AM: Finished matching

        soccRecv: recv failed, error 60

        9/14/16 3:39:46 AM: Copying: 1760 files (3.6 GB) and 0 hard links

        !Trouble reading files, error -559 (network connection timeout)

        9/14/16 3:39:53 AM: Execution incomplete

        ....

     

    I then pressed the Shift key on the attached USB KB to wake up the MBP, and manually ran "Sun.-Fri. Backup" again to get the following log:

     

    Normal backup using Sun.-Fri. Backup at 9/14/16, 3:44:32 AM

        To Backup Set Media Set White...

        Can't access backup client David’s MacBook Pro, error -505 (backup client reserved)

        9/14/16 3:44:54 AM: Execution incomplete

     

    I noticed that there was an automatically repeated updating notice for Adobe Reader (after I had already updated it) on the MBP's monitor.  

     

    ....

     

    I will reboot my MBP now to see if that gets rid of the Adobe message—which has caused -505 trouble in the past. I will then retry the same test overnight.

     

     

    The automatically repeated updating notice, which continued even after I had done the update,  turned out to be from Adobe Flash Player Install Manager.app.  I deleted the install app.  I then reran the same tests early this morning.  I got a -519 error on the first test, but the second test ran fine.

     

    My guess is that, on my MBP, letting the computer go to sleep after 1 hour temporarily disables the Retrospect Client.  This may have something to do with my now having an ATEN CS782DP KVM switch, but I didn't have that switch in February.


  5. Since this is a thread about the cost of Retrospect cloud backup, and since Mayoff may read it, I'll take the liberty of making one post justifying a cost-saving suggestion I posted back in March 2016.  I have now made the suggestion official with a thread in Product Suggestions—Mac OS X, but IME nobody at Retrospect Inc. pays any attention to that forum.  However to avoid choppiness here I won't duplicate links to other threads that are in my linked-to post.

     

    Trigger warning: Reading the next four paragraphs of this post will undoubtedly cause you to at least slap your forehead, when you consider that Retrospect Inc. ignored that suggestion in the Mac 13.5/Windows 11.5 update.

     

    jethro started a thread on March 2nd—one day after Retrospect Mac 13.0 was released—saying "we'd love to augment our existing backup with maybe a weekly data transfer to a cloud storage as a backup of our onsite backup (we'd want our local HD backup to still be primary and work as-is).  .... The total space used for ALL backups (which goes back 4 years now) is about 5TB, spread across 4 hard drives. .... We might be fine transferring either just current data forward, or maybe everything back to a year or so ago ...."  I responded on March 8th with a post setting out a step-by-step procedure by which he could do that.  That thread has become wildly popular, which presumably means that many people want to do the same kind of cloud backup.  

     

    My procedure assumed jethro would do "seeding" of his existing on-site backup data.  By the time WKTimes started a similar thread on September 7th, it had become obvious that "seeding" was now only available—directly or indirectly—from two cloud providers, and costs US$230 and up.  Therefore I rewrote the procedure assuming "seeding" would be replaced by a lengthy Internet upload to the cloud account.  WKTimes only wants to permanently maintain the last two weeks of backups in the cloud, but I told him Retrospect can't groom below a one-month minimum.

     

    The key point is that the first two steps of both versions of my procedure are:

    1) Create a new local Disk or Cloud-with-Disk-local-member Media Set [Disk for non-"seeding", Cloud-with-Disk-local-member for "seeding], specifying "Groom to Retrospect defined policy" with Months to keep = n [n = 12 for jethro, n = 1 for WKTimes].   Choose Performance-optimized grooming.  This would have to be as big as your regular backup Media Set.

    2) Run a Copy Media Set script to copy your regular Media Set to the new local Disk Media Set, with the option Match Source Media Set to destination Media Set unchecked and the option Copy Backups checked.  You will have to Groom the new Media Set afterwards.

     

    That means that jethro would have to buy a 6TB disk drive to be the destination of the Copy Media Set—even though he would immediately be doing grooming to cut the contents down to less than 1TB.  That would have cost him more than US$300 (it's now down to $200 as of September 15th).  WKTimes would also have to buy disk(s) equal in capacity to his regular backup, which "is 'very large' and partially off-site"—even though he would immediately be doing grooming to cut the contents down to the last four weeks.  

     

    How about that excess expense for cloud backup?


  6. Received this reply to my case from Retrospect Support this morning (13 September):

     

    "Agent Response: 

    The Wake on LAN feature is tested with every Retrospect product release. Retrospect 11/13 was released in March and we have really not had any significant reports of trouble with the feature. In fact, I think you are probably the only customer who has been directly asking support about it in the last few months (outside of how to turn the options on). When testing sleep, we typically test after the machine has automatically gone to sleep, since that is what the majority of customers experience. 

     

    ....

    ...."

     

    I have both those options on.  I am using Retrospect Mac 12.5, with version 12.0.2 (116) of the Retrospect Client on my MacBook Pro; I mentioned both those version numbers in my Support case—which is pretty much a copy of my posts in this thread.

     

    The only thing I can speculate at this point is that a machine automatically going to sleep might not have the same effect as putting it to Sleep on the Apple menu.  In my MBP's System Preferences->Energy  Saver, I have both Computer Sleep and Display Sleep set to Never;  I also have Wake for Network Access checkmarked in that same Preferences pane.

     

     

    Last night in my MacBook Pro's System Preferences->Energy  Saver, I changed both Computer Sleep and Display Sleep to 1 hour, and left it running. Early this morning, after verifying by there being no longer any light under the KB that the MBP had gone to sleep, I booted my Mac Pro "backup server".  The scheduled "Sun.-Fri. Backup" got the the following log:

     

    Normal backup using Sun.-Fri. Backup at 9/14/16, 3:36:55 AM

        To Backup Set Media Set White...

       

        9/14/16 3:37:17 AM: Connected to David’s MacBook Pro

        *  Resolved container David’s MacBook Pro to 1 volumes:

        Macintosh HD on David’s MacBook Pro

        -  9/14/16 3:36:55 AM: Copying Macintosh HD on David’s MacBook Pro

        Using Instant Scan

        9/14/16 3:38:17 AM: Found: 626898 files, 150652 folders, 46.6 GB

        9/14/16 3:39:21 AM: Finished matching

        soccRecv: recv failed, error 60

        9/14/16 3:39:46 AM: Copying: 1760 files (3.6 GB) and 0 hard links

        !Trouble reading files, error -559 (network connection timeout)

        9/14/16 3:39:53 AM: Execution incomplete

        Remaining: 1,760 files, 3.6 GB

        Completed: 0 files, 0 B

        Performance: 0 MB/minute

        Duration: 00:02:58 (00:02:49 idle/loading/preparing)

     

    I then pressed the Shift key on the attached USB KB to wake up the MBP, and manually ran "Sun.-Fri. Backup" again to get the following log:

     

    Normal backup using Sun.-Fri. Backup at 9/14/16, 3:44:32 AM

        To Backup Set Media Set White...

        Can't access backup client David’s MacBook Pro, error -505 (backup client reserved)

        9/14/16 3:44:54 AM: Execution incomplete

     

    I noticed that there was an automatically repeated updating notice for Adobe Reader (after I had already updated it) on the MBP's monitor.  

     

    I then stopped-started Retrospect Client on the MBP, and manually ran "Sun.-Fri. Backup" again.  This time it ran fine.

     

    I will reboot my MBP now to see if that gets rid of the Adobe message—which has caused -505 trouble in the past. I will then retry the same test overnight.


  7. Received this reply to my case from Retrospect Support this morning (13 September):

     

    "Agent Response: 

    The Wake on LAN feature is tested with every Retrospect product release. Retrospect 11/13 was released in March and we have really not had any significant reports of trouble with the feature. In fact, I think you are probably the only customer who has been directly asking support about it in the last few months (outside of how to turn the options on). When testing sleep, we typically test after the machine has automatically gone to sleep, since that is what the majority of customers experience. 

    Wake on LAN is supported on Macintosh and Windows with normal backup scripts and proactive backup scripts.  The option must be turned on in the client properties screen and turned on inside the script options. 

    Wake on LAN is not supported with the 6.3 client version.
    "

     

    I have both those options on.  I am using Retrospect Mac 12.5, with version 12.0.2 (116) of the Retrospect Client on my MacBook Pro; I mentioned both those version numbers in my Support case—which is pretty much a copy of my posts in this thread.

     

    The only thing I can speculate at this point is that a machine automatically going to sleep might not have the same effect as putting it to Sleep on the Apple menu.  In my MBP's System Preferences->Energy  Saver, I have both Computer Sleep and Display Sleep set to Never;  I also have Wake for Network Access checkmarked in that same Preferences pane.


  8. This is a rewrite of paragraphs 2, 4, and 5 of the preceding post for the "if you can't do 'seeding'" case, based on merging them into a copy of part C) of this post.  You would want to do the following things:

     

    1)  Create a new local Disk Media Set, specifying "Groom to Retrospect defined policy" with  Months to keep = 1.   Choose Performance-optimized grooming.  This would have to be as big as your regular backup Media Set, unless and until—as I have newly officially suggestedRetrospect Inc. implements an age subset of the "Groom to Retrospect defined policy" option in Copy Media Set with a Disk (not just Cloud) Media Set as destination for Retrospect Mac Ver. 13.5.  It would be nice if there were a Weeks to keep alternative you could set to 2, but there isn't.

     

    2)  Run a Copy Media Set script to copy your regular Media Set to the new local Disk Media Set, with the option Match Source Media Set to destination Media Set unchecked and the option Copy Backups checked  The resultant size—after grooming—should give you a fairly good estimate of the amount of storage you would need in the cloud; get/put requests I don't know about.  If the size of the new Cloud Media Set local disk member is the same as your regular Media set—which it will be except in the unlikely case that Retrospect does the multi-cycling copying-grooming I suggested it might do in sentences 3 through 5 of the first paragraph of this post, you will have to Groom the new Media Set afterwards—or else use a Rule in the Copy Media Set to do the equivalent of grooming.

     

    3)  Meanwhile make the arrangements to setup your cloud account, and keep the account  parameters handy.

     

    4) Create a new Cloud Media Set with a Cloud member, specifying 'Groom to Retrospect defined policy' with Months to keep = 1 and specifying Performance-optimized grooming, and type in the account parameters you have kept handy.

     

    5) Run a Copy Media Set script to copy your new groomed local Disk Media Set to the new Cloud Media Set, with the option Match Source Media Set to destination Media Set unchecked and the option Copy Backups checked.  Check No Verification.  Actually running this script may take hours or days—which is why "seeding" would have been preferable, but thanks to the glories of using the "backup server" as a "second-level client" you can run it over the weekend—or in a separate thread unless you have Retrospect Desktop Edition.  

     

    6) Setup a new Copy Backup script to copy from your regular Media Set to the new Cloud media set, this time with the option Match Source Media Set to destination Media Set checked.  Check No Verification.  Schedule the new Copy Backup daily, at whatever time you want.

     

    7) Schedule a Groom of the new Cloud Media Set to run once every 2 months.

    P.S: Changed my answer to step 2 to say that Copy Media Set can use a Rule as an alternative to grooming per this post.


  9. It sounds to me as if you have some variant of the same requirements that jethro had in this thread.  I would suggest that you consider modifying the procedures in part C) of this post in that thread.

     

    The first modification you would have to make to the linked-to procedures is in step C1), where you would have to change Months to keep = 1.  It would be nice if there were a Weeks to keep alternative you could set to 2, but there isn't.  Also, in step C1) choose Performance-optimized grooming if you have an option; it will AFAIK be the only option if you are doing "seeding".

     

    Whether you would have to make a second modification depends on whether your cloud provider has a "seeding" service, such as I assumed in steps C1) through C5).  Retrospect Mac 13 has provided a neat feature for "seeding" that I assumed back in March 2016 would be used, but I have since learned that only two cloud providers offer any version of "seeding".  Amazon AWS offers "seeding" via a beefed-up large-capacity Snowball drive that they lend to you, but that costs $200 for a 50TB drive plus $30 per TB "seeded".  Iron Mountain offers a "seeding" service for Google Cloud, but it appears that their service involves their doing a high-speed Internet upload to Google of the data from disks/tapes you send to Iron Mountain—and it almost certainly ain't cheap.  Other than that, it appears that no other cloud provider has a "seeding" service.  Of course you could setup Basho Riak S2 on a dedicated server per D) and do your own "seeding", but if you were doing that I assume you would have mentioned it.  If you can live without "seeding", you might consider using DreamHost with Retrospect Inc.'s special deal, under which Cloud storage would only cost you $20/month/TB instead of $30/month/TB with Amazon or Google.

     

    Let's assume that you can't do "seeding", so that you would have to modify steps C1) through C6) in the linked-to procedures.  First, do the modification to step C1) in the second paragraph of this post.  Second, in steps C1) and C2), replace "Cloud Media Set" with "new local Disk Media Set".  This would have to be as big as your regular backup Media Set, unless and until (as I have newly officially suggested) Retrospect Inc. implements an age subset of the "Groom to Retrospect defined policy" option in Copy Media Set with a Disk (not just Cloud) Media Set as destination for Retrospect Mac Ver. 13.5—or else you use a Rule in the Copy Media Set to do the equivalent of grooming..  Third, in step C2) (unless and until you are using a forthcoming Retrospect Mac 13.5 with my suggested feature) you will definitely have to Groom the new Media Set afterwards—or else use a Rule in the Copy Media Set to do the equivalent of grooming.  Fourth, in step C3) omit the drive-shipping operation.  Fifth, in step C4) replace everything prior to typing in the account parameters with "Create a new Cloud Media Set with a Cloud member, specifying 'Groom to Retrospect defined policy' with Months to keep = 1 and specifying Performance-optimized grooming".  Sixth, replace step C5) with "Run a Copy Media Set script to copy your new groomed local Disk Media Set to the new Cloud Media Set, with the option Match Source Media Set to destination Media Set unchecked and the option Copy Backups checked.  Check No Verification."   Actually running this script may take hours or days—which is why "seeding" would have been preferable, but thanks to the glories of using the "backup server" as a "second-level client" you can run it over the weekend—or in a separate thread unless you have Retrospect Desktop Edition.  Seventh, in step C6) replace weekly with daily.  

     

    Finally, whether or not you can do "seeding", add a new step C7) that says to schedule a Groom script for the new Cloud Media Set to run once every two months.

     

    Disclaimer: I've never done any of the above stuff; all I did was to read the Mac User's Guide and look at a couple of Tutorials.

     

    P.S.: Lowered pricing for Amazon AWS Snowball "seeding".  Moved step C7) to separate paragraph, indicating it must be done whether or not you do "seeding". 

     

    P.P.S.: Corrected step C7); you can schedule a Groom script to run less often than once a month.

     

    P.P.P.S: Added options and No Verification to step C5); changed step C6) to run daily.

    P.P.P.P.S: Changed my answer to step C2 to say that Copy Media Set can use a Rule as an alternative to grooming per this post.


  10. It just occurred to me that Magic Packet might not just be a Retrospect, or even Mac OS X, term.  So I did a Google search, and found it in the Wikipedia article on Wake-on-LAN.  Since that section of the article mentions the "target computer's 48-bit MAC [Media Access Control] address", it reminded me that both my client computers have static DHCP addresses set on the router—done at the direction of A. of Retrospect Support back in July 2015 to make sure the "backup server" can find them (this is not mentioned in the Retrospect Mac 13 User's Guide, so I mention that in any post on these forums where it seems appropriate).

     

    That in turn reminded me that I had done a Sources->Locate immediately after both of the first two cases described in the first paragraph of post#7 in this thread.  In both cases, put to sleep via the Apple Menu and put to sleep via a special keyboard combination on the laptop keyboard, Locate failed.  I did Locate after the tests because, when I ran the test for the second case first—expecting it to fail, it unexpectedly succeeded (I then ran Locate after the test for the first case, because my experience has shown that running Locate before a script usually causes it to succeed when it would otherwise fail with a -530 error.) 

     

    Thinking of this just now caused me to wonder if some setting in my Internet-facing router might inhibit Magic Packets, thus inhibiting Retrospect Wake-from-LAN.  I do not have any software firewalls on any of my LAN computers, nor do I have an internal router on my LAN.


  11. Random -505 errors on clients is an issue we are investigating. In this case, it could have been a timing issue between when the machine woke up and when the client started and bound itself to the network adapter. Most users will not get that error.

     

    The Wake on LAN works by Retrospect sending a magic packet to the client machine. The Magic Packet should then wake the machine and allow a backup.

     

     

    I'd love for not-Waking-on-LAN to be a peculiarity of my MacBook Pro hardware and/or its OS.  However color me sceptical.

     

    Mayoff, the key word for me in "The Magic Packet should then wake the machine and allow a backup" is should.  How recently has Retrospect Inc. tested that it does do this?  On what versions of Mac OS X?  With what versions of client hardware?  With scheduled scripts or only with proactive scripts?  Were the clients put to sleep via the Apple Menu, or only from the keyboard?

     

    Note that Apple itself has gotten sloppy with testing recently, which is why I have never upgraded either of my two modern Macs to OS X 10.11 El Capitan.  And Apple has a lot more money than Retrospect Inc..

     

    And what of Retrospect Windows, as discussed in my first paragraph of post #5 in this thread?  Is a Retrospect Windows 11 "backup server" still incapable of sending a Magic Packet to an OS X client?

     

    Finally, for completeness, how about my Digital Audio G4 (mentioned in the last paragraph of post #7, but whose test is linked-to in my fourth paragraph in post #5 ) booted under OS X 10.3?  Obviously it runs the legacy Mac PowerPC 6.3.029 Retrospect Client.  Is that Client incapable of acting on a Magic Packet, because Apple's last PowerPC Mac came out 3 years before Retrospect Mac 8?


  12. The plot thickens slightly.  Just a few minutes ago I put my MacBook Pro to sleep using the special keyboard combination on the laptop keyboard, then booted my Mac Pro "backup server" (Retrospect automatically starts).  The "Sun.Fri. Backup" script got a -505 (backup client reserved) error.  I pressed Shift on the attached USB keyboard to awaken the MBP, logged in, and stopped-started the Retrospect Client—which IME is slightly faster than rebooting the MBP to get rid of a -505.  I then manually started the "Sun.Fri. Backup" script, which ran OK.

     

    FWIW I have occasionally noticed that, when I put my MacBook Pro to sleep using the special keyboard combination on the laptop keyboard, the MBP later turns out to be awake.

     

    The MBP is an Early 2011 MacBook Pro.  Software is per the preceding post.


  13. Wake on Lan works for Proactive backup and traditional backup scripts. If it isn't working for you, please contact support directly. It is supported with Macintosh and Windows clients.

     

     

    As a result of tests made this afternoon, I have resolved this problem—which has bedeviled the Retrospect community for years—into three different basic cases for scheduled scripts.  In the first case, when a Mac client is put to sleep via the Apple Menu, Wake-On-LAN fails with a -519 error.   In the second case, when a Mac laptop client is put to sleep via a special keyboard combination on the laptop keyboard, Wake-On-LAN works.  In the third case, when a Mac laptop client is put to sleep via the same special keyboard combination on an attached keyboard, the script  goes into a Retry loop until it fails with a -559 connection error.

     

    The special keyboard combination is Shift-Control-PowerButton or Shift-Control-MediaEject.  To understand how I came to know about and be using this combination, see the fourth and sixth paragraphs of this post in the Ars Technica Other Hardware forum.  To understand the hardware problem behind it, follow the link in the first paragraph in the linked-to post—which is in a thread that so far mostly describes my experiences with ATEN's CS782DP KeyboardVideoMouse switch.  I was putting my MacBook Pro to sleep via the Apple Menu until early May, when I started using the special keyboard combination; that explains this bug report in mid-February.  Note that I had updated the Retrospect Client on my Macbook Pro from 12.0.2 (116) to 12.5.0.111 just before running the test described in the bug report, which may explain why I got -535 errors instead of -519 errors on the February test.

     

    I am running Retrospect Mac 12.5 on my Mac Pro "backup server", but I reverted to version 12.0.2 (116) of the Retrospect Client on my MBP to try to avoid -530 errors on scheduled backups.  Both my MBP and my Mac Pro are booting OS X 10.10.5.

     

    Since I don't use proactive scripts, I can't speak definitely as to whether and under what circumstances they work with Wake-on-LAN.  However I can easily imagine a user bringing a laptop to the office already put to sleep with the special combination on its own keyboard, cabling the laptop to the office LAN, and having a proactive script work to successfully back it up.

     
    From the cases described in the first paragraph above, the client Wake-on-LAN problem sounds like an interaction between the Retrospect Mac Client software and Mac OS X 10.  Note that on the February test of my "Sat. Backup" Recycle Media Set script, with both my MBP and my Digital Audio G4 (which boots OS X 10.3.9) put to sleep via the Apple Menu, both the MBP and the G4 got -535 errors.

  14. Just to clear up, for anyone who reads this thread in the future, the confusion that exasperated ProFromGrover in his original post:

     

    Retrospect Inc. evidently now agrees with the conclusion that ProFromGrover expresses two posts up from this—that an RDX cartridge should always be defined as a Disk rather than a Removable Disk.  As pointed out by Scillonian in this post in a later thread, Retrospect Windows 11 has changed the option texts in the Create New Backup Set dialog; "note that RDX devices have been moved to Disk from Removable Disk". Retrospect Inc. also created the video linked-to in the OP of this thread one day before Retrospect Windows 11 was released; its evident purpose is to emphasize that same conclusion, particularly for users of previous versions of Retrospect Windows (as ProFromGrover evidently was)—in which the texts for the Create New Backup Set dialog still show RDX under Removable Disk.

     

    A summary of the discussion elsewhere in the thread I have linked to in the paragraph above revolves around the fact that the Removable Disk device type was created for drives that used "super-floppy" (AKA "random-access tape") media.  AFAICT all such drives have not been manufactured since about 2009, but Mayoff of Retrospect Inc. Support says "A large number of customers use Removable Disk Backup Sets and have existing removable disk backup sets."  So Retrospect Inc. fears "a backlash from every user who utilizes that feature", and therefore will not eliminate the Removable Disk device type from Retrospect Windows—even though they eliminated it in 2009 from Retrospect Mac.

     

    RDX drives were introduced in 2004, but they are not "super-floppy" devices.  Instead, as Scillonian says in his first post in this thread, "An RDX cartridge is a SATA hard disk in a standardised drop resistant enclosure that works with a standardised dock. If it is an external USB connected dock it would be no different to connecting a normal USB hard disk."  RDX cartridges are no longer any more drop resistant than ordinary 2.5-inch hard drives—all of which are now built with "ramp loading" or the equivalent, but the standardized "dock" makes them pop-in/pop-out like tape cartridges that older users are familiar with, and the cartridges' SATA connection will supposedly mean that they can be read many years from now inserted into a new-version "dock" that will connect to a computer with whatever cabling is by then the standard.  IMHO Retrospect Inc. should never have described RDX as a Removable Disk device type, but they did and are now stuck with the support consequences.

     

    Whatever you do, don't define a USB thumb drive as a Removable Disk—as Mayoff says can be done.


  15. icnvrs3, I'm going to make an educated guess about you, based on what you've written.  I think you've stumbled into an existing installation of Retrospect Mac (you haven't really said what version—does "Retrospect for Mac OS !0" mean Retrospect Mac 10 or Retrospect for Mac under OS X 10?), having prior experience only with Time Machine.  You assume that, like Time Machine (which I've never used because of unsuitability for my needs), you can muddle along simply by using the User Interface in the Retrospect Console app.  Well you're wrong in your assumption; Retrospect Mac was first introduced in 1985, when Steve Jobs was just about to be fired by Apple because the Mac was initially a sales flop, and has grown over the years to be vastly more sophisticated than Time Machine.  You're going to have to spend an hour or so reading portions of the appropriate Retrospect Mac User's Guide, as linked to in my previous post.

     

    This post in the Ars Technica Mac forum will tell you what I had to  do to get Retrospect Mac 12.0 doing what I wanted it to do for my installation, after having not used it for 5 years.  It says it took me 10.5 hours, but—if you follow my link in the "Sources" paragraph of that post and read the whole linked-to post—you can cut that to 5.5 hours.  You can probably forget about opening port 497; that turns out not to be necessary if you turn off the software firewalls on your LAN computers—leaving the firewalling to be done by your Internet router—and don't have a router within your LAN.

     

    Once you've done that, post your questions in the "Retrospect 9 or higher for Macintosh" forum, not in this forum.  We won't be able to help you unless you include your log in your post: Find your problematic execution of Retrospect by clicking Activities in the sidebar and scrolling down the List view, click the Log (as opposed to Summary) button above the detail for that execution, choose Select All and then Copy from the Edit menu, and then choose Paste from the Edit menu to copy the contents of the log for that execution into your post—editing out any log information you don't think we should see.

     

    BTW Time Machine, at least prior to Mac OS X 10.11 (El Capitan), may not consistently backup your machine(s).  I do not, however, know whether running it at the same time Retrospect is scheduled would interfere with or prevent a Retrospect script from running—but I doubt it.


  16. All references in this post are to the Retrospect Mac 13 User's Guide, whose .PDF you can read or download here (if you are using Retrospect Mac 10, rather than running under OS X 10, you can read or download that UG under here):

     

    First, on page 27, "Storage Deviceshows a list of the storage devices attached to the Retrospect server.  This list does not display hard disks, removable disks [this is a UG infiltration from Retrospect Windows—Retrospect Mac 8 and above has eliminated the Removable Disk type], or NAS volumes (those are shown under Sources); rather, it includes hardware devices such as optical and tape drives and libraries."

     
     Second, on page 40, "Media Sets are the destinations for files and folders that you back up. A Media Set consists of one or more disks, tapes, optical discs, or a single file. Individual pieces of media (for example, tapes, optical discs, or hard disks) are members of a Media Set."  If you haven't read all of Chapter 3: Fundamentals in the UG, you'd be well advised to do so.  Otherwise you're going to get a post from me that says "RTFM".  An alternative would be to look at all the appropriate Mac-labeled tutorial videos here, but—being an old fuddy-duddy—I find it easier to get information from manuals.
     
    Third, this recent post from me, in a thread on the "Retrospect 9 or higher for Macintosh" forum, repeats the fact that IME Retrospect Mac can't wake sleeping Macs to run scheduled scripts.  The jury is still out on waking sleeping Macs for proactive scripts, because I don't run those and we haven't heard back from Mayoff—the head of Retrospect Support.  As discussed in that post, the Mac User's Guide contains information on Wake-on-LAN that seems to be at least obsolete (and that's based on the more charitable of my two hypotheses).
     
    Good luck!

  17. See my bug report here.  My report was for scheduled scripts, but it references an item which is now on page 329 in the Retrospect Windows 11 User's Guide.  Maybe whoever wrote that manual knew something that never made it into the Retrospect Mac User's Guide—namely an admission that Enable Wake-on-LAN does not in fact work even for proactive backups (which I don't use).

     

    The "item which is now on page 329 in the Retrospect Windows 11 User's Guide" was on page 328 (right-hand column) in the Retrospect Windows 7.5 User's Guide.  It seems that Enable Wake-on-LAN was known not to work for Macs at least as early as 2011.  OTOH I happen to have saved a Retro-Talk e-mail announcing the beta of Retrospect Mac 8 in early 2009.  Some of the new features it announces are "Advanced network client support with support for multiple network interfaces and a wake-on-LAN feature [my emphasis] to wake sleeping computers for backup, reducing overall energy expenditure".

     

    Here's one hypothesis: Wake-on-LAN never worked for Macs, in the Retrospect Mac 8 client or thereafter, but Retrospect Inc. left the option in the app and in the Mac User's Guide in hopes that they could fix it in a subsequent release.  I have recapped the history of Retrospect Mac 8 in the first 4 sentences of the third paragraph in this post; I will not repeat that history here to avoid causing pain to certain readers.

     

    Here's another hypothesis: Wake-on-LAN did work for Macs in the Retrospect Mac 8 client, but it stopped working by 2011 because of Apple changes to Mac OS X.  At that point Retrospect Inc. didn't have the heart to remove the option either from the app or from the Mac User's Guide.

     

    Either way it didn't work for me in a test on a scheduled script in February 2016.

     

    The -559 error is not related to Wake on LAN in any way. If the client was sleeping, you would see a 530 error or other error.

     

    The -559 error is a client connection issue that we can help you with by contacting support directly.

     

     

    You're right for scheduled scripts, Mayoff; my test in February 2016 produced -535 errors for my two sleeping clients.

     

    However, since I don't do proactive backup, I don't know what would happen if one connected a sleeping client to a LAN.  Maybe it would get a -559 error from a proactive script even if the connection were totally OK.

     

    So, Mayoff, it's time for you to come clean.  Does Wake-on-LAN work to backup a sleeping Mac client for Mac proactive scripts?  Feel free to run a test.


  18. See my bug report here.  My report was for scheduled scripts, but it references an item which is now on page 329 in the Retrospect Windows 11 User's Guide.  Maybe whoever wrote that manual knew something that never made it into the Retrospect Mac User's Guide—namely an admission that Enable Wake-on-LAN does not in fact work even for proactive backups (which I don't use).


  19. That's interesting.  Back before my -530 problem with my "Sun.-Fri. Backup" No Media Action script miraculously cured itself on 12 June, I had found that I didn't get a -530 error if I booted my Mac Pro "backup server" at least 15 minutes before the 3 a.m. time scheduled for the script—and then booted my MacBook Pro client before 3 a.m..  See especially the P.P.P.P.S. in this post, but also see mentions in previous and subsequent posts in the same thread.


  20. If neither of the two suggestions in the preceding post work, here's a specifically box.com approach—first three paragraphs courtesy of the University of Maryland Baltimore County—that it looks like you can adapt:  

     

    Go to this wiki.umbc.edu page in your web browser.

     

    First, use a different page or tab on your web browser to execute the steps immediately under Tell Me on the wiki.umbc.edu web page to create an external password.  In place of entering "box.umbc.edu" in step 1, follow the logon procedure you use for your box.com account.  Before executing step 2, create a special folder name at the top level of your box.com account specifically for Retrospect backups, e.g. "RetroCloud" (no quotes).  Then follow the procedure in steps 2 through 4.

     

    Next, use Windows Explorer to follow the procedures in the Windows section of the wiki.umbc.edu page.  In step 6, for the "Internet or network address:" field, type in e.g. https://dav.box.com/dav/RetroCloud.  In step 7, in place of the full UMBC email address type in whatever email address you use in your dropbox.com logon, check the box that says “Remember my credentials”, and click OK.  In step 8, type in e.g. "RetroCloud" (no quotes) as the name for the location.  You should end up a with a new location under Computer or ThisPC with the name you just assigned, e.g. "RetroCloud" (no quotes).  This location supposedly should act like a shared Volume.

     

    Finally—here's my adaption, in Retrospect Windows try using e.g. "RetroCloud" (no quotes) as a device under Computer or ThisPC to create one or more Backup Sets per page 400 of the Retrospect Windows 11 User's Guide.  If this works, you should be able to create scripts using those Backup Sets.

     

    I have no idea if this will work, and do not have a box.com account or a Windows machine, so please report back with a new post in this thread.


  21. Note that I've switched the sequence of this and the following posts, and switched the sequence of the two methods within this post. First try one of these two methods as found in the Retrospect Forums search:


     


    1) This is what comes closest to an official best practice: The "Support for cloud storage" New Feature note for Retrospect Windows 8, on page 638 at the back of the Retrospect Windows 11 User's Guide, says "Retrospect 8 supports backing up to Internet-connected (cloud) storage using the WebDAV protocol. Before a WebDAV volume can be used in a disk Backup set or as a source for backups, it must first be set up by going to Configure > Volumes, as described in the Retrospect User’s Guide (see “To add a network volume to the volumes database ....  ). Use http or https when entering the UNC path.".  The place the note says to see to is now My Network Places on page 446 of the Retrospect Windows 11 User's Guide.  The location thus created supposedly should act like a shared Volume; you may want to restrict the location to a special top-level folder within your box.com account created as per the first substantial paragraph in the next post.


     


    2) This was posted on the Retrospect Forums before the Retrospect Windows 8 User's Guide was posted.  Nobody complained that it didn't work: It's this post; note that it is for Retrospect Windows 8.  This supposedly directly creates a Backup Set; you may want to restrict the WebDAV location to a special top-level folder within your box.com account created as per the first substantial paragraph in the next post.


     


    If you try either of these suggestions,  please let us know whether it works via a new post on this thread.



  22. As far as the allowable e-mail notifications are concerned, see the bottom paragraphs of this post by Scillonian.  Bear in mind that infinity is working with Retrospect Windows 8, which is old enough that the capabilities may be different.

     

    And for Heaven's sake, infinity, every morning while you are brushing your hair say 10 times "I live in the 21st Century and I work with RDX drives—not tapes" :rolleyes:.


  23. >Why didn't the Retrospect Inc. engineers simply delete the Removable Disk option from the dialog?

     

    A large number of customers use Removable Disk Backup Sets and have existing removable disk backup sets. This backup set format is not limited to only the media types listed in the dialog box. We have never removed a backup set type from the product (with one small exception). Doing that would result in a backlash from every user who utilizes that feature.

     

    In some cases, even USB thumb drives can even be used with the Removable Disk Backup Set.

     

    Retrospect Inc. has a continuing problem because users think of RDX devices—under whatever brand name—as "super-floppy" drives AKA "random-access tape" drives, as infinity evidently did (s/he says so in his/her second post).  I simply was curious enough to Google "RD1000" and find that it is the Dell brand name for RDX.  Once I saw that, I remembered ProFromGrover's concluding post in his previous thread, in which he says RDX devices should be defined as Disk drives—not Removable Disk drives.  I also knew, from having seriously considered replacing my DAT tape drive with an RDX "dock" and cartridges when I re-activated my use of Retrospect 14 months ago, that RDX cartridges are not "super-floppy" cartridges but full-fledged modern 2.5-inch disk drives.  

     

    However both the devices still mentioned in the text of Removable Disk option in the Retrospect Windows 11 Create New Backup Set dialog, as well as "Zip, REV, SuperDisk, DVD-RAM, and MO" listed on page 48 of the Retrospect Windows 11 User's Guide, are "super-floppy" devices; they are—including  Quantum GoVault—no longer manufactured.  If "a large number of customers use Removable Disk Backup Sets and have existing removable disk backup sets", then I pity them and I pity Retrospect Inc. for having to support them.  But IMHO Retrospect Inc. Support should—in its own interest—make very sure that the probably larger number of customers now using or likely to use RDX devices do not follow in their footsteps.

     

    One step Support could take would be to be more emphatic in Mayoff's "RDX Backup Windows" video.  It should IMHO be revised to explicitly say "Whatever you do, don't define define an RDX device as a Removable Disk."  Probably this revision could be done simply by adding a few seconds to the audio, rather than having to re-shoot the video.

     

    Another step Support could take would be to add a section to "Chapter 1: What's New" in the Retrospect Windows 11 User's Guide.  That section should show a picture of the Create New Backup Set dialog as it is now in the latest version of the app, accompanied by a statement that "The texts of the dialog options have been modified to show RDX devices in the Disk option, because it has been found that defining such devices as Removable Disk causes problems."  It probably would be too much to suggest that Support also modify "... removable disk drives (RDX, REV, etc.)." in "Chapter 2: Getting Started" on page 19 of the User's Guide, because IMHO it appears to now be de facto Retrospect Inc.  policy not to make any modifications to User's Guides except in the "What's New" chapter.

     

    Moreover I assume the "one small exception" is the elimination of the Removable Disk Backup Set (Media Set in Retrospect Mac parlance) type from Retrospect Mac 8, which happened in early 2009.  Page 30 of the Retrospect Mac 8 User's Guide was modified to say "Disk Media Sets replace the less-flexible Removable Disk sets present in older versions of Retrospect"; that modification continues to later versions of the Retrospect Mac User's Guide.  If two years from now I should choose to replace my USB3 G-Tech G-Drive Slims with 500GB USB thumb drives—which ought to be available and price-competitive by then, I would have to define those as Disk devices  because my "backup server" is a Mac.  If that's going to work for me, I don't see why Retrospect Windows users shouldn't be at least strongly urged to define their USB thumb drives as Disk devices.

     

    Please remember that I responded in this thread as a volunteer, and thereby saved Retrospect Inc. the cost of at least a Support call and maybe a lost customer.  If I see any more threads dealing with problems caused by RDX devices being defined to Retrospect Windows as Removable Disk devices, at most I'll simply make a post there consisting entirely of a link to my first post in this thread.

     

    P.S.: I checked with Quantum this afternoon (23 August), and they have not manufactured GoVault "for many years".  So anybody using a device mentioned in the text for the Removable Disk option in the Retrospect Windows 11 Create New Backup Set dialog, or on page 19 of the corresponding User's Guide,  is ipso facto using an obsolete device.

×