cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Manually disabling replica vaults prior to rehost

SOLVED
Highlighted
Regular Member

Manually disabling replica vaults prior to rehost

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. 

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Manually disabling replica vaults prior to rehost

clarification...  If the replicas are not cloned, we leave loopback addresses in place for them in the dev environment.  Example loopback entry:

127.0.0.1   replica.company.com   replica   #Replica server

View solution in original post

2 REPLIES 2

Re: Manually disabling replica vaults prior to rehost

Key steps in the cloning procedure...

  1. Disable Windchill [Windows] service.  If the Windchill service cannot be started, server reboots and automated maintenance tasks won't accidentally start it.  You can disable all Windchill related services but only the Windchill service will conflict with the production environment.
  2. Add loopback entries for all production Windchill servers (e.g. db, app, pub, indexing, PSM, etc.) to the %windir%\system32\drivers\etc\hosts file on the cloned Windchill app server.  Even if someone re-enables the Windows service and tries to start Windchill, the loopback addresses keep it from connecting to the production environment.

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.

Re: Manually disabling replica vaults prior to rehost

clarification...  If the replicas are not cloned, we leave loopback addresses in place for them in the dev environment.  Example loopback entry:

127.0.0.1   replica.company.com   replica   #Replica server

View solution in original post