1 of 1 people found this helpful
You can duplicate your CMDB database to Test CMDB by overwriting or deleting the exiting ( before taking backup of existing CMDB db) and re-create with new from production and then cleanup the server reference if any.
Do you just have the CMDB or is it sitting underneath ITSM as well?
It's fairly easy (with a DBA's help!) to replace your Test DB with the Prod DB, but as Mohammad mentioned, there's quite a bit of data cleanup to do so that the copied Prod DB correctly operates with the Test ARS environment. The article referred to will help with this. Also please remember that there are numerous ar.cfg settings that will likely be different in a (smaller) Test environment.
Carey, right now it's just the CMDB with AI to support BMC Discovery and any other needed sources for a DataPump integration. If you have any ar.cfg tips, that would be greatly appreciated.
Not really. We kept the ar.cfg files different between environments and just flipped the DBs. Other than that we just followed the process outlined in that document refereed to above. I didn't do the actual work so might be missing some details, but that was about it from what I recall.
From the database perspective, there is no such separate 'cmdb' database. It is just a remedy database and it includes everything depending on installed apps (AR+CMDB+ITSM etc).
So you just need to take a backup from production and restore it on Test db server.
ARAdmin is the default owner (default password: AR#Admin#) of ARSystem database so when you restore particular db to another db instance, you need to take care of ARAdmin user as well. (It should not create TWO ARAdmin users after restoration). Once db restore is completed, you need to verify db user and db password parameters in ar.cfg file and then restart remedy services.
Regarding cmdb integration: you may need to change data sources of AI jobs as well so that it should not import data from production sources.