Jump to content

DavidHertzberg

Members
  • Content count

    1,041
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by DavidHertzberg

  1. DavidHertzberg

    Retrospect 13 and Grooming

    My understanding of what you're saying is that jethro should set up his new Cloud Media Set with a local member, turn on either "Groom to Retrospect defined policy" with Months to keep = 12 or "Groom to keep this number of backups" = 52 * number-of-jethro-backups-per-week , and define the size of his local disk member at—let's say—1TB. He should then run a Copy Media Set script with that local member as the Destination. When the script has copied 1TB of his 5TB of backups, it will start grooming because it has run out of space. When it has finished that grooming, it will start copying backups again. When the script has filled up his 1TB again, it will initiate another groom, and this copying-grooming cycling will continue until the Copy Media Set script has finished with the entire 5TB of jethro's regular Source Media Set. It no doubt will not surprise you that I think this cycling is "mentally challenged". It may not surprise you too much that I think that Retrospect 13 will crash before it completes the Copy Media Set script. As a matter of fact, I'm willing to "put my money where my mouth is"—specifically the $69 price of an upgrade from Retrospect 12.5 to Retrospect 13. I'll bet that if either jethro or Retrospect Inc. tries this on a Source Media Set which is 5 times the size of the Destination Media Set, the Copy Media Set script will either (1) take more than 15 hours to complete for each TB in the Source or (2) crash. If I lose the bet, I'll pay for the upgrade—which I wasn't planning to get because my Internet upload speed is too slow for Cloud backup. If I I win the bet, Retrospect Inc. will give me the upgrade for free. Do we have a bet, Robin? If so, please contact jethro and me via e-mail. Either way, I think the general "mentally-challengedness" of this copying-grooming cycling, for potential Cloud backup users of Retrospect 13, explains why I suggest that Retrospect Inc. implement an age subset of "Groom to Retrospect defined policy" for action during the copying part of Copy Media Set to a Cloud Media Set for Retrospect Mac 13.5. P.S.: In first sentence of my first paragraph, added alternative for "Groom to keep this number of backups"—assuming jethro knows how many backups per week he has done to his regular Media Set and wants to keep the latest 52 weeks of backups in his Cloud Media Set. Using this alternative might somewhat speed up the cycling grooms, but I suspect not by all that much—and it might even slow down the cycling grooms. P.P.S. Replaced "brain dead" with "mentally challenged"; I originally wanted to use another term closely related to "brain dead", but I understand that term causes pain to those with relatives who are "mentally challenged". Just to make it clear, I admire Retrospect Inc. for its current computationally-intense implementation of grooming; it's just that that implementation becomes highly inappropriate when applied to what jethro—the forerunner of many other Retrospect users—is trying to do to add cloud backup to his current onsite backup at a reasonable cost.
  2. jethro, I made this post to Mayoff's thread on Mac Ver. 13 Grooming, specifically linking to your requirements for cloud backup and my suggested procedure. I (1) asked if it is true that Retrospect will not do Grooming on a Copy Media Set run, and (2)—assuming that is true—requested that Retrospect Inc. implement an age subset of the "Groom to Retrospect defined policy" option in Copy Media Set with a Cloud Media Set as destination for Retrospect Mac Ver. 13.5. You shouldn't have to buy a 6TB disk drive for your "seeding" when you won't need most of that capacity after grooming, and you shouldn't have to make a an extra multi-hour Groom run when all you want to do is pare your copied Cloud Media Set local disk member down to the past year of backups. P.S.: Ignore this post; Copy Media Set can use a Rule as an alternative to grooming per this post
  3. DavidHertzberg

    Retrospect 13 and Grooming

    Hi Mayoff or bdunagan, I gave jethro advice—based on my reading of the Mac User's Manual and viewing of Tutorials—in this post about how to create a Cloud Media Set copy of his installation's regular Media Set. He's obviously got budget limitations, and is worried about how much cloud space he would have to pay for if he uses a commercial provider. He said he's willing to have the cloud copy contain only the last year of backups, so I suggested he set an appropriate "Groom to Retrospect defined policy" for the Cloud Media Set. I later realized that the Copy Media Set script I suggested in step C2 might not execute the grooming policy (I think I read that somewhere but can't find it); therefore I suggested that, if the disk member of his new Cloud Media Set is as large as his regular Media Set, he might have to run a subsequent Groom operation on it. I realize now that, if my concern is correct, this would mean that jethro would need to dedicate a 6TB disk drive as the destination for his initial Copy Media Set run, even though he hopes to groom the Cloud Media Set to significantly below that size before he ships the disk drive to his cloud provider for "seeding". First, am I correct in thinking that a Copy Media Set script ignores any grooming option? Second, if I am correct in thinking that, I fervently suggest that Retrospect Inc. implement an age subset of "Groom to Retrospect defined policy" for action during the copying part of Copy Media Set to a Cloud Media Set for Retrospect Mac 13.5! Doing that wouldn't involve any complicated CPU-bound processing, just "this backup is older than what the user wants to include in the copy, so let's not copy it". I'm sure that many Retrospect administrator users will thank you for thus making cloud backup affordable and fast.
  4. This morning I did this, and got a -530 error for my MacBook Pro, verified by starting the Console after the LED on my USB3 Media Set disk drive stopped flashing and by looking at the log. As usual after a -530 error, I was able to manually run my "Sun.-Fri. Backup" script for the MBP. I noticed that, when I did so, there was no Instant Scan for the script—which there had been when the script was recently being run as scheduled from when I successfully executed the workaround up through 3 March. My conclusion is that, for me at least, the -530 error occurs when the Engine is started (by booting my Mac Pro) after the scheduled time for the script—whether or not the Console is started when the Engine is started. However, from when I successfully executed the workaround up through 3 March, I could boot the Mac Pro after the scheduled time for the script and the script would automatically be run—as shown by the Console which was in Login Items (which I have been referring to elsewhere in this thread as Startup Items). My version of Retrospect is 12.5, and both the Mac Pro and the MBP are running OS X 10.10.5 (I don't consider OS X 10.11 to be "ready for prime time" yet). P.S.: And it looks like my conclusion in the second paragraph is a winner! This morning (11 March 2016) I left both my MBP and my Mac Pro awake when I went to bed shortly after midnight. When I awoke at 3:20 a.m. the "Sun.-Fri. Backup" script had just finished running fine, including Instant Scan. P.P.S.: Amen to what I said in the P.S.. Yesterday morning (12 March 2016) I left both my MBP and my Mac Pro awake when I went to bed shortly after midnight. When I awoke at 6 a.m. the "Sat. Backup" Recycle Media Set script had finished backing up the MBP, including Instant Scan, and was proceeding to compare it. It went on to backup and compare my other 5 drives, for a total of 8.5 hours. P.P.P.S.: Oops, a further hypothesis bites the dust. This morning (13 March 2016) I woke my MBP up at 2:57 a.m.—3 minutes before "Sun.-Fri. Backup" was scheduled to run—but did not start up my Mac Pro until 3:10 a.m.. "Sun.-Fri. Backup" failed with a -530 error. When I ran it manually, it did not do Instant Scan. My further hypothesis had been that there would be no -530 error if the MBP—and only the MBP—was awakened at least a few minutes before a script was due to run, but the Mac Pro was not booted until after a script was due to run. P.P.P.P.S.: This morning I happened to wake up at 2:45 a.m., 20 minutes before "Sun.-Fri. Backup" was scheduled to run. So I immediately woke up my sleeping MBP, and booted my Mac Pro—which is the Retrospect "backup server" and has the Console among its Login Items. "Sun.-Fri. Backup" ran just fine, including Instant Scan. One notable fact is that, when the incremental "Sun.-Fri. Backup" runs with Instant Scan, it backs up nearly 9GB instead of just over 2GB—taking 17 minutes instead of 4 minutes for the copying phase alone. Based on errors shown in the log, the additional 6GB includes many ~Library/Caches/Firefox/Profiles/ksalhsaz7.default/safebrowsing files (I was using Firefox while "Sun.-Fri. Backup" was running) .
  5. Early this morning (8 March 2016), left my MacBook Pro awake and my Mac Pro "Retrospect server" machines up when I went to bed around 2 a.m., but quit the Console app well before "Sun.-Fri. Backup" was scheduled to run. When I awoke at 6 p.m. the "Sun.-Fri. Backup" No Media action script had run as scheduled, starting at 3 a.m.. No -530 error for the MBP. Tomorrow I'll try this again, but take the Console app out of Startup Items and shut down the Mac Pro well before "Sun.-Fri. Backup" is scheduled to run, then reboot the Mac Pro after "Sun.-Fri. Backup" is scheduled to run . What I'm trying to determine is whether the -530 error for the MBP happens only when the Console is running when the script is ready to run, or whether it occurs when the Engine starts running after the script is ready to run.
  6. C) I think you would want to do the following things: 1) Create a new Cloud Media Set, specifying "Groom to Retrospect defined policy" with Months to keep = 12. However, in the Member Type dialog, setup a new local Media Set member on a separate shippable disk drive, 2) Run a Copy Media Set script to copy your regular Media Set to the new Cloud Media Set local disk member, 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, 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) Ship the drive containing the new Media Set member to your cloud provider. Meanwhile make the arrangements to setup your cloud account, and keep the account parameters handy. 4) For the new Media Set, use the edit-pencil to switch the new Media Set Member Type to Cloud, and type in the account parameters you have kept handy. 5) Have your cloud provider copy the contents of the disk drive you shipped into your cloud account. 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 weekly, at whatever time you want. D) You'd have to setup Basho Riak S2 on the dedicated server, because that database software is compatible with Amazon S3. The software is free, but how much would it cost in people time to set it up? Here's the Retrospect Inc. White paper on how to do it. 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.: Added caution about Groom to my answer step C2. Added caution about No Verification to my answer step C6. P.P.S.: In my answer to D, corrected name of Basho software and added link to White Paper about it. Also made my answer step C2 more precise. P.P.P.S: Enhanced step C1 to give an alternative "Groom to keep this number of backups" specification. P.P.P.P.S: Deleted the "Groom to keep this number of backups" alternative specification step in step C1, because Mayoff says it wouldn't delete much of anything. P.P.P.P.P.S: Changed my answer step C6 to say Copy Backup instead of Copy Media Set, per Tutorial that Mayoff embedded. Also changed my answer step C2 to say checkmark Copy Backups. See my post below for further explanation. P.P.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.
  7. Early this morning (7 March 2016), left my MacBook Pro awake and my Mac Pro "Retrospect server" machines up when I went to bed around 2 a.m.., When I awoke at 5 p.m. the "Sun.-Fri. Backup" No Media action script had run as scheduled, starting at 3 a.m.. No -530 error for the MBP. I believe that several weeks ago I tried this approach of booting the Mac Pro (which has the Retrospect app in its Startup Items) before it was time to run a scheduled script. IIRC it also eliminated the -530 error then also. Tomorrow I'll try this again, but quit the Console app well before "Sun.-Fri. Backup" is scheduled to run.
  8. As of the day before yesterday, error -530 is back on my MacBook Pro. Tried the workaround yesterday. As of this morning, the workaround didn't work. For my failing scheduled "Sun.-Fri. Backup" script, I just run it again from the Console. My scheduled "Sat. Backup" script simply skips the MBP and goes on to backup the next client, so from the Console I submit a "Sun.-Fri. Backup" script to run after it—which backs up the MBP from scratch because the "Sat. Backup" run has done a Recycle Media Set. Therefore no big deal, just a minute per day of inelegance.
  9. Thank you for replying, Robin (but it took a phonecall to Retrospect Inc. Sales to get you to do so). My error was in not looking far down enough in the list of Tutorials to see the Cloud Backup ones under Retrospect for Mac. However the Tutorial you link to is not the correct one for fully answering my question. I see now that the Retrospect Tutorial briefly explains how to "change the set's location in Retrospect to the cloud location" after "seeding". There is another Tutorial that briefly recapitulates that explanation, but goes on to explain how to restore files from a Cloud Media Set that has been copied to a hard drive by the cloud media provider—and the drive then shipped to the user (similar to CP Home's "restore to door" service) to be installed as a local drive. The key concept in both Tutorials is that the top dropdown in an apparently-new Member Type dialog invoked for a Cloud Media Set in the first Tutorial—now also invoked by Media Sets->mediaset->Members->edit-pencil in the second Tutorial—has been enhanced in Version 13 to allow switching between defining a true Cloud Media Set member and a local Media Set member for the same Cloud Media Set. I think this is brilliant. However, I have one rather large quibble. In the words of Dr. Strangelove, "Why didn't you tell anyone?"! Specifically, Retrospect Inc. could IMHO have added that Member Type dialog key concept to "Cloud Backup" in Chapter 1: "What's New" in the Version 13 Mac User's Guide in about three sentences. If they didn't want to bother to do that, they could have added a sentence "Written words cannot explain the beauty of how we do this!", followed by a link to the relevant Tutorials. It's bad enough when a competing cloud backup product (its initials are CP) does its documentation as a set of web pages with links only to the next step down the garden path, so that a potential user has to use Google etc. as the table of contents for the documentation. It's even worse when Retrospect Inc. starts to do its documentation only in videos—without bothering to provide links from the User's Guide to the videos. Some of us older potential users can read text faster than we can watch videos. P.S.: Revised next-to-last sentence in second paragraph, to clarify the key concept. P.P.S.: Further revised next-to-last sentence in second paragraph, to clarify the key concept.
  10. One question I have relating to cloud backup in Ver. 13 concerns "seeding" followed by incremental backups. "Seeding for Cloud Storage" in Chapter 1 of the new Mac User's Guide states: "Seeding allows customers to back up their data to a local hard drive and then send that hard drive to the cloud storage provider. The cloud storage provider then imports that data into the customer's storage location. This process enables customers to send a large amount of data to the provider faster than it would take to upload it. After the data is imported, the customer can change the set's location in Retrospect to the cloud location and begin incremental backups." If the user backs up his/her data to a local hard drive, that would presumably be done after creating a Disk type Media Set for the Recycle Media Set backup—complete with catalog in the usual default location. After the data is imported into the customer's storage location in the cloud, can the user now "change the set's location in Retrospect to the cloud location" by changing the type of that same Media Set from Disk to Cloud—and then plug in all the necessary cloud access information into the change dialog? If that is not possible, can the user create a new Cloud type Media Set, and then copy the catalog of the Disk type Media Set as the catalog of the Cloud type Media Set? I am not familiar with many of the more esoteric capabilities of Retrospect; how would the user do this? By following the "Adding a Media Set’s Catalog" procedure in Chapter 8 of the Mac User's Guide, but changing the Media Set name to that of the Cloud type Media Set? If that too is not possible, would the user have to Recatalog the Cloud type Media Set after it has been imported? That sounds as if it would require the Retrospect server to effectively download some subset of the information for every file stored in the Cloud type Media Set. I now see that there is a Tutorial video entitled "Backup Set transfer to the Cloud for Windows". However I have searched the Mac User's Guide, and there doesn't seem to be any such facility for Retrospect for Macintosh. Version 13.5, perhaps?
  11. Sorry, I meant to post this in Bug Reports—and eventually did so. Moderators please feel free to delete this post here. Motivated by a weird hang on a "Sat. Backup" Recycle Media Set script run that I eventually aborted early Saturday morning, yesterday I tried running my experimental "Sat. Backup Incremental" script with both my client machines set to Sleep in the Apple menu. (I first updated the Retrospect Client on my MacBook Pro from the 12.0 version to the 12.5.0.111 version. The Client on my G4 Digital Audio tower—my other client machine—is the legacy Mac PowerPC 6.3.029 version, because it's running under OS X 10.3—don't ask.) The script run skipped backing up both client machines because of -535 errors, with no hangs. In the Retrospect 12.5 Console, both Clients have the Wake-on-LAN option checkmarked. In System Preferences->Energy Saver: the MBP has Wake for network access checkmarked; the G4 has the Wake for Ethernet administrator access option checkmarked. The last post in this thread in the Mac Retrospect 8 forum says "I can't confirm this myself but I have read in other threads that Retrospect doesn't support Wake on Lan despite it having a check-box indicating it is supported. One other user claimed this is a programming mistake and that this check box doesn't do anything and hasn't for many releases. Apparently many have asked for a true WOL feature to be implemented. " Page 43 of the Mac User's Guide says "Check the box next to Enable Wake-on-LAN if you want to make sure that Retrospect wakes up a sleeping client computer for Proactive Backup activities." Page 346 of the Windows User's Guide says "Retrospect cannot wake a sleeping Mac OS client computer to back it up. Make sure that each Mac OS client’s sleep preference is set to never put the computer to sleep." Does the Client Wake-on-LAN option not work at all, or does it work only for Proactive Backup activities? Either way, Retrospect Inc. should either (1) implement Wake-on-LAN for scripted activities, (2) modify the Client dialog in the Console to indicate that the option is only for Proactive Backup activities, or (3) eliminate the option.
  12. Monday morning I phoned A. of Retrospect tech support about another matter. I then asked whether, using my $119 Desktop Edition of Retrospect, I could run a Retrospect Engine on multiple computers or run the Console app on a different computer than my Engine. I told him I was simply curious, and have no intention of actually trying to do either of those things. A. said—after he finally understood my question— that neither is allowed with the Desktop Edition, and that I would need a $659 Single Server 20 Workstation Clients Edition to do so. I therefore conclude that the Retrospect Mac 12.5 Desktop Edition has been crippled by licensing to externally look like Retrospect up through Mac 6—in which what later became the Console was merely the same-process UI for what later became the Engine. I'm sure Retrospect Inc. does so in order to be able to sell cheaply to little dogs like me without underpricing its products sold to the big dogs. Could I in fact do what A. says I can't?
  13. Monday morning I phoned Retrospect Inc. tech support and spoke to A.. I told him I had run several backup scripts since closing port 497 on my router—including a 7.5-hour "Sat. Backup" Recycle Media Set backup on Saturday, and asked why he had told me last July that it was necessary to open port 497 on an Internet router connected to a LAN with no internal firewalls. It took A. nearly five minutes to concede that it is not necessary to open port 497 in this case, but he didn't explain why he continues to tell other users to open the port. I consider A. a manual component of the Retrospect 12 system. Retrospect Inc. should "fix" his "bug" so he doesn't give out incorrect information to users.
  14. Terminology notes on posts I have made in this topic: Where I have written "server" I meant "Retrospect server" in Retrospect terms. Note that "backup server" is not defined in the Glossary of the Mac User's Guide for Retrospect 12, although it is extensively used throughout that document—frequently abbreviated as "server"—presumably as a synonym for "Retrospect Server". I do not run a Macintosh OS Server machine. Where I have written "local" I meant whatever "Local" means in the Retrospect console—specifically a drive that cannot be Removed in the Sources item. Note that "local" is not defined in the Glossary of the Mac User's Guide for Retrospect 12, although it is extensively used throughout that document. Since the "Overview of the Retrospect Console" section in that document says each set of items is for a particular "Retrospect server", I deduce that "Local" means a drive directly mounted on the particular "Retrospect server" to which the Sources item applies. I run both the Console and and a single Retrospect server on the same Macintosh.
  15. I have 3 Macs at home: a 2011 MacBook Pro running OS X 10.10, a 2000(?) G4 Digital Audio tower that for now must run OS X 10.3, and a 2010 Mac Pro (that I inherited from a dead friend) running OS X 10.10 on the normal boot drive. The Mac Pro is my Retrospect 12 server; the other 2 Macs are clients on an Ethernet LAN. Every Saturday I run a Recycle MediaSet backup of all 6 hard drives (the G4 also has 2 OS 9.1 drives), which takes 7.5 hours. It would make life much simpler if I could get Retrospect to backup the 2 client machines first, which would free up the MacBook Pro after 3 hours and the G4 tower after another 1.5 hours. But Retrospect wouldn't do that; it backed up the MacBook Pro first, then both drives on the Mac Pro (for another 3 hours), and finally the G4 tower drives. I know I could get the desired result by separating the Saturday backup into 2 scripts: one--scheduled first--to backup only the client machines, and another--scheduled after that--to backup only the server machine. But that would be inelegant, so I phoned Retrospect Inc. tech support (I was still within my first 30 days) to ask how to change the order in which Sources back up within a script. The regular tech support guy (whom I will refer to here as A.) said that was "an algorithm that the developers know", but that he didn't know. I thought that was both ridiculous and intriguing, so I started thinking about this "secret unchangeable algorithm". I decided that, if I were programming Retrospect and didn't want to be bothered with making the order of Sources movable in the Console, I would use the alphanumeric sort sequence of each Source's Computer Name--as defined in its Sharing preferences. This explained the machine order I was getting on my Saturday backup script; I had given my machines the Computer Names "David's MacBook Pro", "David's Mac Pro", and "David's Old G4". So I changed the Computer Name on my G4 tower to "Mimi's Old G4" (Mimi being the nickname of my ex-wife, who gave me the tower after she decided to get a PowerBook), and the Computer Name on my Mac Pro to "Ronny's Mac Pro" (Ronny being the name of the dead friend from whom I inherited it). I then stopped and started their Retrospect Clients and Removed and re-Added both clients in the Retrospect Console. The names in the Machine column in the Source and Script Source reports in the Console changed accordingly, but the Saturday script still backed up my machines in the same undesirable order--as shown by running an incremental No Media Action copy of my Saturday script. I realized that the problem was with the two Mac Pro drives; their hidden Machine Names must not have changed because--as drives locally mounted on the server--Retrospect would not permit me to Remove and Add them. So I tried a bold experiment; I shut down the Mac Pro, physically pulled my friend's old "Macintosh HD" (which is not the current-boot-drive "Macintosh HD New"), and rebooted the Mac Pro. Retrospect then permitted me to Remove my friend's old "Macintosh HD" as a Source, because it was no longer locally mounted. Finally I shut down the Mac Pro again, put my friend's old "Macintosh HD" back into the machine, and rebooted it. My friend's old "Macintosh HD" showed up again in the Source report, and I clicked the Script Source checkbox to add it back to my Saturday script. That drive now backs up after "David's MacBook Pro" and "Mimi's Old G4", but "Macintosh HD New" still backs up between "David's MacBook Pro" and "Mimi's Old G4" because its hidden Machine Name is still "David's Mac Pro" instead of "Ronny's Mac Pro"--and I can't change that in Retrospect because I can't run it with the boot/Retrospect drive pulled. The moral of this story is that before installing Retrospect on the server(s) you should decide on what order you want your machines to be backed up by all scripts, and immediately change the Computer Name in the Sharing preferences for every machine--including the Retrospect server(s)--so that the Computer Names sort in the desired order of machine backup. Only after you have done this should you install Retrospect on the server(s). P.S.: It goes without saying that this "secret" should be documented in the User Manual ASAP. I'm also going to file a Product Suggestion that, in the Console Sources report, it at least be made possible to "pre-Remove" a locally-mounted-to-server drive so that it can then be truly Removed for the duration of that Console execution. The Removed local drive would of course show up in Sources again when Retrospect Console is next started--just the way my Removed old "Macintosh HD" showed up when I booted the Mac Pro after putting that drive back into the machine, but it would show up with the current Machine Name and be backed up--once it was re-checkmarked in the appropriate scripts--in the alphanumeric sequence of that current Machine Name. P.P.S.: In case it's not clear, the bug is that--because the locally-mounted-to-Server drive that contains the running executable for Retrospect 12 Server cannot be Removed as a Source--that drive can only be backed up in a within-script sequence dictated by the Server's original Computer Name at the time Retrospect 12 was installed on it. The consequence of the bug is that the locally-mounted-to-Server drive that contains the running executable for Retrospect 12 Server must be backed up in a separate script running before or after a script that also backs up other computers, unless you are happy with the within-script backup sequence that the Server's original Computer Name at the time Retrospect 12 Server was installed on it imposes. P.P.P.S: To improve readability, changed before-and-after-phrase underscores to making word/phrase italic.
  16. Hi Tom, You made your second post in this thread, specifying your client Energy Saver preferences, after I had drafted—but not yet posted—the first version of my post above. I then considered deleting my first paragraph in that post, but decided instead to add the sentence about wake on LAN—since what I said bears repeating even if it doesn't apply in your case. However I failed to spot the clue in Problem 1 in your OP. IMHO your mistake was in changing the name of your machine in Retrospect->Sources->Rename, instead of changing it in System Preferences->Sharing->Computer Name. Although I did not mention it in this thread, I had tried changing the machine name in Retrospect and found it to be ineffective. Assuming the machine is a client, Remove the machine as a Source first, make the name change in System Preferences (if that doesn't change the Client Name in the Status tab of your machine's Retrospect Client, you may have to stop and start the client), then Add it back as a Source and re-checkmark it in your script. As currently programmed, Retrospect->Sources->Rename seems to be a snare and a delusion. At best it is good for neatening the machine name for clarity purposes in the Retrospect Console. It may have been more effective in Retrospect 5, which dealt with machines pre-OS X. P.S.: Added parenthesized note about stopping and starting client to last sentence of second paragraph.
  17. It sounds to me as if Lennart is right. The inability of Retrospect 8 and above (IIRC Retrospect 6 didn't have this limitation—maybe for OS 9 clients) to backup sleeping clients is well-known. It is also well-known that wake for network access is not effective for Retrospect backups. My own experiments on my little LAN have shown these facts to be true. However, also consider my posts here and here and here in a thread on a very similar topic.
  18. I have now noticed a possibly-somewhat-related problem. Last night I tried signing in to this forum from my Mac Pro, using Firefox 41.0.2 under OS X 10.10.5. and I keep getting "Username or password incorrect". I get the same error message when I try to sign in from the Mac Pro using Safari 9.0.2. Last night I even changed my password for the Retrospect forums from my MacBook Pro, just to make sure that it wasn't a question of the Mac Pro using an old password. I can still sign on from the MacBook Pro with the new password using either Firefox 42.0 or Safari 9.0.2—simultaneously. But the new password doesn't help when trying to sign in from the Mac Pro. Here's a wild shot: Is membership on the Retrospect forums tied to a particular MAC address? Both my MacBook Pro and my Mac Pro have hard-coded 192.168.1 local URLs tied to their MAC addresses. P.S.: Problem persists even after Firefox on Mac Pro updated to 43.0.3. P.P.S.: In case it's not obvious, the reason I tried last night to sign into the Retrospect forums from my Mac Pro was to test whether the "styling buttons" problem reported in the OP for this thread is peculiar to the copy of Firefox installed on this MacBook Pro. I normally use the Mac Pro only as a Retrospect backup server.
  19. About two weeks ago I created a new topic here about the use of word styling and “smilies” on the Retrospect Forums. By experimentation I had found out that I could get italic into posts here by using the before-and-after "tags" (not to be confused with Forums tags) that work in the forums on another website. However those forums have buttons beside and above the posting pane that put in the styling "tags" before and after a selected word or phrase, and that put in a specified "smilie" wherever the cursor is. On a whim (it was a Sunday evening) I drafted a post on the other forums by clicking all of its "smilie" buttons, copied and pasted that draft into a post on this forum, and deleted the draft on the other forum. On this forum a number of the "smilies" in the post generated the intended graphic. I then expanded the post with a sober plea for buttons to generate italic, bold, and links with URL hidden behind an underlined word/phrase. The next day I got an e-mail from Robin, saying that somebody had posted spam using my ID and that I should change my Forums password. Maybe he was motivated by the fact that my Topic Title was "Whee! ...". Anyway, my "Whee! ..." topic disappeared from this forum. It turns out I have a web browser problem. I normally use Firefox (now version 42.0) on a Mac under OS X 10.10.5. When I post to the Retrospect Forums from it, clicking the More Reply Options button does not give me a toolbar with styling buttons above the text-entry pane. Three days ago I tried posting from Safari, and there clicking the More Reply Options button does give me a toolbar with styling buttons above the text-entry pane. One thing that may be significant is that I currently have Adobe Flash selectively blocked on Firefox. P.S.: When I Edit this post using Safari (it was originally composed on Firefox), I immediately get the toolbar with styling buttons etc. above the text-entry pane. When I click the Use Full Editor button—still in Safari, the toolbar goes away.
  20. Thinking about this further, in the light of the P.S. of my last post, I have realized that we can replace the concept of the Source's hidden Machine Name with the concept of the Source's Machine Name at the time the Source is checkmarked in a particular script. In other words, if you change a Source's Computer Name in its System Preferences->Sharing, the next time Retrospect is started it will not "notice" and automatically change—in all existing scripts—the sequence in which that Source is backed up—even though it will change the Machine name displayed in reports. However Retrospect will correctly sequence—according to its current Computer Name—a newly-checkmarked Source in a script. This explains why, when I checkmarked "Macintosh HD New" in the "Sat. Backup" script as described in my last post's P.S., it showed up as the last Source of the Details panel in the Summary tab without my having to drag it. This does not significantly change the "moral of this story" in my original post in this thread. Before writing any scripts you should decide on what default order you want your machines to be backed up by all scripts, and immediately change the Computer Name in the Sharing preferences for every machine--including the Retrospect server(s)--so that the Computer Names sort in the desired order of machine backup. However, since you will almost certainly start writing scripts as soon as you install Retrospect on a server(s), you would be well-advised to change Computer Names before installing Retrospect (so I'm not changing the thread title). Yes, as Derek500 has pointed out, you can manually change the sequence of Source backup in a particular script by dragging in the Details panel of its Summary tab. But it's going to be a nuisance to do this after you have already written a number of scripts, so if you have a default sequence you might as well establish it ASAP. Besides, we'll all be older and grayer before Retrospect Inc. gets around to documenting the Details-panel-of-the-Summary-tab-dragging trick.
  21. Here's a Console Backups panel bug that I've noticed again this afternoon, originally associated with the script "Sat. Backup NoMacHDNew" that has since been replaced by the script "Sat. Backup". Retrospect 12.5 all the way. 10 September: The bar graph for last Saturday—which is subdivided by drive in the reverse sequence of their backup (I guess that's reasonable, and the mouse-over display is cool)—shows no subdivision for the first-backed-up drive in "Sat. Backup NoMacHDNew", which is "Macintosh HD" on the client "David's MacBook Pro". The GB for that drive is, however, included in the Total GBs. 12 September: As scheduled every Saturday, today reran "Sat. Backup NoMacHDNew" (Recycle MediaSet) followed by "Sat. Backup OnlyMacHDNew" (No Media Action) to a different MediaSet. As soon as "Sat. Backup NoMacHDNew" had completed, the bug—no subdivision for the first-backed-up drive—appeared on the Console Backups panel—which only shows a bar graph entry for the latest day after at least one script has run on that day. However the subdivision for the first-backed-up drive in "Sat. Backup NoMacHDNew", which is "Macintosh HD" on the client "David's MacBook Pro", re-appeared in the bar graph after "Sat. Backup OnlyMacHDNew" had completed. 15 November: As scheduled every Saturday, yesterday reran "Sat. Backup" (Recycle MediaSet) to a different MediaSet. As soon as "Sat. Backup" had completed, the bug—no subdivision for the first-backed-up drive—appeared on the Console Backups panel. Today the subdivision for the first-backed-up drive in "Sat. Backup", which is "Macintosh HD" on the client "David's MacBook Pro", did not re-appear in the bar graph after "Sun.-Fri. Backup" (No Media Action) had completed.
  22. DavidHertzberg

    Console Backups panel bar graph bug for multi-drive backup

      I have frequently tried quitting and relaunching the entire Retrospect 12.5 application. In fact I normally use my Mac Pro only as a Retrospect server once a day, so I shut down the entire Mac Pro as soon as the daily backup is finished and reboot it the next day. I have not observed the display change in a good way from a new execution of Retrospect within the same week. However in my earlier post in the thread covering 22 November, I did observe the display to change in a further worse way. Within the same execution of Retrospect, I do not know how to quit and relaunch the console (I suppose I could look it up). I'm only a small-scale Retrospect user; I run the entire backup server complex on a single Mac Pro. I'll be glad to help in any way I can in debugging this. And may HaShem have mercy on our souls.
  23. DavidHertzberg

    Console Backups panel bar graph bug for multi-drive backup

    5 December: As scheduled every Saturday, today reran "Sat. Backup" (Recycle MediaSet) to a different MediaSet. The bar graph subdivisions for the six drives were correct. Nothing was different except the (rotated) Media Set onto which the backup took place. I pity the poor Retrospect Inc. programmer who has to debug this mess.
  24. 22 November: As scheduled every Saturday, yesterday reran "Sat. Backup" (Recycle MediaSet) to a different MediaSet. As soon as "Sat. Backup" had completed, the bug described here (no subdivision for the first-backed-up drive, which is "Macintosh HD" on the client "David's MacBook Pro") appeared in the Console Backups panel bar graph. Today—Sunday—that bug was not fixed in the Saturday bar graph after "Sun.-Fri. Backup" (No Media Action) had completed. (In its place a further bug in the Saturday bar graph subdivision for the first-backed-up drive in "Sat. Backup" appeared after "Sun.-Fri. Backup" (No Media Action) had completed.) Retrospect 12.5. The Total GBs for Saturday, even rounding-down the individual drive backed-up amounts, is now about 7GB too low; it appears that the backed-up amount for the second-backed-up drive—"Macintosh HD OS X" on the client "Mimi's Old G4"—is no longer included in the Total GBs for "Sat. Backup"—even though it is a subdivision on the bar graph. This is not a bar graph bug, but a bug in the Total GBs for a particular day in the Console Backups panel. Although I reported it in the last paragraph of the linked-to post in the Console Backups panel bar graph bug topic, I wanted this bug to have its own topic for greater visibility. (I also wanted to test out the url editing tag, to see if it works the same way as it does on the Ars Technica forums; it does—maybe the Retrospect forums should display the same panoply of editing aids including smilies. )
  25. DavidHertzberg

    Console Backups panel bar graph bug for multi-drive backup

    22 November: As scheduled every Saturday, yesterday reran "Sat. Backup" (Recycle MediaSet) to a different MediaSet. As soon as "Sat. Backup" had completed, the bug—no subdivision for the first-backed-up drive—appeared on the Console Backups panel. Today the subdivision for the first-backed-up drive in "Sat. Backup", which is "Macintosh HD" on the client "David's MacBook Pro", did not re-appear in the Saturday bar graph after "Sun.-Fri. Backup" (No Media Action) had completed. In its place (the rightmost place—remember that subdivisions appear in the graph in the reverse sequence of their backup), the subdivision for the last-backed-up drive in "Sat. Backup", which is "Macintosh HD New" on the server "Ronny's Mac Pro", was duplicated in the bar graph for "Sat. Backup" after "Sun.-Fri. Backup" (No Media Action) had completed. The Total GBs for Saturday, even rounding-down the individual drive backed-up amounts, is now about 7GB too low; it appears that the backed-up amount for the second-backed-up drive—"Macintosh HD OS X" on the client "Mimi's Old G4"—is no longer included in the Total GBs—even though it is a subdivision on the bar graph. This is not a bar graph bug, but a bug elsewhere in the Console Backups panel (I can't change the topic title, or I would have).
×