Jump to content

CallMeDave

Members
  • Posts

    5,150
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by CallMeDave

  1. There is no guarantee that the free "AppCleaner" program knows how to uninstall the old Retrospect OS X Client software.
  2. And that's likely the problem. Did you "Add" the network volume to Retrospect's "Sources" list from the giant candy "+" icon? Was the network volume mounted on your Mac at that time? Mac OS X will not allow any filesystem to be mounted with the same name at the same time by different users. The Retrospect engine runs as User 0, while your Finder session is likely a different user ID (generally 501 for the first local user). The first user to mount the volume gets its normal name ("foo") while the next user gets "foo-1". The Finder will hide this, but you can see it in Terminal. Go to Sources and select the share point, then look at the Overview section below, at the Path field. What do you see? Now open Terminal and issue the "mount" command. You should see your network volume there. Do you see it twice? Do you see the modified name OS X has created for the second one? Retrospect will look for volumes on the path you initially set for it. If this path changes (due to user action) the volume won't be found. This issue, in one form or another, has been the most frequently answered question on this (and the previous) Forum since version 5.0.20x shipped back in 2010 or so.
  3. Fine; Retrospect builds a Catalog and tracks files, copying only the first instance and noting the specifics of any additional matching file(s). But that doesn't invalidate the next assertion, to wit "Retrospect won't copy a file to the Media Set if that file is already there..." It won't, unless you configure it to do so. And the program _certainly_ doesn't delete anything already written to a Member of a Media Set; did I misunderstand you to be claiming that? Apologies if so. But it's still unclear what exactly is beyond your understanding. With default settings the program behaves as advertised; a unique file is copied once, additional instances of that same file are noted in the catalog for later Restore but not copied again, and if you want different behavior there are options available. It does this during every Normal backup. What are the "two options" they are forcing you to use? The program has always used a combination of file attributes and location to provide its feature set. No it does't use any HFS specific anything (due to their apparent goal of cross platform compatibility) or hashes. Yes, it can get fooled (there were some early OS X updates from Apple that matched the file attributes while containing different binary data; something with the version control they were using at the time), yes it is rare. Probably a trade off or two involved in the decision (Richard Zulch is a very, very smart engineer...).
  4. If I set it to "Tags => contains" and enter the exact text of a tag that has been applied in the Sources window to a Favorite Folder, nothing shows. If i set it to "Tags => is not" and enter that same text, all my sources show, even the Favorite Folder that has that tag. On a related note, sadly there is no "does not contain" as a choice. I'd say they still don't work. 9.0.1 -dave
  5. Since those two options are on by default for all new Scripts, you must have turned them off yourself. "dedup" probably isn't the right term to use (which is probably why Retrospect doesn't use it). Retrospect won't copy a file to the Media Set if that file is already there, matching the criteria noted above. That's it. It doesn't go through the existing files on a Media Set and de-anything.
  6. Is Retrospect completing the backups? 4-8 lines written to system.log doesn't sound like much of anything to be concerned about, given the amount of data os x writes to that file...
  7. Would you be willing to share with the Forum readers what hardware "Copy HD" is using? Are you restarting or shutting while Retrospect is doing something?
  8. I would assume so, as this is not a Retrospect technical support conduit. For developer tech support you open a ticket from their website. For user community support, both requesting and providing, visit this Forum.
  9. Even worse, the cause was a mix of user-error and unavoidable operating system behavior. See, the name of the share was changed by OSX, not by Retrospect. But it was avoidable if you hadn't mounted myvolume on the Engine host machine as user 501 (or similar) before then expecting/asking Retrospect to mount the same volume as user 0. OSX won't allow the a volume of the same name to be mounted by different users, so OS X will append the unique string ("-1" in this first instance) to the mount point.
  10. You really should use Disk Media Sets here; they distribute the data into multiple file-parts (the way the Internet Backup/Storage Sets did before) instead of a single size-limited file. Likely because you have the remote volume mounted in Finder and Retrospect at the same time, or you configured Retrospect in such a way that it can't see the volume when you try later. This is due to OS X (and unix in general) not allowing a remote volume with a particular name to be mounted more then once (whether it's the same actual volume or not). And to prevent this, OS X has an auto renaming feature to keep itself safe. If you mount a volume in Retrospect, it will mount on the Engine host machine at /Volumes/Foo If you then mount that same volume in Finder, it will mount at /Volumes/Foo-1 Which would be fine; but if you reverse that when first setting up Retrospect, you'll have /Volumes/Foo on the Desktop and Retrospect will be set with the path to /Volumes/Foo-1 Now restart the machine; when Retrospect attempts to connect to the path it was setup with (Foo-1) it won't be found, because until OS X does its naming voodoo that volume simply doesn't exist. The answer? Configure Retrospect after a restart, and don't mount the same destination volume(s) on the machine that hosts the Engine.
  11. More specific information about your software configuration and hardware setup would probably be helpful, and certainly couldn't hurt to provide. "one hard drive to another" would be what, exactly? What does "list of sources to rebuild" mean? Rebuild what? Rebuild how? What types of Sources?
  12. When you click the giant candy sized "+" icon in the Media Sets window, the sheet that drops down is a the same sheet as drops down when you click that same icon in Scripts and Sources. It shouldn't be doing any device accessing at that point. Is this the sheet you're that's freezing?: "Accessing" suggests Retrospect attempting to communicate with device hardware; do you have anything hanging off the XServe? Davd
  13. When you click on the "needs media" icon, a drop down sheet appears. What is shown as the title of that sheet? Dave
  14. Yes. It's the "Overwrite matching files" pop-up menu choice in the Destinations tab of a Copy script. It's the default choice for a new script; what did you change yours to? Dave
  15. Pretty hard to say; you haven't provided much information to go on. What Type of Media Set are you using? What are these 98MB files named? What folder are they in? What are you seeing that indicates no backup was made? What does the log say?
  16. Could you describe your hardware and software configuration, please? Dave
  17. I'd try to help, but I can't get my installation to recognize _any_ volumes on _any_ logged in client at all, ever. Used to work, now it doesn't. If I cared more I suppose I'd test it more, but I don't so I don't. Dave
  18. Yes you can. The first window after selecting "Search for files in selected media sets" displays search criteria choices (using Apple's newest APIs for filtering, one of the only programs I know taking advantage of this Snow Leopard only feature). You can add criteria and sub-criteria (by holding the Option key to see the "+" icon change to an "..." icon). Choices are: Date accessed, Date created Date modified Date backed up If you select January 26 you can restore from the Previous Backup (what used to be called "Snapshot") of how the machine looked that day. If you file was on-disk with a modification date of something earlier (ie November 13th ?) then yes, that's the file you'll get. If you want to search through 10 Past Backups, then yes. But that's not the point of Past Backups, which is why you would want to Search based on name and/or date, location, size, etc. Now, in other places in the interface, the file selection tools are hopelessly broken. So it's possible that it's broken here, too; you'll need to try it.
  19. Let's start at the Sources window (and note the error does not imply a communications issue): > it prompted me that the old client wasn't there - Did you Remove the old instance of the Client from the Sources list, either before or after you added the new instance of the (same) machine? > I double-checked and instructed it to back up the selected volume only of "Macintosh HD" Staying in Sources: - Can you click on the disclosure triangle next to the client computer's name and observe "Macintosh HD" there? - Can you click the "Add Favorite" button for the volume? Do you get the drop-down sheet? - Assuming you are getting the error on a script, have you confirmed in the Sources tab of the Scripts window that the correct volume is selected?
  20. Yes. "[color:purple]!Trouble writing[/color]" means, well, it means what it says; trouble writing data to the backup hardware. Dave
  21. Quite frustrating without context. Any reason you couldn't include some navigation elements to make it easy for viewers to recognize where these are? (in other words, don't make it difficult for people to help you!) I mean really, not even the column headers in the list? No. The "Browse" chicklet in the Past Backups window will reveal a drop-down sheet showing the Source volume (or Favorite Folder) used. This may or may not represent everything being protected in the Media Set. What is the first screenshot of? It's not Past Backups (which doesn't have a "Path" column. It's not "Activities" (which doesn't have a "Browse" button), and without any context of the screen I'm lost. (All Sources I user are Favorite Folders; perhaps root volume sources show as paths in the "Name" column of the Past Backups screen?) Regardless, if you backup all the files in a Source to a Media Set, then run another backup of the same Source to the same Media Set, the green checkmark icon in the Past Backups window will be shown _only_ on changed (and thus re-copied) and/or new items. It's expected behavior. But take special note of the Path column in that first screenshot. Is "Backups-1" the actual name of the shared volume? Is "Users-2" how the share point is configured on the server or the NAS? Dave
  22. Yes. See Table 1 Since the file(s) in question appear to be dynamically (and quite possibly rapidly) created and/or modified, it's unknown what Retrospect is actually choking on or being choked by. Better tests would remove Safari's cache creation from the equation. Create files with long names, with long paths, with and without extensions, and see how Retrospect handles them.
×
×
  • Create New...