Jump to content

Maser

Members
  • Posts

    2,054
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by Maser

  1. Not that I know anything about tape drives, but are you sure the firmware is current the VXA-2? And, yes, I use a big RAID array (that I backup the incremental changes to the media sets to another RAID array once a week.)
  2. In our setup' date=' the network connection name is "Default" with just a dash and multicast works fine. [/quote'] Yeah, this is a weird one. On my test machine, I have the IP address and the multicast sees the clients. On my prod. machine, I have the "-" and it *doesn't* see clients. And both machines are on the same subnet, too!
  3. You still have Retrospect 6 (if I remember you from another thread...), right? Does your drive work with Retrospect 6? If so, if you back up the same source data with the *same tape and drive* -- do you get more data on the tape with Retro 6 than with 8? (I'm just curious as I don't use tape...)
  4. Which option in the Restore Assistant did you choose for the "type of restore"? Do you get any better response if you stop/start the engine (and maybe reboot the server computer after you stop the engine?)
  5. The multicast thing has come up occasionally. In Preferences --> Network -- what do you have for the name and connection in the top box? I believe it's supposed to have the IP address of the engine computer and *not* a "dash" for multicast browsing to work. (And, I'd recommend manually adding the clients anyway by hostname -- assuming you do static DHCP/DNS -- it's a *lot* easier to keep track of things in the long run that way...) Besides, you have to add the sources once anyway, so why not add them by hostname?
  6. A couple of comments... If you use MacPath, you have to add a "/" to indicate a directory. So for your first "ends with Music", it would need to read ends with /Music/ *and* an additional line that says ends with /Test Music/ (using "contains Music" would get both, but might get other things you don't expect. Remember, using "MacPath" has to be very explicit.
  7. Is that the *exact* rule you are trying to create? Or are you asking theoretically how to keep one path containing "x", but not another path containing "x"?
  8. By *actual results* -- you are testing an actual backup (not just confirming in Preview), right?
  9. I've confirmed that there *are* still bugs in the Preview -- and they seem to be rule dependent. For example, if I make a simple rule that has two lines in the Exemptions: Folder Mac Path contains File Name contains The preview looks wrong. But if I remove the "File Name" line -- the preview looks right. But that the results of the rule (meaning the actual backup) works correctly in either case. Which is incredibly frustrating, I'm sure, for people trying this out for the first time! There's probably some trick to putting things in a specific order where it works "right".
  10. (This isn't to say there aren't still bugs in the program -- I'm just saying that syntax is very important when defining rules...)
  11. Right. That rule means nothing on a basic OSX machine. Unless you have a folder at the root level of your drive called "Music"? *Is* means "exactly" in this context.
  12. FWIW -- I just tested my rules against an empty media set. When I use the Backup Wizard and "preview" -- my rules work correctly (ie, when I drill down to my iTunes folder, everything except my "iTunes Music" is selected. As expected. YMMV, I guess.
  13. What if you run a backup to a new media set and use *no rules* -- are you getting everything? And are you sure the clients haven't marked anything "private" from the backup? I guess without some screen shots, we can't really comment further...
  14. So, the above implies you want a rule to work when backing up multiple computers (right?) So, that leads to the obvious question: Do you even *need* to back up the operating system and applications? If not, why not just mark the "Users" folder as the Favorite Folder for each computer and just backup that (and apply your rules accordingly?) Then, if somebody crashes, you just install your "load image" and then restore the users documents accordingly?
  15. And, for what it's worth, I think the *preview* of Rules may be broken. You might have to test an actual backup of stuff...
  16. I don't back up iTunes music on my user computers here. My rule for this is: Folder Name is iTunes Music I do also use "Mac Path", but you have to be extremely explicit if you want to use "is". So I use stuff like: Folder Mac Path contains like: Folder Mac Path contains /Library/Application Support/4D or Folder Mac Path contains /Crossover/Bottles/ Not sure if that will help you or not, but that's what works for me.
  17. You can't backup the catalog of the media set you are backing up to. You might be able to backup *other* catalogs for non-active media sets (admittedly, I've not tried this...). What I do is just do a finder copy of my catalogs manually once a week to an external drive (when I do an archive of my backup sets.)
  18. A1: I believe you can remove *any* .rdb files from a disk media set and redo another catalog rebuild -- the rebuild will only cover the .rdb files it can find (and they can be non sequential). A2: You can't back up a "live" catalog (IIRC) with Retrospect. You *do* have the Catalog file on your internal Engine computer, right? Not on the Drobo? Way up the thread you stated: There was a crash and a recovery about a year ago and I could no longer add to 1-Media Set A This would seem to me that you have other potential problems with the Drobo that might be addressed by reformatting the drive. But that's just a guess at this point.
  19. I think I get why they are doing it that way. Say you want a rule that basically says to exclude (in one rule): all files ending in .mov and greater than 100M *AND* all files ending in .mpg and smaller than 100M You couldn't do this if you started with "ALL" at the top. You'd have to start with an "ANY" at the top and then two sets of "ALL" groups. So, I'm fairly sure this is "by design" and you just have to consider the logic behind it. (But, if that's the case, they shouldn't give you a choice at the top level...)
  20. At many levels, this is non-intuitive but the following should work... In your second rule, hold down the "option" key when clicking on the "+" in the initial "Any" line -- this will change it to "..." From there, you can make an "All" section to include your saved rule and the additional 100M limit. So it would look like: Any of the following are true ---All of the following are true ------Saved rule includes ------File size It's never been clear to many of us why the *initial* "All" can't be selected unless it's by design at this point.
  21. I backup my media sets because I had one of RAIDs lose it's volume (twice!). This hasn't happened again since June (and that was the backup set), so it may have just been a fluke, but I'd rather not lose my sets again. Eventually, I may relax about this. According to the User's Guide about the size of a *file* media set: ...they are limited by the size of the volume on which it is stored, and also the maximum file size of the file system (FAT32, NTFS, HFS+, etc.). And, yes, you should be able to browse the catalog if the media set is off-line.
  22. One thing that comes to mind (as to how I do it) is if you make backups of the media sets. With the disk media set method, you can just back up the incremental .rdb files. With the "file" set, you'd have to back up the whole thing every time.
  23. So, you can restore from one of the sets? Why not try doing a "copy media set" from the "bad" set to a new "good" set and see if that cleans up the problem?
  24. that would be my question -- do you have any rules that would be causing this issue? If you've recycled the backup sets, then they should be empty so there would be nothing for subsequent backups to "match" against.
  25. I don't think you can transfer from an old media set to a new media set if you don't have a valid catalog file for the old media set, can you? I have media sets running that were created in 8.0 and beyond that I've rebuilt the catalog and groomed from without issue. I don't necessarily think it's expected "bit rot", but YMMV. the fact that the same files keep complaining mean to me that there's something wrong with the files for some reason. You could try just moving 2403 and 2404 to a new folder and rebuilding a catalog *just* from those two files. My guess is that won't work, either, but it's worth a shot. Also, have you confirmed you can *Finder copy* the "bad" files from your drive to another drive?
×
×
  • Create New...