Jump to content

jrm_dantz

Members
  • Content count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jrm_dantz

  • Rank
    Occasional Forum Poster
  1. Missing subfolders in linux backup

    Aah, I was going to mention that. No, there are no selectors involved at all.
  2. Missing subfolders in linux backup

    Thanks for the pointer re empty directories -- I think I had seen that before, but had forgotten about it. That clears up a lot, but there are still weirdnesses taking place in /var. I just did a clean backup of my clean Fedora 9 box, and it's failing to back up /var/log and /var/cache, both of which have stuff in them. Plus, new weirdnesses: I looked for other directories called "log", and found /usr/share/cvs/contrib/log. That has something in it, and it's not backed up. Also, none of the /sys directory is getting backed up, and there's definitely stuff down in there. The suspicious person in me is wondering whether there might be some code somewhere in the Linux client that is deciding for me that, for whatever reason, I don't want to bother backing up. Crazy, huh? I could look around more, but I've done about all the free QA work I can justify. Does anyone have any other thoughts?
  3. Missing subfolders in linux backup

    A few more data points in this: * I added /var as a subvolume, and it seemed to pick up the directories and files that had been omitted from the previous backups. * Several directories were missing from /home/ -- these seemed to be ones that were empty. For instance, if there was nothing along or at the bottom of /home/joeuser/a/b/c, neither a, b, nor c would be backed up. Help? I'm rather concerned about how much I can trust these backups.
  4. Missing subfolders in linux backup

    For what it's worth, I was able to replicate this behavior on a second running a virtually clean installation of Fedora 9. Looking at the /var directory, the same subdirectories were (and were not) backed up.
  5. Missing subfolders in linux backup

    No, they don't. The only ones that are there are the ones that seemed to be getting backed up in the first place -- account, db, lib, etc.
  6. Missing subfolders in linux backup

    Yes, they're all there.
  7. My configuration: server: Mac G4 MDD running 10.5.4 and Retrospect 6.1.230 client: Fedora 9, running Retroclient 7.6.100 What's up: Overall, the server and client are working fine; backups are happening. However, the backups are incomplete: some Linux directories are geting backed up, while others don't. For instance, in the /var directory, Retrospect is backing up account, db, lib, local, lock, named, run, spool, www, and yp; it's not backing up cache, cvs, empty, ftp, games, log, nis, opt, preserve, and racoon. I've run a full backup and an incremental, and these directories are picked up on neither. Permissions on the directories seem fine; root owns them all the way down, and they're all read-enabled. Plus, if I set up one of these directories as a subvolume and include it in the list of Sources for the backup script, the directory and its files are detected and backed up. It seems that, once Retrospect knows the files are there, it's happy to back them up; it's just not finding those directories as part of its sweep of the file system. I of course have no idea what other directories might be missing from the backup. Any ideas? This seems pretty serious to me...
  8. Is there any hope of getting this USB 2.0 removable hard disk running under Retrospect 6 on my Mac? Currently, when I try, I get the dialogue box telling me that "Retrospect must be configured to used CD/DVD drives for backup and restore..." (HL-DT-ST DVDRW GSA-S10N). When I click on "Configure", it asks me to insert a blank disc, which I can't do because, well, it's not a CD/DVD. Any thoughts?
  9. I've been doing a full restore on a Powerbook, and encountered the following things: I did a full restore from my most recent backup set, and things went more or less well except that one of my DVDs produced repeated 206 errors (trouble reading / bad media or something). I aborted the restore, started again, reported the DVD as "missing" when its turn came up, and continued to success. Once I got the machine back up, I noticed some missing files. These couldn't be attributed to the bad DVD, since they were files that I knew had been modified just before the last backup was made. I did another restore, this time going down the "Search for files or folders" path. I found and marked the missing folders, and started the retrieval. Retrospect asked for a number of DVDs, including the "bad" one. (I had un-marked the member as "missing" in the Configure area before starting this second backup.) Figuring I had nothing to lose, I put the DVD in, and Retrospect happily pulled some files off it and went on to the rest of the backup, finishing successfully. So, the questions are: (1) Why didn't Retrospect find the missing files when it did the full restore? (2) Why couldn't it properly read from the DVD on the full restore, but handle the search properly? I guess these are mostly academic questions at this point, but I'm still curious. Thanks, Jim
  10. I'm having to do a full-disk restore of my Powerbook (I sent it into AppleCare to have the latch on the display replaced and they wiped my disk and replaced it with a generic Tiger installation. Thanks, Apple...). The good news is that I did a full backup before sending it in; the bad news is that one of my backup DVDs from several months ago is not reading -- I'm getting a series of error 206's (Trouble reading / trouble positioning) for, as near as I can tell, every file on the DVD. All the other DVDs have read successfully, so my current assumption is that I'll have to proceed without this one. So, the question: Is there any way I can find out what files were on the bad DVD without being able to read it? This stuff should be in the backup set catalog somewhere; can I get to it? Thanks, Jim Miller
  11. Score! I copied the file bundle to another disk and back again, and all is well. Thanks much!
  12. Oops -- I'm running Retrospect 6.0.12, and 10.2.4 on both machines.
  13. I've got a Retrospect script to move a file from one machine to another. (It's really a file bundle -- "Show Package Contents" in the finder takes you down into its contents.) Anyway, the script is working correctly, and the file successfully makes it to the other machine. However, it throws the following error during the Compare phase: File "Data File Alias": different creation date/time (src: 1/23/2003 1:31:38 PM, dest: 1/1/1904 12:00:00AM), path: "Volume/Folder/TheFile/Data File Alias" Does anyone have a clue of what's going on here? As I said, the transfer seems to be working properly; the error message is just a bit annoying. Thanks, Jim Miller
  14. Bingo -- I backed off to v. 5.6 (from the Retrospect 5.0 install CD), and everything seems to be working properly. Thanks much! Jim
×