LOCAL_PRECOPY_PATH during migration

[ptc-141591]

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

[ZacharyAlexande]

Gary,

This is a known issue with PTC that I ran into when running through a
migration recently. Try setting your LOCAL_PRECOPY_PATH (on the same drive
on the same server as the install) to E:\temp and put the actual vault in
E:\temp\E\temp. I know this sounds odd, but this is how the migrator reads
the vault file path as explained to me by PTC. Let me know if this helps.

Thanks,
Zack

[RandyJones]

On 03/08/10 09:22, Gary Popick wrote:
> If I have a 9.1 two 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 <file: db=" temp="> or do
> I use E:\temp and the migrator will figure out what to do?

Simply turn off the actual file transfer and do the copy yourself after
File Transfer Data Loader has completed. Set these options in your
migration.properties file:

migration.filetransfer.mapFileHome=/opt/ptc/ILMigration/mapfilehome
fileTransferOption=Copy
withMapFile=true
doFileTransfer=false

>
> 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.

The migrator (at least 9.1 M040 does) will honor this. Make sure you
have these properties set:

wt.fv.useFvFileThreshold=true
wt.fv.fvFileThreshold=100000

If you have file servers setup you also need to set these options on them
also. These settings are on a per fileserver basis.

>
> Thanks


In my case where I have several file servers setup for replicas and have
cache vaults on these I have the following settings:

wt.fv.forceContentToVault=false
wt.fv.useVaultsForAllContent=true

During migration these settings will cause the migrator to stick all
of the files in the cache vault and which means that they then need to
be moved to the master vault. To get around this and have the migrator
stick the files directly in the master vault I temporarily set these
like this just before the File Transfer Data Loader is ran:
wt.fv.forceContentToVault=true
wt.fv.useVaultsForAllContent=false

Then after the File Transfer Data Loader has completed I reset these back
to my production values:
wt.fv.forceContentToVault=false
wt.fv.useVaultsForAllContent=true

--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
Fax: 785-667-2695
------------------------------------------------------------------------

[ChristopheLaudo]

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

[mlovejoy]

Gary

In 9.1 m030, Watch out for the automatic subfolder creator during
migration, even if you set the fv.fvfile.threshold , I ran into a
problem when I was using that functionality. the transfer would be
running along fine, it would create a new folder and then not transfer
anything after it created the folder. which is a pain. I doubled
checked my setting reset the migration and tried again , did this
twice and on the third time , changed over to the technique of

WithMapFile= true and doFileTransfer= false and then manually moving the
files

Marc

Gary Popick wrote:
>
> If I have a 9.1 two 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
> <file: 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
>
>