Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by jrm_dantz

  1. 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?

  2. 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.

  3. 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...

  4. 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?

  5. 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.




  6. 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?



    Jim Miller

  7. 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.



    Jim Miller

  8. I'm running Retrospect 6.0.204 with 5.9.104 drivers on a Mac G4 MDD (10.3.7) with a Pioneer SuperDrive, and am trying to back up onto DVD a Windows machine running XP SP 2 and Retrospect Client 6.5.132. I have 9 gig to back up, so more than one DVD is needed. The backup to the first DVD runs fine, but when I'm prompted for the second, Retrospect hangs -- it never moves on from the file that it was in the middle of backing up at the end of the first DVD, and I get the Spinning Beachball of Death -- the CPU utilization goes up to 100% (most of which is being pulled by Retrospect) and I'm dead in the water. The Retrospect icon in the Dock reports "Application not responding", and I have to force quit the app. Once I've done that, the DVD appears on the desktop with an appropriate name (e.g. 2-BackupSetName). Get Info claims that the DVD now holds 2K of data.


    I've successfully done multi-DVD backups of Mac and Linux clients, so that part of Retrospect is working OK. Arggh. Does anyone have any clues or suggestions?



    Jim Miller

  9. Resetting the clock was a fine idea, but it didn't work -- I'm still being asked to back up a couple of gigs of files, immediately after doing a full backup.


    But this just gets weirder and weirder. After doing the initial full backup (call it B1), I did another, and found that it was asking for a large number of files to be backed up (hence my previous message). So I stopped that backup and tried again (B2), and again (B3), and so on. Here's what I got:


    # files in initial full backup: 172, 531.

    B1 (first normal backup after the full backup): Retrospect wants to back up 92,092 files.

    B2 (after not doing B1, but immediately asking for another normal backup): Retrospect wants to back up 83,973 files. I'd expect some difference due to changes in log files and the like, but not almost 10,000 files.

    B3: 62,679 files

    B4: 72,032 files

    B5: 62,679 files (hmmm -- seen that number before)

    B6: 72032 files


    and so on. For awhile I hoped that it would eventually asymptote to zero, and I could get on with my life. But no -- after awhile, it begins to consistenly bounce around between 50,000 and 60,000 files.


    Yeah, this is pretty annoying.





  10. I'm backing up a bunch of machines from a Mac OS X 10.2.6 machine running Retrospect 6.0.178. One of these machines is running RedHat 9 with retroclient 6.5.108. Here's the problem: I do a full backup of the RedHat machine, and it successfully backs everything up. If I then immediately do another normal backup, Retrospect wants to back up over half the files on the machine (a couple of gig), including some files that I know have not been changed since the previous backup. If I let it back them up and try again, it again wants to back up the same set of files. I've tried blowing away the server's backup set and recreating everything, but it doesn't matter -- the same thing happens. I've tried looking for a pattern among the unchanged files that it wants to re-backup, and can't see any obvious patterns -- the files are all over the place. Grr.


    Any clues or suggestions?



    Jim Miller


  11. Gah -- sorry for the crappy trouble report. I'll think of something to blame it on later. Anyway:


    - What version of the OS X Client is the PowerBook running?


    6.0.108; the Powerbook itself is running 10.3.2.


    - Will the Client stay on after a restart?


    Sometimes. I just checked it now after having rebooted earlier in the day, and it was off.


    - Has the Client software been moved from its default location?


    No -- it's in /Applications.




  12. I'm running 6.0 Workgroup on an Beige G3 running 10.2.6, and am using it to back up a number of Mac, Windows, and Linux clients, including a PowerBook running 10.3.2. Sometimes when I wake the PowerBook from sleep, the client, which had been turned on, is turned off. This of course causes the G3's scheduled backups of the PowerBook to fail. Has anyone else seen this? Is there a fix?



    Jim Miller

  13. When doing a backup of my main 10.2 volume, I have just begun to get the following error:




    Scanning incomplete, error -43 (file/folder not found).


    While scanning volume Mac_OS_X,


    File Mac_OS_X/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/Resources,


    > bad name length: 0


    File Mac_OS_X/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/Resources,


    > bad name length: 0




    and then the backup dies.




    I've tried building a selector to avoid searching down into this directory, but it doesn't seem to work. I can hack around it for now, but I obviously want to be able to get the whole volume properly backing up. Any ideas?






    Jim Miller

  • Create New...