mbizer Posted February 26, 2008 Report Share Posted February 26, 2008 Hi, This is the first time that I've tried to back up my computer running Leopard (10.5.2) using Retrospect 6.1.138 to a remote server over afp. Every time I try, I get this error: - 2/26/2008 3:01:07 PM: Copying properties.plist on Gigas… Scanning incomplete, error -1407 (unknown). Any ideas as to what this could mean? Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted February 26, 2008 Report Share Posted February 26, 2008 - So your Destination is a File Backup Set that lives on the AFP share? - And Retrospect is mounting the remote volume? - Is it always the same file error? - Have you tried with different Sources (such as a defined Subvolume)? - Can you successfully backup to a File Backup Set stored on a locally attached volume? Dave Quote Link to comment Share on other sites More sharing options...
rhwalker Posted February 26, 2008 Report Share Posted February 26, 2008 Quote: to a remote server over afp. What version of AFP? Is the remote server an Apple server? How is the share mounted? Quote Link to comment Share on other sites More sharing options...
mbizer Posted February 26, 2008 Author Report Share Posted February 26, 2008 Yes, destination is a single file backup set that lives on the afp share (at work). Retrospect is mounting the remote volume. Yes, it's always the same file error. I have not tried different sources yet. I have been successful in backing up my entire hard disk via ftp (not afp) to a NAS device on my home LAN. Quote Link to comment Share on other sites More sharing options...
mbizer Posted February 26, 2008 Author Report Share Posted February 26, 2008 What version of afp? The version of afp included in Leopard 10.5.2. The remote server is an Apple server, and the volume is mounted automatically by Retrospect. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted February 26, 2008 Report Share Posted February 26, 2008 Quote: This is the first time that I've tried to back up my computer running Leopard (10.5.2) using Retrospect 6.1.138 to a remote server over afp. Every time I try, I get this error: - 2/26/2008 3:01:07 PM: Copying properties.plist on Gigas… Scanning incomplete, error -1407 (unknown). Ok. Is this a backup or a duplicate (copy)? Does the user being used by Retrospect have appropriate privileges on the share? Quote Link to comment Share on other sites More sharing options...
mbizer Posted February 26, 2008 Author Report Share Posted February 26, 2008 It's a backup. I've backed up to the share before -- but previously under Tiger. The message seems to indicate that the problem is with the source, not the target. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted February 27, 2008 Report Share Posted February 27, 2008 Ok, then answers to Dave's three questions would be helpful: Quote: - Is it always the same file error? - Have you tried with different Sources (such as a defined Subvolume)? - Can you successfully backup to a File Backup Set stored on a locally attached volume? Especially whether it still as a problem with a defined Subvolume source that doesn't include the problematic section of the filesystem that is causing the barfing. I'm also wondering if there is not something odd about having a volume named "properties.plist" (see your log message). Could it be that Leopard's filesystem path handling is having difficulties with a volume that has a name that ends like a system file extension (".plist")? Russ Quote Link to comment Share on other sites More sharing options...
mbizer Posted February 27, 2008 Author Report Share Posted February 27, 2008 Hi, Volume name is "Gigas", NOT "properties.plist". See log. See also my responses to Dave's questions. Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted February 27, 2008 Report Share Posted February 27, 2008 Quote: The message seems to indicate that the problem is with the source, not the target*. The next step then would be to see if the problem is with a specific file or directory on the Source, or with the Source volume itself. Trying to backup some folders defined as Subvolumes would be a good place to start. *note: Retrospect uses Source and Destination to describe what gets backed up to where. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted February 27, 2008 Report Share Posted February 27, 2008 Quote: Volume name is "Gigas", NOT "properties.plist". See log. See also my responses to Dave's questions. Interesting. Here's how my log looks when backing up a client's volume ("RHW iMac HD"): Quote: - 2/25/2008 6:52:43 PM: Copying RHW iMac HD on rhwimac… Quote Link to comment Share on other sites More sharing options...
mbizer Posted February 27, 2008 Author Report Share Posted February 27, 2008 I think I know what happened. I just went into "Sources" for that particular backup script, and it was indeed a folder called "properties.plist". Now when I upgraded to Leopard, I used the erase and install option, and clearly that confused the backup script (indeed, that is the only one that uses a subvolume). So in this case Retrospect must use aliases that don't work properly across volume erasures? Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted February 27, 2008 Report Share Posted February 27, 2008 Quote: So in this case Retrospect must use aliases that don't work properly across volume erasures? No. To track volumes (and defined Subvolumes) Retrospect uses unique file ID numbers assigned by the operating system. That way, if a display name of a volume changes, Retrospect doesn't loose track of it. When you erased the drive and installed OS X, new file IDs were given out to everything on the drive. By coincidence, the ID that Retrospect had in its database for your subvolume existed on your new install, but it was a different directory item that it had been before. An Archive and Install can also cause this issue, as the installer script will erase/create/move items throughout the file structure. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted February 27, 2008 Report Share Posted February 27, 2008 Aliases are what unix calls "symbolic links" (as contrasted with "hard links"). A "hard link" is a pointer to an inode on a volume, just like any other directory entry, and cannot span volumes. A "symbolic link" simply holds the text of the pathname, so it can span volumes. Because a "hard link" does not have any path information, it is insensitive to renaming. Because a "symbolic link" holds the text of the pathname, it breaks whenever anything in the path is renamed. Retrospect subvolumes work on the volume ID, which changes when a new volume is created (erase, etc.). Do you still get this error if you forget the particular subvolume and define a new subvolume for that item? Russ Quote Link to comment Share on other sites More sharing options...
rhwalker Posted February 28, 2008 Report Share Posted February 28, 2008 Simply because the original question of the initial post has not been specifically answered: Scanning incomplete, error -1407 (unknown). Any ideas as to what this could mean? The answer is given in: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Headers/MacErrors.h errFSNotAFolder = -1407, /* Expected a folder, got a file */ Hmm... appears to be some bugs in the new forum software - the path that I cut/pasted above has no spaces, yet appears to have spaces when previewed/posted. Going back to re-edit the text, spaces disappear, reappear on preview. Sigh. Russ Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 28, 2008 Report Share Posted February 28, 2008 Russ, I have noted the problem with long paths and I am checking with the FusionBB guys. Try using the new Code quote for now /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Headers/MacErrors.h Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 28, 2008 Report Share Posted February 28, 2008 Hmm... appears to be some bugs in the new forum software - the path that I cut/pasted above has no spaces, yet appears to have spaces when previewed/posted. Going back to re-edit the text, spaces disappear, reappear on preview. Sigh. I found the "word wrap" setting. I increased it from 25 to 150 (I assume characters). Hopefully this will be long enough Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.