This document was generated from CDN thread
Created by: Thomas Trebing on 21-11-2012 01:39:45 PM
We have the need to migrate a WebEx Social 3.1 install to a new domain name. We'd have a lot of good content that we don't want to lose. Is it possible to change the FQDN of all the hosts withouth breaking everything? Should I just rename the director (can that be done?) and then spin up new hosts for all other roles, let everything replicate and then decomission the old hosts once everything is sync'd up?
What is the best approach?
Subject: RE: Migration 3.1 to new DNS domain
Replied by: Ratnadeep Ray on 22-11-2012 02:18:56 AM
Hi Thomas,
If you want to change the FQDN, then please note the following:-
The FQDN of the NFS can be changed but after changing it in the director, need to make sure that it gets mounted correctly in the places where it gets used viz. app nodes/activemq node.
You change in director and run a "service puppet debug" on all nodes to verify the changes are propogated to all the other nodes
If FQDN of Notifier VM is changed then delete and re-add the notifier in the directory topology. You can do it as below:-
1. Delete the VM.
2. Delete it from Director Topology page.
3. Add it in Director Topology page.
4. Create the VM and configure it with same name what you entered in Director Topology page.
Does this answer your query?
Regards,
Ratnadeep.
