Prinergy Mac Client File-Sharing Protocols
Total Page:16
File Type:pdf, Size:1020Kb
Prinergy Workflow System Version 4 and 5 Mac Client File-Sharing Protocols English Excerpt from Prinergy System Administration Guide, 731-00463C Rev I, October 2008 Contents 1 Qualified tertiary servers and Mac client computer file-sharing protocols 1 2 List of Mac client computer file-sharing protocols and related software 5 3 Limitations of Mac client computer file-sharing protocols 7 4 Understanding file resources 9 File resources..................................................................................................................................................................................9 Storing file resources..................................................................................................................................................................10 Archiving and Mac client computer file-sharing protocols..............................................................................................10 5 Setting up Mac client computer file-sharing protocols 11 Starting SFM to support AFP.....................................................................................................................................................11 Configuring AFP with ExtremeZ-IP..........................................................................................................................................12 Identifying non-SFM servers in the OTHERHOSTS file......................................................................................................16 Updating the SFMHOSTS file....................................................................................................................................................17 Enabling Preps under SMB........................................................................................................................................................18 6 Changing Mac client computer file-sharing protocols 21 Limitations of protocol conversions using Prinergy Administrator.................................................................................21 Converting to SMB with AppleDouble...................................................................................................................................22 Converting to AFP.......................................................................................................................................................................26 Manually converting protocols................................................................................................................................................29 Converting files with Fork Translator......................................................................................................................................31 Troubleshooting...........................................................................................................................................................................32 iv Prinergy Qualified tertiary servers and Mac client computer file-sharing protocols Tertiary servers are qualified for use with Prinergy® only using specific network file-sharing protocols to and from Mac® client computers. Each operating system or platform has a defined service level. Note: Service levels are described below the table. Tertiary server Mac client computer protocol Service level and comments ® Windows Server 2000 and Either of the following protocols: ● Service level 1, if the server is ® Windows Server 2003 purchased from Kodak® ● AFP with SFM ™ ● Service level 3, if the server is ● AFP with ExtremeZ-IP not purchased from Kodak We are working to qualify this operating system for SMB with ADS, if all Mac client computers run Mac OS® X 10.5. Do not use SMB with ADS until it is qualified. Windows 2003 Server Cluster AFP with ExtremeZ-IP Service level 3 We are working to qualify this operating system for SMB with ADS, if all Mac client computers run Mac OS X 10.5. Do not use SMB with ADS until it is qualified. Windows Server 2008 Not currently qualified Not currently qualified We are working to qualify this operating system for SMB with ADS, if all Mac client computers run Mac OS X 10.5. Do not use SMB with ADS until it is qualified. Isilon SMB with AppleDouble Service level 1 We are working to qualify this operating system for SMB with ADS, if all Mac client computers run Mac OS X 10.5. Do not use SMB with ADS until it is qualified. Mac OS X Server 10.4 SMB with AppleDouble Service level 2 until Mac OS X Server 10.5 is qualified. Service level 3 after Mac OS X Server 10.5 is qualified. 2 Chapter 1—Qualified tertiary servers and Mac client computer file-sharing protocols Tertiary server Mac client computer protocol Service level and comments Mac OS X Server 10.5 Qualified for AFP for Prinergy 4.1.2.2 and Service level 2, when this solution higher is qualified Not yet qualified for any other protocol Brisque® Server, which uses Samba AFP via Helios Service level 1 and Helios Archiving is not supported. UNIX® with Samba and an AFP AFP via the AFP server Service level 3 server, such as Helios or Xinet® Archiving is not supported. UNIX with Samba and no AFP server SMB with AppleDouble Service level 3 Service level descriptions Service The solution is documented, tested with every major and minor level 1 upgrade, and fully supported, which means problems are investigated. Service The solution is documented and tested with every major upgrade level 2 but not directly supported. A problem will be investigated only if it meets the following conditions: ● The problem is caused by Prinergy. ● The problem can be replicated on a job volume on the customer's Prinergy primary server. The customer must keep the job volume on the primary server for this purpose. Service The solution is documented but not tested with every major level 3 upgrade and not supported. Support is limited to documentation. A problem will be investigated only if it meets the following conditions: ● The problem is caused by Prinergy. ● The problem can be replicated on a job volume on the customer's Prinergy primary server. The customer must keep the job volume on the primary server for this purpose. After a Prinergy upgrade, you must confirm that the solution still works to your satisfaction. Consider buying a software testing solution to test upgrades before implementing them on a production system. For information about testing solutions, contact your sales representative. 3 Limitations across all solutions Note: Kodak does not support, and assumes no responsibility for, problems or performance issues that may occur as a result of using third-party products. Problems related to third-party products are not covered by Kodak service contracts. ● All servers in your Prinergy system must use the same Mac client computer protocol. Otherwise, Mac users may unknowingly mount the a volume using the wrong protocol, which might cause data loss. ● The Job Replication option cannot be used with any third-party tertiary server. If you want to replicate jobs, you must buy a server from your Prinergy supplier or find an alternate solution. ● A storage area network connected to a tertiary server is qualified and supported, according to the operating system of the tertiary server that it is connected to. Solutions that are permitted but not qualified ● UNIX tertiary server supported by running an NFS client, such as SFU, on all Prinergy primary and secondary servers: This solution is not qualified—it is not documented, tested, or supported. Use it at your own risk.NFS has many known problems and many potential problems, because Microsoft® does not test the solution on all variants of UNIX. If you use this solution, use it only for input volumes, not for job volumes. ● Network-attached storage other than Isilon: This solution is not qualified—it is not documented, tested, or supported.Use it at your own risk. If you use this solution, use it only for input volumes, not for job volumes. ● Storage area network directly connected to the Prinergy primary server: This solution is not qualified—it is not documented, tested, or supported. ● All other configurations not identified above or in the above table. 4 Chapter 1—Qualified tertiary servers and Mac client computer file-sharing protocols List of Mac client computer file-sharing protocols and related software Mac client computers can connect to a Prinergy primary server using several protocols over several types of software. Protocols for connecting Mac client computers in Prinergy SMB Server Message Block protocol, which is built into the Windows operating system SMB is also known as CIFS and Microsoft Windows network. On UNIX servers, SMB can be implemented with the Samba software. SMB handles file resources in the following ways: ● With AppleDouble, using the AppleDouble file format for foreign files AppleDouble stores file resources in separate files with a ._ prefix. For example, a file named input.pdf has a corresponding AppleDouble file that is named ._input.pdf. ● With ADS, storing file resources in alternate data streams (ADS) AFP Apple® Filing Protocol, which is built into the Mac OS On Windows servers, AFP can be implemented via SFM or ExtremeZ-IP. On UNIX servers, AFP can be implemented with Helios, Xinet, and other software. AFP stores file resources in resource forks. NFS Network File System, which is built into the UNIX operating system On Windows servers, NFS can be implemented with SFU. Software to assist Mac client computer connections SFM Microsoft Services for Macintosh®, which