I'm rehosting from production to development. The production server has replica vaults. Is there a way to disable the replica vaults on the development system prior to rehosting, not using Windchill interface to do it?
Here's the problem that just occurred. Data was copied from production to dev on Friday. Weekend maintenance restarted dev and production. Dev was still pointing to the production replica vaults and the when production was restarted it failed to restart because it thought there was an additional cluster (dev windchill system not rehosted). One thought was to disable services from being started on the dev server, but this does not keep an admin from manually starting windchill.
Solved! Go to Solution.
Key steps in the cloning procedure...
We leave the loopback addresses in place until rehosting is complete. That way if we miss a step or mess up part of the rehosting, we are sure it isn't attempting to connect to production. Once the cloned system comes up on its own, we can remove the loopback addresses.