Win2000 SFM and backups

[Michael Russell]

This is a rather simple question, but I can't seem to find an answer to it:

How do I back up the Apple meta-information on my AppleShare volumes?

On my Win2000 server, we have 4 volumes shared on a 750GB array; Backup
Exec is doing nightlies of those volumes, but I'd like to know how the
resource fork is supposed to be backed up.

Thanks,
Michael

 

[Rod Dorman]

This is a rather simple question, but I can't seem to find an answer to it:

How do I back up the Apple meta-information on my AppleShare volumes?

On my Win2000 server, we have 4 volumes shared on a 750GB array; Backup
Exec is doing nightlies of those volumes, but I'd like to know how the
resource fork is supposed to be backed up.

The resource fork is in the same file as the data fork but in a second
stream called:AFP_Resource. Thats why SFM shares must be created on
NTFS volumes and not FAT.

 

[Michael Russell]

The resource fork is in the same file as the data fork but in a second
stream called:AFP_Resource. Thats why SFM shares must be created on
NTFS volumes and not FAT.

If that's the case, then is it true that those files, as long as they
remain on an NTFS file system, will always retain that information? For
example, I could restore the backed-up files to a different Win2k
machine (not running SFM), and copy back to the original machine, and
they would retain the Resource information?

 

[William Smith]

The resource fork is in the same file as the data fork but in a second
stream called:AFP_Resource. Thats why SFM shares must be created on
NTFS volumes and not FAT.

If that's the case, then is it true that those files, as long as they
remain on an NTFS file system, will always retain that information? For
example, I could restore the backed-up files to a different Win2k
machine (not running SFM), and copy back to the original machine, and
they would retain the Resource information?[/QUOTE]

Yes, to a degree. So long as your Mac files reside on an NTFS partition
then the resource forks should be preserved. However, the method you
choose to use to move the files from one server to another could affect
those resource forks. Using a Mac to copy files from one server to
another will preserve the resource forks so long as the Mac is
connecting via AFP (on Mac OS 9 or X) or SMB (on Mac OS X). Using a
Windows workstation to move files may not necessarily preserve the
resource forks.

Hope this helps! bill

 

[Michael Russell]

If that's the case, then is it true that those files, as long as they
remain on an NTFS file system, will always retain that information? For
example, I could restore the backed-up files to a different Win2k
machine (not running SFM), and copy back to the original machine, and
they would retain the Resource information?

Yes, to a degree. So long as your Mac files reside on an NTFS partition
then the resource forks should be preserved. However, the method you
choose to use to move the files from one server to another could affect
those resource forks. Using a Mac to copy files from one server to
another will preserve the resource forks so long as the Mac is
connecting via AFP (on Mac OS 9 or X) or SMB (on Mac OS X). Using a
Windows workstation to move files may not necessarily preserve the
resource forks.

Hope this helps! bill[/QUOTE]

Actually, I guess I'm more confused now. You saw that as long as the
Mac files are on NTFS, then the forks "should" be preserved; what might
cause them to not be preserved?

Also, referring to your last statement, how can I ensure that moving
files via a Windows workstation will preserve the resource forks.

Thanks,
Michael

 

[Rod Dorman]

Actually, I guess I'm more confused now. You saw that as long as the
Mac files are on NTFS, then the forks "should" be preserved; what might
cause them to not be preserved?

Also, referring to your last statement, how can I ensure that moving
files via a Windows workstation will preserve the resource forks.

If you use an older version of MS-Windows (e.g. Win-95, Win-98) that
has no knowledge of alternate streams the only thing that will be
copied is the primary data stream, i.e. the data fork.

If you're planning to move Mac files from one SFM server to another it
would be more efficient to do it from one of the servers to take only
one network hop but as long as a Windows workstation is NTFS aware it
can do the copying.

Just make sure you never use a FAT drive for any intermediate storage.

 

[Michael Russell]

If you use an older version of MS-Windows (e.g. Win-95, Win-98) that
has no knowledge of alternate streams the only thing that will be
copied is the primary data stream, i.e. the data fork.

If you're planning to move Mac files from one SFM server to another it
would be more efficient to do it from one of the servers to take only
one network hop but as long as a Windows workstation is NTFS aware it
can do the copying.

Just make sure you never use a FAT drive for any intermediate storage.

Thanks for the information, I suspected that but wanted to hear it from
someone else.

Michael