Jump to content

Restored files showing up as Unix exe's


Recommended Posts

Hi: recently restored desktop user files from a Retro WG Mac 6.1.138 server, and after the restore (directly to the client machine), the files show up on the user desktop as Unix executables. I thought this only happened if resource fork were *not* backed up or restored properly. But Retrospect doesn't even have the ability to ignore this info, does it?

 

Files work fine if manually opened in correct app, but this isn't super elegant from the user perspective. Can anyone help out here?

Link to comment
Share on other sites

Quote:

- What steps were performed to Restore the files?

- Did the files have type/creator codes when they were backed up?

- Can you confirm what, if any, type/creator codes are in the files now?

- Do the file names have extensions?

Dave

 


 

This was an immediate restore, from the backup server, directly to a subfolder on the same Mac Retro client they were backed up from.

Don't know about the creator codes, but the icons showed up properly before the backup, and all other files on the system are fine, but the ones I restored show as Unix exe's.

File names do not have extensions.

This is happening with Address Book Data files, Word, Excel, PDF, JPG files.

Link to comment
Share on other sites

> This was an immediate restore, from the backup server, directly to a subfolder on the same

>Mac Retro client they were backed up from.

 

- Was this a "Restore files and folders" or a "Replace entire disk" operation?

- If it was the latter, was it a Restore to the same user's account that it had been backed up from?

 

> This is happening with Address Book Data files, Word, Excel, PDF, JPG files.

 

Address Book Data files (such as "/Users/foo/Library/Application Support/AddressBook/AddressBook.data") do not have type/creator codes or resource forks. Apple generally no longer makes applications that use/rely-on metadata for application binding, which is done by Launch Services using file name extensions (which, you'll notice, is ".data" for Address Book Data files).

 

Word and Excel files do get type/creator codes from the application, or they can use extensions too.

 

PDF and JPG files might, or might not, have resource fork info, depending on the application that created them.

 

Just using the AddressBook.data file as an example suggests that something else is going on, or there's something else you're not telling us. Perhaps rebuilding the LaunchServices database might be warranted.

 

Dave

Link to comment
Share on other sites

Quote:

> This was an immediate restore, from the backup server, directly to a subfolder on the same

>Mac Retro client they were backed up from.

 

- Was this a "Restore files and folders" or a "Replace entire disk" operation?

- If it was the latter, was it a Restore to the same user's account that it had been backed up from?

 


 

It was the former.

 

Quote:

 

> This is happening with Address Book Data files, Word, Excel, PDF, JPG files.

 

Address Book Data files (such as "/Users/foo/Library/Application Support/AddressBook/AddressBook.data") do not have type/creator codes or resource forks. Apple generally no longer makes applications that use/rely-on metadata for application binding, which is done by Launch Services using file name extensions (which, you'll notice, is ".data" for Address Book Data files).

 

 


 

True, and this even more implicates Retrospect: without type/creator codes, the AB data files show up with a generic file icon, not a unix executable icon. This seems to indicate that something is happening in the backup/restore process that's changing the file somehow.

 

Quote:

Word and Excel files do get type/creator codes from the application, or they can use extensions too.

 

PDF and JPG files might, or might not, have resource fork info, depending on the application that created them.

 

Just using the AddressBook.data file as an example suggests that something else is going on, or there's something else you're not telling us. Perhaps rebuilding the LaunchServices database might be warranted.

 

Dave

 


 

Well, as I said, I'm *not* just using the AB file as an example - all other file types mentioned are having this same problem after the restore. All other files on the system are fine. And already tried rebuilding LS DB, no luck.

Link to comment
Share on other sites

Quote:

without type/creator codes, the AB data files show up with a generic file icon, not a unix executable icon.

 


 

I don't understand what this means; can you explain? Is this a report of some tests you have tried?

As I noted, the AB files do not have resource forks; the application doesn't use them. The _only_ mechanism OS X has available to assign an icon is by the .data file extension. So on my machine, "without type/creator codes, the AB data files show up with" an Adobe Sound Booth data icon. I certainly wouldn't expect such a file to display a generic file icon on any OS X install, given that Address Book is installed by default.

 

> as I said, I'm *not* just using the AB file as an example - all other file types mentioned are

> having this same problem after the restore.

 

True. But it's the exception that proves the rule. If you're having the problem with a file that does not have a resource fork, starting your search for an answer by going down that path seems ill advised.

 

- Is there any difference if you Restore the files to the Retrospect server machine?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...