Jump to content

rhwalker

Members
  • Content count

    5,089
  • Joined

  • Last visited

Everything posted by rhwalker

  1. rhwalker

    I can't add members to backup sets

    Hard to suggest ideas because you haven't provided any specifics as to your hardware (autoloader, tape drive, interface technology (SCSI, Firewire, etc.), interface card, etc. Russ
  2. rhwalker

    Tandberge Library T-24

    Does it pass the Tandberg diagnostics? That's the first thing to try. If so, then try quitting the Retrospect console, stopping the Retrospect engine, moving the config80.dat and config80.bak files to the desktop (so that Retrospect can't find them), re-enter your licensing information when you start the console and engine, see if the tapes and drive can be seen. If so, then your config80.dat file is hosed, and you need to restore it from a backup (or re-enter everything from scratch). Russ
  3. rhwalker

    Client now showing volumes

    Um, unless something has changed with 8.2, I believe that you are wrong because that's not how it behaved during earlier testing - unless you had the "multi-server" edition, a "server client license" was required for every Retrospect client running Mac OS Server. Russ
  4. It's slightly more complicated than that. The machines on the local LAN will need to be in a subnet that doesn't conflict with the university's subnet assignment(s) (not just those on the University LAN port, but any subnets for which the university broadcasts routing packets). There is no such thing. If a machine has no IP address, then it's unreachable. You will have to give the machines IP addresses, either by manually assigning an IP address, or by running a DHCP server on that LAN, such as the open source DHCP server from ISC. That will also necessitate giving an IP address to the Mac PRO's second ethernet port. Quenching, I'm not trying to be rude here, but, respectfully, you need to brush up a bit on networking basics before you dive in. If you do this wrong, your university might decide to block your Mac PRO from their network. Grave disorder could result if, for example, you start passing bogus routing packets back onto the university's LAN. Russ
  5. rhwalker

    Client now showing volumes

    And you also need a multi-server license. Retrospect, for licensing purposes, counts the Retrospect machine as a "server" and also counts any client machine running Mac OS X Server as a "server". You can purchase "server" client licenses to use with a single-server version, or you can purchase the multi-server version. Error diagnostics when it's a licensing issue are not very good. Russ
  6. rhwalker

    Media Set Member Lost Checkbox

    I've never had a missing member. You asked for a definition of the purpose of the checkbox, and I gave it. It worked as expected for me and for others in testing of prior versions. If you are waiting until the community tests every possible feature to provide you with assurance that there are no bugs, then you will be waiting forever. You should do your own testing on an isolated testbed system of features you need before putting any software, and especially Retrospect 8, into production. That's what we do because our data is valuable. Right now, Retrospect 8 is buggy. Much improved over the beta and 8.0, 8.1 versions, but still has a lot of maturing to do. It works well enough for some people (not us) to deploy into production. Russ
  7. rhwalker

    not seeing 6.3.029 clients

    Consider also that it's something about the OS update after Retrospect install process that changes the firewall configuration. You might have the same problem on this client after a subsequent 10.6.x update. It seems to be a battle with Apple's attempt to make the firewall more bulletproof (for security reasons), adding not only port and protocol lockdown, but lockdown by target applications allowed to use those ports / protocols, complicated by Retrospect's moving/renaming due to rebranding after the EMC to Roxio migration. It just might be that this can only be fixed by a more robust repair procedure by the Retrospect installer. Russ
  8. Yes, contact Roxio support. You should be able to get them to give you a temporary license for 6.x - you've already got the 8.2 license. You are just trying to work around a bug in 8.2 that won't let you use your old 5.x backups. Russ
  9. Retrospect - archive for download of older versions Russ
  10. Retrospect 8.x cannot currently read Retrospect 5.x data. In most cases, it is able to handle Retrospect 6.x data, but, at present, not anything from versions earlier than that. See the Retrospect 8 Read Me: Roxio Retrospect 8 for Macintosh Read Me One workaround that you might try is to run Retrospect 6, convert the Retrospect 5.x backup set to a Retrospect 6 backup set, then run Retrospect 8.2, open the Retrospect 6 backup set. Russ
  11. Suggest you repost in the Retrospect 8 forum. Link is here: Retrospect 8 for Macintosh forum. This forum is for versions of Retrospect prior to 8.x. See this forum's description: Russ
  12. Note that Retrospect writes until it gets an error (EOT, read-after-write error, etc.). In a sense, that's probably good - if you have old tapes that are starting to fail, you need to move on to the next tape and stop using the current tape member. Perhaps the drive needs cleaning? Russ
  13. There is more to creating a bootable volume than just copying files. Device inodes have to be created, links (and symbolic links) have to be crafted, and stuff has to be done for the boot partition. None of this stuff is a part of copying (duplicating) files. That's why a backup is done rather than copying (duplicating). You may be in a bit of a hole. One approach would be to do a clean install of Mac OS X, bring it forward with software updates, etc., then copy certain files on top of that clean install, etc. Very prone to error if you don't know exactly what to do. Good luck. Russ
  14. It won't make any difference if you have the port open. Our server is headless. The only "difference" it would make is to spread the load a bit. In most situations, the Retrospect console is not a very big load - it's just a GUI. The engine does the real work. Some put the console on a separate machine to try to isolate crashing issues. Right now, Retrospect 8, while having come a long way from the 8.0 days, is still not rock solid. Russ
  15. I provided the console port information simply because, in the information that you have provided to date in this thread, there is no information as to where your Retrospect console is running. On the same machine as the Retrospect engine? On some other machine on your LAN? On some computer on the other side of the world on the internet? On an iPhone, using the console app? Just trying to be helpful, Russ
  16. rhwalker

    Media Set Member Lost Checkbox

    It marks the data in the selected media set member(s) as missing. Perhaps, perhaps not. To explain, you have to step back a bit and understand the Retrospect paradigm. Forget the marketing jargon and the terminology that seems to change with each major release. Under the hood, Retrospect behaves like other backup programs, making an initial "full" backup, followed by subsequent "incremental" backups, in subsequent backup sessions. The Retrospect "media set" (f/k/a/ "backup set", f/k/a/ "data set") is a database. Retrospect's "catalog" is its index into that database, telling where files are stored. The Retrospect difference is that, through its "snapshots" (which are contained in the "catalog"), it presents the illusion of a "full backup" during each backup session. In reality, the "snapshot" tells Retrospect where the files are located in the media set for all of the files present during that session, even though only some of the files (depending on your "Rules") were backed up during that session; the catalog entries for older files, which were not backed up in that session, point into earlier backup sessions, as appropriate. When you "groom" the media set, Retrospect preserves only the files in the media set necessary to support the saved snapshots, deletes the rest, and compresses the database (media set). So, when you mark a media set member as "missing", all of the files in that media set member are marked as missing. If none of the missing files are contained in any preserved snapshot, then no files will be backed up in a subsequent session as a result of marking a member "missing". Older files, still present on the source and which were marked as "missing" by marking the media set member as missing, will be backed up in a subsequent backup session providing that those files are caught by the Rules used in that subsequent backup session. If the older files are no longer present on the source, well, of course, then they won't be backed up in a subsequent session because they aren't present at the time of the backup session. The usefulness of the snapshot paradigm comes at restore time, when the user is able to browse the contents of the source using the "snapshot", even though it is a composite history of the source that is being browsed. With other backup programs, in order to restore the contents of a volume, you have to first restore the initial full backup and then all subsequent incremental backups, working your way forward. Clear? Russ
  17. I suggest that you repost in the Mac Retrospect 8.x forum. If you look at the forum description, this forum is: The link is: Retrospect 8 for Macintosh
  18. rhwalker

    Local media gone offline

    This won't get solved unless (and until) the config80.dat file is split into parts, so that the "Past Activities" and some other parts are written separately, apart from the preferences. It's been a request for at least over 18 years that we have been using Retrospect that (a) the config (preferences) file be made user-readable, and ( that the config (preferences) file be split into parts so that the rarely-changed preferences proper don't get re-written as often (and thus the chance of corruption is reduced). Don't hold your breath for this to ever get fixed. I gave up long ago, and just back up the file so that we can recover when (not if) the file becomes corrupted. Russ
  19. rhwalker

    Copying Retrospect 6 tapes?

    There are at least several ways to accomplish something similar to your goal, but only one of them might do exactly what you want. (1) Run Retrospect 6 (which can read your tapes), do a "Transfer" from that backup set (all of the tape members in that backup set, not just those two) to another. This will create a new backup set with a new name, with the contents of the old tapes (providing that you set the filter for the "Transfer" appropriately), but won't be a copy of the old tapes. If you've only got one tape drive, you could use an intermediate disk backup set, then Transfer that disk backup set to the new tape backup set, or you could go tape to tape, if you've got two tape drives. Here, you will end up with a tape backup set readable by Retrospect 6, which is what you started with. While the tapes won't be "copies" of the originals, the backup set will hold the same data. (2) Convert the Retrospect 6 tapes to Retrospect 8 format using Retrospect 8 (requires a catalog rebuild under Retrospect 8, but doesn't change the tapes), then use Retrospect 8 to copy that media set (f/k/a/ "backup set") to a Retrospect 8 tape media set. Could use the intermediate disk media set method of (1), above, or two tape drives. Requires the advanced tape add-on if you have more than one tape drive attached. (3) Install unix tape drivers (Mac OS X does not have tape drivers, but Tolis Group sells "Tolis Tape Tools", which is a set of unix tape drivers), then use the unix "dd" command (see the man page) to go from one set of tapes to another. This will, in fact, duplicate each tape, and is the only way to solve your problem as stated. The problem with (3) is that it may not be possible to do exactly what you want. Tapes don't store a fixed amount of data. The amount of data varies with the tape length and the inter-block spacing, which changes on modern tape drives to keep the tape moving when the i/o pipeline becomes starved (so that you don't "backhitch"). Because Retrospect writes each tape member until it hits EOT, the amount of data on a tape varies from tape to tape, and there may not be room on the destination (copy) tape to hold all of the data on the source tape. Additionally, you will have to do some futzing around so that the destination tape ends up with the same block size as the source tape. Your question seems like a simple one, but sadly, it's not. Good luck. Russ
  20. rhwalker

    7.7.341 keeps losing tapes

    I would bet that this is the issue. If tapes are barcoded, then Retrospect knows where each tape is. If tapes are not barcoded, then Retrospect tries to remember where the tapes are by preserving a tape location cache. I suspect that there is a bug in the tape location cache. I haven't seen this because we, like most people, use barcoded tapes. I suspect that the testing at Retrospect may have been done on barcoded tapes, and that a bug was introduced at some point as versions changed. Russ
  21. rhwalker

    7.7.341 keeps losing tapes

    Are the tapes barcoded?
  22. Interesting to me, too, especially since they charge more for a "server" license. To my mind, the frequent problems people have with software firewalls indicates a problem with either (a) the Retrospect installer, or ( the Retrospect documentation, or © both. I don't see this issue because our xServe doesn't have the software firewall turned on. Our small network is pretty locked down, and access at the edge is well controlled. Yes. I was just trying to point your network investigations in the right direction. You've got the port 497 stuff working. Russ
  23. rhwalker

    Selectors & scripts

    No, no way, no. See the Roxio Retrospect 8.2 Read Me And Rule (f/k/a/ selector) creation is buggy. Russ
  24. rhwalker

    adding clients - multi casting

    What version for the clients? What about their firewalls?
  25. See also the three links upthread that I provided a while back. This is really something that you should be able to work out with Retrospect support. Note that there are three (and perhaps four, depending on where you have the Retrospect console) things that must get through the firewall: (1) port 497 - this is how the client and engine chat to accomplish the backups. (2), (3) subnet broadcast and multicast - used in client discovery (4) port 22024 - used between the Retrospect console (or iPhone app) and engine, goes through firewall if console is on a different machine See: Retrospect engine / console port requirements Russ
×