You should be good with that...remember to make sure you can ping the IP of the new CMDB to and from ADDM and that you have tested the account you will use.
1 of 1 people found this helpful
Assuming that you are using Continuous CMDB Sync, the data will be inserted into the new CMDB dataset as your Discovery jobs are executed. ADDM will find that the data does not exist, and it will insert the data.
I recommend these steps to switch over to the new CMDB:
1) stop discovery runs (you could put the appliance into maintenance mode)
2) stop continuous sync (wait for it to finish processing its queue)
3) change configuration to the new CMDB dataset
4) test the connection to the new CMDB dataset
5) test by sending a couple of hosts to CMDB
6) start continuous sync
7) take appliance out of maintenance mode / start discovery runs again, etc
Thanks Lisa. Yes I am following the same steps. I will let you know if I find any issues.
I added the section, "Preparing synchronization to more than one CMDB" to the documentation that details the steps that Lisa provided in her reply. If you find any issues with the process on your end, please let me know and I will update the documentation as necessary.
It is good that you have added this information in the Documentation.
I am waiting for our new CMDB server to stand up. ( They are rebuilding the Dev environment), I will let you know.