migrate mac files with special characters 1

[schnell]

I have set up a new server and want to transfer the data from the old machine. If I use the consolidation utility, the mac filenames get mangled. If I use a mac to copy them over, I lose the ACLs. Is there a tool that does both?

If there is nothing, it is a small group so recreating the ACLs won't be too hard, but what a pita.

Any help / experience?


Jason

 

[Datong]

Hi, If my memory serves me correctly, there used to be a MAC/OS2 filename support module that needs to be loaded on the volume you are migrating to, to be able to support these special characters. Its been a long time since I even saw a mac but I'm sure I did it years ago. Sorry couldnt be much more help. I have a mac friend and will ask him.

 

[marvhuffaker]

What are you going from, and what are you going to?

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[schnell]

I do have the Mac / long file name support turned on. So copying using a Mac workstation is fine, but I lose all the ACL.

Old machine is Novell 6.0, new is 6.5.

The filenames always look funny when using a PC. You can browse the files, open them etc. For instance, pressing 'Option-v' on a Mac gives you a large check mark in the filename, not unlike a 'square root'. Switching to the same location on my PC I see it as a large empty square character. Which is fine, even using the PC to rename the file and copying the square and pasting it shows up as the check mark on the Mac. When I paste this square in Word on a PC, it changes to a long vertical line with a short line going to the right, from the middle of the long line (Half an 'H' if you will). So it must be the translation of the character code during the migration, because once I do a test copy in the Migration Tool, even on Macs the filename becomes the 'Half H' character where it used to be the 'Check mark'. Does that make any sense?

Thanks for any help!

jason

 

[marvhuffaker]

So use the Mac to copy them, dont' worry about the acl's during that process.

Then, use Trustbar.nlm to handle the trustee file assignments. Run it on the source server-- it makes a trustee.xml file at the volume root.. then move that trustee.xml file onto the new server and run trustbar again and restore. If you don't already have trustbar on your server, you can download it from Novell.


Marvin Huffaker, MCNE

http://www.redjuju.com

 

[schnell]

That is perfect. Thanks for the tip. I had tried looking through the coolsolutions site but didn't see that one!

I shall try it this weekend. One volume is being divided into 2 for logistical reasons, we'll see how this handles it.


jason

 

[marvhuffaker]

It's not a problem if you are changing your volume structure. You'll just have to split and modify the trustees.xml file so that it matches your new setup.

Marvin Huffaker, MCNE

http://www.redjuju.com