Problem copying postscript fonts
We have Extreme Z-IP v8.0.1x120 running on Windoze Server 2008R2 and have been experiencing problems when copying files between volumes on the server for backup. Built-in Windows backup works correctly, all files restored are fine but when we manually copy to a connected hard drive, also shared via ExIP, the postscript fonts are all unusable and zero k in size. I initially thought it was because the external hard drive was not shared in Ext IP so I created a share on a new hard drive we just installed and the postscript fonts are still zero 0 in size after copying. The reason we want to copy the files manually as a backup is because the Window Backup in 2008 uses the .vhd files format and this only supports a max file size of 1.99 TB which is sometimes too small to back up our data drive. If I mount the shared ext hard drive on the mac via AFP all files copy correctly but it is much slower and we would rather copy directly on the server.
As far as we see you are copying your files from one file-server volume to another one, so from Windows to Windows. If this is the use-case, then ExtremeZ-IP / Access Connect is not related since there are no Mac clients [connected via AFP] involved into this process.
With ExtremeZ-IP / Access Connect, Mac users can connect to and mount directories on a Windows file server just as native AFP volumes. With other words, Windows computers can provide AFP file sharing and IP-printing to Mac computers. However, we don't somehow regulate Windows to Windows operations.
So ExZip isn't the problem but any idea what is? I just tried copying postscript fonts to from/to the same volume and postscript fonts do not copy correctly. The odd thing is when you copy using the mac, the postscript fonts are fine but when looking on the server they show up as zero k in size. What is it about postscript fonts that Windows doesn't like? Only their built in Windows backup works correctly for these. I thought that Mac OSX no longer used separate resource and data forks in their files like OS 9 and earlier
So, you're trying to test if you can move or copy the font files from Windows PC to Windows PC after they have been copied over using ExtremeZ-IP. All your attempts have ended up in zero byte files that the Mac doesn't recognize.
Files contain several forks such as a data fork and a resource fork. Many Mac fonts (True Type) will store all the information in the resource fork (Alternate Data Stream) and the data fork will show as 0KB on the server (this is normal). As a workaround, I would try a Microsoft utility called "robocopy", the ADS data should remain intact as well as when using Windows native backup.
>> I thought that Mac OSX no longer used separate resource and data forks in their files like OS 9 and earlier.
No, the original Mac OS 9 file structure was three forks – the data fork, resource fork and Finder information. Starting with Mac OS X 10.4 Tiger, Apple replaced the original Mac OS 9 fork file structure with a new structure called Extended Attributes that allow for an unlimited number of forks. Please feel free to refer to the follwoing KB: http://support.grouplogic.com/?p=1496.