Jump to content

twickland

Members
  • Posts

    1,684
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by twickland

  1. It would appear that Retrospect is attempting to perform a New Media backup. Check the backup schedule in your script and make sure that the action you have selected is "Normal backup."
  2. What do you mean by this? That Retrospect asserts it's not a member of any media set? Or that the catalogue is unavailable? If Retrospect doesn't recognize the tape, you won't be able to rebuild the catalogue. Otherwise, you should be able to point Retrospect to the location of the catalogue, assuming you didn't trash it in the process of uninstalling the app. That should do it. Alternatively, if you don't have a lot of clients, you may find it easier to create a new private/public key combination and then uninstall and reinstall the client software on each of your clients.
  3. The information on your source volumes, scripts, etc. is contained in the file Retro.Config (6.0), located at /Library/Preferences/Retrospect. Unless you are swapping all your old hard drive volumes to the new computer, be aware that Retrospect will recognize that the new ones are different volumes, even if you've named them the same as the old. This may cause more files to be duplicated initially than you expect. A final word: a "duplicate," while useful, is not a "backup." A backup offers you a version history (unless you perform a recycle backup each time), and allows the backup to be compared with the original. The downside, of course, is that a backup set is not Finder-readable; you need Retrospect to perform a restore.
  4. A couple of suggestions: Make sure you've installed the latest version of Retrospect 6 server (6.1.230) and have the latest driver update file (6.1.6.100) in the Retrospect app folder. Both are available for download here. Confirm that your license code is for the "server" version of Retrospect (lesser versions cannot control an autoloader). Make sure you've installed the latest ATTO driver and firmware for your UL4S. Make sure that your Quantum Superloader is a supported device under Retrospect 6. The hardware database is at http://www.retrospect.com/supportupdates/technical/retrospect/device/?path[]=hardware. If you're still having problems, let us know a bit more about your system, including what hardware and OS version you're running.
  5. Grooming is not an option for a tape media set, so that doesn't apply. When retrieving an earlier snapshot from a tape media set, one simply has to insert the correct tape member that holds the corresponding past backup. I've always assumed that that snapshot resides on the tape--and is retrieved--as a single file.
  6. No, which is what makes the change in size so odd. There are a total of 619 backups in the set with probably 40, all incremental, on the last tape member. I would guess that the first 69 GB are not significantly different from the remaining 28 GB on this member. Are you saying that the snapshots are not stored on the tape, but that during a rebuild, Retrospect is recreating them on the fly? That doesn't seem to jibe with the (relative) ease of retrieving earlier snapshots from the media during a restore.
  7. Does anyone know what Retrospect does during and after a fast catalog rebuild? Here's the background: In a problem reported in the bugs section, Retrospect listed a number of files in one tape media set's catalog that had actually been backed up to a different tape media set. Because of this error, the first media set's catalog needed fixing. As an experiment, I told Retrospect to "repair" (rather than "rebuild") the catalog. I inserted the last tape member and happily Retrospect determined on its own that a rebuild was the correct action to take and began performing it. During the rebuild, Retrospect presumably performed a fast catalog rebuild. As I understand it, a fast rebuild means obtaining the catalog covering the earlier tape members from the beginning of this last member and then updating the catalog from that point on. The results were ultimately successful. Here's my question: There was just under 100 GB of data on the last tape member. The rebuild initially began quickly and completed 69 GB on this member in about 20 minutes, but I noticed then that the process was rapidly slowing down. Over the next half-hour, only a few GB were added, and the tape drive was now being accessed only sporadically. I went to Activity Monitor and noted that Retrospect Engine was using only a small CPU percentage and relatively small amount of RAM (around 70 MB). Overall, the CPU was largely idle and there was plenty of free RAM. What I did notice was a lot of writing to disk (writes, not reads). In Finder, the size of the rebuilding catalog was rapidly bloating. Its original size had been just under 1.8 GB on disk, but it was now marching towards 4 GB. At this point I left for the day, having quit the Console in the meantime, so I don't know exactly what happened during the progress up to the end. Launching the Console and checking this morning, I found that the remaining 25 GB or so of data on the tape had taken an additional 4 hours to catalog, which seems absurdly slow. The final size of the catalog, as indicated in Finder, was just under 6 GB, more than triple the size of the original catalog (which, if anything, should already have been larger than expected, since it included files that were not actually on the tape). Here's where things really got weird: After the rebuild, Retrospect no longer knew where the catalog was located. I pointed it to the correct location and then I accessed the catalog (by performing a dummy restore) to see if I could determine if there was anything funny about the file listing that could explain the bloated size of the catalog. The files looked just fine, so I checked the catalog file again in Finder; the file had now shrunk back to the perfectly reasonable size of 1.77 GB! Is it just me or does all of this seem odd? "All" as in the drastically-slowing recatalog process, seemingly-excessive disk writes, bloated rebuilt catalog, losing track of the catalog's location, and finally, the catalog's shrinking only after it had been reaccessed.
  8. So far, so good... Which would generally mean that the Retropect engine had crashed... ... except that, in my experience, the Engine doesn't restart itself without user intervention or a reboot. I'd recommend opening a support incident with Roxio by clicking on "Ask Here" on this page.
  9. This suggests a problem with the media set's catalog. If Retrospect doesn't know about the current member, it will keep asking for a "new member." Try repairing the media set in question, which will require inserting the latest tape member.
  10. We have occasionally experienced situations where the console will incorrectly report that the media set has no members, although it typically reports the correct total space used. Quitting and restarting the console has fixed the problem for us.
  11. There is an option in Preferences/Media to set a timeout period, after which Retrospect will continue with the next scheduled item whenever the correct media is not available. This is actually the same as it was in Retrospect 6.
  12. That's probably not the case. I suspect that you're really using all of the space on your tapes, which only have a native capacity of 200 GB. That "400 GB" capacity is only an estimate, and assumes 50% compression, something that most of us are unlikely to achieve in the real world. Actual rates of compression will depend on what types of files you are backing up (that is, how compressible your data is). Also, if your setup is unable to supply the drive with data as fast as it would like, it will need to backhitch and likely waste tape. If you're getting around 250 GB per LTO2 tape, you are achieving an overall compression rate of approximately 20%, which may actually be quite reasonable.
  13. A simpler way to force an update is to open and close the Retrospect preferences.
  14. Yes and no. Yes, in that you do it the same way in Retro 8 as in Retro 6: prepare to run a backup and then browse the matched files. However, whereas in Retro 6 it was easy to open up the entire directory structure and view the diamonds indicating the files already backed up, in Retro 8 you have to tediously open each folder and subfolder one at a time; there's no option-click shortcut to open everything. Furthermore, while Retro 6 was quite speedy in opening a folder, Retro 8 is annoyingly slow. So, unless you are browsing a small volume or favorite folder--or you have a good idea of exactly what you're looking for--you could find the whole process impracticably burdensome, at least in the current version of Retro 8.
  15. One of the problems is that Retrospect has always stored way too much information in its config files, a problem that has only gotten worse in Retro 8.2. In addition to the console prefs, sources, scripts, rules, media set info, etc., Retrospect stores a lot of the past and future activities information (some of which duplicates in a different form what's included in the log) in the configuration file. All of this requires frequent writing to Config80, increasing the chances of something going awry and bringing down everything with it. Many of us have long wanted Retrospect to separate these functions into different files, but the trend here isn't (and never has been) promising.
  16. It's not quite that bad. As Maser says, use the Restore wizard to search for files across whatever media sets you desire. You can set the search parameters as you please to narrow down what you have to browse through. One thing to be aware of: You can't change the top level in the search from "Any" to "All;" you need to create a sublevel first. To do this, hold down the Option key. The plus symbol button changes to three dots. Click on this button to create your sublevel. (There is also a shortcut that may be a bug: if you click on "None" at the top level, it will create an "All" sublevel.) Yes, Retro 8.2 then does seem to take forever to search the catalogs, but it's almost certainly faster than browsing individual backups.
  17. It is/was, in Retro 6. Nothing is simple in Retro 8.x.
  18. Retro 6.1 had more options for choosing what got backed up. For example, you could configure the client to back up selected volumes/subvolumes, so that you could add the client name to your script or group ("tag" in Retro 8 parlance) and Retrospect would back up just the selected volumes. In Retro 8, you need to create your favorites and then be sure to click the checkboxes only for those favorites in your scripts or tags. If you also check the client volume (or the client source name), you'll back up everything on that volume (or client).
  19. Can we assume the problematic machines are not in a different subnet from the ones that do connect? Are some possibly also connecting wirelessly? Have you confirmed that all are still at the same address where you first added them?
  20. It's not clear what you're doing here or what you mean by "not giving you the directories." You might start by giving us the version of Retrospect you're using. OS version and hardware would also be helpful. Then, describe in detail what steps you're following in your attempted rebuild. Retrospect 6.1 should be able to read any earlier tapes but in practice it sometimes chokes on early file versions. Retrospect 6.0 can have trouble with tapes created in 6.0 but later written to by 6.1. Retrospect 5.1 may be better able to handle an early version tape. It may be downloaded here. I believe your 6.x license code should also work with 5.1.
  21. Be aware that, for clients added directly via an IP address instead of a DNS name, Retrospect 8 typically reports a -519 error in place of the expected -530 error when the client is simply unavailable on the network, such as when it's shut down. Perhaps this may account for some of your instances of this error.
  22. Yes, that's absolutely correct, and it does work but... ...the problem is, how do you really know what you have selected manually? By default, Retrospect 8 selects all files and then stupidly does not indicate by a checkmark or bar whether any files have been selected within a folder unless and until you open that folder. Because you can't option-click on the disclosure triangle to display the entire directory structure, you would have to manually open every folder and subfolder down to the nth level and tediously uncheck every open folder or file that you don't want. In general, unless your source is a favorite folder with only a couple of directory levels, making a manual selection is simply not very practical at this time.
  23. I think I was able to edit the session info out of the link. If it still fails in time, there is an "Error Codes" link in the search bar of the Knowledgebase home page at http://kb.dantz.com/
  24. The support knowledgebase lists a bunch of error codes here. The list includes codes from previous versions of Retrospect and appears not to be comprehensive, but it is a start. Only a few of the error codes have explanatory articles linked to them.
  25. It's not obvious from the nomenclature, but this is the forum for Retrospect 6.1 and earlier. You'll have more luck reposting in the Retrospect 8 forum.
×
×
  • Create New...