7 Replies Latest reply: Nov 23, 2008 12:50 PM by nerowolfe
nerowolfe Level 6 Level 6 (13,070 points)
A new thread with a more specific issue:
What in the world does
Error: (-1426) Applying backup protections to /Volumes....
Mean and why is it happening?
Read my other thread for details, but this "protection" application has been going on for hours.
What gives????

MacBookPro3,1-17"Core2Duo/VistaUlt64SP1; MacBookPro1,1-15"/XPProSP3; Dual G5/XPP, Mac OS X (10.5.5), Homebrew 3GHz ASUS PC, Dell Inspiron8k, Abacus, Sliderule, HP-50G
  • baltwo Level 9 Level 9 (62,210 points)
    According to MacErrors.h (available with Xcode Tools), the error is:

    errFSOperationNotSupported = -1426, /* The attempted operation is not supported */

    A google search for *backup protections* might bring up something that's applicable.
  • nerowolfe Level 6 Level 6 (13,070 points)
    baltwo wrote:
    According to MacErrors.h (available with Xcode Tools), the error is:

    errFSOperationNotSupported = -1426, /* The attempted operation is not supported */

    Now that's really encouraging
    A google search for *backup protections* might bring up something that's applicable.

    Been there, done that.

    If you read my other post, you see that the problem began when TM misread my computer name (the deadly 's thing, I believe.
    I posted some of the error log from the console - and you can clearly see the name misread.
    After changing my computer name and starting the backup again, the error continued.
    After a reboot recently I got a normal backup. I think it's done with smoke and mirrors.

    The good side is that I found out that changing the computer name has no affect on the backup volume. It changes the name and continues as before. I did this on both my computers.

    Lesson learned: if your computer's name is something like
    XYZ's Computer
    change it
    No spaces, no punctuation.

    I got by for a year with the apostrophe.

    Thanks for the info. The error really is "we don't know what the error is"

    Message was edited by: nerowolfe
  • nerowolfe Level 6 Level 6 (13,070 points)
    It fixed itself after some prompting on my part
  • baltwo Level 9 Level 9 (62,210 points)
    Now, that's interesting. BTW, I don't do TM stuff, so never ran across the issue. I only responded because I have MacErrors on the Desktop and it's easy to check for common error numbers.
  • nerowolfe Level 6 Level 6 (13,070 points)
    baltwo wrote:
    Now, that's interesting. BTW, I don't do TM stuff, so never ran across the issue. I only responded because I have MacErrors on the Desktop and it's easy to check for common error numbers.


    Like that rare random and well-know and reported backup failure, this is the second failure I have had with TM, forcing me to start using a new primary backup system (CCC) and consider TM a secondary tool that is not perfectly stable yet, and therefore not suitable for backup in the real sense that it must be perfect - or at least its failure rate should be less than the drive's failure rate.

    What I did learn is that changing the computer name has no negative effect on the backup. It does not start a new backup from scratch, as some of us, including myself, had surmised.
    You would think that this important fact would be well-known, but it is not.

    And as noted, I strongly suggest that anyone with an apostrophe s in the computer name immediately fix it. There were reports early on about this "glitch" which I seemed to have avoided until yesterday.

    I would further add that anyone using TM must also run TMBuddy Widget as a close check on what is happening.

    And of course, remember the words, "Don't Panic." Emotions are anathema to solving computer issues. A "Spokian" attitude is necessary.

    Message was edited by: Theodore
  • baltwo Level 9 Level 9 (62,210 points)
    Well stated. The primary reason I don't use TM is that It needs restoring to verify; whereas, a bootable backup/clone (using CCC, SD!, or Disk Utility) is immediately verifiable. As for the name thing, I always advocate using names without spaces, even though Apple's pattern is to initially name the boot volume Macintosh HD.
  • nerowolfe Level 6 Level 6 (13,070 points)
    baltwo wrote:
    Well stated. The primary reason I don't use TM is that It needs restoring to verify; whereas, a bootable backup/clone (using CCC, SD!, or Disk Utility) is immediately verifiable. As for the name thing, I always advocate using names without spaces, even though Apple's pattern is to initially name the boot volume Macintosh HD.


    I rather suspect that it was not the space that nearly did me it, but the 's and perhaps the subsequent space. This is strange, since it is Apple's policy for the default computer name to be created that way, "XYZ's Computer" for example.
    Now that I know changing my name has no effect on the TM backup, I am tempted to remove the space from the HD Name. The difference is that while my name appears only once, the HD name appears multiple times. I will wait for the next "event" before pursuing that path.

    When the TM screen appears, I can now imagine hearing Dukas and seeing Mickey Mouse.