Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X
If I have a 9.1two server setup. An App server and a DB server. I plan to have the external file vault on the DB server. I'm having trouble figuring out what to use for the LOCAL_PRECOPY_PATH in the fileservers.properties file.
If the 3.4 file vaults were precopied to E:\temp on the DB server and the 9.1 external file vault will reside in E:\fv also on the DB server, what should I set the LOCAL_PRECOPY_PATH value to? Since the migration is running on the App server, do I use \\DB\temp or do I use E:\temp and the migrator will figure out what to do?
Also, since I'm migrating over 500,000 files, does the migrator honor the wt.fv.fvFileThreshold and create new subfolders as needed during the migration? It's configured for automatic folder creation, but when I did the metadata-only test, the FileMap csv file had everything going into one subfolder.
Thanks
Hi Gary,
I usually use the PreCopy option allowing to prep the transfer by copying before hand.
But I have used the Copy option as well. you will need to have an NFS Server running on your target system. Best is to install an Intralink 3.x Fileserver which is an NFS based server.
Otherwise, some options can be read like:
LOCAL_PRECOPY_PATH.your_ilnk_fileservername:D:\ilnk34\vaults\your_vault=/data/tmp/transfer/vaults34/tmp_vault
that's for unix target. I suppose if you use windows try to work with D\:\\ as java based