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.
Solved! Go to Solution.
Are you rehosting between a Unix box and Windows?
The vault locations indicate that you are.
Rehost does not support moving between operating systems.
No we have a nfs mount reference on the production system and a local drive on the target system. Both are windows servers.
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?
And since I only have 1 source and 1 target, do I need to put the .0 on the hostname and path variables?