Summary of responses to "Can a network storage appliance be used for <br /> Pro/INTRALINK 3.4 F
Thanks for all your responses.
THE PROBLEM: In a Windows 2000 server Pro/INTRALINK installation, if you use the plain vanilla method of sharing a drive/directory on a remote machine and then mapping it to the file server as, say "S:\ " you get the following error if you try to create a vault on the mapped drive: "Check if pathname is correct, and does not already exist.". PTC does not support using network mapped drives as file vaults. I do not know if this is new 'functionality' in Pro/INTRALINK 3.4 or if this has always been the case. Some of you have responded that you are presently using mapped drives on a unix Pro/INTRALINK pre-3.4 installation with no problems.
THE SOLUTION: It turns out that there is a new standard, called 'iSCSI' which is supported by the Snap Server. It layers over TCP/IP so that the Snap Server drive appears to the software on the file server as a SCSI device. For more information on this standard see: http://www.diskdrive.com/reading-room/FAQ.html .
In my installation, the hardware guys had not been aware that we would need the iSCSI feature, but when they got involved, the Snap Server was connected to the file server using iSCSI and then formatted NTFS. I have not yet verified that file vaults can be created. Assuming that they can, we will be testing data integrity over the next two weeks.
THE RESPONSES: Have you tried installing the file server component right on the snap server? (No. I had assumed that it could not run programs, since it is a mass storage device, not a computer. If I assumed wrong, please let me know. - AH)