How to move my CAPAM hardware (or VMs) to a new datacenter

Document ID : KB000010010
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

So, you are moving your cluster to a new data center.  We recommend the following basic plan to work with but could involve other changes that need to be accounted for depending on how complex your network or CAPAM setup is:

 

 

Instructions:

 

1- Decide whether you are going to be in production or not when you decide to start this process.  We can assume that you will still be in production.  We are going to leave Node1 in production and move Node2 over to the new data center.  If this is more than two nodes, you would have to decide if you want to have redundancy in the old datacenter or the new datacenter while the hardware is being moved.

 

2- You are still in production and clustered.  Put Node2 into Maintenance Mode by going to Config/Diagnostic/Maintenance Mode and click the “On” button to Turn On Maintenance Mode.  Then go to Config/Synchronization and click the Turn Cluster Off button, breaking the cluster (you can break the cluster from Node1 one or Node 2 in later versions of CAPAM). You will need to point the VIP to Node 1 or have the users log directly into Node1 using its IP, unless the logins are from outside your network, then just redirect the VIP.

 

3- Save and download the database and config from Node1 as a precaution (config will be useless if are changing your IPs / subnet).  If you have to reconfigure the Network info, this can be done from the front LCD panel.

 

4- Edit Node2’s IP/subnet info on the Config/Network page and edit the IP info on the Config/Synchronization page.  While on/in the Synchronization page, move the Node1 IP down, and move the Node2 IP up to the top.  If you are changing all the IPs, then move Node2's new IP the top IP.

 

5- If you are changing IPs and subnets, you may need to edit your target devices as well.  You can do this manually on the Devices page on the Dashboard.  If you have a large amount of target devices, you can facilitate this process by going to Devices/ Import/Export Devices/and click on Export Devices.  You can edit this list and import the same list with all your target device IP changes.

6- Now go to Config/Power and select Power Off or Stop Instance to shutdown Node2.

 

7- Your Node2 hardware has now been moved to the new data center.   Connect power cord(s), and power on Node2 and take it out of Maintenance Mode.  Make sure the unit is accessible on the network, and that you can reach the target devices.

 

8- Set the VIP to reach only Node2 (new Primary) and then put Node1 into Maintenance mode.

 

9- Change the Config/Network info and the Config/Synchronization info in the same way that you updated Node2 (with Node2’s IP address at the top in the primary position.  Use Config/Power to powerdown Node1.

 

10- Node1 is now in the new datacenter.  Connect power cord(s) and power on Node1 (new Secondary), and make sure that it is accessible on the network.

 

11- Go to Node2(new Primary), and in/on the Config/Synchronization page and starting at the left, click Save Config Locally, then click Save to Cluster, and then click on Turn Cluster On.

12- Once the cluster has formed, which means that the database has been passed between Node2 and Node1, all information is synchronized and Node2 is the new Primary and Node1 is the new Secondary and all targets should be reachable (as long as all the IP and subnet information is correct or has been edited for the new data center).

Additional Information:

This document covers everything you need to know for a data center change, but there could be some things I have not covered for your specific configuration.  There could be LDAP servers, NTP servers or any other external IP source such as a recording server, Syslog server or any other server that CAPAM communicates with besides the other node(s) and the target servers.