Re: Converting Macintosh Files
- From: Paul Nelson <nelson@xxxxxxxxxxx>
- Date: Thu, 02 Mar 2006 10:25:56 -0600
Some additional notes:
1) William is correct - Apple's use of SMB does not recognize the defacto
standard method of storing resource forks the way Microsoft, Thursby,
ExtremeZ do. If you have a lot of data in the original Microsoft SFM
format, you are probably better off using a third party solution.
2) That said, I would bet that your problem is related to file names as much
as resource forks. William is correct again that the streams used in
Macintosh files are not any different that ones used by Microsoft Office.
It should not matter to Data Protection Manager, but it might. File names
with characters that Mac users love (like slashes, bullets) often drive
Windows software nuts. Even with a third party product, you may continue to
have problems with existing products, because these products don't rename
files that already exist. You might benefit from using a program that will
scan your file system and rename files that have funny characters in them.
3) If you get an evaluation of DAVE, Thursby's support department should be
able to help you identify and correct problems with Data Protection Manager.
Paul Nelson
Thursby Software Systems, Inc.
in article mecklists-C2DF92.22513701032006@xxxxxxxxxxxxxxxxxxxx, William
Smith at mecklists@xxxxxxxxxxxxxxxxxxxx wrote on 3/1/06 10:51 PM:
In article <#pcjpsOPGHA.2176@xxxxxxxxxxxxxxxxxxxx>,
"Lisa Parris" <lisa@xxxxxxxxxxxxxxxx> wrote:
Hi William,
Part of our Disaster Recovery plan depends on Microsoft's Data Protection
Manager which is basically a product that replicates files and changes to
files over the network on a nearly continuous basis. The only data we're
having trouble with is the Macintosh data that's stored on the one server
that's running SFM.
Microsoft says that the Macintosh data may contain "alternate streams" which
could be causing a problem. Not to sound like an idiot but I don't know
exactly what that means (is that related to forks?). We're having problems
with really long filenames and filenames that have unsupported characters
among other things. If I'm understanding correctly, which I'm probably not,
you're saying that for each Macintosh file on the network, there's a hidden
(or not hidden) file "._filename" which corresponds to it?
Thanks for the reply and any additional help you can give me!
Hi Lisa!
I'm completely unfamiliar with Microsoft's Data Protection Manager but
it does have a newsgroup where you may want to ask about Mac files
microsoft.public.dataprotectionmanager.
Although Mac files do use alternate streams to store the resource fork
information as Rod points out in his response to you, I find it
difficult to believe that they aren't supported. Macs aren't the only
users of multiple streams. It's hardly data protection if it doesn't
protect all data.
The AFP version on Windows server is 2.2, which doesn't support file
names longer than 31 characters. The ExtremeZ-IP server software uses
AFP 3.2, which not only supports the 254 character maximum but also
supports Mac OS X 10.4 (Tiger) Access Control Lists (ACLs).
You're correct that for every file your Macs place on the server when
connected via SMB that there will be an additional "._" file. Depending
on your Windows settings, hidden files may be set to be shown and these
files will propagate to the top of the file list because of their names.
These files don't exist when Macs connect via AFP, but instead that
information gets put into the alternate data stream.
Hope this helps! bill
.
- References:
- Converting Macintosh Files
- From: Lisa Parris
- Re: Converting Macintosh Files
- From: William Smith
- Re: Converting Macintosh Files
- From: Lisa Parris
- Re: Converting Macintosh Files
- From: William Smith
- Converting Macintosh Files
- Prev by Date: Re: Converting Macintosh Files
- Next by Date: remap network drive on a mac laptop
- Previous by thread: Re: Converting Macintosh Files
- Next by thread: Re: Converting Macintosh Files
- Index(es):
Relevant Pages
|