What is the process of migrating Idash from our old server to new server?
Release : 12.1
Component : CA WORKLOAD AUTOMATION iDASH FOR CA 7
The simplest way to accomplish this is to follow these steps below:
1) Make a backup of the existing idash on the older server
2) Upgrade iDash to the new release
3) on the new server install the newest release of iDash here as well
4) You can point iDash to use the same database as the old server.
5) Once iDash is installed on the server, stop the services and copy over the IDASH_HOME/log/sla directory from the older server.
6) Also If you're running CA7 make sure to copy over the IDASH_HOME/dat/ca7 directory so that the existing seed data will there before they bring up iDash on the server.
7. copy dat/audit to maintain audit records.
Note: Bringing up iDash that has previously processed events without a seed data can lead to potential loops where iDash needs to catch up events, but can't process events without job definitions, and also can't get job definitions because the seed data events are in the recovery events.
If the client wishes to upgrade their iDash version as well as make a move to new hardware, these must be done separately. Either upgrade, then migrate or migrate then upgrade. Do not attempt to do both at the same time, as this will cause issues with the DB.
Shut down iDash on both the primary and secondary servers.
Install iDash on the new servers, using the DB connection information from the existing installation. Error messages indicating that DB tables and indexes already exist will be displayed during the install. This is expected and can be safely overlooked.
At the end of the installation, they will be asked if they wish to start iDash. They need to respond "no". iDash should remain inactive on the new servers until the appropriate file transfers have been done.
Copy certain files from the existing iDash servers over to the new ones. Make sure to transfer the files to the appropriate server. ie: The files from the old primary server should be transferred to the new primary server, and the same for the old and new secondary servers.
If any customizations have been made to Java options or Tomcat (such as min/max memory settings or SSH enablement), those changes should be ported over to the new servers as well.
Start iDash on the new servers. Pay close attention to the error logs and the GUI display for a time to make sure things are operating as normal.