Jump to content

CallMeDave

Members
  • Content count

    5,150
  • Joined

  • Last visited

  • Days Won

    4

CallMeDave last won the day on April 22 2013

CallMeDave had the most liked content!

Community Reputation

7 Neutral

About CallMeDave

  • Rank
    Grand Wizard of Backup

Profile Information

  • Gender
    Not Telling
  1. Bump: Do you have anything in the Privacy tab of the Retrospect Client preference pane?
  2. Not true; the "Back up:" popup menu selection in the Volume section of the Sources->Options tab has no effect on the volume listings in the Sources window above. Easy test; set "Back up:" to "Selected Volumes" and then un-check everything. Note that the listing above remains unchanged, even after a client Refresh.
  3. No, nor should it be. Although "Home" is the boot volume hosting your Retrospect OS X Client software, "/Volumes" is a directory used by OS X to mount filesystems for use by the system. Retrospect doesn't use this, so no matter if you click on "Browse" or "Add Favorites" with a system volume selected, you won't find anything in the Volumes directory inside. Correct; "Firefly" is the machine name, and Favorite Folders are folders inside of volumes. You must select the volume inside which resides the folder you want to define as a favorite. No; all directly attached logical volumes should be shown under a client machine's name in the Sources list. This is not correct behavior, as I note above. You should be seeing all the logical volume partitions on your physical drive. Retrospect lists all directly attached volumes in alpha order, without any sorting or designation as to what physical drive they're a partition of. Since the Retrospect Console application is not showing you the information you expect to see, that leaves the client software as the likely cause. Do you have anything in the Privacy tab of the Retrospect Client preference pane?
  4. CallMeDave

    Cloning with Retrospect 10

    Even when you're logged out of OS X there is a lot of open file activity. Expecting to get an exact clone of a running system onto another volume is unreasonable. For example, mdworker is famously intensive, and evidence of a difference in the destination is to be expected.
  5. Actually you could use the feature of limiting the percentage of the volume used for the Media Set (if that feature were reliable), to avoid the Catalog file being the cause of the volume filling. One problem is that with the Catalog on a Member you can't add another Member without having _both_ members online. The original poster described her system being a "laptop" (MacBook?) with a (single?) external drive. Maintaining the Catalog this way would preclude the ability to span the Media Set onto any additional physical media unless she was willing to physically connect two external drives each time the backup ran. There are other problems, too. Dave
  6. Looks like it to me. Previous behavior 10.1 - Select "Backup" icon from task bar at top - Select "Browse" chicklet button at right of Source volume - Select a folder from drop-down sheet - Click "Done" - Observe pop-up menu "Select a rule to identify files to back up." changes from "All Files" To "Manual file selection" - Observe pop-up menu then changes back to "All files" without user intervention That would be bug #3692 noted by David W Lee in this post: http://forums.retrospect.com/index.php?/topic/150368-cant-backup-manually-selected-files In 10.2.0 (201) all the above steps are the same except for the last; the pop-up menu keeps the "Manual file selection" setting, and in fact you can change that pop-up to something else and then _back_ to Manual and it will retain the selection choice you made. Now that I've updated I can't go back for further investigation of 10.1 behavior, and I have not actually tried a manually selected backup with 10.2, but it does look good!
  7. You put that in quotes, but there is no such setting in Retrospect. Are you saying that you are using Disk Media Sets? You shouldn't do that. If you don't have adequate space for the Retrospect Catalog file on your boot drive you should store it on another volume, just not on a Member volume of the same Media Set. Then simply Exclude the folder that contains the Catalog file from TimeMachine. More then just not recommended (there are those quotes again!), it's against the design of the program. Retrospect has _always_ been designed to maintain the Catalog file separately from the copied data, with the exception of File Storage/Backup/Media Sets which were deigned specifically to provide the functionality you're looking for (within the constraints present for the various versions of the program). It's like running your classic engine on unleaded gas; sure it'll work, until it doesn't anymore... Since the manager of Retrospect tech support suggests loading of corrupted catalogs is a possible cause, are you certain there are no Catalog files on your boot drive that Retrospect might be trying to load? You've searched exhaustively for ".rbc" files?
  8. CallMeDave

    Unable to Restore Any Data

    Correct. The Locate drop-down sheet will display all directly attached volumes and all volumes that have been configured as a Source. Retrospect does not use /Volumes to display anything in this window. If these are FireWire disks connected to the machine HOSTING THE RETROSPECT ENGINE, they should just show up in the drop-down sheet you get when pressing the Locate button in the Media Sets window. Not nested anywhere, just listed along with the boot drive. The Engine runs as a root process, so it doesn't matter under what account the Console is running. As long as the disk is physically connected you should see it listed in the Locate window. Swear the Engine and the Console and the FireWire drive are all on the same Macintosh computer?? A Member of a Disk Media set is unique only by the presence of a Retrospect folder; the disk remains unaltered in every other respect. The Console can be run either on the same machine or on any other machine with access to the Engine host. The Engine can't be configured without using the Console application (AFAIK; I don't think they've added any CLI tools; they should). Answered above; because it has no need to.
  9. CallMeDave

    Unable to Restore Any Data

    What exact steps are you taking to get there? While /Library/Application Support/Retrospect/Catalogs/ is the default location to save newly created catalogs, if you configured your Media Set to keep its catalog file somewhere else, then the state of the default folder is unrelated to the discussion. Oh, and you don't need to specify <Mac HD> if you use the root forward slash; the path is quite specific and complete without it! Yes you are; it's the Retrospect application, and without it you wouldn't be doing anything. Twickland is using "Console" to differentiate between the Retrospect "Engine". Huh? A link "to" the Catalog file located where? Why? You don't need to do any *nix magic; Retrospect will expect to see the Catalog file on the path specified in the Media Sets window; what does that path show? Why are you talking about restored Catalog files; you state early on that "The catalogue files are present..."
  10. CallMeDave

    Unable to run Mac client

    If the Client software is not on, then it's not a communication issue. It means the Client is not on. What do you see in the window? Is "Client Name:" showing? I'm assuming the Lock icon in the lower left is unlocked? So a restart of the OS X 10.8.x machine running Retrospect Client 10.2.0.201 does not result in the client process running? What _does_ get it running again? Just multiple reboots? Is the "retroclient" process running on the machine? Is there anything helpful in /var/log/retroclient.log ? Have you uninstalled the client and reinstalled?
  11. Since Retrospect 10.x consists of two interworking software components, the RetroEngine daemon and the management console application: - What does "non-responsive" mean in this context? What did you see? What did you try? - What exactly did you force quit? - How exactly did you force quit "it" ? To avoid Forum respondents attempting to provide answers you have already received, what did Retrospect support tell you? - What are the exact steps you are taking? - How did you create your Restore script?
  12. Actually it would help others to help you if you provided as much information as possible, even if that information refers to convoluted steps.
  13. Robin, I'm months late commenting on this, but I have to ask: The issue is Client connectivity, not disk accessibility. While non-Server OS X does unmount externally attached volumes, one would assume the boot drive would remain available even without any instance of loginwindow running. And for most folks, Retrospect OS X Client is in place to _read/backup_ the contents of volumes on the client computer. A limitation that Retrospect can only access internal physical-drive-hosted volumes when no user is logged in would be a bummer, but better then what appears to be the case that the entire client machine is unresponsive to network traffic. And if in fact it's "normal behavior" for Retrospect to be blind to a client computer without a user logged into the Finder, why is this fact not in the online documentation (or in the tech specs, for that matter)? http://retrospect.com/en/documentation/user_guide/mac10
  14. Was a user logged into the client machine at the time you tried to connect to it? Sounds right to me; I have all sorts of third party System Preferences that don't exist as application packages. What version of the Retrospect OS X Client software did you install?
  15. prl asked: Which Retrospect v10, specifically? To which Dennis responded: This thread will live forever, and prl would have to cross-check the date of your post against the release dates of the software builds just to get the answer to his question. Be a lot easier if you just said which version of Retrospect v10, specifically... -dave
×