Rehosting 11.0 m030 renaming FV path

[slhumphrey]

I am doing a rehost and the file vault paths are changing.  I don't want it to copy vault data (we have already created stub files in the new location). Can I not just specify the fv path (source and target) but not copy the vault files? Here's what I would have in the rehost.properties file.

target.fv.required=true

source.fv.hostname.0= source.intranet.com

target.fv.hostname.0= target.intranet.com

source.fv.path.0=\\source\Windchill_Vaults
#staging.fv.path.0=E:\vaultStaging\vault1
target.fv.path.0=E:\Windchill_Vaults

[BenLoosli]

Are you rehosting between a Unix box and Windows?

The vault locations indicate that you are.

Rehost does not support moving between operating systems.

[slhumphrey]

Hi Ben,

No we have a nfs mount reference on the production system and a local drive on the target system.  Both are windows servers.

Sandra

[BenLoosli]

Sandra,

That should work. I always copy my vaults over before running the rehost.

Ben

[slhumphrey]

I have already copied the files over.  So when I make the following configurations, it will update the database with the target fv path without trying to copy any of the vault files?

source.fv.hostname.0= production.intranet.com
target.fv.hostname.0= dev.intranet.com

#target.fv.required=false

source.fv.path.0=\\NFS_server\Windchill_Vaults
target.fv.path.0=E:\Windchill_Vaults

[BenLoosli]

Yes

It will only update the pointers in the DB to the new hostname and vault location.

[slhumphrey]

And since I only have 1 source and 1 target, do I need to put the .0 on the hostname and path variables?

Sandra

[BenLoosli · Accepted solution]

Not sure

I left them on mine incase the code was looking for a numeric sequence number and started the count at 0.

[slhumphrey]

Ok. Thank you for your help!

Sandra